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 1961457 - RFE: Allow product configuration to specify multiple default base repos and update repos
Summary: RFE: Allow product configuration to specify multiple default base repos and u...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-18 01:42 UTC by Neal Gompa
Modified: 2022-11-18 07:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-18 07:27:46 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Neal Gompa 2021-05-18 01:42:57 UTC 
Description of problem:
In the CentOS Stream Hyperscale SIG, we're working on building a spin to showcase our work on top of CentOS. However, something that I ran into is that Anaconda has hard-wired assumptions of a singular base repo and hard-wired update repos.

This needs to be made configurable in the product configuration file so that SIGs can declare multiple base repositories.

Version-Release number of selected component (if applicable):
33.16.4.15-1.el8.0.2

Additional info:
It seems like this was partially implemented in Anaconda 34 to support declaring update repositories: https://github.com/rhinstaller/anaconda/pull/3023

However, there is no equivalent counterpart for base repositories.
Comment 2 Vendula Poncova 2021-05-18 13:24:09 UTC 
Hi Neal,

we plan to drop the concept of a base repo and support a list of repositories instead. It is the next step of our Anaconda modularization effort. I am not able to estimate the impact of this change yet, but I don't think we will be able to backport it to RHEL.

We could probably backport the updates_repositories configuration option and move the list of allowed base repo names into the configuration files, but that will not enable multiple base repos. Have you tried to use the support for the closest mirror? Couldn't you use additional repositories instead of multiple base repositories?
Comment 3 Neal Gompa 2021-05-18 13:29:57 UTC 
(In reply to Vendula Poncova from comment #2)
> Hi Neal,
> 
> we plan to drop the concept of a base repo and support a list of
> repositories instead. It is the next step of our Anaconda modularization
> effort. I am not able to estimate the impact of this change yet, but I don't
> think we will be able to backport it to RHEL.
> 

That's awesome, I guess this would be in RHEL 9 Anaconda, though?

> We could probably backport the updates_repositories configuration option and
> move the list of allowed base repo names into the configuration files, but
> that will not enable multiple base repos. Have you tried to use the support
> for the closest mirror? Couldn't you use additional repositories instead of
> multiple base repositories?

I could use additional repositories. The main thing is I don't want it to be easy for people to accidentally set a broken configuration. And I want it to be configuration I can ship in a package so that it's easy for me to build media with it.
Comment 4 Vendula Poncova 2021-05-18 14:12:32 UTC 
(In reply to Neal Gompa from comment #3)
> (In reply to Vendula Poncova from comment #2)
> > Hi Neal,
> > 
> > we plan to drop the concept of a base repo and support a list of
> > repositories instead. It is the next step of our Anaconda modularization
> > effort. I am not able to estimate the impact of this change yet, but I don't
> > think we will be able to backport it to RHEL.
> > 
> 
> That's awesome, I guess this would be in RHEL 9 Anaconda, though?
> 

It will be in RHEL 10.

> > We could probably backport the updates_repositories configuration option and
> > move the list of allowed base repo names into the configuration files, but
> > that will not enable multiple base repos. Have you tried to use the support
> > for the closest mirror? Couldn't you use additional repositories instead of
> > multiple base repositories?
> 
> I could use additional repositories. The main thing is I don't want it to be
> easy for people to accidentally set a broken configuration. And I want it to
> be configuration I can ship in a package so that it's easy for me to build
> media with it.

When the source is set to a closest mirror, the installer should be able to use every enabled repository found in /etc/anaconda.repos.d (unless we think it is an update repository). One of the repos needs to be have a name of a base repo, but otherwise, we don't really care what is there. At least, that's how I understand it.

About the additional repositories, I guess we could figure out how to specify them from the Anaconda configuration files. However, people can still disable these in the Source spoke.
Comment 6 RHEL Program Management 2022-11-18 07:27:46 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.