Description of problem: ========================== when you create a new image without giving it a name on the initial 'file upload' or 'from url' page, the ui allows it to continue. This is okay because it ultimately uses the name from within the template itself as it is a required xml element. However, on the screen that renders after the xml validation, a few sentences display referencing the template/deployable as "". This page should use the same name value found in the template as it is ultimately used to create the template and deployable if selected. The markup and image references in "" were succesfully validated. You may now save the image, and create a deployable. rpm -qaAutomatically make "" deployable. Version-Release number of selected component (if applicable): ================================================================= aeolus-all-0.7.0-4.el6.noarch aeolus-conductor-0.7.0-4.el6.noarch aeolus-conductor-daemons-0.7.0-4.el6.noarch aeolus-conductor-doc-0.7.0-4.el6.noarch aeolus-configure-2.4.0-3.el6.noarch rubygem-aeolus-cli-0.2.0-3.el6.noarch rubygem-aeolus-image-0.2.0-1.el6.noarch
Created attachment 542204 [details] ss
Patch sent to the list: https://fedorahosted.org/pipermail/aeolus-devel/2011-December/007257.html
Fixed in commit: f31b995436facd1c446ba6c5b45d4d676407689a
The image now takes name from deployable . Verified in 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
These bugs are verified, removing from ce-sprint
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