Description of problem (please be detailed as possible and provide log snippests): - Cu was trying to upgrade OCD from v4.7 to v4.8. - The upgrade was stuck thus cu has deleted the CSV of v4.7. - After that, they installed the OCS v4.8 on the same cluster. - The installed CSV is in a Pending state. It complaints about some resources that're in NotSatisfied and NotPresent state. Version of all relevant components (if applicable): v4.7 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? - The cluster is not healthy and CSV is stuck in a Pending state Is there any workaround available to the best of your knowledge? N/A Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 3 Can this issue reproducible? - I tried to reproduce the issue by deleting the installed CSV and then installing the upgraded one but the upgrade went successful in the test cluster. - The OCS cluster was upgraded to v4.8. Can this issue reproduce from the UI? N/A If this is a regression, please provide more details to justify this: N/A Steps to Reproduce: N/A Actual results: - The new version of CSV is stuck in a Pending state. Expected results: - The CSV should be successfully installed. Additional info: In the next comments:
*** Bug 2015521 has been marked as a duplicate of this bug. ***
Hello, apologies for the delay. Without a must-gather from before the original CSV was deleted I can't say much about this. Offhand I would say uninstall any existing OCS from the Operator Hub UI, then try installing OCS 4.7 and see if that succeeds. Once there, try the upgrade to 4.8 again and send a must-gather if it fails again.