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

Improve interface activation logic in NetworkManager

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • NetworkManager-1.53.3-1.el10
    • Moderate
    • 1
    • rhel-net-mgmt
    • ssg_networking
    • 5
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • NMT SST - 2025Q2
    • Hide

      Definition of Done:

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.

      Given a system administrator is configuring an OVS interface on a host,

      When the network is brought up and the OVS database is not yet fully ready,

      Then NetworkManager must avoid activating the OVS interface until ovsdb->ready is set to TRUE, preventing race conditions and orphaned interfaces, and automatically re-check and activate the OVS interface once OVSDB is ready. 

      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

      ( ) Code changes are included in a downstream build attached to an errata.


      ( ) All required testing (manual and/or automated) passes successfully.


      ( ) Related documentation updates (if applicable) have been completed.

      Show
      Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. Given a system administrator is configuring an OVS interface on a host, When the network is brought up and the OVS database is not yet fully ready, Then NetworkManager must avoid activating the OVS interface until ovsdb->ready is set to TRUE, preventing race conditions and orphaned interfaces, and automatically re-check and activate the OVS interface once OVSDB is ready.  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 ( ) Code changes are included in a downstream build attached to an errata. ( ) All required testing (manual and/or automated) passes successfully. ( ) Related documentation updates (if applicable) have been completed.
    • Pass
    • Automated
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      Based on this upstream discussions: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2139  NetworkManager should not prematurely consider OVS interfaces “available” when ovsdb->ready is not yet set to TRUE, but must still allow non-OVS devices (like physical ports in a bond) to activate even if their carrier is down initially. This ticket aims to refine the activation process so OVS interfaces wait until OVSDB is ready while still handling other device types correctly.

              rhn-engineering-vbenes Vladimir Benes
              rh-ee-sfaye Stanislas Faye
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: