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

IgnitionServer proxy configuration is not ready for IPv6

XMLWordPrintable

    • No
    • Hypershift Sprint 238
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      When you have a HCP running and it's creating the HostedCluster pods it renders this IgnitionProxy config:
      
      defaults
        mode http
        timeout connect 5s
        timeout client 30s
        timeout server 30s
      
      frontend ignition-server
        bind *:8443 ssl crt /tmp/tls.pem
        default_backend ignition_servers
      
      backend ignition_servers
        server ignition-server ignition-server:443 check ssl ca-file /etc/ssl/root-ca/ca.crt
      
      This Configuration is not supported on Ipv6 causing the worker nodes to fail downloading the Ignition Payload

       

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

      MCE 2.4
      OCP 4.14

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create a HostedCluster with the networking parameters set to IPv6 networks.
      2. Check the IgnitionProxy config using: 
      
      oc rsh <pod>
      cat /tmp/haproxy.conf

      Actual results:

      Agent pod in the destination workers fails with:
      
      Jul 26 10:23:44 localhost.localdomain next_step_runne[4242]: time="26-07-2023 10:23:44" level=error msg="ignition file download failed: request failed: Get \"https://ignition-server-clusters-hosted.apps.ocp-edge-cluster-0.qe.lab.redhat.com/ignition\": EOF" file="apivip_check.go:160"

      Expected results:

      The worker should download the ignition payload properly

      Additional info:

      N/A

              jparrill@redhat.com Juan Manuel Parrilla Madrid
              jparrill@redhat.com Juan Manuel Parrilla Madrid
              Liangquan Li Liangquan Li
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: