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

Ironic API proxy pods crash loop if IPv6 is used

XMLWordPrintable

    • 1
    • Metal Platform 225
    • 1
    • Approved
    • False
    • Hide

      None

      Show
      None
    • NA

      Description of problem:

      METAL-256 introduced Ironic API proxy pods. The pods start with IPv4, but crash loop if IPv6 is used. Blocks Assisted ZTP flow (This was with converged flow DISABLED)
      
      
      [root@ocp-edge34 opt]# oc get pods -n openshift-machine-api
      NAME                                                  READY   STATUS             RESTARTS         AGE
      cluster-autoscaler-operator-85b7c7c69b-2wdh9          2/2     Running            2 (14h ago)      15h
      cluster-baremetal-operator-8555c9dc87-t5rm4           2/2     Running            0                15h
      control-plane-machine-set-operator-6c4f7fff6f-fts4p   1/1     Running            0                15h
      ironic-proxy-67wkh                                    0/1     CrashLoopBackOff   164 (108s ago)   13h
      ironic-proxy-9qg6h                                    0/1     CrashLoopBackOff   163 (106s ago)   13h
      ironic-proxy-hxft5                                    0/1     CrashLoopBackOff   164 (108s ago)   13h
      machine-api-controllers-6b4f47899b-7xqb8              7/7     Running            0                14h
      machine-api-operator-544587645d-9rv4m                 2/2     Running            0                15h
      metal3-7688b65d7f-kc2mg                               5/5     Running            0                13h
      metal3-image-cache-4w24m                              1/1     Running            0                14h
      metal3-image-cache-q7p54                              1/1     Running            0                14h
      metal3-image-cache-vhnkj                              1/1     Running            0                14h
      metal3-image-customization-5dcd9f4fb7-lpmrq           1/1     Running            0                13h
      

      Apache is used for the underlying proxy, and I believe the ipv6 address probably just needs to be surrounded in brackets to pass syntax.

      + python3 -c 'import os; import sys; import jinja2; sys.stdout.write(jinja2.Template(sys.stdin.read()).render(env=os.environ))'
      + exec /usr/sbin/httpd -DFOREGROUND
      AH00526: Syntax error on line 8 of /etc/httpd/conf.d/ironic-proxy.conf:
      ProxyPass Unable to parse URL: https://fd2e:6f44:5dd8::79:6388/
      
      Version-Release number of selected component (if applicable):
      OCP hub 4.12.0-ec.3
      2.2.0-DOWNANDBACK-2022-09-26-15-59-33
      

       

      How reproducible:
      100%
      

       

      Steps to Reproduce:
      

      1. Deploy ocp bm compact/HA cluster with ipv6
      2. Deploy MCE + Assisted Service
      3. Try to deploy a spoke via full ZTP

      Actual results:
      Spoke BMH on Hub cluster do nothing:
      mstat-0                 mstat-master-0-0-bmh                                                  true             10h
      mstat-0                 mstat-master-0-1-bmh                                                  true             10h
      mstat-0                 mstat-master-0-2-bmh                                                  true             10h
      mstat-0                 mstat-worker-0-0-bmh                                                  true             10h
      mstat-0                 mstat-worker-0-1-bmh                                                  true             10h
      
      

       

      Expected results:
      ZTP flow happens and spoke cluster deployed
      

       

      Additional info:
      

       

      
      

            rhn-engineering-dtantsur Dmitry Tantsur
            chadcrum Chad Crum
            Pedro Jose Amoedo Martinez Pedro Jose Amoedo Martinez
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: