Output: Running scope as unit: run-r962ebe3c3bd94fdda50ad52ea708c915.scope mount.nfs: access denied by server while mounting ntap-phx2-c01-fedora01-nfs.storage.phx2.redhat.com://openshift-stg-registry Warning FailedMount 1m (x2 over 3m) kubelet, osbs-aarch64-master01.stg.arm.fedoraproject.org Unable to mount volumes for pod "docker-registry-1-8q5px_default(28bc38fc-d492-11e8-85c3-525400e0ac42)": timeout expired waiting for volumes to attach/mount for pod "default"/"docker-registry-1-8q5px". list of unattached/unmounted volumes=[registry-storage]
We have tried with @kevin to disable the persistent storage here but it seems that it is needed :pensive:
When do you need this? (YYYY/MM/DD)
When is this no longer needed or useful? (YYYY/MM/DD)
If we cannot complete your request, what is the impact?
Metadata Update from @cverna: - Issue tagged with: OSBS
So, I can make storage volumes here... but can the aarch64 and x86_64 ones share ? Or are they completely seperate clusters?
ie, do I need only a osbs-stg-registry/osbs-prod-registry, or do I need osbs-aarch64-stg-registry/osbs-aarch64-prod-registry/osbs-x86_64-stg-registry/osbs-x86_64-prod-registry
?
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
As discussed on IRC, lets try to use the same storage volume but with different directories per arch for example x86_64/ and aarch64/
x86_64/
aarch64/
Should be done for stg. We can setup prod if this works out.
So I think I goofed this up by not having the correct inventory in the first time. I tried again this morning with the nfs storage commented out and the registry pod is running correctly :smile:
Thanks for the help
Metadata Update from @cverna: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
ok. I deleted the netapp volumes/export-policy.
Login to comment on this ticket.