+++ This bug was initially created as a clone of Bug #2256903 +++

+++ This bug was initially created as a clone of Bug #2255315 +++

+++ This bug was initially created as a clone of Bug #2255310 +++

Description of problem (please be detailed as possible and provide log
snippests):
odf-operator should update it's upgradeable conditions based on the dependents

Version of all relevant components (if applicable):
4.14

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?
yes


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Install odf-operator and observe it's dependents (ocs, mcg and csi-addons) are also installed
2. Update either mcg or csi-addon operator condition (oc get condition) for not upgradeable status, can use a cmd like
> oc -nopenshift-storage patch condition <mcg-name> --type merge -p '{"spec": {"conditions": [{"lastTransitionTime":"2023-12-19T04:06:22Z","message":"MSG","reason":"RSN","status":"False","type":"Upgradeable"}]}}'


Actual results:
- odf-operator condition is not reflecting not upgradeable status

Expected results:
- odf-operator condition should reflect not upgradeable status

Additional info:
- during testing once odf-operator reflects the correct status, remove the condition on it's dependent and odf-operator also should update it's condition

--- Additional comment from RHEL Program Management on 2023-12-20 09:18:30 IST ---

This bug having no release flag set previously, is now set with release flag 'odf‑4.15.0' to '?', and so is being proposed to be fixed at the ODF 4.15.0 release. Note that the 3 Acks (pm_ack, devel_ack, qa_ack), if any previously set while release flag was missing, have now been reset since the Acks are to be set against a release flag.

--- Additional comment from RHEL Program Management on 2024-01-05 11:32:46 IST ---

This BZ is being approved for an ODF 4.14.z z-stream update, upon receipt of the 3 ACKs (PM,Devel,QA) for the release flag 'odf‑4.14.z', and having been marked for an approved z-stream update

--- Additional comment from RHEL Program Management on 2024-01-05 11:32:46 IST ---

Since this bug has been approved for ODF 4.14.5 release, through release flag 'odf-4.14.z+', and appropriate update number entry at the 'Internal Whiteboard', the Target Release is being set to 'ODF 4.14.5'