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 1481289 - katello-change-hostname should ask for credentials if not provided
Summary: katello-change-hostname should ask for credentials if not provided
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: John Mitsch
QA Contact: Jan Hutař
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-14 13:44 UTC by Peter Ondrejka
Modified: 2019-09-25 21:23 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:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 20805 0 None None None 2017-08-30 12:41:58 UTC

Description Peter Ondrejka 2017-08-14 13:44:19 UTC 
Description of problem:

Currently when changing hostname without specifying username and password:

# katello-change-hostname -y newname
/usr/sbin/katello-change-hostname:191:in `precheck': undefined local variable or method `opt_parser' for main:Object (NameError)
	from /usr/sbin/katello-change-hostname:212:in `<main>'

or

# ]# katello-change-hostname  newname
***WARNING*** This script will modify your system. You will need to re-register any satellite clients registered to this system after script completion. Foreman Proxies will have to be re-registered and reinstalled. If you are using custom certificates, you will have to run the satellite-installer again with custom certificate options after this script completes. Have you taken the necessary precautions (backups, snapshots, etc...) and want to proceed with changing your hostname? 
 [y/n]:/usr/sbin/katello-change-hostname:191:in `precheck': undefined local variable or method `opt_parser' for main:Object (NameError)
	from /usr/sbin/katello-change-hostname:212:in `<main>'


Version-Release number of selected component (if applicable):
Satellite 6.3 snap 11

Expected results:
Some user-friendly message asking user to pass -u and -p options. Possibly, in the interactive mode katello-change-hostname could ask for credentials just after the [y/n] dialog
Comment 2 Mike McCune 2017-08-15 17:31:44 UTC 
John, is this something needed or helpful to katello-change-hostname?
Comment 3 John Mitsch 2017-08-28 13:53:23 UTC 
Mike, yes this would be helpful, I'll work on this
Comment 4 John Mitsch 2017-08-30 12:41:56 UTC 
Created redmine issue http://projects.theforeman.org/issues/20805 from this bug
Comment 5 Satellite Program 2017-08-30 16:11:43 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20805 has been resolved.
Comment 9 Bryan Kearney 2018-02-21 17:10:45 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.