+++ This bug was initially created as a clone of Bug #1792005 +++
+++ This bug was initially created as a clone of Bug #1792004 +++
+++ This bug was initially created as a clone of Bug #1791863 +++
--- Additional comment from Samuel Padgett on 2020-01-16 19:53:02 UTC ---
I believe this is happening because the CVO is not removing the console-operator readiness probe added in 4.3 when downgrading to 4.2.
The 4.2 operator deployment manifest does not have a readiness probe:
The 4.3 operator deployment does:
The failing 4.2 console-operator pod has the probe when it shouldn't:
Since the 4.2 console operator has no `/readyz` endpoint, the readiness probe fails:
> Jan 16 03:34:39.681 W ns/openshift-console-operator pod/console-operator-7bb76df6d6-m4qh7 Readiness probe failed: HTTP probe failed with statuscode: 404 (390 times)
The workaround would be to edit the console-operator deployment YAML after downgrade to manually from the liveness and readiness probes.
We don't support chained rollbacks, so no one would expect to upgrade from 4.1 to 4.2 to 4.3 then eventually back to 4.1, if the probe wasn't added in 4.2 should we really be fixing this in 4.1 at this point in the lifecycle?
I guess other as of yet unknown 4.1 to 4.2 upgrades could be adding a liveness probe we're worried about?
> I guess other as of yet unknown 4.1 to 4.2 upgrades could be adding a liveness probe we're worried about?
Yeah, this would be the only reason we'd need this in 4.1. Mostly backporting is easier than worrying if we'll need the fix, because this change is ~9 safe lines.
Since we don't support an upgrade from 4.1 to 4.2 to 4.3 then eventually back to 4.1(from comment1), and currently a probe was not added during 4.1-4.2 upgrade. So do regression test against 4.1-4.2-4.1 for this bug's verify.
Verify on path 4.1-4.2-4.1, console operator downgraded succeed, but other operators failed, will track it in another bug. Close this one.
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.