Description of problem: An operator has been installed from a CSV e.g. 1.0.0 and set to manual approval. A new CSV (1.1.0) with replaces 1.0.0 is published and a pending installplan created. A new CSV (1.0.1) with replaces 1.0.0 is published and nothing is done. The 1.1.0 CSV is edit to have replaces 1.0.1 - invalidating the installplan. There is no route to install 1.0.1 in this scenario, another bug with id 1841175 prevents the deletion of the installplan to have an accurate one created and approving the pending installplan would install 1.1.0 rather than 1.0.1 Version-Release number of selected component (if applicable): How reproducible: This can be reproduced Steps to Reproduce: 1. Install operator from CSV 1.0.0 and set to manual approval 2. Create a 1.1.0 CSV that replaces 1.0.0 3. Create a 1.0.1 CSV that replaces 1.0.0 4. Update the 1.1.0 CSV to replace 1.0.1 Actual results: No way to install the 1.0.1 CSV Expected results: The installplan for 1.1.0 would be modified or recreated to be a pending install for the 1.0.1 CSV. Additional info:
This seems like another manifestation of https://bugzilla.redhat.com/show_bug.cgi?id=1841175, which is that when subscriptions are set to manual approval OLM doesn't recreate install plans on changes. Marking this as a duplicate and pushing over there for further discussion. *** This bug has been marked as a duplicate of bug 1841175 ***