Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-46904

autoconnect of VLAN over OVS internal interface not working

XMLWordPrintable

    • NetworkManager-1.48.10-1.el9
    • None
    • None
    • ZStream
    • 1
    • rhel-sst-network-management
    • ssg_networking
    • 5
    • Hide
      Customer Jira ID Case ID Status Details
      TPG Telecom Ltd
             		 RHEL-46904 03874656 The customer is seeing VLAN interfaces created over OVS internal interfaces becoming deactivated when attempting to bring up the OVS interface using nmcli. This occurs because the VLAN connection is blocked from autoconnecting after a failure and does not recover even when the parent interface becomes available again.
      A fix has been implemented and merged upstream and a RHEL 9.4 scratch build has been provided to the customer for testing in their OpenShift 4.16 environment. The next step is to confirm the fix with the customer and move forward this issues into Release Pending state.
      Show
      Customer Jira ID Case ID Status Details TPG Telecom Ltd   RHEL-46904 03874656 The customer is seeing VLAN interfaces created over OVS internal interfaces becoming deactivated when attempting to bring up the OVS interface using nmcli. This occurs because the VLAN connection is blocked from autoconnecting after a failure and does not recover even when the parent interface becomes available again. A fix has been implemented and merged upstream and a RHEL 9.4 scratch build has been provided to the customer for testing in their OpenShift 4.16 environment. The next step is to confirm the fix with the customer and move forward this issues into Release Pending state.
    • False
    • Hide

      None

      Show
      None
    • None
    • NMT - RHEL-9.5 DTM 24
    • Approved Blocker
    • Hide

      Given a system administrator has configured a VLAN over an OVS internal interface,

      When they execute nmcli c up ovs0-if to bring up the OVS internal interface connection,

      Then, the VLAN interface (ovs0.100) should remain activated and not be deactivated by NetworkManager.

      Definition of Done:

      • The implementation meets the acceptance criteria
      • Integration tests are written and pass
      • The code is part of a downstream build attached to an errata
      • The fix is backported into rhel-9.4
      Show
      Given a system administrator has configured a VLAN over an OVS internal interface, When they execute nmcli c up ovs0-if to bring up the OVS internal interface connection, Then, the VLAN interface (ovs0.100) should remain activated and not be deactivated by NetworkManager. Definition of Done: The implementation meets the acceptance criteria Integration tests are written and pass The code is part of a downstream build attached to an errata The fix is backported into rhel-9.4
    • Pass
    • None
    • None

      What were you trying to do that didn't work?

      With VLAN created over OVS internal interface, the `nmcli c up ovs0-if` will cause VLAN been deactivated.

      Please provide the package NVR for which bug is seen:

      NetworkManager-1.48.4-1.el9

      How reproducible:

      100%

      Steps to reproduce

       echo '---
interfaces:
- name: dummy1
  type: dummy
- name: ovs0
  type: ovs-interface
- name: br0
  type: ovs-bridge
  state: up
  bridge:
    port:
    - name: ovs0
    - name: dummy1
- name: ovs0.100
  type: vlan
  vlan:
    id: 100
    base-iface: ovs0' | sudo nmstatectl apply -
sudo nmcli c up ovs0-if
sudo nmcli c show

      Expected results

      The `ovs0.100` remain activated.

      Actual results

      The `ovs0.100` been deactivated.

        1. nm.log
          481 kB

              liangwen12year Wen Liang
              fge@redhat.com Gris Ge
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              1 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: