Hide Forgot
Created attachment 550029 [details] name Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Multiple images with same name can be created . 2. Shouldn't there be validation on image name to be unique ? 3. Name comes from template . <template> <name>RHEL_westest01</name> <os> <name>RHEL-6</name> <version>1</version> <arch>x86_64</arch> <rootpw>dog8code</rootpw> <install type="url"> <url>http://download.devel.redhat.com/released/RHEL-6-Server/6.1/x86_64/os/</url> </install> </os> <description>RHEL61 x86_64 </description> </template> If i use the same template again and again it creates multiple images with same name as in screenshot. 4. We can use the "Name" field while creating image which is not mandatory and is of no use now . Actual results: Expected results: Additional info: rpm -qa|grep aeolus aeolus-conductor-doc-0.8.0-0.20111222233342gitd98cb57.el6.noarch rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.noarch rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.noarch aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-configure-2.5.0-0.20111222173430git17b704a.el6.noarch aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch
Created attachment 550030 [details] same_name
It's not simple to add unique name validation: - image is saved only in warehouse, adding uniquness check means fetching&parsing of all images in warehouse ('name' is saved only in xml body, not as metadata - image object can be created both by imagefactory or aeolus-image-rubygem lib (used by cli and UI), none of them checks uniqueness ATM
adding to ce-sprint-next
adding to ce-sprint
removing ce-sprint-next tracker
Whilst it is possible to have identically named images, they're stll uniquely identifiable by the UUID, which is the handle by which they are referenced in deployable definitions etc. Given the complexity of the underlying changes required to change current behaviour, as described in Jan's comment above, the current behaviour won't change in the scope of 1.0
ack.. You could check for unique template names for just the WEBUI.. but a user could still create a dupe via the cli.. pushing the check for uniqueness to warehouse.. which is a whole other ball of wax Lets revisit this next release... closing this.. things will change too much I suspect to bother leaving it open