Bug 2104820 - base-iface field at OVS vxlan port is empty
Summary: base-iface field at OVS vxlan port is empty
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Networking
Version: 4.10.3
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
: 4.10.3
Assignee: Petr Horáček
QA Contact: Nir Rozen
URL:
Whiteboard:
Depends On: 2078940
Blocks: 2078573 2080528 2104439 2104457
TreeView+ depends on / blocked
 
Reported: 2022-07-07 08:36 UTC by Quique Llorente
Modified: 2022-07-20 16:01 UTC (History)
12 users (show)

Fixed In Version: kubernetes-nmstate-handler-container-v4.10.3-4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2078940
Environment:
Last Closed: 2022-07-20 16:01:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2022:5675 0 None None None 2022-07-20 16:01:47 UTC

Comment 1 Petr Horáček 2022-07-07 09:47:50 UTC
This issue prevents upgrade to 4.11. We have a hot-fix ready and are in process of applying it to 4.10. We should have a new build by Friday.

Comment 3 Yossi Segev 2022-07-08 09:22:22 UTC
Verified on:
CNV: 4.10.3
cluster-network-addons-operator: v4.10.3-4
kubernetes-nmstate-handler-container: v4.10.3-4
nmstate: 1.0.2-19.el8_4.noarch


1. Apply a basic linux-bridge NNCP:
$ cat << EOF | oc apply -f -
> apiVersion: nmstate.io/v1
> kind: NodeNetworkConfigurationPolicy
> metadata:
>   name: br1test-nncp
> spec:
>   desiredState:
>     interfaces:
>     - bridge:
>         options:
>           stp:
>             enabled: false
>         port:
>         - name: ens9
>       ipv4:
>         dhcp: false
>         enabled: false
>       ipv6:
>         enabled: false
>       name: br1test
>       state: up
>       type: linux-bridge
>   nodeSelector:
>     node-role.kubernetes.io/worker: ""
> EOF
nodenetworkconfigurationpolicy.nmstate.io/br1test-nncp created

[cnv-qe-jenkins@n-yoss-410-upg-s4brp-executor basic-bridge-vm]$ oc get nncp br1test-nncp -w
NAME           STATUS
br1test-nncp   
br1test-nncp   
br1test-nncp   Available

2. Wait for the policy to succeed:
$ oc get nncp br1test-nncp -w
NAME           STATUS
br1test-nncp   
br1test-nncp   
br1test-nncp   Available

3. Verify the created bridge is found in NodeNetworkState:
$ oc get nns n-yoss-410-upg-s4brp-worker-0-6hhpg -o yaml
...
    - bridge:
        options:
          group-addr: 01:80:C2:00:00:00
          group-forward-mask: 0
          hash-max: 4096
          mac-ageing-time: 300
          multicast-last-member-count: 2
          multicast-last-member-interval: 100
          multicast-querier: false
          multicast-querier-interval: 25500
          multicast-query-interval: 12500
          multicast-query-response-interval: 1000
          multicast-query-use-ifaddr: false
          multicast-router: 1
          multicast-snooping: true
          multicast-startup-query-count: 2
          multicast-startup-query-interval: 3125
          stp:
            enabled: false
            forward-delay: 15
            hello-time: 2
            max-age: 20
            priority: 32768
        port:
        - name: ens9
          stp-hairpin-mode: false
          stp-path-cost: 100
          stp-priority: 32
          vlan:
            enable-native: false
            mode: trunk
            trunk-tags:
            - id-range:
                max: 4094
                min: 2
      ipv4:
        address: []
        dhcp: false
        enabled: false
      ipv6:
        address: []
        autoconf: false
        dhcp: false
        enabled: false
      lldp:
        enabled: false
      mac-address: FA:16:3E:7A:E6:B7
      mtu: 1450
      name: br1test
      state: up
      type: linux-bridge

Comment 9 errata-xmlrpc 2022-07-20 16:01:37 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Virtualization 4.10.3 Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2022:5675


Note You need to log in before you can comment on or make changes to this bug.