Facing issue with pmm pod not in running state

[rajb-duplo]

I have been using below Mongodb operator and PMM chart version. Pods don't get in ready state after so many attempts. can you please help is it known issue with new release?

PMM chart version : 1.4.0
psmdb-operator-1.19.0

2025-02-18 17:26:41,574 INFO spawned: 'postgresql' with pid 635
2025-02-18 17:26:42,576 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-18 17:26:42,577 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:26:42,580 INFO spawned: 'postgresql' with pid 636
2025-02-18 17:26:42,601 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:26:44,583 INFO spawned: 'postgresql' with pid 637
2025-02-18 17:26:45,590 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-18 17:26:45,591 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:26:45,593 INFO spawned: 'postgresql' with pid 638
2025-02-18 17:26:45,613 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:26:47,595 INFO spawned: 'postgresql' with pid 639
2025-02-18 17:26:48,207 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:26:50,600 INFO spawned: 'postgresql' with pid 640
2025-02-18 17:26:50,683 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:26:54,604 INFO spawned: 'postgresql' with pid 641
2025-02-18 17:26:55,602 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-18 17:26:55,603 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:26:55,605 INFO spawned: 'postgresql' with pid 642
2025-02-18 17:26:55,628 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:26:57,607 INFO spawned: 'postgresql' with pid 643
2025-02-18 17:26:57,630 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:27:00,610 INFO spawned: 'postgresql' with pid 644
2025-02-18 17:27:00,631 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:27:04,616 INFO spawned: 'postgresql' with pid 645
2025-02-18 17:27:04,664 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:27:09,422 INFO spawned: 'postgresql' with pid 646
2025-02-18 17:27:09,472 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:27:14,634 INFO spawned: 'postgresql' with pid 647
2025-02-18 17:27:14,692 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:27:21,667 INFO spawned: 'postgresql' with pid 648
2025-02-18 17:27:21,689 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:27:29,423 INFO spawned: 'postgresql' with pid 649
2025-02-18 17:27:29,479 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:27:37,687 INFO spawned: 'postgresql' with pid 650
2025-02-18 17:27:37,708 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:27:47,693 INFO spawned: 'postgresql' with pid 651
2025-02-18 17:27:47,716 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:27:58,199 INFO spawned: 'postgresql' with pid 652
2025-02-18 17:27:58,486 INFO exited: postgresql (exit status 1; not expected)
2025-02-18 17:27:58,698 INFO gave up: postgresql entered FATAL state, too many start retries too quickly
2025-02-18 17:29:11,786 INFO exited: pmm-managed (exit status 1; not expected)
2025-02-18 17:29:12,790 INFO spawned: 'pmm-managed' with pid 653
2025-02-18 17:29:13,826 INFO success: pmm-managed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-18 17:34:13,412 INFO exited: pmm-managed (exit status 1; not expected)
2025-02-18 17:34:13,469 INFO spawned: 'pmm-managed' with pid 658
2025-02-18 17:34:14,505 INFO success: pmm-managed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-18 17:39:13,875 INFO exited: pmm-managed (exit status 1; not expected)
2025-02-18 17:39:14,878 INFO spawned: 'pmm-managed' with pid 663
2025-02-18 17:39:15,912 INFO success: pmm-managed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

above logs are getting in pmm-0 pod recursively.

Also getting warning logs with password in plaintext format.

time="2025-02-18T17:24:09.318+00:00" level=warning msg="Configuration warning: unknown environment variable "PMM_SERVER_API_KEY=dummy-values"."

[jvpasinatto]

Hello @rajb-duplo,
PMM chart 1.4.0 deploys PMM 3 that is not yet supported by PSMDB Operator 1.19.0

Please try it with PMM chart 1.3.21

Thanks!