Delete /etc/resolv.conf in captured image #6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Created |
|
Failed on upload to s3 because of lack of quota. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
CI on
arcusis broken with the previous imageopenhpc-220526-1354.qcow2. That image was built on arcus'sportal-internalsubnet and /etc/resolv.conf contains that subnets DHCP addresses as the nameservers. When booted on theilab-60subnetcloud-initdetects there is dns information on the subnet, disables network manager's control of /etc/resolv.conf, and APPENDS (rather than rewriting entirely) one of the ilab-60 subnet's nameservers (which are external cambridge ones) to /etc/resolv.conf. The upshot is that /etc/resolv.conf onilab-60contains two nameservers which the VM can't connect to, so it eventually falls back to the last one. However the fallback is slow enough (~16s) to entirely break e.g.dnf install.Note the previous image works on smslabs as the subnet used there does not contain dns information, hence network manager is left in control of /etc/resolv.conf and can entirely rewrite it.
The fix is simply to delete
/etc/resolv.conf; this enables either network manager or cloud-init to generate it in full on boot.NB: This also bumps the base image from RockyLinux 8.5 to 8.6, seeing as a rebuild was required anyway.