-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
4.10.z
-
Moderate
-
None
-
Refinement Backlog
-
1
-
Rejected
-
False
-
Description of problem:
When reconciling dependencies for a subscription that is set for manual approval, the OLM determined to auto approve the install plan resulting in the remaining sub to be auto upgraded instead of just installing the dependencies that were removed.
Version-Release number of selected component (if applicable):
4.10.28
How reproducible:
1 out of 1. I have not attempted to recreate manually yet.
Steps to Reproduce:
1. Install ODF 4.10.5 2. Delete dependency subs (for this case we did MCG and OCS) 3. OLM will install removed deps but also upgrade ODF to 4.10.8 when we only wanted to reinstall the bad subs.
Actual results:
InstallPlan for missing dependencies is created and auto approved
Expected results:
InstallPlan for missing dependencies is created but is not approved
Additional info:
The background for this case is involving another issue. Customer was wanting to see the manual IP for upgrading ODF to 4.10.8, but it was never generating. We found out that the currentCSV fields were missing from OCS and MCG operators (dependency operators). Once we deleted the Sub and CSV for each, the OLM generated install plan for 2 missing Subs, auto approved it, but then created install plan for upgrading to 4.10.8 and auto approved that. We are not sure why the currentCSV field data was missing, but installedCSV was still present and had correct CSV values. The case 03337097 does have attached must-gathers. Most recent must-gather is from after deleting the olm / catalog operators and then shortly after that, deleting the sub / csv combo and shows the upgrade path generation. There are older must-gathers too with the state where no IP is generated for 4.10.8. It also contains the subs / csv with the issue of no currentCSV field.