Volume creation error - how to determine reason programmatically

Asked by Joe D'Andrea on 2015-05-01

For /v2/​{tenant_id}​/volumes/​{volume_id}​ when volume status is "error" is there any way, using the API/CLI, to discover more context around the error, e.g., a root or other cause?

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu cinder Edit question
Assignee:
No assignee Edit question
Last query:
2015-05-05
Last reply:
2015-09-08
Joe D'Andrea (joedandrea) said : #1

By comparison, Cinder backup objects set fail_reason in the event of an error. Is there something similar for volume creation?

Joe D'Andrea (joedandrea) said : #2

Update: Per DuncanT there is no such way at the moment, and there will be a cross-project session at the Liberty Summit to discuss the best way to go about fixing this.

Dilip S M (itzdilip) said : #4

there is command cinder-manage logs error

did you try?

Can you help with this problem?

Provide an answer of your own, or ask Joe D'Andrea for more information if necessary.

To post a message you must log in.