Openshift Image Registry cannot write to persistent volume #1937
-
Hi, I have a NFS server that I've been using to create persistent volumes for OKD. I've created one for openshift image registry with the following permissions within the NFS server:
I'm using OKD 4.15 baremetal and followed the steps in the documentation to deploy the registry. It was working nicely and was writing to the persistent volume, which out of the blue, it has stopped doing. I can't think of anything that could've caused the issue. I have tried with a debug pod to see the container user groups and I can see that it's part of "root" group.
Despite this, when trying to access the persistent volume from within the container, I get permission denied.
I am using podman to manage images. When trying
Pod logs show the following errors:
Which as far as I can tell, is pointing to the same issue of persistent volume not accessible anymore. I've tried deleting everything including the deployment, service, route, persistent volume and persistent volume claims; and then rebuilding the registry again but no luck. Please let me know what other info I need to provide. Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
It was an internal issue of a config change that didn't persist across reboot in the nfs config. |
Beta Was this translation helpful? Give feedback.
It was an internal issue of a config change that didn't persist across reboot in the nfs config.