Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-2247

Configure CRI-O to pick up CNIs from /opt/cni/bin over /usr/libexec/cni

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Undefined Undefined
    • openshift-4.16
    • None
    • None
    • None
    • None
    • uShift Sprint 248, uShift Sprint 249, uShift Sprint 250

      We want to use CNIs from OpenShift's container-network-plugins container image because the releases are synced compared to RHEL having different schedule.

      Therefore we need to configure CRI-O to first select CNIs we'll provide over CNIs from containernetwork-plugins RPM (/usr/libexec/cni), but not remove that path entirely so CRI-O can still access its default network plugins.

      Relevant CRI-O log:

      level=warning msg="Error validating CNI config file /etc/cni/net.d/100-crio-bridge.conflist: [failed to find plugin \"bridge\" in path [/opt/cni/bin]]"
      
      level=warning msg="Error validating CNI config file /etc/cni/net.d/200-loopback.conflist: [failed to find plugin \"loopback\" in path [/opt/cni/bin]]" 

       

              pmatusza@redhat.com Patryk Matuszak
              pmatusza@redhat.com Patryk Matuszak
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: