-
Notifications
You must be signed in to change notification settings - Fork 275
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
CrashLoopBackOff status on helm-install-rke2-coredns pod after upgrade #5492
Comments
mgfritch
added a commit
to mgfritch/rke2-charts
that referenced
this issue
Feb 21, 2024
fixup for rancher#400 Issue: rancher/rke2#5492 Signed-off-by: Michael Fritch <[email protected]>
mgfritch
added a commit
to mgfritch/rke2
that referenced
this issue
Feb 21, 2024
fixup for 2b6f138 Issue: rancher#5492 Signed-off-by: Michael Fritch <[email protected]>
This was referenced Feb 21, 2024
Closed
Closed
Validated with RC v1.29.2-rc2+rke2r1
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environmental Info:
RKE2 Version:
v1.29.2-rc1+rke2r1 and below RCs
Node(s) CPU architecture, OS, and Version:
Linux ip-xx 5.15.0-1031-aws #35-Ubuntu SMP Fri Feb 10 02:07:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
1 server / HA setup (3 servers + 1 agent)
Describe the bug:
After a simple upgrade, the
helm-install-rke2-coredns
pod goes in to CrashLoopBackOff statusPod logs shows error
Steps To Reproduce:
Expected behavior:
Actual behavior:
The
helm-install-rke2-coredns
pod goes in to CrashLoopBackOff stateBefore upgrade
Additional context / logs:
Pod describe
Pod logs
The text was updated successfully, but these errors were encountered: