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

Apply route rules without priority twice, the rule priority increased

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • None
    • Low
    • rhel-net-mgmt
    • ssg_networking
    • 3
    • False
    • False
    • Hide

      None

      Show
      None
    • No
    • None
    • Hide

      Given a system administrator applying a route rule without an explicit priority via a rules.yaml configuration (See description)

      When they apply the rules.yaml configuration twice using nmstatectl.

      Then the priority of the applied route rule should remain consistent after both applications.

      Definition of done

      • The implementation meets the acceptance criteria
      • unit tests and integration tests are written and pass
      • The code is part of a build attached to an errata
      Show
      Given a system administrator applying a route rule without an explicit priority via a rules.yaml configuration (See description) When they apply the rules.yaml configuration twice using nmstatectl . Then the priority of the applied route rule should remain consistent after both applications. Definition of done The implementation meets the acceptance criteria unit tests and integration tests are written and pass The code is part of a build attached to an errata
    • None
    • Automated
    • If docs needed, set a value
    • None
    • 0

      Description of problem:
      Currently, apply route rules without priority, nmstate/NM set it as prioity 30000. When apply the same state twice, the prioiry will change to 30001. Repeat and it will change to 30002,30003, etc.

      Version-Release number of selected component (if applicable):
      nmstate-2.2.7-1.el9.x86_64
      nispor-1.2.10-1.el9.x86_64
      NetworkManager-1.42.2-1.el9.x86_64
      DISTRO=RHEL-9.2.0-20230314.47

      How reproducible:
      100%

      Steps to Reproduce:
      cat << EOF > rules.yaml
      route-rules:
      config:

      • ip-from: 8.8.8.8/24
        ip-to: 200.1.1.1/24
        route-table: 100
        routes:
        config:
      • destination: 0.0.0.0/0
        next-hop-interface: veth0
        next-hop-address: 100.1.1.254
        table-id: 100
        interfaces:
      • name: veth0
        type: veth
        state: up
        ipv4:
        enabled: true
        address:
      • ip: 100.1.1.1
        prefix-length: 24
        veth:
        peer: veth0_p
        EOF
        nmstatectl apply rules.yaml
        ip rule # 30000
        nmstatectl apply rules.yaml
        ip rule # 30001

      Actual results:
      0: from all lookup local
      1000: from all lookup [l3mdev-table]
      30001: from 8.8.8.0/24 to 200.1.1.0/24 lookup 100 proto static
      32766: from all lookup main
      32767: from all lookup default

      Expected results:
      Nothing changed

      Additional info:
      It comes from https://bugzilla.redhat.com/show_bug.cgi?id=1911397#c6, in the earlier version, nmstate won't change the priority.

              rh-ee-sfaye Stanislas Faye
              rh-ee-mshi1 Mingyu Shi
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: