Bug 1493472

Summary:	katello-change-hostname's behavior before installing capsule
Product:	Red Hat Satellite	Reporter:	Peter Ondrejka <pondrejk>
Component:	Packaging	Assignee:	Evgeni Golov <egolov>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.2.12	CC:	chrobert, egolov
Target Milestone:	6.4.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-16 19:35:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Peter Ondrejka 2017-09-20 09:35:18 UTC

Description of problem:

In case you have the satellite-capsule package already installed but you didn't install the capsule yet with satellite-installer, using katello-change-hostname will fail even when trying to see help:

]# katello-change-hostname -h
/usr/bin/katello-change-hostname:40:in `readlink': No such file or directory - /etc/foreman-installer/scenarios.d/last_scenario.yaml (Errno::ENOENT)

Some message informing user about the problem would be nice here.

Version-Release number of selected component (if applicable):

katello-capsule-3.0.0-25.el6sat.noarch

Comment 1 Evgeni Golov 2017-09-20 09:50:39 UTC

Created redmine issue http://projects.theforeman.org/issues/21028 from this bug

Comment 3 Satellite Program 2018-01-05 11:09:25 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21028 has been resolved.

Comment 4 Peter Ondrejka 2018-07-09 11:33:25 UTC

verified on sat 6.4 capsule and maintain snap 11, help is now displayed as expected, when attempting to run hostname change, a proper help message is displayed (This utility can't run on a non-katello system.)

Comment 5 Bryan Kearney 2018-10-16 19:35:31 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:2927