Warning message

A translation for your language preference does not exist.

The OVN Kubernetes localnet secondary network configuration does not support more than one bridge per network interface

Solution Unverified - 업데이트됨 - 한국어 번역 요청

문제

  • Why is the localnet network connectivity unstable when more than one ovs bridge is assigned to a network interface?

  • The applied NodeNetworkConfigurationPolicy CR is separate by bridge configuration and assigned to the same port:

    $ oc get nncp localnet-ovs-bridge -oyaml
    apiVersion: nmstate.io/v1
    kind: NodeNetworkConfigurationPolicy
    metadata:
    name: localnet-ovs-bridge
    spec:
    desiredState:
    interfaces:
    - bridge:
        allow-extra-patch-ports: true
        options:
          stp: false
        port:
        - name: ens3 #<---
      [...]
      name: br-ovs #<---
      state: up
      type: ovs-bridge
    ovn:
      bridge-mappings:
      - bridge: br-ovs
        localnet: localnet-network
        state: present
    $ oc get nncp localnet-ovs-bridge-test -oyaml
    apiVersion: nmstate.io/v1
    kind: NodeNetworkConfigurationPolicy
    metadata:
    name: localnet-ovs-bridge-test
    spec:
    desiredState:
    interfaces:
    - bridge:
        allow-extra-patch-ports: true
        options:
          stp: false
        port:
        - name: ens3 #<---
      [...]
      name: br-ovs-test #<---
      state: up
      type: ovs-bridge
    ovn:
      bridge-mappings:
      - bridge: br-ovs-test
        localnet: localnet-network-test
        state: present
    

환경

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Kubernetes NMState Operator

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