Improve error log when instance snapshot fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
vu tran | ||
Queens |
New
|
Undecided
|
Unassigned | ||
Rocky |
New
|
Undecided
|
Unassigned | ||
Stein |
Fix Released
|
Undecided
|
Unassigned | ||
Train |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
If glance backend store is set to use filesystem storage and this storage is running out of space when if glance is trying to create a instance snapshot, then in nova-compute log the following message is displayed:
2016-08-08 22:24:31.644 TRACE oslo_messaging.
2016-08-08 22:24:31.644 TRACE oslo_messaging.
2016-08-08 22:24:31.644 TRACE oslo_messaging.
It's a little bit annoying that we're logging the HTTP error from glance and that we don't specify the image uuid.
Steps to reproduce:
* set glance's config filesystem_
* start nova instance
* keep invoking "nova image-create" to create instance image snapshot, eventually the backend filesystem storage would run out of space
* on nova-compute log see the HTTP error message above.
Changed in nova: | |
assignee: | nobody → vu tran (vu-tran) |
Changed in nova: | |
status: | New → In Progress |
Changed in nova: | |
assignee: | vu tran (vu-tran) → Stephen Finucane (stephenfinucane) |
Changed in nova: | |
assignee: | Stephen Finucane (stephenfinucane) → Matt Riedemann (mriedem) |
Changed in nova: | |
importance: | Undecided → Low |
assignee: | Matt Riedemann (mriedem) → vu tran (vu-tran) |
There are no currently open reviews on this bug, changing
the status back to the previous state and unassigning. If
there are active reviews related to this bug, please include
links in comments.