Bug 2005137

Summary: Update of the Registry Name Pattern fails
Product: Red Hat Satellite Reporter: Vladimír Sedmík <vsedmik>
Component: RepositoriesAssignee: Ian Ballou <iballou>
Status: CLOSED ERRATA QA Contact: Vladimír Sedmík <vsedmik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.10.0CC: iballou, zhunting
Target Milestone: 6.10.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-4.1.1.29-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-16 14:13:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vladimír Sedmík 2021-09-16 21:11:26 UTC 
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
Comment 2 Brad Buckingham 2021-09-20 13:13:02 UTC 
Is this a regression from Satellite 6.9?
Comment 3 Vladimír Sedmík 2021-09-20 16:08:59 UTC 
Yes it is, compared to 6.9.6.
Comment 4 Ian Ballou 2021-09-21 14:56:52 UTC 
Created redmine issue https://projects.theforeman.org/issues/33534 from this bug
Comment 9 Vladimír Sedmík 2021-10-04 16:26:11 UTC 
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.
Comment 12 errata-xmlrpc 2021-11-16 14:13:51 UTC 
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