This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2167378 - The satellite-change-hostname command asks to re-register the clients using old deprecated registration method
Summary: The satellite-change-hostname command asks to re-register the clients using o...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Griffin Sullivan
QA Contact: Satellite QE Team
URL:
Whiteboard:
: 2224026 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-06 13:03 UTC by Jayant Bhatia
Modified: 2024-06-06 16:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 16:06:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-17402 0 None Migrated None 2024-06-06 16:06:03 UTC

Description Jayant Bhatia 2023-02-06 13:03:52 UTC 
Description of problem:
After satellite-change-hostname has been completed successfully, at the end, the same command asks to re-register the client using old deprecated method.

Version-Release number of selected component (if applicable): satellite-6.13.0-4.el8sat.noarch


How reproducible: Always


Steps to Reproduce:
1. Run below command on Satellite machine to change its hostname.

       # satellite-change-hostname new_sat_fqdn --username admin --password redhat

2. Allow the command to execute successfully.


Actual results: The command throws below output on screen at the end.

~~~~~~~~~~
**** Hostname change complete! ****
IMPORTANT:

  You will have to install the new bootstrap rpm and reregister all clients and Capsules with subscription-manager
  (update organization and environment arguments appropriately):

  yum remove -y katello-ca-consumer*
  rpm -Uvh http://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm
  subscription-manager register --org="Default_Organization" --environment="Library" --force

  Then reattach subscriptions to the client(s) and run:

  subscription-manager refresh
  yum repolist


  On all Capsules, you will need to re-run the satellite-installer with this command:

  satellite-installer --foreman-proxy-foreman-base-url https://satellite.example.com \
                                  --foreman-proxy-trusted-hosts satellite.example.com

  If Puppet is enabled on the Capsule, add the following to the installer command:

                                  --puppet-server-foreman-url https://satellite.example.com

  Short hostnames have not been updated, please update those manually.
~~~~~~~~~~

Here we are asking user to manually remove the katello-ca-consumer package, install the new katello-ca-consumer package and then re-run 'subscription-manager register' command which is a deprecated method now.


Expected results: Instead of above method, we should ask user to generate curl command using Global Registration Template method and use it to re-register the client machine back with Satellite.


Additional info: "Chapter 3. Registering Hosts to Satellite" in following documentation: https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/managing_hosts/index?lb_target=preview&check_logged_in=1
Comment 3 Eric Helms 2023-07-27 13:25:31 UTC 
*** Bug 2224026 has been marked as a duplicate of this bug. ***
Comment 7 Eric Helms 2024-06-06 16:06:04 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.