Hide Forgot
Currently the OSE and AEP channels have cockpit-kubernetes and receive the rest of the cockpit packages from RHEL Extras. Since these need to be version synced, OSE and AEP channels need to switch to a matching cockpit-kubernetes version as Extras is updated to 7.3.1.
Today, latest 3.2, 3.3 puddle update cockpit-kubernetes to ver 122 (3.1 still 118). Following test steps in above comment, installed 3.3 env and checked. The rebase also works well!
Thanks! Following test steps in above comment: Installed 3.2 env: [root@host-8-175-18 ~]# openshift version openshift v3.2.1.17 kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 And checked the rebase as above comment, it works well in 3.2 env. In sum, the rebase works well in 3.4, 3.3, 3.2. Moving to VERIFIED.
Correct, in Extras 7.3.1 we rebase to Cockpit 122, but OCP 3.4 is released slightly afterward, hence 122 in 3.4 once it's out. We update cockpit-kubernetes ASYNC with the Extras releases, but the registry-console container is released on OCP schedule (at least that's what we did so far). I didn't add the build for 3.4 in this advisory, because that isn't live when the advisory is pushed live.
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-2016:2869