-
Bug
-
Resolution: Done
-
Critical
-
4.12
-
None
-
Critical
-
None
-
SDN Sprint 232
-
1
-
Proposed
-
False
-
This is a clone of issue OCPBUGS-6092. The following is the description of the original issue:
—
Description of problem:
While configuring 4.12.0 dualstack baremetal cluster ovs-configuration.service fails
Jan 19 22:01:05 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[14588]: Attempt 10 to bring up connection ovs-if-phys1 Jan 19 22:01:05 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[14588]: + nmcli conn up ovs-if-phys1 Jan 19 22:01:05 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[26588]: Error: Connection activation failed: No suitable device found for this connection (device eno1np0 not available because profile i s not compatible with device (mismatching interface name)). Jan 19 22:01:05 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[14588]: + s=4 Jan 19 22:01:05 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[14588]: + sleep 5 Jan 19 22:01:10 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[14588]: + '[' 4 -eq 0 ']' Jan 19 22:01:10 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[14588]: + false Jan 19 22:01:10 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[14588]: + echo 'ERROR: Cannot bring up connection ovs-if-phys1 after 10 attempts' Jan 19 22:01:10 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[14588]: ERROR: Cannot bring up connection ovs-if-phys1 after 10 attempts Jan 19 22:01:10 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[14588]: + return 4 Jan 19 22:01:10 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[14588]: + handle_exit Jan 19 22:01:10 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[14588]: + e=4 Jan 19 22:01:10 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[14588]: + '[' 4 -eq 0 ']' Jan 19 22:01:10 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[14588]: + echo 'ERROR: configure-ovs exited with error: 4' Jan 19 22:01:10 openshift-worker-0.kni-qe-4.lab.eng.rdu2.redhat.com configure-ovs.sh[14588]: ERROR: configure-ovs exited with error: 4
Version-Release number of selected component (if applicable):
4.12.0
How reproducible:
So far 100%
Steps to Reproduce:
1. Deploy dualstack baremetal cluster with bonded interfaces(configured with MC and not NMState within install-config.yaml) 2. Run migration to second interface, part of machine config - contents: source: data:text/plain;charset=utf-8,bond0.117 filesystem: root mode: 420 path: /etc/ovnk/extra_bridge 3. Install operators: * kubevirt-hyperconverged * sriov-network-operator * cluster-logging * elasticsearch-operator 4. Start applying node-tunning profiles 5. During node reboots ovs-configuration service fails
Actual results:
ovs-configuration service fails on some nodes resulting in ovnkube-node-* pods failure oc get po -n openshift-ovn-kubernetes NAME READY STATUS RESTARTS AGE ovnkube-master-dvgx7 6/6 Running 8 16h ovnkube-master-vs7mp 6/6 Running 6 16h ovnkube-master-zrm4c 6/6 Running 6 16h ovnkube-node-2g8mb 4/5 CrashLoopBackOff 175 (3m48s ago) 16h ovnkube-node-bfbcc 4/5 CrashLoopBackOff 176 (64s ago) 16h ovnkube-node-cj6vf 5/5 Running 5 16h ovnkube-node-f92rm 5/5 Running 5 16h ovnkube-node-nmjpn 5/5 Running 5 16h ovnkube-node-pfv5z 4/5 CrashLoopBackOff 163 (4m53s ago) 15h ovnkube-node-z5vf9 5/5 Running 10 15h
Expected results:
ovs-configuration service succeeds on all nodes
Additional info:
- clones
-
OCPBUGS-6092 ovs-configuration.service fails - Error: Connection activation failed: No suitable device found for this connection
- Closed
- is blocked by
-
OCPBUGS-6092 ovs-configuration.service fails - Error: Connection activation failed: No suitable device found for this connection
- Closed
- links to