Bug 2208340

Summary: rhsm kickstart command does not work with livemedia-creator
Product: Red Hat Enterprise Linux 9 Reporter: Brian Lane <bcl>
Component: loraxAssignee: Brian Lane <bcl>
Status: CLOSED MIGRATED QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: unspecified    
Version: 9.2CC: jstodola
Target Milestone: rcKeywords: MigratedToJIRA, Triaged
Target Release: ---Flags: pm-rhel: mirror+
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: 2023-09-18 13:49:08 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 Brian Lane 2023-05-18 16:06:26 UTC
Description of problem:
When using the rhsm kickstart command with livemedia-creator on RHEL the installation is terminated before it installs the packages.

The problem is that Anaconda tries to mount the repositories from the cdrom/dvd before trying the CDN specified by the rhsm command. livemedia-creator sees the error and assumes the installation has failed so it kills the VM before Anaconda has fallen back to the CDN source.

Version-Release number of selected component (if applicable):
lorax-34.9.23-1
anaconda-38.23.4-2

How reproducible:
Always

Steps to Reproduce:
1. Make a kickstart using rhsm for the content
2. Run livemedia-creator with the kickstart
3. Observe that the installation fails after an error

    18:10:59,811 ERR anaconda:packaging: base repo (CDROM/file:///run/install/sources/mount-0000-cdrom) not valid -- removing it

Upstream patch for lorax to work around this:
https://github.com/weldr/lorax/pull/1325

(Anaconda should probably also be changed to more intelligently select the base repo when using kickstart and rhsm but this should work around it for now).

Comment 6 RHEL Program Management 2023-09-18 13:48:28 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 7 RHEL Program Management 2023-09-18 13:49:08 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.