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

additional network ignored on SingleStackIPv6 IPI installation

XMLWordPrintable

    • +
    • Important
    • None
    • ShiftStack Sprint 263
    • 1
    • Proposed
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Additional network is not correctly configured on the secondary interface inside the masters and the workers.

      With install-config.yaml with this section:

      # This file is autogenerated by infrared openshift plugin                                                                                                                                                                                                                                                                    
      apiVersion: v1                                                                                                                                                                                                                                                                                                               
      baseDomain: "shiftstack.local"
      compute:
      - name: worker
        platform:
          openstack:
            zones: []
            additionalNetworkIDs: ['26a751c3-c316-483c-91ed-615702bcbba9']
            type: "worker"
        replicas: 3
      controlPlane:
        name: master
        platform:
          openstack:
            zones: []
            additionalNetworkIDs: ['26a751c3-c316-483c-91ed-615702bcbba9']
            type: "master"
        replicas: 3
      metadata:
        name: "ostest"
      networking:
        clusterNetworks:
        - cidr: fd01::/48
          hostPrefix: 64
        serviceNetwork:
          - fd02::/112
        machineNetwork:
          - cidr: "fd2e:6f44:5dd8:c956::/64"
        networkType: "OVNKubernetes"
      platform:
        openstack:
          cloud:            "shiftstack"
          region:           "regionOne"
          defaultMachinePlatform:
            type: "master"
          apiVIPs: ["fd2e:6f44:5dd8:c956::5"]
          ingressVIPs: ["fd2e:6f44:5dd8:c956::7"]
          controlPlanePort:
            fixedIPs:
              - subnet:
                  name: "subnet-ssipv6"
      pullSecret: |
        {"auths": {"installer-host.example.com:8443": {"auth": "ZHVtbXkxMjM6ZHVtbXkxMjM="}}}
      sshKey: <hidden>
      additionalTrustBundle: <hidden>
      imageContentSources:
      - mirrors:
        - installer-host.example.com:8443/registry
        source: quay.io/openshift-release-dev/ocp-v4.0-art-dev
      - mirrors:
        - installer-host.example.com:8443/registry
        source: registry.ci.openshift.org/ocp/release
      

      The installation works. However, the additional network is not configured on the masters or the workers, which leads in our case to faulty manila integration.

      In journal of all OCP nodes, it's observed logs repeteadly like below one from the master-0:

      Nov 14 13:21:44 ostest-kmmtt-master-0 NetworkManager[1126]: <info>  [1731590504.9667] device (enp4s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
      Nov 14 13:21:44 ostest-kmmtt-master-0 NetworkManager[1126]: <warn>  [1731590504.9672] device (enp4s0): Activation: failed for connection 'Wired connection 1'
      Nov 14 13:21:44 ostest-kmmtt-master-0 NetworkManager[1126]: <info>  [1731590504.9674] device (enp4s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
      Nov 14 13:21:44 ostest-kmmtt-master-0 NetworkManager[1126]: <info>  [1731590504.9768] dhcp4 (enp4s0): canceled DHCP transaction
      Nov 14 13:21:44 ostest-kmmtt-master-0 NetworkManager[1126]: <info>  [1731590504.9768] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
      Nov 14 13:21:44 ostest-kmmtt-master-0 NetworkManager[1126]: <info>  [1731590504.9768] dhcp4 (enp4s0): state changed no lease
      

      Where that server has specifically an interface connected to the subnet "StorageNFSSubnet":

      $ openstack server list | grep master-0
      | da23da4a-4af8-4e54-ac60-88d6db2627b6 | ostest-kmmtt-master-0       | ACTIVE | StorageNFS=fd00:fd00:fd00:5000::fb:d8; network-ssipv6=fd2e:6f44:5dd8:c956::2e4            | ostest-kmmtt-rhcos                            | master    |
      

      That subnet is defined in openstack as dhcpv6-stateful:

      $ openstack subnet show StorageNFSSubnet
      +----------------------+-------------------------------------------------------+
      | Field                | Value                                                 |
      +----------------------+-------------------------------------------------------+
      | allocation_pools     | fd00:fd00:fd00:5000::fb:10-fd00:fd00:fd00:5000::fb:fe |
      | cidr                 | fd00:fd00:fd00:5000::/64                              |
      | created_at           | 2024-11-13T12:34:41Z                                  |
      | description          |                                                       |
      | dns_nameservers      |                                                       |
      | dns_publish_fixed_ip | None                                                  |
      | enable_dhcp          | True                                                  |
      | gateway_ip           | None                                                  |
      | host_routes          |                                                       |
      | id                   | 480d7b2a-915f-4f0c-9717-90c55b48f912                  |
      | ip_version           | 6                                                     |
      | ipv6_address_mode    | dhcpv6-stateful                                       |
      | ipv6_ra_mode         | dhcpv6-stateful                                       |
      | name                 | StorageNFSSubnet                                      |
      | network_id           | 26a751c3-c316-483c-91ed-615702bcbba9                  |
      | prefix_length        | None                                                  |
      | project_id           | 4566c393806c43b9b4e9455ebae1cbb6                      |
      | revision_number      | 0                                                     |
      | segment_id           | None                                                  |
      | service_types        | None                                                  |
      | subnetpool_id        | None                                                  |
      | tags                 |                                                       |
      | updated_at           | 2024-11-13T12:34:41Z                                  |
      +----------------------+-------------------------------------------------------+
      

      I also compared with ipv4 installation, and the storageNFSsubnet IP is successfully configured on enp4s0.

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

      • 4.18.0-0.nightly-2024-11-12-201730,
      • RHOS-17.1-RHEL-9-20240701.n.1

      How reproducible: Always
      Additional info: must-gather and journal of the OCP nodes provided in private comment.

              mdemaced Maysa De Macedo Souza
              rlobillo Ramón Lobillo
              Itshak Brown Itshak Brown
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: