Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-10368

NMstate at day1 not interpreting wait-ip setting

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • No
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      NMstate "wait-ip" setting is not interpreted as may-fail in NM connection files.
      

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

      4.12.Z
      

      How reproducible:

      Always reproduce in IPv4 or IPv6
      

      Steps to Reproduce:

      1. Prepare the install-config.yaml (attached) with NMstate settings
      2. Deploy the cluster using baremetal IPI
      3. Verify the generated <interface>.nmconnection files in the nodes
      

      Actual results:

      *wait-ip*: setting does not includes the respective *may-fail* setting in   <interface>.nmconnection files
      

      Expected results:

      *wait-ip*: setting should include a respective *may-fail* setting in   <interface>.nmconnection files
      

      Additional info:

      We are using NMstate settings like this in the install-config.yaml for each node:

      interfaces:
      - ipv4:
          auto-dns: true
          dhcp: true
          enabled: true
        ipv6:
          auto-dns: true
          dhcp: true
          enabled: true
        link-aggregation:
          mode: 802.3ad
          options:
            miimon: 100
          port:
          - ens1f0
          - ens1f1
        mtu: 9000
        name: bond0
        state: up
        wait-ip: ipv4+ipv6
        type: bond
      

      From a deployed node we see it generates the bond0.nmconnection file but there are no may-fail=false options in the [ipv4] or [ipv6] sections

      [core@master-0 ~]$ sudo cat /etc/NetworkManager/system-connections/bond0.nmconnection                                                           
      [connection]                                                                
      id=bond0                                                                    
      uuid=3b5e4e76-94a5-4c45-9e31-09d3b20a38f5                               
      type=bond                                                               
      autoconnect-slaves=1                                                                     
      interface-name=bond0                                                                     
                                                                                                                                                                      
      [ethernet]                                                                                                                                             
      mtu=9000                                                                                                                                               
                                                                                                                                                             
      [bond]                                                                                                                                                 
      miimon=100                                                                                                                                             
      mode=802.3ad
      
      [ipv4]
      dhcp-timeout=2147483647
      method=auto
      
      [ipv6]
      addr-gen-mode=eui64
      dhcp-iaid=mac
      dhcp-timeout=2147483647
      method=dhcp
      ra-timeout=2147483647
      

      When using nmstatactl from the CLI in a Fedora laptop, we see the wait-ip options generates a may-fail=false in the [ipv4] and [ipv6] sections, so probably the OCP 4.12 images are using an old version of nmstatectl ?

      $ rpm -qf $(which nmstatectl)
      nmstate-2.2.5-1.fc37.x86_64
      
      $ nmstatectl gc bonding-integration/nmstate/cluster6-vanilla-dualstack.yaml 
      [2023-03-15T20:54:20Z WARN  nmstate::ifaces::inter_ifaces] Assuming undefined port ens1f0 as ethernet
      [2023-03-15T20:54:20Z WARN  nmstate::ifaces::inter_ifaces] Assuming undefined port ens1f1 as ethernet
      NetworkManager:
      - - bond0.nmconnection
        - |
          [connection]
          autoconnect=true
          autoconnect-slaves=1
          id=bond0
          interface-name=bond0
          type=bond
          uuid=925b4a95-2de0-5b2d-bcf5-8b684a7e9cb4
      
          [bond]
          miimon=100
          mode=802.3ad
      
          [ipv4]
          dhcp-client-id=mac
          dhcp-timeout=2147483647
          ignore-auto-dns=false
          ignore-auto-routes=false
          may-fail=false
          method=auto
          never-default=false
      
          [ipv6]
          addr-gen-mode=0
          dhcp-duid=ll
          dhcp-iaid=mac
          dhcp-timeout=2147483647
          ignore-auto-dns=false
          ignore-auto-routes=false
          may-fail=false
          method=dhcp
          never-default=false
          ra-timeout=2147483647
      
          [ethernet]
          mtu=9000
      
      

              bnemec@redhat.com Benjamin Nemec
              rhn-gps-manrodri Manuel Rodriguez
              None
              None
              Qiong Wang Qiong Wang
              None
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: