During a recent install of Openshift we noticed a new version 3.7.1. The install completed. When we deployed our applications which use PVC for data storage. These mounts would not complete. They would continually time out.
Here is the error from the events 24m 24m 1 git-2-qhffc Pod Warning FailedMount kubelet, techpubs.mdc.usaorbea.lab MountVolume.MountDevice failed for volume "pvc-7c8a703c-3205-11e8-97c9-005056bef3d7" : failed to mount the volume as "ext3", it already contains mpath_member. Mount error: mount failed: exit status 32 Mounting arguments: --description=Kubernetes transient mount for /var/lib/origin/openshift.local.volumes/plugins/kubernetes.io/vsphere-volume/mounts/[vSphere-Pure-01] kubevols/kubernetes-dynamic-pvc-7c8a703c-3205-11e8-97c9-005056bef3d7.vmdk --scope -- mount -t ext3 -o defaults /dev/disk/by-id/wwn-0x6000c29c0fe8f9bd63e5fb4601560add /var/lib/origin/openshift.local.volumes/plugins/kubernetes.io/vsphere-volume/mounts/[vSphere-Pure-01] kubevols/kubernetes-dynamic-pvc-7c8a703c-3205-11e8-97c9-005056bef3d7.vmdk mount: /dev/sde is already mounted or /var/lib/origin/openshift.local.volumes/plugins/kubernetes.io/vsphere-volume/mounts/[vSphere-Pure-01] kubevols/kubernetes-dynamic-pvc-7c8a703c-3205-11e8-97c9-005056bef3d7.vmdk busy What I eventually found was two packages that got installed either during the package update or during openshift-ansible installation. The packages were device-mapper-multipath and device-mapper-multipath-libs. What I'm trying to determine is whether the mount command is not restricting the flags it uses but dynamically adds flags based on some form of discovery. _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
