Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 881287[details]
activation key 'test' with blank system limit
Description of problem:
I was trying to set some value for system limit while creating activation key. Then I just passed blank value under the limit textbox and it was accepted by UI.
Version-Release number of selected component (if applicable):
snap5 compose4* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.7-1.el6_5.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.9.7-1.el6_5.noarch
* candlepin-tomcat6-0.9.7-1.el6_5.noarch
* elasticsearch-0.90.10-4.el6sat.noarch
* foreman-1.5.0.16-1.el6sat.noarch
* foreman-postgresql-1.5.0.16-1.el6sat.noarch
* foreman-proxy-1.5.4-1.el6sat.noarch
* foreman-release-1.5.0-0.develop.201403311342git846433a.el6.noarch
* foreman-selinux-1.5.0-0.develop.el6sat.noarch
* katello-1.5.0-19.el6sat.noarch
* katello-apache-1.0-1.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.5-1.el6sat.noarch
* katello-installer-0.0.32-1.el6sat.noarch
* katello-repos-1.5.1-1.git.14.0868bd1.el6.noarch
* openldap-2.4.23-32.el6_4.1.x86_64
* pulp-katello-plugins-0.2-1.el6sat.noarch
* pulp-nodes-common-2.3.1-0.4.beta.el6sat.noarch
* pulp-nodes-parent-2.3.1-0.4.beta.el6sat.noarch
* pulp-puppet-plugins-2.3.1-0.4.beta.el6sat.noarch
* pulp-rpm-plugins-2.3.1-0.4.beta.el6sat.noarch
* pulp-selinux-2.3.1-0.4.beta.el6sat.noarch
* pulp-server-2.3.1-0.4.beta.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-ldap_fluff-0.2.2-2.el6sat.noarch
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.0.8-1.el6sat.noarch
* rubygem-hammer_cli-0.1.0-5.el6sat.noarch
* rubygem-hammer_cli_foreman-0.1.0-6.el6sat.noarch
* rubygem-hammer_cli_foreman_tasks-0.0.2-2.el6sat.noarch
* rubygem-hammer_cli_katello-0.0.3-12.el6sat.noarch
How reproducible:
always
Steps to Reproduce:
1. create activation key
2. set the system limit to with blank values" "
3. edit with space bar and save it
Actual results:
activation key can be created with unknown/blank value
Expected results:
user shouldn't be allowed to create activation key with unknown/blank system limit. A validation error should be raised.
Additional info:
Comment 1RHEL Program Management
2014-04-01 10:56:14 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
@Tom, I've validated activation-key related stuff with old two-tupane UI.. And If I recall correctly, there we were using '-1' value to set the limit to 'unlimited'. And for blank value, a validation error was raised.
So I was expecting same validation error here with new UI. But looks like we can no more use -1 for setting the limit to unlimited. If setting blank value is a expected behaviour to indicate "unlimited" then I'm fine with it.
Created attachment 881287 [details] activation key 'test' with blank system limit Description of problem: I was trying to set some value for system limit while creating activation key. Then I just passed blank value under the limit textbox and it was accepted by UI. Version-Release number of selected component (if applicable): snap5 compose4* apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.9.7-1.el6_5.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.9.7-1.el6_5.noarch * candlepin-tomcat6-0.9.7-1.el6_5.noarch * elasticsearch-0.90.10-4.el6sat.noarch * foreman-1.5.0.16-1.el6sat.noarch * foreman-postgresql-1.5.0.16-1.el6sat.noarch * foreman-proxy-1.5.4-1.el6sat.noarch * foreman-release-1.5.0-0.develop.201403311342git846433a.el6.noarch * foreman-selinux-1.5.0-0.develop.el6sat.noarch * katello-1.5.0-19.el6sat.noarch * katello-apache-1.0-1.noarch * katello-ca-1.0-1.noarch * katello-certs-tools-1.5.5-1.el6sat.noarch * katello-installer-0.0.32-1.el6sat.noarch * katello-repos-1.5.1-1.git.14.0868bd1.el6.noarch * openldap-2.4.23-32.el6_4.1.x86_64 * pulp-katello-plugins-0.2-1.el6sat.noarch * pulp-nodes-common-2.3.1-0.4.beta.el6sat.noarch * pulp-nodes-parent-2.3.1-0.4.beta.el6sat.noarch * pulp-puppet-plugins-2.3.1-0.4.beta.el6sat.noarch * pulp-rpm-plugins-2.3.1-0.4.beta.el6sat.noarch * pulp-selinux-2.3.1-0.4.beta.el6sat.noarch * pulp-server-2.3.1-0.4.beta.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-ldap_fluff-0.2.2-2.el6sat.noarch * ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch * ruby193-rubygem-runcible-1.0.8-1.el6sat.noarch * rubygem-hammer_cli-0.1.0-5.el6sat.noarch * rubygem-hammer_cli_foreman-0.1.0-6.el6sat.noarch * rubygem-hammer_cli_foreman_tasks-0.0.2-2.el6sat.noarch * rubygem-hammer_cli_katello-0.0.3-12.el6sat.noarch How reproducible: always Steps to Reproduce: 1. create activation key 2. set the system limit to with blank values" " 3. edit with space bar and save it Actual results: activation key can be created with unknown/blank value Expected results: user shouldn't be allowed to create activation key with unknown/blank system limit. A validation error should be raised. Additional info: