Skip to content
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

fix: vm-type is not overriding as expected #2578

Merged
merged 1 commit into from
Nov 4, 2024

Conversation

umagnus
Copy link
Contributor

@umagnus umagnus commented Oct 31, 2024

What type of PR is this?

/kind bug

What this PR does / why we need it:

fix: vm-type is not overriding as expected

Which issue(s) this PR fixes:

Fixes #2533

Requirements:

Special notes for your reviewer:
azuredisk log:

I1104 06:08:41.447295       1 azuredisk.go:223] override VMType(vmss) in cloud config as standard
I1104 06:08:41.447305       1 azuredisk.go:230] disable UseInstanceMetadata for controller
I1104 06:08:41.447316       1 azuredisk.go:242] cloud: AzurePublicCloud, location: eastus2, rg: MC_aks-yxytest_group_aks-yxytest_eastus2, VMType: standard, PrimaryScaleSetName: aks-userpool-34645390-vmss, PrimaryAvailabilitySetName: , DisableAvailabilitySetNodes: false
I1104 06:08:41.450388       1 mount_linux.go:285] 'umount /tmp/kubelet-detect-safe-umount492110992' failed with: exit status 32, output: umount: /tmp/kubelet-detect-safe-umount492110992: must be superuser to unmount.
I1104 06:08:41.450432       1 mount_linux.go:287] Detected umount with unsafe 'not mounted' behavior
I1104 06:08:41.450485       1 driver.go:82] Enabling controller service capability: CREATE_DELETE_VOLUME
I1104 06:08:41.450493       1 driver.go:82] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME

test to add a log in GetNodeVMSet function to print az.VMType, and it returns:

I1104 08:09:17.486821       1 azure.go:1498] getNodeVMSet: vmType is "standard", return VMSet directly

The VMType is overrided as standard

Release note:

none

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 31, 2024
@k8s-ci-robot
Copy link
Contributor

Hi @umagnus. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 31, 2024
@cvvz
Copy link
Member

cvvz commented Nov 1, 2024

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 1, 2024
@umagnus
Copy link
Contributor Author

umagnus commented Nov 1, 2024

/retest

2 similar comments
@umagnus
Copy link
Contributor Author

umagnus commented Nov 3, 2024

/retest

@umagnus
Copy link
Contributor Author

umagnus commented Nov 4, 2024

/retest

@k8s-ci-robot
Copy link
Contributor

@umagnus: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-azuredisk-csi-driver-external-e2e-single-az 7b8a159 link true /test pull-azuredisk-csi-driver-external-e2e-single-az

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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-sigs/prow repository. I understand the commands that are listed here.

Copy link
Member

@andyzhangx andyzhangx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 4, 2024
@andyzhangx andyzhangx merged commit 2393fce into kubernetes-sigs:master Nov 4, 2024
22 of 24 checks passed
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx, umagnus

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 4, 2024
@andyzhangx
Copy link
Member

/cherrypick release-1.31

@andyzhangx
Copy link
Member

/cherrypick release-1.30

@andyzhangx
Copy link
Member

/cherrypick release-1.29

@andyzhangx
Copy link
Member

/cherrypick release-1.28

@k8s-infra-cherrypick-robot

@andyzhangx: #2578 failed to apply on top of branch "release-1.29":

Applying: fix override vmtype
Using index info to reconstruct a base tree...
M	pkg/azuredisk/azuredisk.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/azuredisk/azuredisk.go
CONFLICT (content): Merge conflict in pkg/azuredisk/azuredisk.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 fix override vmtype

In response to this:

/cherrypick release-1.29

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-sigs/prow repository.

@k8s-infra-cherrypick-robot

@andyzhangx: new pull request created: #2580

In response to this:

/cherrypick release-1.31

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-sigs/prow repository.

@k8s-infra-cherrypick-robot

@andyzhangx: new pull request created: #2581

In response to this:

/cherrypick release-1.30

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-sigs/prow repository.

@k8s-infra-cherrypick-robot

@andyzhangx: #2578 failed to apply on top of branch "release-1.28":

Applying: fix override vmtype
Using index info to reconstruct a base tree...
M	pkg/azuredisk/azuredisk.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/azuredisk/azuredisk.go
CONFLICT (content): Merge conflict in pkg/azuredisk/azuredisk.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 fix override vmtype

In response to this:

/cherrypick release-1.28

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-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

--vm-type is not overriding as expected
5 participants