Closed wilmardo closed 5 years ago
Is fixed in the latest canary, I will close the issue but leave it for reference, for who is searching trough the issues (like I did).
Sorry for opening the issue but I couldn't find any information about it :)
I0315 13:24:07.598278 20530 mount_linux.go:515] Attempting to determine if disk "/dev/nbd0" is formatted using blkid with args: ([-p -s TYPE -s PTTYPE -o export /dev/nbd0])
I0315 13:24:07.602091 20530 mount_linux.go:518] Output: "", err: exit status 2
I0315 13:24:07.602196 20530 mount_linux.go:489] Disk "/dev/nbd0" appears to be unformatted, attempting to format as type: "xfs" with options: [/dev/nbd0]
I0315 13:24:07.948260 20530 mount_linux.go:493] Disk successfully formatted (mkfs): xfs - /dev/nbd0 /var/lib/kubelet/pods/92e0efe4-4725-11e9-8f60-dac245f50f13/volumes/kubernetes.io~csi/pvc-839a3b86-4725-11e9-8f60-dac245f50f13/mount
I0315 13:24:07.948296 20530 nsenter_mount.go:80] nsenter mount /dev/nbd0 /var/lib/kubelet/pods/92e0efe4-4725-11e9-8f60-dac245f50f13/volumes/kubernetes.io~csi/pvc-839a3b86-4725-11e9-8f60-dac245f50f13/mount xfs [defaults]
I0315 13:24:07.948329 20530 nsenter.go:130] Running nsenter command: nsenter [--mount=/rootfs/proc/1/ns/mnt -- /bin/systemd-run --description=Kubernetes transient mount for /var/lib/kubelet/pods/92e0efe4-4725-11e9-8f60-dac245f50f13/volumes/kubernetes.io~csi/pvc-839a3b86-4725-11e9-8f60-dac245f50f13/mount --scope -- /bin/mount -t xfs -o defaults /dev/nbd0 /var/lib/kubelet/pods/92e0efe4-4725-11e9-8f60-dac245f50f13/volumes/kubernetes.io~csi/pvc-839a3b86-4725-11e9-8f60-dac245f50f13/mount]
I have same issue can success mount first volume but second will failed it trying find all nbd pid and error when mount first volume and try reuse nbd0 when mount second volume
I0508 15:21:03.326551 21961 rbd_attach.go:105] found nbds max parameters file at /sys/module/nbd/parameters/nbds_max
I0508 15:21:03.326613 21961 rbd_attach.go:117] rbd-nbd: max_nbds: 16
I0508 15:21:03.326653 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd0: open /sys/block/nbd0/pid: no such file or directory
I0508 15:21:03.326698 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd1: open /sys/block/nbd1/pid: no such file or directory
I0508 15:21:03.326755 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd2: open /sys/block/nbd2/pid: no such file or directory
I0508 15:21:03.326806 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd3: open /sys/block/nbd3/pid: no such file or directory
I0508 15:21:03.326834 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd4: open /sys/block/nbd4/pid: no such file or directory
I0508 15:21:03.326887 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd5: open /sys/block/nbd5/pid: no such file or directory
I0508 15:21:03.326939 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd6: open /sys/block/nbd6/pid: no such file or directory
I0508 15:21:03.326997 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd7: open /sys/block/nbd7/pid: no such file or directory
I0508 15:21:03.327033 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd8: open /sys/block/nbd8/pid: no such file or directory
I0508 15:21:03.327088 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd9: open /sys/block/nbd9/pid: no such file or directory
I0508 15:21:03.327133 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd10: open /sys/block/nbd10/pid: no such file or directory
I0508 15:21:03.327173 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd11: open /sys/block/nbd11/pid: no such file or directory
I0508 15:21:03.327203 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd12: open /sys/block/nbd12/pid: no such file or directory
I0508 15:21:03.327234 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd13: open /sys/block/nbd13/pid: no such file or directory
I0508 15:21:03.327285 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd14: open /sys/block/nbd14/pid: no such file or directory
I0508 15:21:03.327342 21961 rbd_attach.go:159] did not find valid pid file in dir /sys/block/nbd15: open /sys/block/nbd15/pid: no such file or directory
full log: container.log
@james58899 Have you tried with the canary tag? That fixed the problem for me :)
@wilmardo I tried change rbdplugin using canary tag but did not help
@james58899 is there a way we can reproduce this issue?
@Madhu-1 I am not sure how reproduce but I set mounter: rbd-nbd
in storageclass will cause this issue.
Cluster info: OS: Ubuntu 18.04.2 Docker: 18.09.5 Kubernetes: 1.13.5 (kubeadm) Ceph: 14.2.1 (rook 1.0.0)
@james58899 if possible i will try to reproduce and update the issue
@Madhu-1 Can be reproduce or need more information?
@james58899 forgot about this issue. I will test this out shortly.
As the title state, the format of disk fails due missing entry in /etc/fstab or at least that seems the issue to me from the logs. I don't know how to proceed further as this seems an issue with the code itself or at least a case which isn't handled since it tries to format an undefined("") disk:
kubectl get nodes --show-labels
(please ignore the notReady nodes, cluster is in parts at the moment due missing resources). The cluster is running on CoreOScsi-rbdplugin
csi-provsioner
csi-attacher
If any log information is missing or you guys would like to peep at the kubectl files, I am happy to provide it!