Hide Forgot
Description of problem: We should validate 1. a name has been entered 2. a deployable has been selected once those two are validated, then enable the "next" button [root@qeblade30 ~]# rpm -qa | grep aeolus rubygem-aeolus-cli-0.3.0-7.el6.noarch aeolus-conductor-doc-0.8.0-16.el6.noarch aeolus-configure-2.5.0-11.el6.noarch rubygem-aeolus-image-0.3.0-6.el6.noarch aeolus-all-0.8.0-16.el6.noarch aeolus-conductor-0.8.0-16.el6.noarch aeolus-conductor-daemons-0.8.0-16.el6.noarch see screenshots
Created attachment 558648 [details] ss
Created attachment 558649 [details] ss2
it look like duplicate to this https://bugzilla.redhat.com/show_bug.cgi?id=770902
*** Bug 770902 has been marked as a duplicate of this bug. ***
fixed in git commit 8088844d7da43b78d817f71a49ed86d55898076b
8088844 84c3d5e in aeolus-conductor-0.8.0-27
fails.. the name should be validated on the page in comment #1 [root@qeblade31 yum.repos.d]# rpm -qa | grep aeolus aeolus-conductor-daemons-0.8.0-35.el6.noarch rubygem-aeolus-image-0.3.0-9.el6.noarch rubygem-aeolus-cli-0.3.0-10.el6.noarch aeolus-all-0.8.0-35.el6.noarch aeolus-conductor-0.8.0-35.el6.noarch aeolus-conductor-doc-0.8.0-35.el6.noarch aeolus-configure-2.5.0-15.el6.noarch
I just tested this on aeolus-conductor-0.8.3-1 since that's what I had available. And my observation is same as in comment #7. If the button is not supposed to be enabled until both 1. a name has been entered 2. a deployable has been selected then that is not happening. The next button is enabled upon initial page load.
Looks like 389c931573964a1f52f68e7f7363794d5725c20d addresses this BZ but it was not pulled over to product. Will pick this over to product and incorporate in a new build once the outage on the system hosting the git repo has ended.
Observed that 1. "Next" button was enabled, when only "Name" was given, but on click of "Next" button it displayed appropriate error message (PFA:no_app.png) 2. Also observed that when, a. Click on "New Application" b. Just click on "name" text field c. And now click on any where on the page d. keep Default selected Application blueprint Observed that "Next" button was enabled, and in the next page when "launch" button was clicked only it is displayed the error (PFA: error.png) on: rpm -qa | grep aeolus aeolus-configure-2.5.3-1.el6.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch aeolus-conductor-doc-0.8.12-1.el6_2.noarch aeolus-conductor-daemons-0.8.12-1.el6_2.noarch aeolus-all-0.8.12-1.el6_2.noarch aeolus-conductor-0.8.12-1.el6_2.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch
Created attachment 578549 [details] no_app
Created attachment 578550 [details] error
Moving status to assigned , due to observation #2(in Comment 11),i feel it is expected to valid the "Name" field and then enable the "Next" button.
Patch from thrcka here: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-April/010052.html Note that per IRC discussion, this issue is not actually a blocker; only the original issue was. I ACKed and pushed to master: bc828ab376a15ae9ac7ae3bc0c26d9f3e790a6f7 Moving back to MODIFIED.
Cloning the bug to take care of the following issue.. Will mark the original as verified.. > > 2. Also observed that when, > a. Click on "New Application" > b. Just click on "name" text field > c. And now click on any where on the page > d. keep Default selected Application blueprint > > Observed that "Next" button was enabled, and in the next page when "launch" > button was clicked only it is displayed the error (PFA: error.png) > > on: > > rpm -qa | grep aeolus > aeolus-configure-2.5.3-1.el6.noarch > rubygem-aeolus-cli-0.3.1-1.el6.noarch > aeolus-conductor-doc-0.8.12-1.el6_2.noarch > aeolus-conductor-daemons-0.8.12-1.el6_2.noarch > aeolus-all-0.8.12-1.el6_2.noarch > aeolus-conductor-0.8.12-1.el6_2.noarch > rubygem-aeolus-image-0.3.0-12.el6.noarch
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