Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-20413

[QE Epic] os-net-config conflict resolution verification between ifcfg and NetworkManager

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • rhos-18.0.14 FR 4
    • None
    • None
    • None
    • [QE Epic] os-net-config conflict resolution verification between ifcfg and NetworkManager
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • ?
    • ?
    • Done
    • RHOSSTRAT-660 - os-net-config should resolve conflicts between ifcfg and NM connections
    • ?
    • rhos-connectivity-nfv
    • ?
    • 33% To Do, 22% In Progress, 44% Done

      QE verification effort for os-net-config conflict resolution functionality between ifcfg and NetworkManager connections. Related to parent feature RHOSSTRAT-660.

      This task tracks the QE verification effort covering comprehensive testing scenarios for both ifcfg and nmstate providers to ensure proper conflict handling and resolution across various network configurations including bonds, bridges, teams, and VLANs.

      Test Areas:

      The basic idea of the verification will involve creation of various devices of types using cloud-init , ifcfg, nmcli commands

      • ethernet
      • linux bonds
      • ovs_bridge with/without ovs bonds
      • ovs_bridge with linux bonds
      • ovs_user_bridge without dpdk bonds
      • ovs_user_bridge with dpdk bonds
      • vlans on linux bonds, interfaces, ovs_bridge, ovs_user_bridge
      • sriov pf
      • sriov vf
      • All above cases with NIC partitioning

      Create a config.yaml to remove the devices by using the device names and types like below

      remove_config:
      - remove_type: linux_bond
        remove_name: bond_api
      - remove_type: sriov_vf
        remove_name: sriov:nic4:0
      - remove_type: sriov_vf
        remove_name: sriov:nic3:0
      - remove_type: sriov_pf
        remove_name: nic6
      - remove_name: br-link0
        remove_type: ovs_user_bridge
      - remove_name: dpdkbond0
        remove_type: ovs_dpdk_bond
      - remove_name: dpdk0
        remove_type: ovs_dpdk_port
      - remove_name: dpdk1
        remove_type: ovs_dpdk_port
      - remove_name: sriov:nic3:3
        remove_type: sriov_vf
      - remove_name: sriov:nic4:3
        remove_type: sriov_vf
      - remove_type: ovs_user_bridge
        remove_name: br-dpdk0
      - remove_type: ovs_dpdk_port
        remove_name: dpdk2
      - remove_type: interface
        remove_name: nic5 

      The config.yaml shall also include the network_config section.

      Run os-net-config with the remove_config of the required devices and then check if the device is removed. 

      Acceptance Criteria:

      The verification of the removal could be confirmed by checking for the absence of configured device in

      • nmcli c s
      • ls /etc/sysconfig/network-scripts/ifcfg-* 
      • ls /etc/sysconfig/network-scripts/route-* 
      • grep $device /var/lib/os-net-config/sriov_config.yaml
      • grep $device /var/lib/os-net-config/dpdk_mapping.yaml
      • grep $device /etc/udev/rules.d/80-persistent-os-net-config.rules

       

              rdiazcam@redhat.com Ricardo Diaz Campos
              arn1@redhat.com Abhiram R N
              rhos-dfg-nfv
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: