Node deployment failed due to WWN [tinyipa]

Greetings!

The difference is in large part block device utilities we utilize to collect that data, where in TinyIPA they have a number of limitations which can reflect in ways such as this. TinyIPA is also only intended for CI testing of ironic, and should never be used for physical baremetal deployment.

You *really* should be building an IPA image or using non-tinyipa built image. For example https://tarballs.opendev.org/openstack/ironic-python-agent/dib/ipa-centos9-master.tar.gz is Centos9 based and should work for you.

When you say if you build a custom image, it takes 12 minutes to deploy. Can you provide us some details? We've seen some issues in the past with hosts where numerous network interfaces can take a long time to resolve for network connectivity. If you can breakdown what is taking so long with the overall host, we might be able to help provide a solution.

-Julia

Hey Thank you so much Julia, So lets eliminate TinyIPA part, its of no use for Baremetal, so lets eliminate.

The other major part its taking time to deploy around 12min.

And as I said here,

* If I use custom IPA images build with [1],
* and corresponding generated images [2],
* I am able to provision the baremetal node.

* Only the case I do see is
  A) ipa.initramfs is almost 1G in size.
  B) And slowness in deployment, [scans all hardware and then report back, slowing down]
  c) DHCP for all networks,
* Here is my <>.json file that I am using for enrolment. [3]

* So my observation is/was during deployment it scans all interfaces and take long to resolve the network connectivity, Even I had modify the image and modify the interfaces file to DHCP on only 1 network, but as initramfs is doing scan before qcow2 directsync it hung up thr for almost 2/3 min.

[1]
~~~
ironic-python-agent-builder -o ironic-python-agent ironic-python-agent-ramdisk --release jammy ubuntu
~~~

[2]
~~~
()[root@spare httpboot]# ls -lhrt ubu_ipa/
total 983M
-rw-r--r-- 1 root root 971M May 9 05:52 ipa.initramfs
-rw-r--r-- 1 ironic ironic 12M May 9 05:52 ipa.kernel
-rw-r--r-- 1 root root 94 May 9 07:27 ipa.kernel.sha256
-rw-r--r-- 1 root root 96 May 9 07:28 ipa.initramfs.sha256
()[root@spare httpboot]#
~~~

[3]
~~~
{
    "baremetal1": {
      "name": "baremetal1",
      "driver": "ipmi",
      "driver_info": {
        "ipmi_address": "172.29.xxx.30",
        "ipmi_port": "623",
        "ipmi_username": "xxxxx",
        "ipmi_password": "xxxxx"
      },
      "ipv4_address": "172.xx.xxx.15",
      "ipv4_subnet_mask": "255.255.255.0",
      "ipv4_gateway": "172.xx.xxx.1",
      "ipv4_nameserver": "172.xx.xx.47",
      "inventory_dhcp": true,
      "nics": [
        {
          "mac": "14:23:f2:79:2b:xx"
        }
      ],
      "properties": {
        "cpu_arch": "x86_64",
        "root_device": {"wwn": "0x600062b2169e51002d719a7648740109"}
      },
      "instance_info": {
        "image_source": "http://172.29.xx.30:8080/mini-jammy.qcow2",
        "image_checksum": "eb1b8264b4d0403d6e276eebe9b6c014",
        "configdrive": {
          "meta_data": {
            "hostname": "baremetal_001.xxxxx.lan"
          }
        }
      }
    }
}
~~~

@ironic team, any update please, let me know if you need logs from ironic.

I just tweak the change:

~~~
./usr/local/sbin/dhcp-all-interfaces.sh
~~~

~~~
#!/bin/bash
interfaces=$(ls /sys/class/net/ | grep -v lo)
first_interface=$(echo "$interfaces" | head -n1)
dhclient -v "$first_interface"
~~~

~~~
find . | cpio -o -H newc | gzip > ipa.initramfs
~~~

Able to perform introspection. Saved a lot of time.

Thanks,

Nilesh, can you confirm you issue was fixed? Thanks! I'm marking the bug as triaged and low priority since you mentioned you were able to perform introspection.

Thank you