yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #69198
[Bug 1728689] Re: Misleading log message when location list is empty
Reviewed: https://review.openstack.org/516441
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=9e9743f5713948c9530aed603e7cc52b85c3b879
Submitter: Zuul
Branch: master
commit 9e9743f5713948c9530aed603e7cc52b85c3b879
Author: Brian Rosmaita <rosmaita.fossdev@xxxxxxxxx>
Date: Mon Oct 30 16:11:46 2017 -0400
Clarify log message
The current message logged when showing image locations or direct_url
is enabled makes it sound like there's a problem with the storage
backend, whereas it's really just an explanation of why the locations
or direct_url are empty/missing in the image response. This patch
rewrites the message to say that explicitly.
Change-Id: I9768fbba73aa290a7d159c01bd5ac0e9237f48ed
Closes-bug: #1728689
** Changed in: glance
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1728689
Title:
Misleading log message when location list is empty
Status in Glance:
Fix Released
Bug description:
When (a) show_multiple_locations=True or show_image_direct_url=True
and (b) an image has an empty location list, and (c) any call that
returns an image record is made, a message is logged saying: "There is
not available location for image <image_id>". This message is
misleading because it sounds like there's a problem with the backing
store, whereas all it means is that the locations list for that image
is empty. It's a minor problem, but it's come up in the glance
channel recently [1,2], so it is causing some operator unpleasantness.
[1] http://eavesdrop.openstack.org/irclogs/%23openstack-glance/%23openstack-glance.2017-10-06.log.html#t2017-10-06T13:19:04
[2] http://eavesdrop.openstack.org/irclogs/%23openstack-glance/%23openstack-glance.2017-10-11.log.html#t2017-10-11T18:59:31
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1728689/+subscriptions
References