Bug 1968608 - katello-change-hostname assumes answers file location
Summary: katello-change-hostname assumes answers file location
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: satellite-change-hostname
Version: 6.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.10.0
Assignee: satellite6-bugs
QA Contact: Jaroslav Henner
URL:
Whiteboard:
Depends On:
Blocks: 1957813
TreeView+ depends on / blocked
 
Reported: 2021-06-07 16:14 UTC by Ian Ballou
Modified: 2021-11-16 14:11 UTC (History)
4 users (show)

Fixed In Version: katello-4.1.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 14:11:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 32743 0 Normal Ready For Testing katello-change-hostname assumes answers file location 2021-06-07 16:14:31 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:11:51 UTC

Description Ian Ballou 2021-06-07 16:14:30 UTC
The right way to determine the answers file location is to read the scenario file and use the value for :answer_file. However, the script now assumes it's always ${scenario}-answers.yaml which can lead to incorrect behavior.

Comment 1 Ian Ballou 2021-06-07 16:14:34 UTC
Created from redmine issue https://projects.theforeman.org/issues/32743

Comment 2 Ian Ballou 2021-06-07 16:14:35 UTC
Upstream bug assigned to ekohlvan

Comment 3 Bryan Kearney 2021-06-07 20:06:13 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32743 has been resolved.

Comment 4 Ewoud Kohl van Wijngaarden 2021-09-16 13:07:47 UTC
The reproducer is (on the original host), consider the active scenario file (/etc/foreman-installer/scenarios.d/satellite.yaml). That contains a key :answer_file which points (as the name indicates) to an answer file. Move the file and change the scenario file to match.

This is pretty much step 1 and 4 of https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/html/installing_satellite_server_from_a_disconnected_network/installing-satellite-server-disconnected#configuring-satellite-automatically-using-an-answer-file_satellite but instead of copying, move the file. That guarantees it to fail. Having differing answers is also a valid way to verify, but harder to because you can easily miss thing.

Note that that documentation caused the customer to have a problem. In 6.10 it should be gone from the docs, but technically it's still valid and we'll have upgrading users.

Comment 5 Jaroslav Henner 2021-09-20 13:32:23 UTC
I changed the debug level of the foreman-proxy using the modified answer file on new location and then ran `satellite-installer --scenario satellite`. This in turn changed the debug level.

I have no means to test this doesn't break when doing the satellite-change-hostname, but the satellite-change-hostname does call the installer which seem fine, so I consider this as VERIFIED.

Comment 8 errata-xmlrpc 2021-11-16 14:11:38 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 (Moderate: Satellite 6.10 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:4702


Note You need to log in before you can comment on or make changes to this bug.