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: | lorax | Assignee: | 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.0 | CC: | anilsson, atodorov, bmidwood, elpereir, stefw, tbowling, toneata | |
Target Milestone: | rc | Keywords: | ZStream | |
Target Release: | 8.0 | |||
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
Managed to build an image by only enabling redhat.repo via subscrition manager. Moving to VERIFIED. 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 |