-
Notifications
You must be signed in to change notification settings - Fork 610
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
[manila-csi-plugin] Cannot extend pvc #2619
Comments
hey @stevenyslins The request failed in manila; it appears you have access to the manila CLI; could you try this:
(or maybe there's some detail there around why the share wasn't extended as you expected. If there's something failing on the backend, you might need to contract your cloud provider. |
My instruction is as follows, and I am also the administrator of this OpenStack installation. Thank you for your response.
|
That's great; because from the error message below; it looks like an ir-recoverrable error occurred on the backend driver's attempt to extend the share.
Can you look at your manila-share log file and determine happened here? From the o/p it appears you are using the Generic driver - which creates cinder volumes and exports them as NFS/CIFS shares. Maybe the extension request failed to get communicated to cinder? Or maybe it failed during the interaction? Does this always occur? |
At
And in the Cinder log, I cannot find any helpful information.
Additionally, when I use the Manila CLI to extend the volume, it works.
|
Thanks; from the error its apparent that
when performing an unmount operation; which is strange because the list of exports to remove is compiled by executing Does this always happen when the extension is requested via manila-csi? The reason I ask is because there is no difference in the API calls between manila-csi and the manila CLI you're using: https://github.com/gophercloud/gophercloud/blob/3bb883c4ebe42c7eb9382406e4b3f9e1cc3743ca/openstack/sharedfilesystems/v2/shares/requests.go#L310 To triage the exportfs behavior, I'm curious what's the operating system of the manila service image in your environment? and what version? |
Yes, when using the
Our environment runs the Manila service on the following operating system:
And manila image as follows:
Thank you for your response. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Is this a BUG REPORT or FEATURE REQUEST?:
What happened:
When I extend the volume, my pvc get
Extending Error
statusWhat you expected to happen:
Resize volume succeeded
How to reproduce it:
Need to create a
neutron-net
andneutron-subnet
.storageclass.yaml
apply storageclass yaml
pvc.yaml
apply pvc.yaml
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: