docker-flexvol icon indicating copy to clipboard operation
docker-flexvol copied to clipboard

Pod stuck in `ContainerCreating` state in k8 1.12.3

Open surbhibakhtiyar opened this issue 7 years ago • 4 comments

While creating pod using this driver it gives the following error :

  Warning  FailedMount  6s (x5 over 14s)  kubelet, 10.xx.xx.xx  MountVolume.SetUp failed for volume "test" : invalid character '/' looking for beginning of value

The same script docker-flexvol.sh works fine with k8 1.10.11 but not 1.12.3

surbhibakhtiyar avatar Jan 11 '19 11:01 surbhibakhtiyar

@dims ^^

surbhibakhtiyar avatar Jan 11 '19 11:01 surbhibakhtiyar

@surbhibakhtiyar i tried the steps outlined in README.md against latest kubernetes and i don't see the issue. Can you please try the exact same steps as in the readme including the my-container-image container and let me know please?

dims avatar Jan 18 '19 15:01 dims

@dims I tried the exact same steps as in the readme including the my-container-image container but it didn't work for me. It gives same error

apiVersion: v1
kind: Pod
metadata:
  name: nginx
  namespace: testNamespace
spec:
  containers:
  - name: nginx
    image: nginx
    volumeMounts:
    - name: test
      mountPath: /data
    ports:
    - containerPort: 80
  volumes:
  - name: test
    flexVolume:
      driver: "dims.io/docker-flexvol"
      options:
        image: "registry.ng.bluemix.net/test/my-container-image"
        name: "/data-store"
  imagePullSecrets:
  - name: mysecret
  nodeSelector: 
    kubernetes.io/hostname: xxxx
  

Error:

Events:
  Type     Reason       Age               From                   Message
  ----     ------       ----              ----                   -------
  Normal   Scheduled    12s               default-scheduler      Successfully assigned testNamespace/nginx to 10.xx.xx.xxx
  Warning  FailedMount  4s (x5 over 12s)  kubelet, 10.xx.xx.xxx  MountVolume.SetUp failed for volume "test" : invalid character '/' looking for beginning of value

surbhibakhtiyar avatar Feb 11 '19 10:02 surbhibakhtiyar

@surbhibakhtiyar can you check the kubelet logs (on the node where the failure occurs) and look for the same error (and look if there are any more information just before this problem occurs?)

dims avatar Feb 11 '19 12:02 dims