Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-18279

Bonded IPv6-only spoke install fails on dual stack hub with proxy.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • ACM 2.12.2
    • False
    • Hide

      None

      Show
      None
    • False
    • Important
    • None

      Description of problem:

      An ACM dual-stack hub is failing to install an IPv6-only, bonded spoke cluster in a proxied environment.
          

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

      Hub: 
      OCP: 4.16.30
      ACM: 2.12.2
      MCE: 2.7.3
          

      How reproducible:

      Not here with KVM hosts, but the customer is using bare metal.  They are also using a Cilium CNI.
          

      Steps to Reproduce:

          1.  On a dual stack 4.16 hub cluster, an attempt is made to install an IPv6-only spoke cluster.
          2.  Use ZTP manifests with the SiteConfig specifying interface bonding.
          3.  Inspection passes but host installation fails.
          

      Actual results:

      Inspection passes and host installation begins, but fails due to image pull failures reaching a public IPv6 address, hence not using proxy info.
          

      Expected results:

      Installation pulls images and succeeds.
          

      Additional info:

      - A dual-stack spoke installation in this environment is successful.
      - Sosreport data from the bootstrap indicate the proper proxy environment variables present.  The podman process running has them correctly, however CRI-O does not.
      
      
          

              ncarboni@redhat.com Nick Carboni
              rhn-support-cshepher Christine Shepherd
              Vladislav Kolodny Vladislav Kolodny
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: