Percona pods dosent get ready after helm update

[prawal10]

Hi,
I am using PMM chart version : 1.4.0 with default values, inital deployment is fine but after i change something in values file example adding limit and resources in pmmResources parameter the percona pod dosent get in ready state logs -

2025-03-03 10:07:49,787 INFO Included extra file "/etc/supervisord.d/grafana.ini" during parsing
2025-03-03 10:07:49,788 INFO Included extra file "/etc/supervisord.d/pmm.ini" during parsing
2025-03-03 10:07:49,788 INFO Included extra file "/etc/supervisord.d/qan-api2.ini" during parsing
2025-03-03 10:07:49,788 INFO Included extra file "/etc/supervisord.d/supervisord.ini" during parsing
2025-03-03 10:07:49,788 INFO Included extra file "/etc/supervisord.d/victoriametrics.ini" during parsing
2025-03-03 10:07:49,788 INFO Included extra file "/etc/supervisord.d/vmalert.ini" during parsing
2025-03-03 10:07:49,788 INFO Included extra file "/etc/supervisord.d/vmproxy.ini" during parsing
2025-03-03 10:07:49,789 INFO Set uid to user 1000 succeeded
2025-03-03 10:07:49,793 INFO RPC interface 'supervisor' initialized
2025-03-03 10:07:49,793 INFO supervisord started with pid 1
2025-03-03 10:07:50,799 INFO spawned: 'pmm-init' with pid 12
2025-03-03 10:07:50,811 INFO spawned: 'postgresql' with pid 13
2025-03-03 10:07:50,815 INFO spawned: 'clickhouse' with pid 14
2025-03-03 10:07:50,827 INFO spawned: 'grafana' with pid 15
2025-03-03 10:07:50,833 INFO spawned: 'nginx' with pid 16
2025-03-03 10:07:50,837 INFO spawned: 'victoriametrics' with pid 17
2025-03-03 10:07:50,841 INFO spawned: 'vmalert' with pid 18
2025-03-03 10:07:50,846 INFO spawned: 'vmproxy' with pid 19
2025-03-03 10:07:50,849 INFO spawned: 'qan-api2' with pid 20
2025-03-03 10:07:50,943 INFO spawned: 'pmm-managed' with pid 21
2025-03-03 10:07:51,008 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:07:51,070 INFO exited: qan-api2 (exit status 1; not expected)
2025-03-03 10:07:51,367 INFO exited: grafana (exit status 1; not expected)
2025-03-03 10:07:51,983 INFO success: pmm-init entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-03-03 10:07:51,984 INFO success: clickhouse entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-03-03 10:07:51,984 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-03-03 10:07:51,984 INFO success: victoriametrics entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-03-03 10:07:51,984 INFO success: vmalert entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-03-03 10:07:51,984 INFO success: vmproxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-03-03 10:07:51,984 INFO success: pmm-managed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-03-03 10:07:52,026 INFO spawned: 'postgresql' with pid 350
2025-03-03 10:07:52,105 INFO spawned: 'qan-api2' with pid 351
2025-03-03 10:07:52,131 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:07:52,388 INFO spawned: 'grafana' with pid 370
2025-03-03 10:07:52,577 INFO exited: grafana (exit status 1; not expected)
2025-03-03 10:07:53,773 INFO success: qan-api2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-03-03 10:07:54,182 INFO spawned: 'postgresql' with pid 420
2025-03-03 10:07:54,202 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:07:54,594 INFO spawned: 'grafana' with pid 442
2025-03-03 10:07:55,057 INFO exited: grafana (exit status 1; not expected)
2025-03-03 10:07:55,615 INFO exited: pmm-init (exit status 0; expected)
2025-03-03 10:07:58,063 INFO spawned: 'postgresql' with pid 486
2025-03-03 10:07:58,066 INFO spawned: 'grafana' with pid 487
2025-03-03 10:07:58,163 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:07:58,211 INFO exited: grafana (exit status 1; not expected)
2025-03-03 10:08:03,070 INFO spawned: 'postgresql' with pid 496
2025-03-03 10:08:03,107 INFO spawned: 'grafana' with pid 497
2025-03-03 10:08:03,225 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:08:03,250 INFO exited: grafana (exit status 1; not expected)
2025-03-03 10:08:08,993 INFO spawned: 'postgresql' with pid 504
2025-03-03 10:08:08,996 INFO spawned: 'grafana' with pid 505
2025-03-03 10:08:09,074 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:08:09,204 INFO exited: grafana (exit status 1; not expected)
2025-03-03 10:08:15,084 INFO spawned: 'postgresql' with pid 514
2025-03-03 10:08:16,083 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-03-03 10:08:16,085 INFO spawned: 'grafana' with pid 515
2025-03-03 10:08:16,086 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:08:16,089 INFO spawned: 'postgresql' with pid 516
2025-03-03 10:08:16,124 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:08:16,242 INFO exited: grafana (exit status 1; not expected)
2025-03-03 10:08:18,093 INFO spawned: 'postgresql' with pid 524
2025-03-03 10:08:18,110 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:08:21,096 INFO spawned: 'postgresql' with pid 525
2025-03-03 10:08:22,095 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-03-03 10:08:22,096 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:08:22,098 INFO spawned: 'postgresql' with pid 526
2025-03-03 10:08:22,119 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:08:23,992 INFO spawned: 'postgresql' with pid 527
2025-03-03 10:08:23,995 INFO spawned: 'grafana' with pid 528
2025-03-03 10:08:24,100 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:08:24,132 INFO exited: grafana (exit status 1; not expected)
2025-03-03 10:08:26,104 INFO spawned: 'postgresql' with pid 536
2025-03-03 10:08:27,107 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-03-03 10:08:27,107 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:08:28,106 INFO spawned: 'postgresql' with pid 537
2025-03-03 10:08:28,131 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:08:29,423 INFO spawned: 'postgresql' with pid 538
2025-03-03 10:08:29,450 INFO exited: postgresql (exit status 1; not expected)
2025-03-03 10:08:32,115 INFO spawned: 'postgresql' with pid 539

