Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ImportVol not working for additional backend in kubernetes #492

Open
virendra-sharma opened this issue Feb 28, 2019 · 10 comments
Open

ImportVol not working for additional backend in kubernetes #492

virendra-sharma opened this issue Feb 28, 2019 · 10 comments
Assignees
Milestone

Comments

@virendra-sharma
Copy link

virendra-sharma commented Feb 28, 2019

Unable to importVol from additional backend in kubernetes 1.13 setup. getting doryd error log as below.

Error log of doryd

7:19:04 provisioner.go:237: statusLogger: provision chains=0, delete chains=0, parked chains=0, ids tracked=0, connection=valid
07:19:05 class.go:75: unable to find a class named
07:19:05 claim.go:77: error getting class named  for pvc pvc-importvol. err=unable to find a class named

Steps performed

  1. created volume (Test_vol) in 3PAR1 array.
  2. Created pv, pvc with below yml files.
  3. observed volume not imported.

container logs

container_logs.txt

YAML's

importvol_pv.yml

apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv-import-volume
spec:
    capacity:
      storage: 35Gi
    accessModes:
    - ReadWriteOnce
    flexVolume:
      driver: hpe.com/hpe
      options:
        name: "IMPORTED-VOLUME"
        importVol: "Test_vol"
        backend: "3PAR1"

importvol_pvc.yml

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: pvc-importvol
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 35Gi

Note:- Able to import same volume through docker command. (docker volume create -d hpe --name imported_vol -o importVol=Test_vol -o backend=3PAR1).

@nilangekarss
Copy link
Collaborator

Can you also put the container logs for the same?

@virendra-sharma
Copy link
Author

container_logs.txt
Please find attached container_logs.

@wdurairaj
Copy link
Collaborator

@virendra-sharma , I did some experimentation on this one. Seems like in static provisioning only when you do a pod mount referencing a pvc claim, then the volume is created..

Can you try creating a pod like this

sudo kubectl create -f - << EOF
---
apiVersion: v1
kind: Pod
metadata:
  name: pod1
spec:
  containers:
  - name: nginx
    image: nginx
    volumeMounts:
    - name: export
      mountPath: /export
  restartPolicy: Always
  volumes:
  - name: export
    persistentVolumeClaim:
      claimName: pvc-importvol
EOF

@wdurairaj
Copy link
Collaborator

After the above pod creation, docker volume ls would list the volume IMPORTED-VOLUME

@virendra-sharma
Copy link
Author

@wdurairaj I have followed steps given by you. pod came in running status and post that "docker volume ls" showed "IMPORTED-VOLUME" created.

@wdurairaj
Copy link
Collaborator

@virendra-sharma, as per your previous update, can i close this issue ?

@virendra-sharma
Copy link
Author

@wdurairaj I have observed on some of setup static volume get created before pod, so it will be good if you suggest one specific condition for it.

@wdurairaj wdurairaj added medium and removed high labels Apr 9, 2019
@wdurairaj
Copy link
Collaborator

@virendra-sharma , until you confirm if this problem exists in some other environments as per your last comment, I have to downgrade the priority to "medium", since there is a solution to the issue and no more it can be a blocker.

@prablr79 prablr79 modified the milestones: 3.1, 3.2 Apr 10, 2019
@prablr79 prablr79 added low and removed medium labels Apr 16, 2019
@prablr79
Copy link
Contributor

moved to 3.2 release

@prablr79
Copy link
Contributor

moved to 3.2.1 Release., this need further investigation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants