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

nmstatectl gc mode does not support blackhole routes

    • nmstate-2.2.36-1.el9
    • No
    • Moderate
    • ZStream
    • 1
    • rhel-sst-network-management
    • ssg_networking
    • 1
    • False
    • Hide

      None

      Show
      None
    • None
    • NMT - RHEL-9.6/RHEL 10 DTM 2
    • Approved Blocker
    • None

      Description of problem:

      Upon trying to add a blackhole route while creating a 3 node cluster using agent based installer, the installation does succeed, but the route does not get added on the nodes. The issue is observed on openshift version 4.15.10. The blackhole routes mentioned in the agent-config.yaml file is as below.
      
      ~~~
      routes:
              config:
                - destination: 0.0.0.0/0
                  next-hop-address: x.x.x.x
                  next-hop-interface: ens192
                - destination: x.x.x.x/16
                  route-type: blackhole
      ~~~
      
      The cluster does get installed successfully with this set of networking configurations, but the route does not get added.

      Version-Release number of selected component (if applicable):

          

      How reproducible:

      Attempt to install a cluster using agent based installer with version 4.15.10 by adding the blackhole route in the agent-config.yaml file.

      Steps to Reproduce:

      1. Create a agent-config file with the blackhole route added along with install-config file 
      2. Boot the master nodes with the agent iso.
      3. After the install completes, check the routes in the master nodes. The route would not be present.
          

      Actual results:

      The installation goes succeed but the route does not get added. 

      Expected results:

      The blackhole route should get added at install time.

      Additional info:

      - The support for the `route-type` field has been added in nmstate 2.2.20 version. Hence, the openshift 4.15.10 was tried as version 4.15.10 has nmstate version 2.2.23.
      
      - I was able to replicate the issue our lab environment. The .nmconnection files does not have any details of the blackhole route provided in agent-config file. The drive link below has the details of command output of nmconnection file and ip route.
      
      Drive Link - https://docs.google.com/document/d/1bZC-OSsu2ss6H9JA8FJamec9hpdofAa1t3oHYFEpJrg/edit?usp=sharing
      
      - Agent config file used by the customer. Same was used in my replication attempt. 
      
      Drive Link - https://drive.google.com/file/d/1C8IMQ5W--WIEvZmfgRHAJleoTeq6z8MY/view?usp=drive_link
      
      - I was able to gather a agent-gather from my rendezvous host once the installation starts. There is a nmstateconfig.yaml file having the details of the blackhole route, but the ens192.nmconnection file does not have any details of the route. The below drive link has the agent-gather. 
      
      Drive Link - https://drive.google.com/file/d/1vis6XheJ4kW4cyjfGJ_W3iRVauax3T08/view?usp=sharing
      
      

              fge@redhat.com Gris Ge
              rhn-support-adikulka Aditya Kulkarni
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated: