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 1296908[details]
error on discovered host console when both values set to "empty"
Description of problem:
In 6.3 snap5, we see some new discovery settings like:
hostname_facts
hostname_prefix
If we set both values to empty then discovery will fail w/ error:
Exception: Invalid_facts: hash doesn't contain valid value for any of the facts in discovery_hostname
So as per above error, user shouldn't allow to set any of the above setting as "empty", ideally, hostname_facts shouldn't set as empty. On setting it empty, user should get an error message.
Version-Release number of selected component (if applicable):
sat6.3 beta snap5
How reproducible:
always
Steps to Reproduce:
1. go to settings -> discovered
2. set empty value for both Hostname_prefix and Hostname_facts
3.
Actual results:
as expected host discovery failed w/ error:
Exception: Invalid_facts: hash doesn't contain valid value for any of the facts in discovery_hostname
Expected results:
User should not be allowed to change set "Hostname_facts" as empty" and error should be raised.
Additional info:
Similar issue needs to be fixed in hammer.
]# hammer -u admin -p changeme settings set --name discovery_hostname --value ""
Setting [discovery_hostname] updated to []
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
VERIFIED
on sat6.9.0-14.0
the aforementioned facts can't be blank now.
trying to change it via UI -> results in 422.
using CLI (API):
[root@qe-sat69-rhel7-tier3 ~]# hammer setting set --name discovery_hostname --value ""
Could not update the setting:
Value can't be blank
[root@qe-sat69-rhel7-tier3 ~]# hammer setting set --name discovery_prefix --value ""
Could not update the setting:
Value can't be blank
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 (Moderate: Satellite 6.9 Release), 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-2021:1313
Created attachment 1296908 [details] error on discovered host console when both values set to "empty" Description of problem: In 6.3 snap5, we see some new discovery settings like: hostname_facts hostname_prefix If we set both values to empty then discovery will fail w/ error: Exception: Invalid_facts: hash doesn't contain valid value for any of the facts in discovery_hostname So as per above error, user shouldn't allow to set any of the above setting as "empty", ideally, hostname_facts shouldn't set as empty. On setting it empty, user should get an error message. Version-Release number of selected component (if applicable): sat6.3 beta snap5 How reproducible: always Steps to Reproduce: 1. go to settings -> discovered 2. set empty value for both Hostname_prefix and Hostname_facts 3. Actual results: as expected host discovery failed w/ error: Exception: Invalid_facts: hash doesn't contain valid value for any of the facts in discovery_hostname Expected results: User should not be allowed to change set "Hostname_facts" as empty" and error should be raised. Additional info: