#8647 issues starting pods with volume mounts in communishift
Closed: Fixed 4 years ago by kevin. Opened 4 years ago by dustymabe.

Describe what you would like us to do:

In the fedora-coreos-1581642152 namespace in communishift I'm trying to start the jenkins deployment config. The pods that are created fail to come up because the volume mounts are hitting an error when mounting:

Generated from kubelet on os-node06.fedorainfracloud.org
MountVolume.SetUp failed for volume "openshift-05gb-02" : mount failed: exit status 32 Mounting command: systemd-run Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/59cd5004-4ec8-11ea-b186-405cfda580af/volumes/kubernetes.io~nfs/openshift-05gb-02 --scope -- mount -t nfs storinator01.fedorainfracloud.org:/srv/nfs/openshift-5gb-02 /var/lib/kubelet/pods/59cd5004-4ec8-11ea-b186-405cfda580af/volumes/kubernetes.io~nfs/openshift-05gb-02 Output: Running scope as unit: run-r16fe986caaf64b50bedf88cdd2254783.scope mount.nfs: mounting storinator01.fedorainfracloud.org:/srv/nfs/openshift-5gb-02 failed, reason given by server: No such file or directory 

If you try to start a new rollout of the deployment (oc rollout latest dc/jenkins --namespace fedora-coreos-1581642152) you can watch the events for the generated pod from the console (they should look like the failure I pasted above).


Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: communishift

4 years ago

This should be fixed now. I recreated a number of those. If it still happens, feel free to re-open.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata