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

[RFE] Support retry upon missing interface

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

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • rhel-9.6
    • nmstate
    • None
    • No
    • None
    • rhel-net-mgmt
    • ssg_networking
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • 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 sysadmin managing a host where the VLAN parent (e.g., a VRF device) is managed by a separate orchestrator such as OVN and is not yet available at the time of NNCP application,

      When Nmstate applies a desired state that includes a VLAN over the to-be-created interface,

      Then Nmstate must attempt retries with a backoff strategy for a configurable duration before failing, allowing successful application once the parent device appears, thereby avoiding unnecessary NNCP failure due to orchestration race conditions.


      ( ) Integration test case is available upstream.


      ( ) Code is reviewed and merged upstream.


      ( ) Preliminary testing is done.


      ( ) Upstream documentation is written in the upstream MR.


      ( ) Release notes text is written in the RHEL issue.


      ( ) A demo is recorded

      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 sysadmin managing a host where the VLAN parent (e.g., a VRF device) is managed by a separate orchestrator such as OVN and is not yet available at the time of NNCP application, When Nmstate applies a desired state that includes a VLAN over the to-be-created interface, Then Nmstate must attempt retries with a backoff strategy for a configurable duration before failing, allowing successful application once the parent device appears, thereby avoiding unnecessary NNCP failure due to orchestration race conditions. ( ) Integration test case is available upstream. ( ) Code is reviewed and merged upstream. ( ) Preliminary testing is done. ( ) Upstream documentation is written in the upstream MR. ( ) Release notes text is written in the RHEL issue. ( ) A demo is recorded
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

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

      When a NNCP in openshift-nmstate is attaching port to a VRF but the VRF is created by OVN, nmstate will fails with error `Interface eth1 desired controller vrf0 not found` because OVN might starts after openshift-nmstate operator. Instead of failing NNCP, nmstate should keep retrying on missing interfaces.

      What is the impact of this issue to you?

      NNCP attach port to VRF controlled by OVN.

      Please provide the package NVR for which the bug is seen:

      nmstate-2.2.44-1.el9

      How reproducible is this bug?:

      100%

      Steps to reproduce

      1. Use nmstate to attach an interface to non-exist VRF interface via `controller` property with options introduced by this RFE
      2. Open another terminal, create the VRF by ip command.

      Expected results

      Port attached to VRF after it been created.

      Actual results

      Nmstate fails with error.

              nm-team Network Management Team
              fge@redhat.com Gris Ge
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: