Don't use dhcp4 for none mode #6001
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the context, we had an strange behavior where an host installed with IPv6 stack only got an Ipv4 address only during the first boot due to the start of a systemd service called chrony-wait. This is because during the first boot the xcp-networkd looks for a configuration from
/etc/firstboot.d/data/management.conf
and if theMODE=none
it uses DHCP4. And as chrony-wait is started it got a source in IPv4 before XAPI had time to reconfigure it using IPv6 stack. So we think that if the MODE is none we shouldn't use DHCP4.Regards,
Guillaume