Created attachment 578442 [details] one_letter_no_activation The event that detects user inputs is behaving improperly for the instance launch-time parameter fields. By entering a single character for the parameter value, the "Finalize" button stays grayed out. (In screenshot) By entering two characters for the parameter value, the "Finalize" button activates. (In screenshot) Then by removing the two character from the parameter values, the "Finalize" button stays activated. (In screenshot) In addition, pasting a value into the parameter field also does not activate the "Finalize" button.
Created attachment 578443 [details] two_letter_activation
Created attachment 578444 [details] no_letter_activation
[root@qeblade30 ~]# rpm -qa | grep "aeolus" aeolus-conductor-doc-0.8.10-1.el6_2.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-all-0.8.10-1.el6_2.noarch aeolus-conductor-daemons-0.8.10-1.el6_2.noarch aeolus-configure-2.5.3-1.el6.noarch aeolus-conductor-0.8.10-1.el6_2.noarch
Patch on list: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-April/010029.html
Pushed f94a89a84fe53770f2e708c60728d11f589cb124 to master.
And on 1.0-product, e451adcde460142fc823b81b5b0c39b49aecc18d
This is working afaict.. I'll move this to verified tomorrow.
(In reply to comment #0) > Created attachment 578442 [details] > one_letter_no_activation > > The event that detects user inputs is behaving improperly for the instance > launch-time parameter fields. > > By entering a single character for the parameter value, the "Finalize" button > stays grayed out. (In screenshot) fixed > > By entering two characters for the parameter value, the "Finalize" button > activates. (In screenshot) same.. working > > Then by removing the two character from the parameter values, the "Finalize" > button stays activated. (In screenshot) fixed > > In addition, pasting a value into the parameter field also does not activate > the "Finalize" button. paste fixed [root@qeblade30 ~]# rpm -qa | grep aeolus aeolus-configure-2.5.3-1.el6.noarch aeolus-conductor-0.8.13-1.el6_2.noarch aeolus-all-0.8.13-1.el6_2.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-conductor-daemons-0.8.13-1.el6_2.noarch aeolus-conductor-doc-0.8.13-1.el6_2.noarch [root@qeblade30 ~]#
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