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.

Description of problem:

This is a follow-up of BZ #1915353.
When adding a repository, it's possible to use an already-defined repo ID, as shown in the example below:

baseos-pulp.txt:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
name = "baseos-pulp"
type = "yum-baseurl"
url = "http://pulp.dist.prod.ext.phx2.redhat.com/content/dist/rhel8/8/$basearch/baseos/os/"
check_gpg = false
check_ssl = false
gpgkey_urls = []
id = "baseos"
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

# composer-cli sources add baseos-pulp.txt
-> OK

This ends up having 2 "baseos" sources.

# composer-cli sources list
baseos
baseos
appstream


Addtionally, it's unclear which one takes precedence and how to show information onthe newly added one.
Finally it's not possible to delete that broken source anymore, since "baseos" is a read-only "system" source.

# composer-cli sources delete baseos
[...] baseos is a system source, it cannot be deleted.


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

composer-cli-28.14.55-2.el8.x86_64


How reproducible:

ALWAYS, see above.

Thanks for the report! This seems like something we should simply refuse.

PR to fix the issue upstream - https://github.com/osbuild/osbuild-composer/pull/1183

[root@kvm-02-guest10 ~]# cat myrepo.toml 
name = "baseos duplicate"
id = "baseos"
type = "yum-baseurl"
url = "http://download.devel.redhat.com/rhel-8/rel-eng/RHEL-8/latest-RHEL-8/compose/BaseOS/x86_64/os"
check_gpg = false
check_ssl = true
system = true

[root@kvm-02-guest10 ~]# rpm -q composer-cli 
composer-cli-28.14.57-1.el8.x86_64

# composer-cli sources add myrepo.toml 
2021-02-12 07:36:03,577: baseos is a system source, it cannot be changed.


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 (osbuild bug fix and enhancement update), 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-2021:1825