@Vu, as we discussed offline trying to reproduce it once more on OCP 4.3 here as last week we didn't see this issue in OCP 4.3:
the access to the cluster should be available in the job description:
Currently it is installing OCS 4.3 and will continue with upgrade.
Please do not do any changes in the cluster now as it can break the automation. You can just connect to check the progress, it should be OK if no changes made in cluster ;)
Once you will see from console output of the job that it's paused and waiting for user input you can do any disruptive operations or changes in cluster.
I can ping you if I will be still online, otherwise we will need to count only on collected data from job itself which I will be available after the job will finish here:
Looks like upgrade started OK on OCP 4.3 but then we hit another noobaa related issue. But OLM started rolling upgrade of OCS fine in the job mentioned above.
If someone is curious about must gather logs from OCP 4.3 execution they are here:
We are looking at the issue on noobaa, however this is does prevent the progress on this BZ right ?
fixing direction of BZ dependency.. ;-)
Nimrod on OCP 4.4 we cannot even start upgrade cause of OLM issue.
On OCP 4.3 the upgrade to OCS 4.4 will start OK, but then it's failing on noobaa BZ:
So basically we cannot really confirm that upgrade working even on OCP 4.3.
But actually without running any pre upgrade tests we passed the whole upgrade.
*** This bug has been marked as a duplicate of bug 1834936 ***