What were you trying to do that didn't work?

After updating a RHEL for Edge 9.6 commit, by applying EUS patches, pmlogger.service does not start after rebooting on the new deploy.

It appears the UID/GID of the pcp user has changed, preventing pmlogger to write into /var/log/pcp/pmlogger.

In the meantime, it has been suggested to define a fixed UID in /etc that takes precedence over the one defined in /usr/lib/passwd, and running a chown on the files that needs to (in /var/lib/pcp and /var/log/pcp).

As per the following article, https://lwn.net/Articles/1018082/ 

I understand the issue is common in this environment.

What is the impact of this issue to you?

Cannot upgrade the image without fixing the issue afterwards.

Please provide the package NVR for which the bug is seen:

pcp-6.3.7-1.el9_6.x86_64

osbuild-composer-149-3.el9_7.x86_64

How reproducible is this bug?:

Always for the customer.

Expected results

The pmlogger service can start after an `rpm-ostree upgrade`.

Actual results

15176 16:22:49.405769 openat(AT_FDCWD</var/log/pcp/pmlogger/r760>, "/var/log/pcp/pmlogger/r760/20260127.16.22-98.index", O_WRONLY|O_CREAT|O_TRUNC, 0666 <unfinished ...>
15176 16:22:49.405796 <... openat resumed>) = -1 EACCES (Permission denied) <0.000014>