I've setup a CD4PE install using http://github.com/MikaelSmith/cd4pe-k8s. When I try to cd to the persistent volume it creates, it times out. Looking at events for the temporary pod it created, I see
Normal Scheduled 25s default-scheduler Successfully assigned cd4pe-1/washjf7kc to node-1
Warning FailedMount 8s (x6 over 24s) kubelet, node-1 MountVolume.SetUp failed for volume "pvc-e7d42aee-51ba-4ae9-a216-9aeaf566bd11" : mount command failed, status: Failure, reason: Rook: Mount volume failed: failed to attach volume pvc-e7d42aee-51ba-4ae9-a216-9aeaf566bd11 for pod cd4pe-1/washjf7kc. Volume is already attached by pod cd4pe-1/cd4pe-0. Status Running
There's two bugs here. We should be able to find that warning in Wash logs or output. And we should be able to inspect a volume that's already mounted (ideally by execing in the container that's mounted it, which will be faster than scheduling a temporary container).
I've setup a CD4PE install using http://github.com/MikaelSmith/cd4pe-k8s. When I try to cd to the persistent volume it creates, it times out. Looking at events for the temporary pod it created, I see
There's two bugs here. We should be able to find that warning in Wash logs or output. And we should be able to inspect a volume that's already mounted (ideally by execing in the container that's mounted it, which will be faster than scheduling a temporary container).