create-env.sh fails in Minikube environment

[tschwaller]

Disk creation failed in Minikube environment. What could be the reason?

./deployment/minikube/scripts/create-env.sh
...
...
Started deploying
  Waiting for the agent on VM '54c7a391-5c97-4a16-60e3-3e7ada55e156'... Finished (00:00:00)
  Stopping jobs on instance 'unknown/0'... Finished (00:00:00)
  Deleting VM '54c7a391-5c97-4a16-60e3-3e7ada55e156'... Finished (00:00:01)
  Creating VM for instance 'bosh/0' from stemcell 'loewenstein/bosh-stemcell-kubernetes-ubuntu-trusty-go_agent:3445.11'... Finished (00:00:02)
  Waiting for the agent on VM 'a8579f87-2140-490b-66b4-22cf2fedb966' to be ready... Finished (00:00:12)
  Creating disk... Failed (00:05:36)
Failed deploying (00:05:52)

Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)

Deploying:
  Creating instance 'bosh/0':
    Updating instance disks:
      Updating disks:
        Deploying disk:
          Creating disk with size 10000, cloudProperties property.Map{}, instanceID a8579f87-2140-490b-66b4-22cf2fedb966:
            CPI 'create_disk' method responded with error: CmdError{"type":"Bosh::Clouds::CloudError","message":"Unknown error: 'Timeout \"Waiting for PVC to be bound\"'","ok_to_retry":false}

Exit code 1

[loewenstein]

Hi Tom,

looks like a problem with dynamic volume provisioning. Could you have a look at the output of kubectl get pvc and kubectl describe pvc <pvc id> with one of the youngest persistent volume claims.

The version of minikube would be interesting too so that I could try to reproduce in exactly your environment.

If the problem persists it would be great to get a debug log of BOSH_LOG_LEVEL=debug BOSH_LOG_PATH=./debug.log bosh create-env

[loewenstein]

@tschwaller ^^

[tschwaller]

Will do...

[loewenstein]

@tschwaller any update on this one?