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 900674[details]
Logs from production.log
Description of problem:
I was trying to update the host-collection limit to blank and was expecting a validation error but when I set a blank value, a long exception was raised under production.log. Please see the attachement for logs.
[root@dhcp207-55 ~]# hammer host-collection update --id 3 --max-content-hosts ""
Could not update the the host collection:
comparison of Fixnum with nil failed
Version-Release number of selected component (if applicable):
sat6 beta snap7 compose2 (Satellite-6.0.3-RHEL-6-20140528.4)
How reproducible:
always
Steps to Reproduce:
1. set --max-content-hosts to blank ("")
2.
3.
Actual results:
Expected results:
there shouldn't be ISE in production.log and a proper validation error should be raised.
Additional info:
Comment 1RHEL Program Management
2014-05-30 09:27:31 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.
Verified with snap10 compose2.
Looks like issue has been fixed now. I'm not able to reproduce this issue with latest compose.
[root@dhcp201-161 ~]# hammer host-collection update --id 1 --max-content-hosts " "
Could not update the the host collection:
Validation failed: Content host limit must be a positive integer value.
so moving this verified.
Created attachment 900674 [details] Logs from production.log Description of problem: I was trying to update the host-collection limit to blank and was expecting a validation error but when I set a blank value, a long exception was raised under production.log. Please see the attachement for logs. [root@dhcp207-55 ~]# hammer host-collection update --id 3 --max-content-hosts "" Could not update the the host collection: comparison of Fixnum with nil failed Version-Release number of selected component (if applicable): sat6 beta snap7 compose2 (Satellite-6.0.3-RHEL-6-20140528.4) How reproducible: always Steps to Reproduce: 1. set --max-content-hosts to blank ("") 2. 3. Actual results: Expected results: there shouldn't be ISE in production.log and a proper validation error should be raised. Additional info: