yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #52901
[Bug 1594385] Re: Nova does not report signature verification failure
Reviewed: https://review.openstack.org/332802
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f39e660baf5543fa1acc95c106fd4d98a69e69a9
Submitter: Jenkins
Branch: master
commit f39e660baf5543fa1acc95c106fd4d98a69e69a9
Author: dane-fichter <dane.fichter@xxxxxxxxxx>
Date: Mon Jun 27 12:55:02 2016 -0700
Improve image signature verification failure notification
This change modifies the exception handling when Nova's
image signature verification fails so that the build is
aborted and instance's fault shows the error.
Change-Id: I05d877fe92593edaaa8b93b87b4b787827cae8f0
Closes-bug: #1594385
** Changed in: nova
Status: In Progress => 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/1594385
Title:
Nova does not report signature verification failure
Status in OpenStack Compute (nova):
Fix Released
Bug description:
When verifying Glance image signatures, Nova does not report a
meaningful error message to the end user. Instead, Nova gives the end
user a "No hosts available" message.
How to verify this behavior:
- Enable Nova's verify_glance_signatures configuration flag
- Upload an image to Glance with incorrect or missing signature metadata
- Attempt to boot an instance of this image via the Nova CLI
You should get an error message with the text "No valid host was
found. There are not enough hosts available". This does not describe
the failure and will lead the end user to think there is an issue with
the storage on the compute node.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1594385/+subscriptions
References