Description of problem (please be detailed as possible and provide log snippests): This was discussed on engineering weekly meeting that when QE tried to verified some of the BZ which required starting point this combination OCS/OCP version == 4.4 . We couldn't install this version as only visible version was OCS 4.6. Version of all relevant components (if applicable): OCP 4.4 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Cannot deploy OCS 4.4 anymore Is there any workaround available to the best of your knowledge? Install internal build from catalog source Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? Yes Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Install OCP 4.4 2. There is no OCS 4.4 available in operator hub, only 4.6 3. Actual results: There is no OCS 4.4 available in operator hub, only 4.6 Expected results: Even there is no support on OCS 4.4 I think we still should be able to deploy older version o older platform version. Additional info: Neha also brought up that it might be problematic for upgrade. If there is some customer with 4.4, they will not be able to upgrade to 4.5
Let's not change the target release field, it is set automatically once we have all the acks. If you want to move it to 4.10, just change the proposed flag like I did here.