In https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/25990/pull-ci-openshift-origin-master-e2e-aws-serial/1372911814169333760 2 unexpected clusteroperator state transitions during e2e test run network was Degraded=false, but became Degraded=true at 2021-03-19 15:29:36.316089722 +0000 UTC -- Error while updating operator configuration: could not apply (apps/v1, Kind=DaemonSet) openshift-multus/network-metrics-daemon: could not update object (apps/v1, Kind=DaemonSet) openshift-multus/network-metrics-daemon: Operation cannot be fulfilled on daemonsets.apps "network-metrics-daemon": the object has been modified; please apply your changes to the latest version and try again network was Degraded=true, but became Degraded=false at 2021-03-19 15:29:38.429966802 +0000 UTC -- The error is a 409 which is normal (and is probably happening because the daemonset status is being updated because nodes are changing). Network operator needs to handle 409 requests and retry the operation always - these are normal parts of being a client on kube. Setting to high because going degraded creates operational noise in the fleet and should not happen.
*** This bug has been marked as a duplicate of bug 1939726 ***