-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Determine root filesistem device and partition before running growpart #8024
Determine root filesistem device and partition before running growpart #8024
Conversation
Hi @mlorenzo-stratio. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
@mlorenzo-stratio Thanks 👍 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: floryut, mlorenzo-stratio The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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
growpart
instead of assuming it will always be/dev/sda1
Which issue(s) this PR fixes:
Fixes #7958
Special notes for your reviewer: We use
terraform
to deploy Azure environments with several disks on each VM. It often happens that a device other than/dev/sda1
is 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?: