-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.13.0
-
No
-
CFE Sprint 241
-
1
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-14402. The following is the description of the original issue:
—
Description of problem:
When set insecure = true in the registries config file location, oc-mirror still use https to connect the registry.
Version-Release number of selected component (if applicable): 4.13
How reproducible: always
Steps to Reproduce:
1) Create local registry by podman with insecure policy;
2) use imagesetconfig to mirror operator to localhost registry :
cat config-oci.yaml
apiVersion: mirror.openshift.io/v1alpha2
kind: ImageSetConfiguration
mirror:
operators:
- catalog: oci:///home/ocmirrortest/noo/redhat-operator-index
packages:
- name: cluster-kube-descheduler-operator
`oc-mirror --config config-oci.yaml docker://localhost:5000 --include-local-oci-catalogs --oci-insecure-signature-policy --dest-use-http`
3) use the imagesetconfig and registries.conf accordingly to mirror to remote registry :
cat registry.conf [[registry]] location = "registry.redhat.io/openshift4" insecure = false blocked = false mirror-by-digest-only = false prefix = "" [[registry.mirror]] location = "localhost:5000/openshift4" insecure = true
`oc-mirror --config config-oci.yaml docker://ec2-3-12-147-78.us-east-2.compute.amazonaws.com:5000 --include-local-oci-catalogs --oci-registries-config=/home/ocmirrortest/13762/registry.conf --source-use-http`
Actual results:
see logs like : err Get "https://localhost:5000/v2/": http: server gave HTTP response to HTTPS client
Expected results:
should use http for the insecure==true setting registry .
Additional info:
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
-
RHBA-2023:5382
OpenShift Container Platform 4.13.z bug fix update
