To Reproduce Steps to reproduce the behavior:

1. Deploy RHOSO18.0.6
2. Check logs of openstack-baremetal-operator
3. Define OpenStackProvisionServer CR like below.

   apiVersion: baremetal.openstack.org/v1beta1
   kind: OpenStackProvisionServer
   metadata:
     name: openstack-data-plane-provisionserver
     namespace: openstack
   spec:
     port: 6190
   

We can find the log like below.

# oc logs -c manager openstack-baremetal-operator-controller-manager-54b8599f6-77xkd -n openstack-operators | grep ini
2025-06-03T05:41:47Z    INFO    openstackprovisionserver-resource       OpenStackProvisionServer defaults initialized   {"defaults": {"OSContainerImageURL":"quay.io/podified-antelope-centos9/edpm-hardened-uefi:current-podified","AgentImageURL":"quay.io/openstack-k8s-operators/openstack-baremetal-operator-agent:latest","ApacheImageURL":"registry.redhat.io/ubi9/httpd-24:latest","OSImage":"edpm-hardened-uefi.qcow2"}}

Expected behavior

• The image's url should point to registry.redhat.io

Bug impact

• The customer must be define the image url based on the current openstackversion CR.

Known workaround

• Define OpenStackProvisionServer CR like below

  apiVersion: baremetal.openstack.org/v1beta1
  kind: OpenStackProvisionServer
  metadata:
    name: openstack-data-plane-provisionserver
    namespace: openstack
  spec:
    agentImageUrl: registry.redhat.io/rhoso-operators/openstack-baremetal-agent-rhel9@sha256:61479d622c744a92e504713876d1cbbb205179ba34b4627e5fc33ad7d5a775dc
    apacheImageUrl: registry.redhat.io/ubi9/httpd-24@sha256:366cc5bc3b96069fecaa0abeb9d3510c507e69a20de1d205d881da8ae8561ab4
    nodeSelector:
      node-role.kubernetes.io/openstack-provision: ""
    osContainerImageUrl: registry.redhat.io/rhoso/edpm-hardened-uefi-rhel9@sha256:867ec72c514f00df7d3dd30d9de052fa6aadaf0227a8b004787a836c4d5eaf5e
    port: 6190
  

Additional context