Description of problem: cluster bootstrapping fails during the ocp installation cluster-etcd-operator fail with the error: bootstrap_ip.go:146] Filtered address 10.46.8.142/22 ens3 bootstrap_ip.go:146] Filtered address 2620:52:0:2e08:dd8a:2551:72ec:e12f/64 bootstrap_ip.go:146] Filtered address fe80::647f:1864:d3af:9504/64 bootstrap_ip.go:146] Filtered address 127.0.0.1/8 lo bootstrap_ip.go:146] Filtered address ::1/128 bootstrap_ip.go:188] Found routable IPs [] render.go:63] couldn't find any bootstrap node IPs root cause in OCP 4.6, cluster-etcd-operator changed the bootstrap IP discovery behavior [0] , to comply with the new behavior we need to add: `machineCIDR` to install-config.yaml, [0] https://github.com/openshift/cluster-etcd-operator/pull/384
Just add some note from our talk today Evgeny: - machineNetwork deprecates machineCIDR, we should have one or another not both. machineNetwork must match the API_VIP and INGRESS_VIP subclass. Example: API_VIP: 192.168.1.80 INGRESS_VIP: 192.168.1.81 $ cat install-config.yaml <snip> networking: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 networkType: OpenShiftSDN machineNetwork: - cidr: 192.168.1.0/24 <------------- here serviceNetwork: - 172.30.0.0/16 platform: ovirt: api_vip: 192.168.1.80 ingress_vip: 192.168.1.81 ovirt_cluster_id: 40285c82-00e0-11ea-acb1-ecf4bbf47b7c ovirt_network_name: ovirtmgmt ovirt_storage_domain_id: 449a0e7b-38b7-4468-9d84-5c00da12b7b7 vnicProfileID: 0000000a-000a-000a-000a-000000000398 </snip>
for backward compatibility, this PR [0] makes this configuration not mandatory, once merged it should work without any changes in install-config.yaml from our part. this is the PR fixing this in the 4.6 CI [1]. [0] https://github.com/openshift/cluster-etcd-operator/pull/388 [1] https://github.com/openshift/cluster-etcd-operator/pull/10197
*** This bug has been marked as a duplicate of bug 1846093 ***