Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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:
Update of the Registry Name Pattern fails if a Container repo already exists.


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


How reproducible:
always


Steps to Reproduce:
1. Sync a Container image repo to the Satellite (for example foreman/foreman from quay.io)
2. In UI > Content > Lifecycle Envs > Library try to change the Registry Name Pattern to one of the provided in examples


Actual results:
Fails with `An error occurred saving the Environment: There was an issue with the backend service pulp: 404 Not Found`


Expected results:
No error and successful update of existing repository

Is this a regression from Satellite 6.9?

Yes it is, compared to 6.9.6.

Created redmine issue https://projects.theforeman.org/issues/33534 from this bug

Verified on 6.10.0 snap 21 - name pattern is updated successfully as well as the existing repo url. Content can be pulled to the client from the updated repository.

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 (Moderate: Satellite 6.10 Release), 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/RHSA-2021:4702