openstack cinder storageclass does not provide ReadWriteMany accessmode

[josedev-union]

invalid AccessModes [ReadWriteMany]: only AccessModes [ReadWriteOnce] are supported

[frittenlab]

To use ReadWriteMany volumes you will also need a multi attach volume type in openstack. If you run the command:

openstack volume type list

You should be able to see the available volume types. We have two types and one of them supports multi attach. I created a separate storage class to support ReadWriteMany volumes which references the volume type id:

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: read-write-many
provisioner: cinder.csi.openstack.org
parameters:
  type: b9a45f96-37cc-4e0b-888d-c1j8969

You will also need to use these versions of the images:

k8scloudprovider/openstack-cloud-controller-manager:v1.19.2
k8scloudprovider/cinder-csi-plugin:v1.19.0

There is more information here:

multi-attach-volumes

[jichenjc]

yeah, we support multiple attach feature which is added recently @josedev-union please check above comments and see whether it works for you then we can close this issue, thanks

[josedev-union]

that is cool 👍

[andy-vm]

Hi @jichenjc may I double confirm if openstack-cloud-controller-manager is required to enable RWX for cinder?

I installed latest cinder-csi-plugin but still not able to have RWX, RWO works

thanks

[tipmg]

Hello, @jichenjc I installed latest cinder-csi-plugin and check logs openstack-cinder-csi-nodeplugin: Enabling volume access mode: SINGLE_NODE_WRITER Also I checked the source code and found it.

Please reopen this Issue.

[jichenjc]

/reopen

[k8s-ci-robot]

@jichenjc: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jichenjc]

I didn't go to detail now, let's reopen and if we don't need fix ,let's close later

thanks @tipmg

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[josedev-union]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.