ussuri baremetal hci deployment, overcloud iPXE looping

[Tsvetomir Penchev]

I am trying to install openstack container based ussuri on 3 controllers and 2 HCI nodes. Controller nodes are VMs, and HCI nodes are HPE DL380 Gen10 servers.

Introspection passed without problems, but when I try to deploy overcloud, baremetal machines can not pass iPXE section. Attached screenshots from introspection and deployment.

I was looking on folders and logs but I am not familiar with all processes and steps. Mainly I can see that during deployment filename which is processed is undionly.kpxe when during introspection it is inspector.ipxe

Images are buld on-the-fly. Attached some execution commands and screenshots

I can provide specific information from logs or undercloud folders.
Have tcpdump also but is too big and don't know what to look for..

[Tsvetomir Penchev (tspenchev)]

undercloud info

[Tsvetomir Penchev (tspenchev)]

Someone can share, based on what information below rows are generated for dnsmasq process?
Seems that there is difference between controller and computehci nodes maybe this is the reason for failing iPXE detection and providing different filename for computehci nodes.

tag:port-4ad60ae6-f484-48f3-b32f-095da408736d,150,10.96.213.145
tag:port-4ad60ae6-f484-48f3-b32f-095da408736d,66,10.96.213.145
tag:port-4ad60ae6-f484-48f3-b32f-095da408736d,option:server-ip-address,10.96.213.145
tag:port-4ad60ae6-f484-48f3-b32f-095da408736d,tag:!ipxe,67,undionly.kpxe
tag:port-4ad60ae6-f484-48f3-b32f-095da408736d,tag:ipxe,67,http://10.96.213.145:8088/boot.ipxe

(also attached some info from deployment)