[patch] Add Fix for OLM Subscriptions get to ConstraintsNotSatisfiable state

[Bhautik-Vala]

JIRA ISSUE: https://jsw.ibm.com/browse/MASCORE-13497

Updated applySubscription() in olm.py to detect the OLM ConstraintsNotSatisfiable scenario where a CSV already exists but is not referenced by a subscription.

Changes done

• added detection for the ResolutionFailed / ConstraintsNotSatisfiable condition
• parsed the subscription error message to identify the impacted CSV
• covered 2 cases in the logic:
  • marketplace_cache case, where OLM can recover after cleanup and retry
  • catalog_behind case, where we cleanup and fail clearly because retry alone will not fix it, catalog rebuild needed
• added mock tests in test_olm_constraints.py, and test coverage is working fine

Testing
This issue is mainly seen during a fresh operator release/update window, so it is not reproducible reliably right now . Because of that, validation was done through mock-based unit tests covering the recovery scenarios, and those tests are passing.

[terc1997]

catalog_behind means that the requiredVersion is not available in the catalog ?

[durera]

Isn't this primarily related to the use of development catalogs/builds in long-life environments (which isn't/never has been supported)? If we are going to deliver this the testing needs to be incredibly thorough, because the actions being taken here generally speaking do not happen in real world scenarios, and taking these kinds of actions is dangerous.

[Bhautik-Vala]

Yes mainly we found this issue in long life dev env like IVTs. I am really not sure does it happen in real Env with static catalog, and as u said the testing is very complex here and we faces this issue only in very small window of the month when operator release done. so what coule be next step now - can we close this issue - #44? @durera