Description:

 
We have observed inconsistency in RHODS 1.23 bundle and related_images

1. Go to RHODS 1.23 advisory: https://errata.devel.redhat.com/advisory/109953 > Builds > odh-operator-bundle-container-v1.23.0-14
2. The previous link will bring you to https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=2410485
3. Now we can see related_images:

            sha256 for ose-prometheus-alertmanager in related_images doesn't match the sha256 if the alertmanager                  pod running at redhat-ods-monitoring:

•  related_images: registry.redhat.io/openshift4/ose-prometheus-alertmanager@sha256:169b788b3f8eb8909ecc1d698ab0a6bf103b49043c7f5fd569789b179928def6
• pod:            registry.redhat.io/openshift4/ose-prometheus-alertmanager@sha256:b180f86ebeccbab28b05f75a570ead59fc1462a77dde648b2b1d1ebe9e33cbdb                                                            

             sha256 for ose-prometheus in related_images doesn't match the sha256 if the prometheus pod             

             running at redhat-ods-monitoring:                                                             

• related_images: registry.redhat.io/openshift4/ose-prometheus@sha256:c432e571eb737d55323b5f350b5f714803bf525144cfee3f20782660d9bf10ad',
• pod:            registry.redhat.io/openshift4/ose-prometheus@sha256:62c89e82fdf9639eace286d11c91e6d1c3fdd3437e081ed9dce6f5ea783c660f

As discussed with rh-ee-dchouras , this is not a blocker for the release as it is utilizing the older image rather than picking from operator-bundle-container.

This issue is seen in both upgrade and fresh cluster rhods installations. Have the same behaviour in previous releases as well.