OCP 4.2 ImageRegistry fails with nfs-storage on s390x about image-registry HOT 7 CLOSED

are you able to mount the storage volume in question from a standard pod?

mount.nfs: No route to host makes it seem like the issue here is w/ your PV setup more than the registry itself.

from image-registry.

Its on libvirt KVM where bastion is having ip: 192.168.79.1.
nfs PV is

[root@localhost ~]# oc get pv nfs-storage -n openshift-image-registry -o yaml
apiVersion: v1
kind: PersistentVolume
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"PersistentVolume","metadata":{"annotations":{},"name":"nfs-storage"},"spec":{"accessModes":["ReadWriteMany","ReadWriteOnce"],"capacity":{"storage":"100Gi"},"claimRef":{"apiVersion":"v1","kind":"PersistentVolumeClaim","name":"image-registry-storage","namespace":"openshift-image-registry"},"nfs":{"path":"/home/nfsshare","server":"192.168.79.1"},"persistentVolumeReclaimPolicy":"Recycle","volumeMode":"Filesystem"},"status":{}}
  creationTimestamp: "2020-01-24T12:37:00Z"
  finalizers:
  - kubernetes.io/pv-protection
  name: nfs-storage
  resourceVersion: "20593093"
  selfLink: /api/v1/persistentvolumes/nfs-storage
  uid: 379c807d-3ea6-11ea-8a3e-525400da7041
spec:
  accessModes:
  - ReadWriteMany
  - ReadWriteOnce
  capacity:
    storage: 100Gi
  claimRef:
    apiVersion: v1
    kind: PersistentVolumeClaim
    name: image-registry-storage
    namespace: openshift-image-registry
    resourceVersion: "20593090"
    uid: 5ba8e1da-3ea6-11ea-8a3e-525400da7041
  nfs:
    path: /home/nfsshare
    server: 192.168.79.1
  persistentVolumeReclaimPolicy: Recycle
  volumeMode: Filesystem
status:
  phase: Bound
[root@localhost ~]#

[root@localhost ~]# oc get pod -n openshift-image-registry | grep image-registry
image-registry-5598d76584-4wfxq                    0/1     ContainerCreating   0          144m  --> With NFS failing with error mount.nfs: No route to host
image-registry-8fdfb6c68-pdf8f                     1/1     Running             0          5h26m  --> EmptyDir
[root@localhost ~]#

I tried to login to pod image-registry-8fdfb6c68-pdf8f ( EmptyDir) and tried mounting... but it is not allowed to mount as non-root user.

Please let me know, if I am trying correct or understand correctly...

from image-registry.

I tried to login to pod image-registry-8fdfb6c68-pdf8f ( EmptyDir) and tried mounting... but it is not allowed to mount as non-root user.

That's not what i meant. I meant just create your own pod (running whatever image you want) that mounts the PV in the same way that the registry pod does.

That said, I see you have 2 registry instances running, so it seems like one of them was able to mount the NFS volume and one was not? Assuming the two pods are running on different nodes, it would seem likely that the issue is with one of your nodes not being able to reach the NFS server.

from image-registry.

/lifecycle stale

from image-registry.

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

from image-registry.

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

from image-registry.

@openshift-bot: Closing this issue.

from image-registry.