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

Nmstate should omit query only property in gen_diff output

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

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • rhel-10.2
    • nmstate
    • None
    • None
    • Low
    • rhel-net-mgmt
    • 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.

      None

      ( ) 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. None ( ) 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 applying this YAML with the query-only property `max-vfs`, nmstatectl shows the wrong `max-vfs` at the end as difference between pre-apply state and post-apply state.

      interfaces:
- name: ens3f0
  type: ethernet
  state: up
  ethernet:
    sr-iov:
      total-vfs: 2
      max-vfs: 1

      What is the impact of this issue to you?

      Cosmetic

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

      nmstate-2.2.59-0.20260204.2716gitd43f75c0.el9.x86_64.rpm

      How reproducible is this bug?:

      100%

      Steps to reproduce

      1. Find a SRIOV ready server
      2. Apply above YAML

      Expected results

      route-rules: {}
routes: {}
interfaces:
- name: ens3f0
  type: ethernet
  state: up
  ethernet:
    sr-iov:
      total-vfs: 2
      max-vfs: 1
ovn: {}

      Actual results

      route-rules: {}
routes: {}
interfaces:
- name: ens3f0
  type: ethernet
  state: up
  ethernet:
    sr-iov:
      total-vfs: 2
      max-vfs: 63
ovn: {}

              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: