Created attachment 593172 [details] Screenshot of misaligned parameters. Description of problem: With Aeolus 0.10.2 on F16 (official upstream rpms), columns in the "Launch" page for showing Deployable parameters are misaligned. See attached screenshot for details. Version-Release number of selected component (if applicable): $ rpm -qa|grep -i aeolus aeolus-all-0.10.2-1.fc16.noarch aeolus-conductor-0.10.2-1.fc16.noarch aeolus-conductor-daemons-0.10.2-1.fc16.noarch aeolus-configure-2.6.0-1.fc16.noarch aeolus-conductor-devel-0.10.2-1.fc16.noarch aeolus-conductor-doc-0.10.2-1.fc16.noarch rubygem-aeolus-image-0.5.0-1.fc16.noarch rubygem-aeolus-cli-0.5.0-1.fc16.noarch $ rpm -qa|grep -i deltacloud deltacloud-core-0.5.0-2.fc16.noarch deltacloud-core-vsphere-0.5.0-2.fc16.noarch rubygem-deltacloud-client-0.5.0-1.fc16.noarch deltacloud-core-rhevm-0.5.0-2.fc16.noarch deltacloud-core-ec2-0.5.0-2.fc16.noarch How reproducible: Every time. Steps to Reproduce: 1. Define a deployable with several parameters. Dan Radez's wordpress.xml for example. 2. Click the Aeolus "Launch" button to launch the deployable. 3. The screen which appears, asking for parameter details, has the problem. Misaligned columns, descriptions, etc. Expected results: Should be visually lined up, so users can tell what belongs to what.
Bumping the priority of this, as it break screencasting. :(
Fixing patch was pushed to the master branch with commit # eb0f8f7745d5f41e81c12877d848282e399a373d Please verify it
Deployable parameters, in the Aeolus "Launch" screen, are aligned now. see attached scrrenshot. verified: rpm -qa | grep aeolus rubygem-aeolus-image-0.3.0-12.el6.noarch rubygem-aeolus-cli-0.7.2-1.el6cf.noarch aeolus-conductor-doc-0.13.14-1.el6cf.noarch aeolus-configure-2.8.7-1.el6cf.noarch aeolus-all-0.13.14-1.el6cf.noarch aeolus-conductor-0.13.14-1.el6cf.noarch aeolus-conductor-daemons-0.13.14-1.el6cf.noarch
Created attachment 618119 [details] alignment
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-1516.html