-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
4.19.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Cluster installation perma-failures in CI due to *RolloutHung: DaemonSet "/openshift-multus/multus-additional-cni-plugins" rollout is not making progress
* is causing Component Readiness failures and merge blocks.
Version-Release number of selected component (if applicable):
4.19.0
How reproducible:
Seen in many places in CI:
https://storage.googleapis.com/test-platform-results/pr-logs/pull/openshift_images/198/pull-ci-openshift-images-master-e2e-aws/1879195383599468544/build-log.txt
https://storage.googleapis.com/test-platform-results/pr-logs/pull/openshift_images/198/pull-ci-openshift-images-master-e2e-aws/1879093481838743552/build-log.txt
https://storage.googleapis.com/test-platform-results/pr-logs/pull/openshift_images/198/pull-ci-openshift-images-master-e2e-aws/1878935519505682432/build-log.txt
Steps to Reproduce:
1. CI logs included above.
2.
3.
Actual results:
Cluster fails to complete bootstrap due to Daemonset RolloutHung for multus-additional-cni-plugins
Expected results:
Cluster installs without errors.
Additional info:
A search over 3 days in shows it is seen in other jobs too, starting about 2 days ago: https://search.dptools.openshift.org/?search=Cluster+operator+network+Degraded+is+True+with+RolloutHung%3A+DaemonSet&maxAge=72h&context=1&type=junit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job
