Hide Forgot
Description of problem: Mar 29 07:18:46.840: INFO: cluster upgrade is failing: Cluster operator kube-apiserver is still updating: upgrading kube-apiserver from to 1.12.4 https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.0/731 How reproducible: flake Note: We are seeing this form of failure for several operators, I will cross link them as i open the bugs. I have not dug into whether this operator specifically failed to upgrade, or if something earlier in the process took so long that this operator was the "victim" of the eventual timeout. As you investigate the job that failed, feel free to reassign this if you think there is a root cause that is independent of your operator. If your operator currently lacks sufficient events/logs/etc to determine when it started upgrading and what it was doing when we timed out, consider using this bug to introduce that information.
Related operator failed to upgrade bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1694216 https://bugzilla.redhat.com/show_bug.cgi?id=1694220
Operator versioning was reworked recently, we haven't seen this since that, moving to QA.
Upgrade testing from 4.0.0-0.10 to 4.0.0-0.11 succeeds without the issue, moving to 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-2019:0758