Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Right now if any changes are made to /etc/osbuild-composer/repositories/ a service restart is required since the repos are only read at service start.
If this were to read the repos each time, then we would not have to restart the service for each change.
This would allow users to change repository configurations easier.
It could potentially help another rfe for "composer-cli sources info" to show which .repo file its reading from
This bug will be migrated to Jira shortly. We were asked to migrate at least one bug to Jira before the mass-migration begins, so I've chosen this one.
Migrated to https://issues.redhat.com/browse/RHEL-707, the rest of this bug's lifecycle will happen there. Note that we don't plan to migrate any other bugs at the moment, this was just a test. Note that the mass-migration will happen later in 2023 if nothing changes.