[BUG] Unable to detect boot params during PXE boot

[abhishek-sa1]

Describe the bug
I have 3 nodes and in 2 of the nodes boot params are reflecting in ochami commands and not listing in the curl query.

curl "[http://10.15.0.1:8081/boot/v1/bootscript?mac=xx:3f:72:f7:98:xx"](http://10.15.0.1:8081/boot/v1/bootscript?mac=04:3f:72:f7:98:32%22)
#!ipxe
sleep 10
chain https://${SYSTEM_URL}/apis/bss/boot/v1/bootscript?mac=xx:3f:72:f7:98:xx&arch=${buildarch}

To Reproduce
Steps to reproduce the behavior:
Deploy openchami and configure the the BSS.

Expected behavior
Boot params should be configured properly.

Screenshots

Servers (please complete the following information):

• OS: RHEL
• Version 10

[alexlovelltroy]

looks like SYSTEM_URL isn't being replaced. Where are you setting it?

[abhishek-sa1]

Identified the issue, if we increase the digit after index n, PXE boot fails. We need to fix n0 always for dell servers

[erl-hpe]

I just ran into this issue in my OpenCHAMI on vTDS work as well. On vTDS the XNAMEs are meaningful (at least for now) as they are on HPE/Cray systems and the n<index> term identifies the node index under the control of a given BMC (the b<index>) term. Being able to support systems where a single BMC controls multiple nodes, and where the BMC is identified by the XNAME is going to be an important use case, at least for the immediate future, so not supporting node indices greater than 0 will be a real problem. I would like to re-open this issue to address that problem.

[alexlovelltroy]

We think this is at least partially related to ochami #55