Comment 1 for bug 1915050

Revision history for this message
Ghada Khalil (gkhalil) wrote :

Adding investigation by Don Penney:
The nodes are installing fine, and the kickstarts are generating initial network-scripts with BOOTPROTO=dhcp. On the initial boot of the node post-install, the interface configuration is then done via DHCP.

The DHCP package was recently upversioned, Jan 22, from 4.2.5-68 to 4.2.5-82:
https://review.opendev.org/c/starlingx/integ/+/771752
https://review.opendev.org/c/starlingx/tools/+/771744 (dependeny update)

Perhaps something in this update is resulting in the resulting DHCP address having /128