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

cloud provider vsphere pod didn't restart gracefully as expected #1212

Open
XudongLiuHarold opened this issue Aug 22, 2024 · 2 comments · May be fixed by #1213
Open

cloud provider vsphere pod didn't restart gracefully as expected #1212

XudongLiuHarold opened this issue Aug 22, 2024 · 2 comments · May be fixed by #1213
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@XudongLiuHarold
Copy link
Member

XudongLiuHarold commented Aug 22, 2024

What happened?

In https://github.com/kubernetes/cloud-provider-vsphere/blob/master/cmd/vsphere-cloud-controller-manager/main.go#L273, cloud provider vsphere is using klog.Fatalf to log information, it will exit directly so the stop channel didn't receive the signal

klog.Fatalf("restarting pod because received event %v\n", event)
stopCh <- struct{}{}

What did you expect to happen?

The pod should not exit at klog.Fatalf and allow the signal to be send to the channel

How can we reproduce it (as minimally and precisely as possible)?

existing in current version

Anything else we need to know (please consider providing level 4 or above logs of CPI)?

No response

Kubernetes version

$ kubectl version
# paste output here
v1.31.0

Cloud provider or hardware configuration

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Kernel (e.g. uname -a)

Install tools

Container runtime (CRI) and and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

Others

@XudongLiuHarold XudongLiuHarold added the kind/bug Categorizes issue or PR as related to a bug. label Aug 22, 2024
@XudongLiuHarold
Copy link
Member Author

/assign

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
3 participants