Bug 719383

Summary: new deployable missing check on hw profile names
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: aeolus-conductorAssignee: Jan Provaznik <jprovazn>
Status: CLOSED CURRENTRELEASE QA Contact: Dave Johnson <dajohnso>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.3.1CC: dajohnso, deltacloud-maint, jprovazn, slinaber, ssachdev, whayutin
Target Milestone: alpha   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://<ip_addr>/conductor/deployments/new
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-08 13:47:53 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 2011-07-06 16:27:03 UTC 
Description of problem:

Playing around with deployables, I found that dropping a character from either the image id or the build id is flagged as an error prior to adding the deployable, stating that the particular id could not be found.  But, if you do this with the hw profile name, it is not flagged as an error until you actually start the deployable which is a little late, especially in multi-assembly deployments.


Version-Release number of selected component (if applicable):
aeolus-configure-2.0.1-0.el6.20110628141215gitb8aaf85.noarch
rubygem-aeolus-cli-0.0.1-1.el6.20110701204941gitd66e27c.noarch
aeolus-conductor-doc-0.3.0-0.el6.20110701204941gitd66e27c.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110701204941gitd66e27c.noarch
aeolus-all-0.3.0-0.el6.20110701204941gitd66e27c.noarch
aeolus-conductor-0.3.0-0.el6.20110701204941gitd66e27c.noarch


Steps to Reproduce:
1.  Create a deployable xml with a bad build id
2.  Create a new deployment for a pool specifying xml from step 1
3.  Notice an error is thrown on a bad id and the deployable is not added
4.  Create a deployable xml and specify a non-existent hw profile
5.  Create a new deployment for a pool specifying xml from step 4
6.  Notice that the bad hw profile is not flagged as a error and you can proceed to starting the deployment.
  
Actual results:


Expected results:


Additional info:
Comment 1 Steve Linabery 2011-07-18 16:27:07 UTC 
4cd3a5eec2639018d8598ebbfc836dd77e1f6635 is in rpm on fp testing
Comment 2 Dave Johnson 2011-07-20 19:24:30 UTC 
Looks good with the following rpms:

[root@ibm-x3650-04 ~]# rpm -qa | grep aeolus
rubygem-aeolus-image-0.0.1-1.el6.20110719153543gitd39221e.noarch
aeolus-conductor-0.3.0-0.el6.20110719153543gitd39221e.noarch
aeolus-all-0.3.0-0.el6.20110719153543gitd39221e.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110719153543gitd39221e.noarch
aeolus-configure-2.0.1-1.el6.20110719144238git5ffa131.noarch
aeolus-conductor-doc-0.3.0-0.el6.20110719153543gitd39221e.noarch
Comment 3 wes hayutin 2011-08-01 19:53:53 UTC 
release pending...
Comment 4 wes hayutin 2011-08-01 19:55:52 UTC 
release pending...
Comment 6 wes hayutin 2011-12-08 13:47:53 UTC 
perm close