-
Notifications
You must be signed in to change notification settings - Fork 62
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
Comments
Can you also put the container logs for the same? |
container_logs.txt |
@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
|
After the above pod creation, |
@wdurairaj I have followed steps given by you. pod came in running status and post that "docker volume ls" showed "IMPORTED-VOLUME" created. |
@virendra-sharma, as per your previous update, can i close this issue ? |
@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. |
@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. |
moved to 3.2 release |
moved to 3.2.1 Release., this need further investigation |
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
container logs
container_logs.txt
YAML's
importvol_pv.yml
importvol_pvc.yml
Note:- Able to import same volume through docker command. (docker volume create -d hpe --name imported_vol -o importVol=Test_vol -o backend=3PAR1).
The text was updated successfully, but these errors were encountered: