Bug 786731 - Deployable get added with invalid build id
Summary: Deployable get added with invalid build id
Keywords:
Status: CLOSED EOL
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-02 09:15 UTC by Aziza Karol
Modified: 2020-03-27 18:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:

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

Description Aziza Karol 2012-02-02 09:15:36 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
I created  deployable xml with valid image id and invalid build id.
deployable got added successfully.

currently only image id is being validated.Build id should also be validated.


Expected results:
validation required for build id also

Additional info:
rpm -qa | grep aeolus
rubygem-aeolus-image-0.3.0-7.el6.noarch
aeolus-conductor-doc-0.8.0-17.el6.noarch
rubygem-aeolus-cli-0.3.0-7.el6.noarch
aeolus-configure-2.5.0-11.el6.noarch
aeolus-conductor-daemons-0.8.0-17.el6.noarch
aeolus-all-0.8.0-17.el6.noarch
aeolus-conductor-0.8.0-17.el6.noarch
Comment 1 wes hayutin 2012-02-02 15:25:44 UTC 
hrm.. agreed.. but only the image id is required.. valid bug, lower priority
Note You need to log in before you can comment on or make changes to this bug.