WIP: Fix IPv6 issue in grub configuration on alicloud #142
Conversation
This file contains 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
StefanWutz
changed the title
|
DO NOT MERGE. According to alicloud the Bionic stemcell image will be manipulated during image upload and the kernel boot parameter We are validating if this change can be removed or the correct behavior can be applied to the CPI. |
|
The kernel boot parameters will be changed when uploading an Ubuntu Bionic image to alicloud. This includes the deletion of the parameter |
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.
This PR is a workaround to fix the IPv6 issues on alicloud as described in #132.
Problem:
IPv6 is disabled
ipv6.disable=1using the kernel boot parameters defined in the grub configuration/etc/default/grub. However on alicloud the kernel boot parameteripv6.disable=1disappeared in files/etc/default/gruband/boot/grub/grub.cfgafter a vm was created. Obviously bosh-agent removed the parameter from configuration, but this is not the case as it only operate on file/boot/grub/grub.cfg. The logs are not showing any process which is manipulating the grub configuration on startup.The file
/etc/default/grubshould never be changed on a vm, so we should expect:but we found:
The root cause is still unknown.
Workaround:
For alicloud we add a new configuration item GRUB_CMDLINE_LINUX_DEFAULT to the grub configuration specifying again the kernel boot parameter
ipv6.disable=1. This change will survive the boot process and IPv6 on alicloud is disabled. Enable IPv6 using the bosh-agent works as expected (tested).