Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1948593

Summary: Wildcard entries are parsed incorrectly from the Image CR
Product: OpenShift Container Platform Reporter: Urvashi Mohnani <umohnani>
Component: NodeAssignee: Urvashi Mohnani <umohnani>
Node sub component: CRI-O QA Contact: Sunil Choudhary <schoudha>
Status: CLOSED NEXTRELEASE Docs Contact:
Severity: medium    
Priority: unspecified CC: aos-bugs
Version: 4.8   
Target Milestone: ---   
Target Release: 4.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-12 22:06:36 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 Urvashi Mohnani 2021-04-12 14:35:05 UTC
Description of problem:

When using a wildcard entry in the cluster wide Image CR for allowed/blocked/insecure registries, the entry is parsed incorrectly and placed under Registry.Endpoint.Location instead of Registry.Prefix in the registries.conf file.

images.config.openshift.com CR example:
---
spec:
  registrySources:
    insecureRegistries:
      - *.wildcard-reg.com
---

Results in an entry in /etc/containers/registries.conf

[[registry]]
Location = *.wildcard-reg.com
Insecure = true
Prefix = ""

When it should be:

[[registry]]
Prefix = *.wildcard-reg.com
Insecure = true

Comment 1 Urvashi Mohnani 2021-04-12 22:06:36 UTC
Deferring this to 4.9 as it could cause podman to break in 4.8. Will fix during the next release dev period.