Description of problem: This bug is used to track what should be the acceptable behavior of asb/tsb operator and broker when upgrading for 4.3 to 4.4 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. set up a OCP4.3 cluster 2. install asb with channel:4.3 3. provision mediawiki and mariadb apb 4. upgrade the cluster to 4.4 Actual results: 1. set up OCP4.3 cluster successfully 2. install asb successfully 3. provision mediawiki and mariadb apb successfully 4. upgrade 4.4 successfully, asb operator and the broker with channel 4.3 still works, mediawiki apb and mariadb apb works.The 4.3 asb operator and broker can work on a 4.4 cluster. Expected results: As asb will be removed for 4.4 1. Can a 4.3 asb operator and broker be installed on a 4.4 cluster? 2. Or no asb operator and broker can be installed on a 4.4 cluster? 3. If a 4.3 cluster with asb installed, will we stop the cluster from upgrading? Additional info:
Adding 'TestBlocker' keyword since it is blocking asb upgrade testing.
> 1. Can a 4.3 asb operator and broker be installed on a 4.4 cluster? It will show up in the catalog because all the old version (4.1,4.2 and 4.3 channels will be available) > 2. Or no asb operator and broker can be installed on a 4.4 cluster? See above, you can install an older version, we have no way of stopping you (OLM feature ask, they can file an RFE). > 3. If a 4.3 cluster with asb installed, will we stop the cluster from upgrading? +1 no we will not stop the upgrade So the results you experienced are the correct ones.
Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581