[cinder-csi-plugin] New cinder volumes are created when ephemeral volume fails to attach

[creatica-soft]

[cinder-csi-plugin] If an ephemeral volume fails to attach for any reason, cinder-csi-plugin will keep creating new volumes

/kind bug

What happened:
If an ephemeral volume fails to attach for any reason, cinder-csi-plugin will keep creating new volumes. To stop it, I have to delete the deployment and then manually delete all these volumes from openstack. The current limit of the number of volumes in centos guest seems to be 26 from vda to vdz. So new volumes fail to attach after that limit.

What you expected to happen:
The plugin will try to attach the same volume.

How to reproduce it:
Same as in #1403

Anything else we need to know?:
This is a continuation from #1403.

Environment:

• openstack-cloud-controller-manager(or other related binary) version: 1.20.2
• OpenStack version: Pike
• Others: k8s 1.19.6

[ramineni]

/assign

[ramineni]

@creatica-soft In what state the volume is after attach failed?

[creatica-soft]

@ramineni It is available. It fails to mount because the number of scsi devices on a single bus, i.e. scsi controller exceeds 32 (well, 26 in this case: letters from a to z). Scsi controllers are not hot-pluggable in KVM, so a reboot is required for the VM even when a controller is added dynamically. But then in order to reboot, one would need to drain the node, at which point all the volumes will be unmounted and the extra scsi controller would not be required. So not sure if KVM will remove it prior to reboot or not - haven't tested this.

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[ramineni]

/remove-lifecycle stale

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[ramineni]

/remove-lifecycle stale

[ramineni]

@creatica-soft we are planning to deprecate Inline ephemeral volumes feature in favor of generic ephemeral volumes.
please check #1493 for more details.

Suggest to use generic ephemeral volumes instead.

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[ramineni]

Inline ephemeral volumes feature is deprecated from 1.24. Please use generic ephemeral volumes instead

[ramineni]

/close

[k8s-ci-robot]

@ramineni: Closing this issue.

In response to this:

/close

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.