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 989128[details]
host limit is not marked as mandatory variable with (*).Also, If I set the host_limit blank, UI raises error "is not a number". which is misleading.
Description of problem:
On 'Discovery_rule page, host limit should be marked as mandatory variable with (*).
If I set the host_limit blank, UI raises error "is not a number".
which is misleading. I set the host_limit blank, so Ideally UI should raise error: Host_limit can't be blank.
In short Host_limit should be consistent with Priority field.
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150205.0
Sat6.1 Beta snap1 compose3
How reproducible:
always
Steps to Reproduce:
1. create a discovery rule with blank host_limit
2.
3.
Actual results:
host limit is not marked as mandatory variable with (*).
If I set the host_limit blank, UI raises error "is not a number".
which is misleading.
Expected results:
Host limit should be marked as mandatory variable with (*).
If I set the host_limit blank, so Ideally UI should raise error: Host_limit can't be blank.
Additional info:
Moving to POST since upstream bug http://projects.theforeman.org/issues/9366 has been closed
-------------
Ori Rabin
Applied in changeset commit:foreman_discovery|4c104cf6b66cf35931153e7d5643f6defd5d96a3.
Verified with snap11/rc5 (Satellite-6.1.0-RHEL-7-20150407.1).
Now if user leaves the host limit blank then UI auto sets the limit to '0' '0'== unlimited. Moving this to verified.
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.
https://access.redhat.com/errata/RHSA-2015:1592
Created attachment 989128 [details] host limit is not marked as mandatory variable with (*).Also, If I set the host_limit blank, UI raises error "is not a number". which is misleading. Description of problem: On 'Discovery_rule page, host limit should be marked as mandatory variable with (*). If I set the host_limit blank, UI raises error "is not a number". which is misleading. I set the host_limit blank, so Ideally UI should raise error: Host_limit can't be blank. In short Host_limit should be consistent with Priority field. Version-Release number of selected component (if applicable): Satellite-6.1.0-RHEL-6-20150205.0 Sat6.1 Beta snap1 compose3 How reproducible: always Steps to Reproduce: 1. create a discovery rule with blank host_limit 2. 3. Actual results: host limit is not marked as mandatory variable with (*). If I set the host_limit blank, UI raises error "is not a number". which is misleading. Expected results: Host limit should be marked as mandatory variable with (*). If I set the host_limit blank, so Ideally UI should raise error: Host_limit can't be blank. Additional info: