So resource parameters are generally 0 because you're consuming a whole baremetal node when you deploy one. In regards to pxe, Ironic does not set up a PXE server, it manages files in a folder which should be available by a PXE server you configure. Kolla should be doing that for you, as far as I'm aware. Generally it sounds like a networking issue, like maybe the baremetal node is not attached to the right interface or neutron namespace. I would likely start by trying to make sure you can see the PXE traffic being originated by the baremetal nodes from the neutron qrouter dhcp namespace, and then beginning to troubleshoot from that point of view since a machine hanging at a "Start PXE" prompt generally means it is not getting a DHCP response. -Julia On Thu, Feb 15, 2024 at 10:40 AM Jayesh Chaudhari < jayesh.chaudhari1990@gmail.com> wrote:

Hi Julia,

Thank you for putting light on interfaces thing. To answer your question, yes my nova-compute can see my baremetal node. But all resource parameters are showing value set to 0.

Also when I am trying to create nova server it was unable to pxeboot server, it stuck over ">>Start PXE over IPv4." In logs I can not see ironic-tftp log. I am following the below workflow.

[image: ironic-workflow.png]

Thanks, Jayesh

On Thu, Feb 15, 2024 at 7:51 PM Julia Kreger <juliaashleykreger@gmail.com> wrote:

...

Greetings,

The ipmi hardware is loaded based upon your enable_$INTERFACE-TYPE_interfaces parameters in ironic.conf. If not specifically configured, and only the hardware type is set, the result is a union of what is available based upon the configuration, unless an explicit default is set on the node.

It is entirely possible to have a node without a console, bios, inspect, raid, or rescue interfaces. You need "boot", "deploy", and "management" interfaces in working order. In the case you noted, you don't have an image_source being populated from nova to signal what instance image to utilize. This is normal for an unscheduled node.

So the question is, is nova-compute, which needs to be configured for ironic, able to see the node. I would consult nova-compute.log, and see if it sees the node. It might be that the node is lacking a "resource_class", which is an explicit requirement for nova to be aware of it.

Hope that helps,

-Julia

On Wed, Feb 14, 2024 at 10:44 PM Jayesh Chaudhari < jayesh.chaudhari1990@gmail.com> wrote:

...

Hi All,

I am following the below document for implementing Ironic in my Kolla-Ansible Cloud which is on yoga version.

https://docs.openstack.org/kolla-ansible/yoga/reference/bare-metal/ironic-gu...

I can add a baremetal node with this in the "baremetal node list" and make it available. But when I am trying to create a nova server it fails trying to find the host. I tried to troubleshoot and find that "openstack baremetal node validate <nodeid>" command shows 1. bios - Driver ipmi does not support bios (disabled or not implemented) 2. console - Driver ipmi does not support console (disabled or not implemented) 3. deploy - Node failed to validate deploy image info. Some parameters were missing. Missing are ['instance_info.image_source'] 4. inspect - Driver ipmi does not support inspect (disabled or not implemented) 5. raid - Driver ipmi does not support raid (disabled or not implemented) 6. rescue - Driver ipmi does not support rescue (disabled or not implemented)

Can you please guide me with documentation for setting these options. Or correct me if I am missing anything. Also above documents show steps to create deploy-vmlinuz and deploy-initrd only. Please guide me for steps creating deploy_kernel and deploy_ramdisk.

Thanks, Jayesh