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 1506588 - `satellite-change-hostname` advises to use "foreman-installer --capsule-parent-fqdn ..." on capsules, but that option does not exist
Summary: `satellite-change-hostname` advises to use "foreman-installer --capsule-paren...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: John Mitsch
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-26 11:19 UTC by Jan Hutař
Modified: 2019-09-26 16:11 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 17:10:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 21492 0 None None None 2017-10-27 14:41:48 UTC

Description Jan Hutař 2017-10-26 11:19:48 UTC 
Description of problem:
`satellite-change-hostname` advises to use "foreman-installer --capsule-parent-fqdn ..." on capsules, but that option does not exist


Version-Release number of selected component (if applicable):
satellite-6.3.0-21.0.beta.el7sat.noarch
satellite-common-6.3.0-21.0.beta.el7sat.noarch


How reproducible:
always


Steps to Reproduce:
1. Rename satellite which have some external capsule
   [root@sat630 ~]# satellite-change-hostname sat630-fake.example.com -u admin --password changeme
2. Use steps it prints on the capsule (first reregister and then rerun installer on capsule)


Actual results:
[root@sat630 ~]# satellite-change-hostname sat630-fake.example.com -u admin --password changeme
[...]
**** Hostname change complete! **** 
IMPORTANT:

  If you want to use custom certificates, re-run the foreman-installer with custom certificate options.

  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://sat630-fake.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 foreman-installer with this command:

  foreman-installer --capsule-parent-fqdn sat630-fake.example.com \
                                  --foreman-proxy-foreman-base-url  https://sat630-fake.example.com \
                                  --foreman-proxy-trusted-hosts sat630-fake.example.com

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

Now on capsule after reregistration:

[root@caps630 ~]# foreman-installer --capsule-parent-fqdn sat630-fake.example.com \
>                                   --foreman-proxy-foreman-base-url  https://sat630-fake.example.com \
>                                   --foreman-proxy-trusted-hosts sat630-fake.example.com
ERROR: Unrecognised option '--capsule-parent-fqdn'


Expected results:
When you use "--foreman-proxy-content-parent-fqdn" instead of "--capsule-parent-fqdn" it seems to work.
Comment 3 John Mitsch 2017-10-27 14:41:46 UTC 
Connecting redmine issue http://projects.theforeman.org/issues/21492 from this bug
Comment 4 Peter Ondrejka 2017-10-31 09:13:24 UTC 
Well, not a blocker but I'd rather see satellite-installer instead of foreman-installer in the success message
Comment 5 Brad Buckingham 2017-10-31 13:07:33 UTC 
Can we create a second bug for the issue raised by comment 4?  I agree it also needs to be addressed at least by GA; however, it is separate from the error that caused the original failure.
Comment 6 Peter Ondrejka 2017-10-31 13:15:47 UTC 
ok, here: https://bugzilla.redhat.com/show_bug.cgi?id=1507925
Comment 7 Brad Buckingham 2017-10-31 14:17:29 UTC 
Thanks Peter!
Comment 8 Bryan Kearney 2018-02-21 16:44:41 UTC 
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-2018:0336
Comment 9 Bryan Kearney 2018-02-21 17:10:53 UTC 
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-2018:0336
Note You need to log in before you can comment on or make changes to this bug.