Version: CI Platform: baremetal, IPI What happened? CI jobs are failing with bootstrapping errors like 2020-09-29 18:51:34 level=info msg="Cluster operator network Progressing is True with Deploying: DaemonSet \"openshift-multus/multus-admission-controller\" is not available (awaiting 3 nodes)" For example: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-etcd-operator/450/pull-ci-openshift-cluster-etcd-operator-release-4.4-e2e-metal-ipi/1310995092688867328 What did you expect to happen? The CI job should pass. How to reproduce it (as minimally and precisely as possible)? Submit a patch against a 4.4 branch for an IPI component like the baremetal-operator. Anything else we need to know? This is blocking a feature patch, https://github.com/openshift/baremetal-operator/pull/63
I tested locally and can confirm bootstrap failure with 4.4.0-0.ci-2020-09-30-103924 when configured to use ipv6 The same build with ipv4 works though, so we may have some regression specific to ipv6
Yep, in my case it was also IPv6 deployment.
We didn't have install-gather working on baremetal in 4.4, so someone would need to collect the logs by hand and pinpoint the failure. Did anyone who ran a local install collect any more information?
It seems this will require the same fix as https://bugzilla.redhat.com/show_bug.cgi?id=1888352 backported, moving the component to ovn-kubernetes
yeah, already filed but the bot didn't link it here because the 4.5 bz is "invalid" because it's not verified yet
This is being fixed by removing this job; we do not need to support IPv6 in 4.4.
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633