Noticed this in skew tests, but it can also happen when the CVO gets rescheduled onto a different machine during an upgrade.
We should be setting resource requests, looking at e2e runs it's ~ 10m CPU and 50Mi mem, roughly 1Mi disk.
Fixed by https://github.com/openshift/cluster-version-operator/pull/276
Run upgrade from 4.4.0-0.nightly-2020-01-08-233510 to 4.4.0-0.nightly-2020-01-09-013524, checked extract job runs in burstable qos(expected):
# ./oc get pod version--8hprx-2nbbg -ojson|jq .status.qosClass
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.