-
Notifications
You must be signed in to change notification settings - Fork 26
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
CPEM 3.8.0 sometimes fails to start up properly #525
Labels
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Jun 19, 2024
/remove-lifecycle stale |
k8s-ci-robot
removed
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Jun 27, 2024
/triage accepted |
k8s-ci-robot
added
the
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
label
Jun 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've noticed a problem after switching to the latest CPEM 3.8.0 that sometimes it won't start up properly on new cluster nodes.
We just see these messages in the log over and over:
If I change the version in the
cloud-provider-equinix-metal
ds to3.7.0
it starts up fine. Also, if I then change the version back to3.8.0
it also starts up successfully.I haven't been able to reproduce this reliably or tie it to a specific configuration, it just seems to happen sporadically.
PACKNGO_DEBUG=1 doesn't seem to work but here's the output from the logs with
--v=5
:The text was updated successfully, but these errors were encountered: