Contrail sets 'siaddr' field in DHCP reply to address of TSN node. According to rfc2131 https://www.ietf.org/rfc/rfc2131.txt 'siaddr' is recognized by PXE client as tftp server to boot from, even when option 66 tftp-server-name is set. The good explanation of 'siaddr' field is in https://tools.ietf.org/html/rfc5859
It leads to failed deployment of Baremetal node which doesn't support IPXE. IPXE doesn't use 'siaddr' or option 66. It use only option 67 - which is direct http or ftp link.
To fix this we need to either:
* drop setting siaddr field in DHCP reply ('siaddr' is optional field)
* try to copy value from option 66 - tftp-server-name, may not work when we set dns name as 'siaddr' is address field.
Contrail sets 'siaddr' field in DHCP reply to address of TSN node. According to rfc2131 https:/ /www.ietf. org/rfc/ rfc2131. txt 'siaddr' is recognized by PXE client as tftp server to boot from, even when option 66 tftp-server-name is set. The good explanation of 'siaddr' field is in https:/ /tools. ietf.org/ html/rfc5859
It leads to failed deployment of Baremetal node which doesn't support IPXE. IPXE doesn't use 'siaddr' or option 66. It use only option 67 - which is direct http or ftp link.
To fix this we need to either:
* drop setting siaddr field in DHCP reply ('siaddr' is optional field)
* try to copy value from option 66 - tftp-server-name, may not work when we set dns name as 'siaddr' is address field.