fix(ubuntu): restablish empty default grub cmdline after cloud-init install #982
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.
Summary of Pull Request
I ran into #981 today, it seems to come from
GRUB_CMDLINE_LINUX_DEFAULT
being set onpacker
template provisioning viacloud-init
installer.It is set by packer
boot_command
on kernel cmdline arguments and tellcloud-init
to use a specific DataSource (nocloud-net
ornocloud
) and the installer persists these arguments on grub configuration in/etc/default/grub
.It it the reason why
cloud-init
does not readVMware
DataSource.I ended up with this Pull Request to restablish an empty
GRUB_CMDLINE_LINUX_DEFAULT
aslate_command
It works on my side
Tested on
Ubuntu 22.04 LTS
Hope it'll help someone.
Type of Pull Request
type/bug
type/feature
ortype/enhancement
type/docs
type/refactor
type/chore
Please describe:
Related to Existing Issues
Closes #981
Test and Documentation Coverage
Breaking Changes?