CNI migration towards OVN-Kubernetes affects RHODF nad assigned to the primary interface

Solution Unverified - Updated -

Issue

  • Why don't the ODF pods start properly after the CNI migration towards OVN-Kubernetes?

    $ oc get events -n openshift-storage | grep -v Normal | grep <nad-name>
    error adding container to network "nad-name": failed to create macvlan: device or resource busy <----
    
  • Why is not the assigned interface from net-attach-def available in the node?

    $ oc get net-attach-def -n openshift-storage <nad-name> -oyaml
    spec:
    config: '{ "cniVersion": "0.3.1", "type": "macvlan", "master": "bond0" <-----,  
    "mode": "bridge", "ipam": { "type": "whereabouts", "range": "xxx.xxx.1.0/24" } }'
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat OpenShift Data Foundation

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content