Bug 781639

Summary: displayed rhevm image uri doesn't match anything in rhevm ui
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: aeolus-conductorAssignee: Maros Zatko <mzatko>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0.0CC: akarol, deltacloud-maint, mzatko, slinaber, ssachdev
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://hostname/conductor/images/<image_hash>
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-30 17:12:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
ss none

Description Dave Johnson 2012-01-13 23:51:40 UTC 
Description of problem:
==================================
On the image details page at the url on this bug, each provider that has a account with a push image shows an image uri (that is suppose to help the user identify the image in the 3rd party cloud app) which is the case with vmware and ec2.  

Rhevm however is not this easy.  When we push a image to rhevm, we name the template image with the provider_image_id hash but rhevm creates its own uuid to identify the image which we call the target_id and is the value display in the conductor ui.  

The problem comes when the user looks at the rhevm ui to find the template, the value in the conductor ui does not match what is displayed in the rhvm ui.  That rhevm uuid is only visible in the rhevm api and its xml output.

mock provider doesn't have a third party ui to match so not really worried about it.

Version-Release number of selected component (if applicable):
=================================================================
aeolus-all-0.8.0-5.el6.noarch
aeolus-conductor-0.8.0-5.el6.noarch
aeolus-conductor-daemons-0.8.0-5.el6.noarch
aeolus-conductor-doc-0.8.0-5.el6.noarch
aeolus-configure-2.5.0-4.el6.noarch
rubygem-aeolus-cli-0.3.0-3.el6.noarch
rubygem-aeolus-image-0.3.0-2.el6.noarch
Comment 1 Dave Johnson 2012-01-13 23:52:22 UTC 
Created attachment 555163 [details]
ss
Comment 2 Martyn Taylor 2012-01-16 15:33:48 UTC 
*** Bug 781640 has been marked as a duplicate of this bug. ***
Comment 3 Angus Thomas 2012-01-18 10:49:56 UTC 
Tomas,

Can you please establish what additional identifiers for an image are available from the DC API? If the UI can be enhanced to include an additional useful identifier then please implement that.

Any further work required, such as a change to the deltacloud driver etc., will fall outside the scope of the 1.0 release.
Comment 4 Maros Zatko 2012-01-27 13:04:27 UTC 
fixed in axiom/1.0-staging

commit c678fabdadb6b83aa5cbf50244f0a4a38b5b8a51
Author: Maros Zatko <mzatko>
Date:   Thu Jan 26 14:45:13 2012 +0100

    BZ 781639: added column with Image UUID to provider images view
    
    https://bugzilla.redhat.com/show_bug.cgi?id=781639
    
    This allows you to identify image in RHEV-M.
Comment 5 Steve Linabery 2012-01-31 22:29:29 UTC 
c678fab is in aeolus-conductor-0.8.0-17
Comment 6 Dave Johnson 2012-02-01 16:41:16 UTC 
good 2 go with:

aeolus-all-0.8.0-17.el6.noarch
aeolus-conductor-0.8.0-17.el6.noarch
aeolus-conductor-daemons-0.8.0-17.el6.noarch
aeolus-conductor-doc-0.8.0-17.el6.noarch