| 2023-11-28 14:31:12 |
Federico Bosi |
description |
On MAAS 3.4-RC1, I configured a subnet my:prefix:141::/80.
The rack controller has address my:prefix:141::rack.
MAAS correctly hands out DHCPv6 addresses but when the image boots, the cloud-config-url kernel parameter has the rack's ip without square brackets (see attachment) and fails saying it cannot parse the url as the added port makes in invalid.
The host then fails to enlist sayng that no datasource can be found.
If in the custom kernel parameter I override it by adding
`cloud-config-url="http://[my:prefix:141::rack]:5248/MAAS/metadata/latest/enlist-preseed/?op=get_enlist_preseed"` the node enlists successfully. |
On MAAS 3.4-RC1, I configured a subnet my:prefix:141::/80.
The rack controller has address my:prefix:141::rack.
MAAS correctly hands out DHCPv6 addresses but when the image boots, the cloud-config-url kernel parameter has the rack's ip without square brackets (see attachment) and fails saying it cannot parse the url as the added port makes in invalid.
The host then fails to enlist saying that no datasource can be found.
If in the custom kernel parameters I override it by adding
`cloud-config-url="http://[my:prefix:141::rack]:5248/MAAS/metadata/latest/enlist-preseed/?op=get_enlist_preseed"` the node enlists successfully. |
|
