Determine root filesistem device and partition before running growpart #20
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
unai-ttxu
pushed a commit
that referenced
this pull request
Oct 6, 2021
unai-ttxu
pushed a commit
that referenced
this pull request
Dec 21, 2021
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.
Already merged on kubespray: kubernetes-sigs#8024
What type of PR is this?
/kind bug
What this PR does / why we need it:
When running on Azure it determines root filesystem device and partition to run
growpartinstead of assuming it will always be/dev/sda1Which issue(s) this PR fixes:
Fixes kubernetes-sigs#7958
Special notes for your reviewer: We use
terraformto deploy Azure environments with several disks on each VM. It often happens that a device other than/dev/sda1is the root filesystem device on several VMs, maybe due to race conditions when deploying Azure disks and attaching them to VMs.Does this PR introduce a user-facing change?: