yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #16573
[Bug 1333742] [NEW] Timeout while attaching cinder volumes in proxy configuration
Public bug reported:
Hey,
I am seeing a problem when attaching multiple volumes to a host.
My setup:
Between the cinder client and cinder-api process there is a proxy. If the request for detachment does not return any value for more than a minute the proxy will time out the connection.
What I am missing is the difference between a dead process and a process which is working, especially if the work can need longer then a special time. Is there a possibility to have more communication/information between the cinder-api and the cinder client, such as:
Request to attach ->
Still attaching <- (every 10 seconds)
Attached <-
BR Nikolas
PS: Can you tell me which entity in the cinder api is exactly receiving the http request? I have found the entity where cinder client starts the http request.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1333742
Title:
Timeout while attaching cinder volumes in proxy configuration
Status in OpenStack Compute (Nova):
New
Bug description:
Hey,
I am seeing a problem when attaching multiple volumes to a host.
My setup:
Between the cinder client and cinder-api process there is a proxy. If the request for detachment does not return any value for more than a minute the proxy will time out the connection.
What I am missing is the difference between a dead process and a process which is working, especially if the work can need longer then a special time. Is there a possibility to have more communication/information between the cinder-api and the cinder client, such as:
Request to attach ->
Still attaching <- (every 10 seconds)
Attached <-
BR Nikolas
PS: Can you tell me which entity in the cinder api is exactly receiving the http request? I have found the entity where cinder client starts the http request.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1333742/+subscriptions
Follow ups
References