To Reproduce Steps to reproduce the behavior:

1. Perform OSP minor update as per https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html-single/deploying_an_overcloud_in_a_red_hat_openshift_container_platform_cluster_with_director_operator/index#proc_updating-the-openstackclient-pod_preparing-OSPdO-for-a-minor-update
   There is a step to manually modify osp-director-operator CSV in this document

   <Change 17.1.3 to 17.1.X>
   
                     - name: OPENSTACKCLIENT_IMAGE_URL_DEFAULT
                       value: registry.redhat.io/rhosp-rhel9/openstack-tripleoclient:17.1.6
                     - name: HEAT_API_IMAGE_URL_DEFAULT
                       value: registry.redhat.io/rhosp-rhel9/openstack-heat-api:17.1.6
                     - name: HEAT_ENGINE_IMAGE_URL_DEFAULT
                       value: registry.redhat.io/rhosp-rhel9/openstack-heat-engine:17.1.6
                     - name: MARIADB_IMAGE_URL_DEFAULT
                       value: registry.redhat.io/rhosp-rhel9/openstack-mariadb:17.1.6
                     - name: RABBITMQ_IMAGE_URL_DEFAULT
                       value: registry.redhat.io/rhosp-rhel9/openstack-rabbitmq:17.1.6

2. Perform OCP update from OCP 4.16 to 4.18
3. The change made in osp-director-operator CSV is reverted during the OCP update

   <The version is reverted to 17.1.3 automatically during the OCP update>
   
                     - name: OPENSTACKCLIENT_IMAGE_URL_DEFAULT
                       value: registry.redhat.io/rhosp-rhel9/openstack-tripleoclient:17.1.3
                     - name: HEAT_API_IMAGE_URL_DEFAULT
                       value: registry.redhat.io/rhosp-rhel9/openstack-heat-api:17.1.3
                     - name: HEAT_ENGINE_IMAGE_URL_DEFAULT
                       value: registry.redhat.io/rhosp-rhel9/openstack-heat-engine:17.1.3
                     - name: MARIADB_IMAGE_URL_DEFAULT
                       value: registry.redhat.io/rhosp-rhel9/openstack-mariadb:17.1.3
                     - name: RABBITMQ_IMAGE_URL_DEFAULT
                       value: registry.redhat.io/rhosp-rhel9/openstack-rabbitmq:17.1.3

Expected behavior

• osp-director-operator CSV keeps the manual change

Bug impact

• OCPdO pods might be unexpectedly reverted to old OSP version 17.1.3

Known workaround

• I think we can perform the same manual change again

Is this an expected behavior or bug?
If it's an expected behavior, do we need documentation or KCS describing this behavior?