Red Hat Bugzilla – Bug 863055
Image import is not working with "Cloud Resource Provider's Image ID "
Last modified: 2012-12-04 10:23:19 EST
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Its a related bug of https://bugzilla.redhat.com/show_bug.cgi?id=857899
2.Tried to import image using "Cloud Resource Provider's Image ID"
3.Its says "The requested image was not found on the Cloud Resource Provider"
4.But when i tried to import with the UUID, the image import worked
NOT sure the image import should work with Image uuid or Cloud Resource Provider's Image ID
Can any one please look in to
rpm -qa | grep aeolus
Created attachment 621564 [details]
Created attachment 621565 [details]
Created attachment 621566 [details]
Created attachment 621567 [details]
Looks like the real issue is the mis-labeled Cloud Provider's Image ID field in the image details page. Patch created:
In case I wasn't the only one baffled by this, here is what I've figured out after talking to Mainn:
1.) On the image import page, using something like "ami-b5e955dc" (as in the screenshot) is correct. That is what we call the "Cloud Resource Provider's Image ID." It's what the remote cloud provider uses to identify images.
2.) The bug here is not on the image import page. It is on the image *detail* page, where we showed the provider's image ID (in #1) under the label "Image UUID", which was plain wrong. We also had "Cloud Resource Provider's Image ID" displaying some sort of UUID, which was also plain wrong.
3.) Mainn's patch fixes #2. There is no change to the image import page, which is correct. (#813218 fixed that.)
On master and 1.1:
Author: Tzu-Mainn Chen <firstname.lastname@example.org>
Date: Thu Oct 4 13:04:46 2012 -0400
BZ863055 - correct provider's image ID field
Signed-off-by: Matt Wagner <email@example.com>
(cherry picked from commit 67980a6375a7674322bbb00d75f1a0eb39867a5e)
Cloud Resource Provider's Image ID shows the image id and UUID is removed.
rpm -qa|grep aeolus
Created attachment 625247 [details]
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.