Bug 772353 - odd import image workflow can cause: Failed. Response code = 400. Response message = Bad Request.
Summary: odd import image workflow can cause: Failed. Response code = 400. Response me...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Martyn Taylor
QA Contact: wes hayutin
URL: https://qeblade31.rhq.lab.eng.bos.red...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-06 22:18 UTC by wes hayutin
Modified: 2012-05-15 21:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 21:33:29 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0583 0 normal SHIPPED_LIVE new packages: aeolus-conductor 2012-05-15 22:31:59 UTC

Description wes hayutin 2012-01-06 22:18:05 UTC 
Description of problem:
env -> images -> import
1. setup us-east-1 provider/account etc..
2. import RHEL 6.1 ami-31d41658, pick us-east-1 provider
3. name it.. continue
4. customers now have the option to delete the image.. 
either using the "x" or "delete link"
5. get message  "Target Image Deleted"

6. now click build on the ec2 provider

get "Close
Warnings

    Failed. Response code = 400. Response message = Bad Request.
"


IMHO the template should be removed from the system or some other action.  This template is now dead in the water.


[root@qeblade31 ~]# rpm -qa | grep aeolus
aeolus-configure-2.6.0-0.20120105171403gitf0043e8.el6.noarch
aeolus-conductor-doc-0.9.0-0.20120105223209git5e068fe.el6.noarch
rubygem-aeolus-cli-0.4.0-0.20120105171410git2c6b457.el6.noarch
rubygem-arel-2.0.10-0.aeolus.el6.noarch
aeolus-conductor-daemons-0.9.0-0.20120105223209git5e068fe.el6.noarch
rubygem-ZenTest-4.3.3-2.aeolus.el6.noarch
aeolus-conductor-0.9.0-0.20120105223209git5e068fe.el6.noarch
rubygem-aeolus-image-0.4.0-0.20120105171419git8108b42.el6.noarch
aeolus-all-0.9.0-0.20120105223209git5e068fe.el6.noarch
Comment 1 wes hayutin 2012-01-06 22:20:52 UTC 
It also seems you are able to continue in the workflow and build a deployable and try to launch .. where of course things go horribly wrong..
Comment 2 wes hayutin 2012-01-12 16:32:14 UTC 
adding to ce-sprint
Comment 3 wes hayutin 2012-01-12 16:39:15 UTC 
removing ce-sprint-next tracker
Comment 4 Martyn Taylor 2012-01-20 14:43:05 UTC 
This is because imported images have no template associated with them.  Delete through the UI seems to remove the target image only leaving build + image hanging around.  The build button assumes that a valid template is available which in the case of a deleted import is not.

We shall remove any imported images completely.
Comment 5 wes hayutin 2012-01-24 17:24:20 UTC 
try w/ non imported builds
Comment 6 Steve Linabery 2012-01-27 06:35:05 UTC 
345ad8e in aeolus-conductor-0.8.0-13
Comment 8 Shveta 2012-02-07 17:05:04 UTC 
imported image when deleted removes the outline completely from UI.
Hence cannot be built

verified inrpm -qa|grep aeolus
aeolus-conductor-daemons-0.8.0-21.el6.noarch
aeolus-configure-2.5.0-12.el6.noarch
aeolus-conductor-doc-0.8.0-21.el6.noarch
rubygem-aeolus-image-0.3.0-7.el6.noarch
rubygem-aeolus-cli-0.3.0-8.el6.noarch
aeolus-conductor-0.8.0-21.el6.noarch
aeolus-all-0.8.0-21.el6.noarch
Comment 9 errata-xmlrpc 2012-05-15 21:33:29 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
Note You need to log in before you can comment on or make changes to this bug.