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

[s390x] : ABI Day2 operation fails with Unable to pull Ignition content error.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.17
    • None
    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of the problem:

      Trying ABI Day2 operation and Its unable to pull ingnition image.

      How reproducible:

       

      Steps to reproduce:

      1. Deploy an ABI HA cluster

      2. Prepare nodes-config.yaml file to add an additional node for day2 operation

      3. create nodes-s390x image (follow the steps here) https://github.com/openshift/installer/blob/master/docs/user/agent/add-node/add-nodes.md

      Actual results:

      Its not able to fetch ignition which second boot and gives below error in assisted-service logs.

      level=warning msg="Ignition is empty or invalid - can't get disk encryption" func=github.com/openshift/assisted-service/internal/host/hostutil.GetDiskEncryptionForDay2 file="/> time="2024-07-30T06:31:05Z" level=warning msg="Failed to generate steps for command *hostcommands.tangConnectivityCheckCmd" func="github.com/openshift/assisted-service/internal/host/hostcommands.(*Instru>

      Api server http://api.agent.abisno.com:22624/config/worker ,  is not working for IPV4.
      But with ipv6 we are getting response. Also while performing netstat we can see 22624 is enabled only for tcp6 only.

      $ sudo netstat -anp | grep 22624 tcp6 0 0 :::22624 :::* LISTEN 5901/machine-config

      Response for ipv4
       

      $ curl http://api.agent.abisno.com:22624/config/worker curl: (7) Failed to connect to api.agent.abisno.com port 22624: Connection refused 
      $ curl http://127.0.0.1:22624/config/worker -O % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:decrement:-- --:decrement:-- --:decrement:-- 0 curl: (7) Failed to connect to 127.0.0.1 port 22624: Connection refused

      When we tried the same with ipv6 on localhost, got this response.
       

      curl http://[::1]:22624/config/worker {"ignition":{"version":"2.2.0"},"passwd":{"users":[{"name":"core" ****
       
      

       

      Expected results:

      Additional Node should get attached

              jpoulin Jeremy Poulin
              dveerabh@redhat.com Neeraj Mishra
              Manoj Hans Manoj Hans
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: