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