Bug 2010865

Summary:	Satellite provisioning not rolled back if subscription attempt fails with error
Product:	Red Hat Enterprise Linux 9	Reporter:	Martin Kolman <mkolman>
Component:	anaconda	Assignee:	Martin Kolman <mkolman>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	jkonecny, jstodola, mkolman, pjanda, rvykydal
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	anaconda-34.25.0.20-1.el9	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-17 12:30:42 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 Martin Kolman 2021-10-05 14:12:45 UTC

Description of problem: If user sets a Satellite URL at installation time, the installation environment will be provisioned to communicate with the given Satellite instance instead of the Red Hat hosted subscription infrastructure.

If the user then decides to unregister, Anaconda rolls the "Satellite provisioning" back so that it is easily possible to try registering again to Red Hat hosted subscription infrastructure or a different Satellite instance.

Unfortunately this rollback does not happen if the registration process fails for some reason (such as for example wrong password) and the installation environment will remain provisioned for the given Satellite instance.

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

How reproducible:
anaconda-33.16.6.1-1

Steps to Reproduce:
1. attempt to register to a Satellite instance from Anaconda with wrong password

Actual results:
Registration fails, Anaconda reports error & system remains provisioned for Satellite.

Easy way to check for this is to open /etc/rhsm/rhsm.conf and check the "prefix" key in the "[server]" section. If you see "prefix = /rhsm" then the system is provisioned for Satellite.

Expected results:
Registration fails, Anaconda reports error & Satellite provisioning is rolled back.

Easy way to check for this is to open /etc/rhsm/rhsm.conf and check the "prefix" key in the "[server]" section. If you see "prefix = /subscription" then the system is pointing to the Red Hat subscription infrastructure.

Comment 2 Martin Kolman 2021-10-13 16:45:01 UTC

PR: https://github.com/rhinstaller/anaconda/pull/3651

Comment 7 Jan Stodola 2021-11-22 09:05:38 UTC

anaconda-34.25.0.20-1.el9 is included in RHEL-9.0.0-20211121.7, moving to VERIFIED.

Comment 9 errata-xmlrpc 2022-05-17 12:30:42 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 (new packages: anaconda), 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/RHBA-2022:2326