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.

Bug 1663950

Summary: Composer: All image builds from a RHEL host fail when only CDN repos are available
Product: Red Hat Enterprise Linux 8 Reporter: Lars Karlitski <lueberni>
Component: loraxAssignee: Brian Lane <bcl>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact: Eliane Ramos Pereira <elpereir>
Priority: unspecified    
Version: 8.0CC: anilsson, atodorov, bmidwood, elpereir, stefw, tbowling, toneata
Target Milestone: rcKeywords: ZStream
Target Release: 8.0Flags: tbowling: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: lorax-28.14.26-1.el8 Doc Type: Bug Fix
Doc Text:
.Image Building no longer fails when using `lorax-composer` API Previously, when using `lorax-composer` API from a subscribed RHEL system, the image building process always failed. Anaconda could not access the repositories, because the subscription certificates from the host are not passed through. To fix the issue update `lorax-composer`, `pykickstart`, and `Anaconda` packages. That will allow to pass supported CDN certificates.
Story Points: ---
Clone Of:
: 1691969 1693801 1777265 (view as bug list) Environment:
Last Closed: 2019-11-05 20:42:41 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:
Bug Depends On: 1663952, 1663954, 1691970, 1691971, 1693802, 1693976, 1702370, 1711869, 1712054    
Bug Blocks: 1691969, 1693801, 1700898, 1701002    

Description Lars Karlitski 2019-01-07 11:20:16 UTC
When using lorax-composer from a subscribed RHEL system, the image building process always fails.

This is because Anaconda cannot access the repositories, because the subscription certificates from the host are not passed through.

This was already a problem in RHEL 7:

    https://bugzilla.redhat.com/show_bug.cgi?id=1627911

I've proposed a fix for this upstream, but it depends on changes in pykickstart and anaconda (I'll attach bugs shortly here):

    https://github.com/weldr/lorax/pull/561

Comment 1 Andreas Nilsson 2019-02-13 17:00:54 UTC
JIRA ticket: https://projects.engineering.redhat.com/browse/COMPOSER-254

Comment 7 Alexander Todorov 2019-08-23 12:54:44 UTC
Managed to build an image by only enabling redhat.repo via subscrition manager. Moving to VERIFIED.

Comment 9 errata-xmlrpc 2019-11-05 20:42:41 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/RHBA-2019:3328