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

nmstatectl show stuck forever

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

    • nmstate-2.2.45-1.el10
    • No
    • Low
    • ZStream
    • rhel-net-mgmt
    • ssg_networking
    • 3
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Approved Blocker
    • 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 running an OpenShift cluster or RHEL and they invoke nmstatectl show,

      When OVSDB produces a response whose size is exactly a multiple of 4096 bytes and Nmstate attempts to read the response from the OVSDB JSON-RPC socket,

      Then, Nmstate should properly detect the end of the message and complete the response parsing,
      and must not hang indefinitely.

      ( ) 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.

      ( ) All necessary backports to the related RHEL streams (linked as 'relates' in this issue) have been completed and verified.

      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 running an OpenShift cluster or RHEL and they invoke nmstatectl show, When OVSDB produces a response whose size is exactly a multiple of 4096 bytes and Nmstate attempts to read the response from the OVSDB JSON-RPC socket, Then, Nmstate should properly detect the end of the message and complete the response parsing, and must not hang indefinitely. ( ) 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. ( ) All necessary backports to the related RHEL streams (linked as 'relates' in this issue) have been completed and verified.
    • Pass
    • Automated
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      When applying this YAML on empty OVSDB node, `nmstatectl apply` stuck.

      ---
interfaces:
- name: ovs1
  type: ovs-interface
  state: up
  ovs-db:
    external_ids:
      a: 1
      b: 2
      c: 3
      d: 4
      f: 4
- name: br0
  type: ovs-bridge
  state: up
  bridge:
    port:
     - name: ovs1
     - name: ovs2
     - name: ovs3
     - name: ovs4
     - name: ovs5
     - name: ovs6
     - name: ovs7
     - name: ovs8
     - name: ovs9
     - name: ovs10
     - name: ovs11
     - name: ovs12
     - name: ovs13
     - name: ovs14
     - name: ovs15
     - name: ovs16
     - name: ovs17

              nm-team Network Management Team
              fge@redhat.com Gris Ge
              se-network management se-network management
              Network Management Team Network Management Team
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: