yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #90353
[Bug 1613770] Fix included in openstack/nova stein-eol
This issue was fixed in the openstack/nova stein-eol release.
** Changed in: nova/stein
Status: Fix Committed => Fix Released
--
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/1613770
Title:
Improve error log when instance snapshot fails
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) queens series:
New
Status in OpenStack Compute (nova) rocky series:
New
Status in OpenStack Compute (nova) stein series:
Fix Released
Status in OpenStack Compute (nova) train series:
Fix Released
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.rpc.server HTTPOverLimit: 413 Request Entity Too Large
2016-08-08 22:24:31.644 TRACE oslo_messaging.rpc.server Image storage media is full: There is not enough disk space on the image storage media.
2016-08-08 22:24:31.644 TRACE oslo_messaging.rpc.server (HTTP 413)
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_store_datadir to small size 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1613770/+subscriptions
References