Bug 784969

Summary: importing rhevm image needs to check provider specified
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: aeolus-conductorAssignee: Tomas Hrcka <thrcka>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0.0CC: akarol, athomas, deltacloud-maint, hbrock, ssachdev, thrcka
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-15 22:25:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dave Johnson 2012-01-26 19:42:52 UTC 
Description of problem:
=======================================
When importing a rhevm image, the user specifies the template_id and the provider to map the image too. 

The problem is when I specify a image that is on a ProviderB but specify ProviderA in the conductor ui import form.  

The import process just checks that the image exists, if so it links the image to the provider the user specified (which may or may not be correct).  There doesn't seem to be any check to make sure the provider the user specified actually contains the image.

When this happens.  The UI will say the image is available on ProviderA but will be added to the hypervisor that is part of ProviderB and stay in a Pending (Down) state.


Version-Release number of selected component (if applicable):
==============================================================
aeolus-all-0.8.0-12.el6.noarch
aeolus-conductor-0.8.0-12.el6.noarch
aeolus-conductor-daemons-0.8.0-12.el6.noarch
aeolus-conductor-doc-0.8.0-12.el6.noarch
aeolus-configure-2.5.0-8.el6.noarch
deltacloud-core-0.5.0-4.rc1.el6.noarch
deltacloud-core-ec2-0.5.0-4.rc1.el6.noarch
deltacloud-core-rhevm-0.5.0-4.rc1.el6.noarch
deltacloud-core-vsphere-0.5.0-4.rc1.el6.noarch
rubygem-aeolus-cli-0.3.0-5.el6.noarch
rubygem-aeolus-image-0.3.0-4.el6.noarch
rubygem-deltacloud-client-0.4.0-3.el6.noarch



How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Tomas Hrcka 2012-02-01 13:18:47 UTC 
There is a validation and it is working for me as expected. Can you retest on latest version of aeolus?
Comment 2 Dave Johnson 2012-02-22 21:59:06 UTC 
Seems better now in aeolus-conductor-0.8.0-33.el6.noarch
Comment 3 errata-xmlrpc 2012-05-15 22:25:21 UTC 
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.

http://rhn.redhat.com/errata/RHEA-2012-0583.html