Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Composer is unusable from RHEL (see bug #1663950), because it cannot pass subscription information to anaconda.
I've proposed a patch upstream to pykickstart (see bug #1663952) and anaconda to do that:
https://github.com/rhinstaller/anaconda/pull/1745
I realize that this is a very late change, but it's fairly low impact on anaconda and would make composer usable at all on these systems.
Hi Lars,
can you describe the use case in detail? From the description I don't know how the process of passing subscription information to anaconda should work. Will this feature introduce any change in Anaconda installation?
We need more detailed information to provide the qe_ack since for any change in 8.0.1 there should be implemented a new gating test.
Thanks.
(In reply to Peter Kotvan from comment #3)
> Hi Lars,
>
> can you describe the use case in detail? From the description I don't know
> how the process of passing subscription information to anaconda should work.
> Will this feature introduce any change in Anaconda installation?
>
> We need more detailed information to provide the qe_ack since for any change
> in 8.0.1 there should be implemented a new gating test.
Sure! Composer uses the host's repositories as a source for the images it creates. Currently, the image installation fails if the host is a RHEL host with repositories that require a valid subscription. It makes Composer unusable without a nasty workaround.
This is because there's no way for Composer to pass the repository's configured client certificate to Anaconda. To fix this, I've added options to the kickstart commands `repo` and `url` which allow specifying paths to the needed cert (see the linked pykickstart bug). This is a natural extension to those commands: they already accept other options related to a repository.
This Anaconda patch only makes it use those options, by passing them further down to its invocation of dnf.
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/RHBA-2019:3417