fix: prevent first boot name resolution failures #52
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.
Description
Without masking systemd-networkd before first boot, there were often (the slower the hardware, the more likely) failures in name resolution during first boot. Everything went well until at some point in time the dns resolution stopped working and the install of each single apt package took 3 minutes. Although the installation finishes more or less successfully and the missing packages are installed by the first ansible pull after 2nd boot, it can prolong first boot time by 60 minutes or more.
There might be more elegant solutions, but it looks so wrong to have both the (ubuntu server) systemd-networkd and (ubuntu client) NetworkManager network managements active at the same time.