Bug 790434

Summary: Unique Instance name validation required for multi assembly deployment
Product: [Retired] CloudForms Cloud Engine Reporter: Shveta <ssachdev>
Component: aeolus-conductorAssignee: Shveta <ssachdev>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, athomas, deltacloud-maint, jguiditt, mtaylor, ssachdev
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: v0.8.0-35 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-15 22:36:49 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
multiassembly
none
unique_assembly_name none

Description Shveta 2012-02-14 14:31:02 UTC
Created attachment 561915 [details]
multiassembly

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Built and created a multi assembly deployment with 4 assemblies
2. with same assembly name (didn't get any validation message for unique name )
3. Launched instance , it only launched one instance and for rest it said
"Name already taken"
  

========================deployable=======================

<deployable name="shv_dep">
<description>This is an example deployment</description>
<assemblies>
<assembly name="frontend" hwp="hwp1">
<image id="7fe5fcc2-e88c-45e2-b3c0-69d750a4a1f0" build="766af2d1-74e4-47fa-9a23-ee580dc3e721">
</image>
</assembly>
<assembly name="frontend" hwp="hwp1">
<image id="dbc58cc4-b45a-44f8-87e4-a5b19becdcfc" build="78c5b013-8186-4651-8405-7a49ab3836bc">
</image>
</assembly>
<assembly name="frontend" hwp="hwp1">
<image id="16ccfe53-f4ec-485a-9763-f2694974d24e" build="7b4a7f18-df91-4388-994c-010ad440f1b4">
</image>
</assembly>
<assembly name="frontend" hwp="hwp1">
<image id="184e2fc8-b2bc-4202-a0de-eb6d5450cbda" build="893d75c7-d6bb-4377-9c30-399556f97583">
</image>
</assembly>
</assemblies>
</deployable>
Actual results:


Expected results:


Additional info:

rpm -qa|grep aeolus
aeolus-conductor-doc-0.8.0-26.el6.noarch
rubygem-aeolus-cli-0.3.0-8.el6.noarch
rubygem-aeolus-image-0.3.0-7.el6.noarch
aeolus-configure-2.5.0-13.el6.noarch
aeolus-conductor-daemons-0.8.0-26.el6.noarch
aeolus-conductor-0.8.0-26.el6.noarch
aeolus-all-0.8.0-26.el6.noarch

Comment 1 wes hayutin 2012-02-14 22:37:03 UTC
hrm.. I'd like to see this fixed for sure.. the word is multi assemblies applications are not fully supported.. marking priority medium

Comment 2 Jason Guiditta 2012-02-22 21:03:54 UTC
pushed to master:

commit 81c1888d110691081272abc8ef114dd816d09e71
Author: Martyn Taylor <mtaylor>
Date:   Thu Feb 16 10:53:44 2012 +0000

    BZ#790434 Check unique assembly names on deployable xml
    
    https://bugzilla.redhat.com/show_bug.cgi?id=790434
    
    Minor changed added (Jason Guiditta)

Comment 3 Shveta 2012-02-23 13:15:42 UTC
Created attachment 565300 [details]
unique_assembly_name

Unique name validation done for assemblies

rpm -qa|grep aeolus
aeolus-conductor-0.8.0-35.el6.noarch
rubygem-aeolus-cli-0.3.0-10.el6.noarch
aeolus-conductor-doc-0.8.0-35.el6.noarch
rubygem-aeolus-image-0.3.0-9.el6.noarch
aeolus-all-0.8.0-35.el6.noarch
aeolus-conductor-daemons-0.8.0-35.el6.noarch
aeolus-configure-2.5.0-15.el6.noarch

Comment 4 errata-xmlrpc 2012-05-15 22:36:49 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