-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
4
-
False
-
-
False
-
?
-
openstack-operator-container-1.0.15-2
-
None
-
-
-
-
EDPM Sprint 10, EDPM Sprint 11
-
2
-
Important
When following our disconnected docs, the ansible vars that are needed to configure the mirror on the EDPM nodes are not added to the generated NodeSet inventory automatically as they should be.
The ansible vars that should be added are:
edpm_podman_disconnected_ocp edpm_podman_registries_conf
The code from openstack-operator that triggers adding the vars looks for the existence of ImageContentSourcePolicy and ImageDigestMirrorSet resources in the cluster before it adds the ansible vars (openstack-operator/pkg/dataplane/util/image_registry.go).
The issue is that after following our disconnected docs[1] , no ImageContentSourcePolicy is created so the ansible vars don't get added to the inventory.
The fix would be modify the image_registry.go code to no longer look for ImageContentSourcePolicy resources. It only needs to look for ImageDigestMirrorSet resources.
The strikethrough text above might only apply to deployments without https://github.com/openstack-k8s-operators/openstack-operator/commit/872123050e9af884b089fce2e6b5a4188b9f5f72
The workaround is to create an empty ImageContentSourcePolicy in the cluster like so:
apiVersion: operator.openshift.io/v1alpha1
kind: ImageContentSourcePolicy
metadata:
name: openstack-empty-icsp
spec:
repositoryDigestMirrors: []
- is related to
-
OSPRH-19793 /etc/containers/registries.conf overwritten by different ansible variables
-
- Review
-
- links to
- mentioned on