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 1650363 - Add support for running lorax-composer without any system provided repositories enabled
Summary: Add support for running lorax-composer without any system provided repositori...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lorax
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Brian Lane
QA Contact: Release Test Team
Vladimír Slávik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-16 00:19 UTC by Brian Lane
Modified: 2019-06-14 01:00 UTC (History)
2 users (show)

Fixed In Version: lorax-28.14.17-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-14 01:00:03 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Brian Lane 2018-11-16 00:19:07 UTC
In some situations you may not want to use any of the system provided repositories with lorax-composer. Most of the plumbing is already there, it just needs a cmdline switch to turn off copying from /etc/yum.repos.d/

Add --no-system-repos command to start it without any of the repos from /etc/yum.repos.d/, all repos will have to be added via the sources api or copied directly into /var/lib/lorax/composer/repos.d/

Comment 1 Brian Lane 2018-11-16 00:21:11 UTC
https://github.com/weldr/lorax/pull/526

Comment 3 Alexander Todorov 2019-02-06 10:36:52 UTC
Tried running manually lorax-composer --no-system-repos with and without repo files under /var/lib/lorax/composer/repos.d/.
When no repos available I can't start the compose, when I define repos under /var/lib/lorax/composer/repos.d/ composer is able to depsolve and proceed with building the compose. Moving to VERIFIED.


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