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.
DescriptionJitendra Yejare
2020-01-10 10:46:59 UTC
Description of problem:
satellite-change-hostname isnt updating the dynamic dns file "var/named/dynamic/db.{dns}"
Version-Release number of selected component (if applicable):
Satellite 6.7 snap 1 to 7, Satellite 6.6.z
How reproducible:
Always
Steps to Reproduce:
1. Install satellite 6.7 that has hostname say 'x'.
2. Run satellite-change-hostname with different hostname say 'y'.
3. Check the hostname is changed in the dynamic DNS file of the satellite. (i.e "var/named/dynamic/db.{dns}")
Actual results:
1. The new hostname entry is not updated in dynamic dns file.
2. This resulted in PXE Discovery to fail as the discovered host is not able to find satellite with the hostname.
Expected results:
1. The new hostname entry should be updated in dynamic dns file.
2. This PXE Discovery should pass and discovered host should be able to find satellite with the hostname.
Additional info:
Discovery post satellite-change-hostname was working earlier in Satellite 6.6 GA and we can say its now a regression(in 6.6.z and 6.7) but I have never checked satellite-change-hostname does change the entry or not.
Hi Jitendra,
On Sat 6.7 snaps, does PXE discovery succeed *before* you change the hostname?
Is satellite-change-hostname the only method being used to change the Satellite's hostname?
Are you able to provide a reproducer / more detailed reproduction steps / more details about the error/failure condition?
Thanks
(In reply to Jeremy from comment #4)
> Hi Jitendra,
>
> On Sat 6.7 snaps, does PXE discovery succeed *before* you change the
> hostname?
Yes, the Discovery works on a fresh box (before changing the hostname, but I didn't explicitly check on the machine I reproduced this issue).
> Is satellite-change-hostname the only method being used to change the
> Satellite's hostname?
Yes, that's the only and official way of changing the satellite hostname.
> Are you able to provide a reproducer / more detailed reproduction steps /
> more details about the error/failure condition?
Yes, I can provide you the reproducer system and steps, ping me on the #satellite6-qe channel.
> Thanks
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-2020:1454
Description of problem: satellite-change-hostname isnt updating the dynamic dns file "var/named/dynamic/db.{dns}" Version-Release number of selected component (if applicable): Satellite 6.7 snap 1 to 7, Satellite 6.6.z How reproducible: Always Steps to Reproduce: 1. Install satellite 6.7 that has hostname say 'x'. 2. Run satellite-change-hostname with different hostname say 'y'. 3. Check the hostname is changed in the dynamic DNS file of the satellite. (i.e "var/named/dynamic/db.{dns}") Actual results: 1. The new hostname entry is not updated in dynamic dns file. 2. This resulted in PXE Discovery to fail as the discovered host is not able to find satellite with the hostname. Expected results: 1. The new hostname entry should be updated in dynamic dns file. 2. This PXE Discovery should pass and discovered host should be able to find satellite with the hostname. Additional info: Discovery post satellite-change-hostname was working earlier in Satellite 6.6 GA and we can say its now a regression(in 6.6.z and 6.7) but I have never checked satellite-change-hostname does change the entry or not.