Is it a known issue or is there a fix for this? Any help is appreciated.

Thank you.

[prawal10]

when i check the postgres logs it says postgres folder need 0700 permission

[root@percona-pmm-0 srv] # tail logs/postgresql14.log
2025-03-05 15:48:19.395 UTC [487] FATAL:  data directory "/srv/postgres14" has invalid permissions
2025-03-05 15:48:19.395 UTC [487] DETAIL:  Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).
2025-03-05 15:48:22.993 UTC [529] FATAL:  data directory "/srv/postgres14" has invalid permissions
2025-03-05 15:48:22.993 UTC [529] DETAIL:  Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).
2025-03-05 15:48:28.000 UTC [543] FATAL:  data directory "/srv/postgres14" has invalid permissions
2025-03-05 15:48:28.000 UTC [543] DETAIL:  Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).
2025-03-05 15:48:33.742 UTC [556] FATAL:  data directory "/srv/postgres14" has invalid permissions
2025-03-05 15:48:33.742 UTC [556] DETAIL:  Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).
2025-03-05 15:48:40.008 UTC [571] FATAL:  data directory "/srv/postgres14" has invalid permissions
2025-03-05 15:48:40.008 UTC [571] DETAIL:  Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).

with old version v1.3.21 postgres folder has correct permission, i thinkj its hardcoded in the image, is there any fix for it?

[rf-radovitsa]

I can confirm this issue.

2025-03-11 04:32:22.346 UTC [578] FATAL:  data directory "/srv/postgres14" has invalid permissions
2025-03-11 04:32:22.346 UTC [578] DETAIL:  Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).
2025-03-11 04:32:31.341 UTC [589] FATAL:  data directory "/srv/postgres14" has invalid permissions
2025-03-11 04:32:31.341 UTC [589] DETAIL:  Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).
2025-03-11 04:32:41.348 UTC [600] FATAL:  data directory "/srv/postgres14" has invalid permissions
2025-03-11 04:32:41.348 UTC [600] DETAIL:  Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).
2025-03-11 04:32:52.352 UTC [611] FATAL:  data directory "/srv/postgres14" has invalid permissions
2025-03-11 04:32:52.352 UTC [611] DETAIL:  Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).

NAME    NAMESPACE       REVISION        UPDATED                                 STATUS          CHART           APP VERSION
pmm     pmm             9               2025-03-07 17:36:59.467343595 +0100 CET deployed        pmm-1.4.0       3.0.0

[rf-radovitsa]

#499