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

[csi-cinder-plugin] CSI-Cinder Plugin Sending Requests to Incorrect Cinder API URL, Causing Overload and HTTP 503 Responses #2765

Open
scroveez opened this issue Feb 5, 2025 · 0 comments

Comments

@scroveez
Copy link

scroveez commented Feb 5, 2025

Description:
We’ve identified an issue with the CSI-Cinder plugin where it is sending requests to the wrong URL for the Cinder API. The plugin is using the URL: https://cinder_api_url:8776/ while the correct URL should include the /v3.

As a result, Cinder is responding with an HTTP 300 (Multiple Choices) error, which is overloading the Cinder API and, in some cases, leads to intermittent HTTP 503 (Service Unavailable) responses due to the high volume of requests being made to the wrong URL.

Steps to Reproduce:

  1. Deploy CSI-Cinder plugin.
  2. Observe the incoming requests to the Cinder API.
  3. Notice that the plugin is using the incorrect URL without the /v3 path.
  4. This results in Cinder responding with HTTP 300, leading to increased load and HTTP 503 responses.

Expected Behavior:
The CSI-Cinder plugin should be sending requests to the correct URL: https://cinder_api_url:8776/v3 , this will prevent HTTP 300 responses and the subsequent overload on the Cinder API

Actual Behavior:
The CSI-Cinder plugin is currently sending requests to this URL: https://cinder_api_url:8776/ , which does not include /v3

Impact:
This issue is causing the Cinder API to respond with HTTP 300, leading to high traffic and occasional HTTP 503 (Service Unavailable) responses, impacting the stability of the Cinder API.

Additional Information:

  • The issue only appears when requests are sent to the incorrect URL.
  • Monitoring and logs indicate a high number of HTTP 300 responses, followed by HTTP 503 due to load on the Cinder API.

Environment:

  • CSI-Cinder plugin version: [v1.31.2]
  • Cinder API version: [v3]
  • Cloud Provider: [OpenStack Yoga on-prem, Ubuntu 20.04]
  • K8S version: MicroK8s v1.32.1 revision 7589
  • Configuration used with CSI-Cinder:
[Global]
auth-url=https://mydomain:5000/v3
region=xyz

application-credential-id=my_cred_id
application-credential-secret=my_cred_secret

[LoadBalancer]
floating-network-id=b37a7409-78c9-4518-bd9d-a1cfaf1f6f6a
subnet-id=1ba8f3df-b61a-40bb-87d8-ad401f574ed0
member-subnet-id=2381d4e7-fed8-4bba-97a9-98ceb086b065
internal-lb=false
lb-provider=amphora

[BlockStorage]
ignore-volume-az=yes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant