Cloning for 4.11 so the bot will be happy. +++ This bug was initially created as a clone of Bug #2052058 +++ Description of problem: The test "[bz-Machine Config Operator] Nodes should reach OSUpdateStaged in a timely fashion" is failing due to missing OSUpdateStarted events that should have been recorded by the openshift-tests watcher, but weren't. We believe this is a defect somewhere in the disruption monitoring framework but are unsure where. The events exist when queried at the end of CI in gather-extra/must-gather. How reproducible: Rare but happening daily several times. https://search.ci.openshift.org/?search=but+no+OSUpdateStarted+event+was+recorded&maxAge=48h&context=1&type=bug%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job To fix we will break up the test, stop failing the existing one when we see these events missing, and add a new test which will flake when this happens so we can track it clearly and separately.
Verified based on https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade/1491298228346294272 where we see the msising OSUPdateStarted event test flake, as desired, and no fail on the previous OSUpdateStaged test.
OCP is no longer using Bugzilla and this bug appears to have been left in an orphaned state. If the bug is still relevant, please open a new issue in the OCPBUGS Jira project: https://issues.redhat.com/projects/OCPBUGS/summary