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.
Hi Peter, that is surprising to me! On my Snap 15 I don't see any problems after using satellite-change-hostname. I need to learn more about your setup to get to the root of the problem and a box I can log in to that's exhibiting the issue would be ideal. My assumption is that you installed a fresh snap 15, changed the hostname w/ sat-change-hostname and saw the failure in 'hammer ping'. If that's not accurate please share as much detail as possible in terms of how your setup has diverged from my assumption. Thank you
Hey, it was an automation run that was supposed to do what you describe, but looking closer at the results it turns out that candlepin_events were already dead when rename started, so it is the initial health check ping that fails. It could be due to some interference with other tests, will investigate more, but I consider it not a blocker for this bz
Comment 6Sudhir Mallamprabhakara
2021-03-16 03:10:47 UTC
Peter - clone of this BZ is marked Verified. Any updates from your investigation??
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