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 1915351 - RFE: be able to use composer without CDN connection
Summary: RFE: be able to use composer without CDN connection
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: osbuild-composer
Version: 8.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: 8.5
Assignee: Image Builder team
QA Contact: Release Test Team
Eliane Ramos Pereira
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-12 13:55 UTC by Renaud Métrich
Modified: 2024-03-25 17:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
.Ability to override official repositories available By default, the `osbuild-composer` backend has its own set of official repositories defined in the `/usr/share/osbuild-composer/repositories` directory. Consequently, it does not inherit the system repositories located in the `/etc/yum.repos.d/` directory. You can now override the official repositories. To do that, define overrides in the `/etc/osbuild-composer/repositories` and, as a result, the files located there take precedence over those in the `/usr` directory.
Clone Of:
Environment:
Last Closed: 2022-02-07 08:53:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-96076 0 None None None 2021-09-22 11:04:25 UTC

Description Renaud Métrich 2021-01-12 13:55:08 UTC
Description of problem:

It appears that it's currently not possible to use composer-cli/osbuild-composer without being registered against CDN.
- it's not possible to modify "baseos" and "appstream" repositories because these are "system" ones
- if you add your own offline repositories, this doesn't work either, "composer-cli blueprints depsolve" or other commands fail with "RHSM secrets not found on host"

Major companies are not registered against CDN, so it should be possible for them to use the tool anyway.


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

composer-cli-28.14.55-2.el8.x86_64
osbuild-composer-20.1-1.el8.x86_64


How reproducible:

ALWAYS.

Comment 1 Tom Gundersen 2021-01-13 17:57:14 UTC
Thanks for reaching out Renaud. This is indeed not supported, but a workaround exists. The base repositories are defined in `/usr/lib/osbuild-composer/repositories/rhel-8.json`, and you can override these by making a copy of the file and put it in `/etc/osbuild-composer/repositories/` where you can edit them to point to the right URLs (and disable rhsm).

Please let us know whether or not that works for you!


Note You need to log in before you can comment on or make changes to this bug.