Description of problem: Version-Release number of selected component (if applicable): Katello Version: 1.1.12-1.git.188.8955f22.el6_3 How reproducible: Steps to Reproduce: 1. Go to orgs, click New Organization 2. Fill in a name "foo" 3. Actual results: now what? Save button is disabled, user has no clue why or what to do next Expected results: Save button is enabled. Additional info: The purpose of this appears to be to autogenerate a label. The app cannot wait for the focus to change to do this, it has to be a keypress event or something "sooner" than waiting for the user to be confused and click somewhere else.
In order to resolve this one, we'll enable the save button and auto-generate a label if the user clicks save without a labeling having been specified. In the success notice, we'll include text similar to: Organization abc created. Note: Since a label was not been provided, a label of 'abc' has been automatically assigned. If you would like a different label, please delete the organization and recreate it with the desired label.
katello github pull request: https://github.com/Katello/katello/pull/759 katello github commit: 4d860bf8187600f3e9196b6d1fceefe2348a9788
@Brad: the save button was enabled before I even typed any values into the form. Is this the designed behavior? I saw two distinct behaviors while verifying this: 1. I created organization Bar with default environment DEV. When I clicked the save button I got the following notifications: * "Organization 'Bar' was created." [GREEN in color] * "A label was not provided during environment creation; therefore, a label of 'DEV' was automatically assigned. If you would like a different label, please delete the environment and recreate it with the desired label." [GREY in color] 2. I created the Foo organization but did not provide a default environment. When I clicked the save button I got the following notifications: * "Organization 'Foo' was created." [GREEN in color] * "Click on 'Add Environment' to create the first environment " [GREY in color] Though it seems that behavior (1) does follow the explanation from comment #2, imo it does not match the expected behavior for (2). I'll be perfectly fine with filing a separate BZ and ask for (2) to also display the same message as (1) informing of the default label that was created, just for standardization of the web ui experience. I will wait for your comment/suggestion before closing this.
Verified using: * candlepin-0.7.8-1.el6cf.noarch * candlepin-selinux-0.7.8-1.el6cf.noarch * candlepin-tomcat6-0.7.8-1.el6cf.noarch * katello-1.1.12-12.el6cf.noarch * katello-all-1.1.12-12.el6cf.noarch * katello-candlepin-cert-key-pair-1.0-1.noarch * katello-certs-tools-1.1.8-1.el6cf.noarch * katello-cli-1.1.8-6.el6cf.noarch * katello-cli-common-1.1.8-6.el6cf.noarch * katello-common-1.1.12-12.el6cf.noarch * katello-configure-1.1.9-6.el6cf.noarch * katello-glue-candlepin-1.1.12-12.el6cf.noarch * katello-glue-pulp-1.1.12-12.el6cf.noarch * katello-qpid-broker-key-pair-1.0-1.noarch * katello-qpid-client-key-pair-1.0-1.noarch * katello-selinux-1.1.1-1.el6cf.noarch * pulp-1.1.12-1.el6cf.noarch * pulp-common-1.1.12-1.el6cf.noarch * pulp-selinux-server-1.1.12-1.el6cf.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/RHSA-2012-1543.html
getting rid of 6.0.0 version since that doesn't exist