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

Cannot create multiple VLAN ingress/egress QoS mapping

XMLWordPrintable

    • NetworkManager-1.51.6-1.el9
    • No
    • Important
    • rhel-sst-network-management
    • ssg_networking
    • 3
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Hide

      Given a system administrator managing a system that requires VLAN interfaces with multiple ingress and egress QoS mappings,

      When they configure a VLAN interface using NetworkManager with specific mappings (e.g., 2:2 3:3 for both ingress and egress),

      Then NetworkManager should correctly apply and reflect the configured mappings in the system, such that the output of ip -d link show <interface> displays both the ingress and egress QoS mappings as specified.

      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
      Show
      Given a system administrator managing a system that requires VLAN interfaces with multiple ingress and egress QoS mappings, When they configure a VLAN interface using NetworkManager with specific mappings (e.g., 2:2 3:3 for both ingress and egress), Then NetworkManager should correctly apply and reflect the configured mappings in the system, such that the output of ip -d link show <interface> displays both the ingress and egress QoS mappings as specified. 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
    • Requested
    • None
    • None

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

      NetworkManager cannot create multiple VLAN QoS mapping with property

      vlan.egress-priority-map "2:2 3:3"

      or

      vlan.ingress-priority-map "2:2 3:3"

      What is the impact of this issue to you?

      It is common to have multiple QoS mapping for VLAN.

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

      NetworkManager-1.51.5-33642.copr.83d99669f5.el9.x86_64

      How reproducible is this bug?:

      100%

      Steps to reproduce

      sudo nmcli c add type vlan ifname eth1.100 \
    connection.id eth1.100 ipv4.method disabled ipv6.method disabled \
    vlan.parent eth1 vlan.id 100 vlan.egress-priority-map "2:2 3:3" \
    vlan.ingress-priority-map "2:2 3:3"
sudo nmcli c up eth1.100
ip -d link show eth1.100

      Expected results

      [fge@c9s ~]$ sudo ip -d link show eth1.100
9: eth1.100@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:23:45:67:89:1a brd ff:ff:ff:ff:ff:ff promiscuity 0  allmulti 0 minmtu 0 maxmtu 65535
    vlan protocol 802.1Q id 100 <REORDER_HDR>
      ingress-qos-map { 2:2 3:3 }
      egress-qos-map { 2:2 3:3 } addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 tso_max_size 524280 tso_max_segs 65535 gro_max_size 65536

      Actual results

      Only egress-qos-map

      { 3:3 }

      found in ip link output, and ingress-qos map is empty.

              rh-ee-jvaclav Ján Václav
              fge@redhat.com Gris Ge
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: