Fix getVMManagementTypeByIPConfigurationID() #5948
Conversation
k8s-ci-robot
added
release-note
k8s-ci-robot
added
cncf-cla: yes
lzhecheng
force-pushed
the
getVMManagementTypeByIPConfigurationID-cache-force-refresh
branch
from
ed80312
to
47e3035
Compare
k8s-ci-robot
added
size/S
lzhecheng
force-pushed
the
getVMManagementTypeByIPConfigurationID-cache-force-refresh
branch
from
47e3035
to
feccc62
Compare
lzhecheng
force-pushed
the
getVMManagementTypeByIPConfigurationID-cache-force-refresh
branch
from
feccc62
to
386f3e6
Compare
If VM not existing in cache, force cache refresh again. If the node is not in the cache, assume the node has joined after the last cache refresh and attempt to refresh the cache. Signed-off-by: Zhecheng Li <zhechengli@microsoft.com>
lzhecheng
force-pushed
the
getVMManagementTypeByIPConfigurationID-cache-force-refresh
branch
from
386f3e6
to
223c621
Compare
Thank you for reminding. This failure comes from the log change in this PR and it is fixed. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lzhecheng, tallaxes 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 |
k8s-ci-robot
added
the
lgtm
|
/retest |
|
/cherry-pick release-1.29 |
|
@feiskyer: once the present PR merges, I will cherry-pick it on top of release-1.29 in a new PR and assign it to you. In response to this:
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. |
|
/cherry-pick release-1.28 |
|
@feiskyer: once the present PR merges, I will cherry-pick it on top of release-1.28 in a new PR and assign it to you. In response to this:
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. |
|
/cherry-pick release-1.27 |
|
@feiskyer: once the present PR merges, I will cherry-pick it on top of release-1.27 in a new PR and assign it to you. In response to this:
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. |
|
@feiskyer: new pull request created: #5970 In response to this:
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. |
|
@feiskyer: new pull request created: #5971 In response to this:
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. |
|
@feiskyer: new pull request created: #5972 In response to this:
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. |
lzhecheng
deleted the
getVMManagementTypeByIPConfigurationID-cache-force-refresh
branch
What type of PR is this?
/kind bug
What this PR does / why we need it:
Force cache refresh for getVMManagementTypeByIPConfigurationID(). The reason is that when a new standalone VM is included in the cluster, CCM cannot tell its VM type with stale cache.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: