-
Notifications
You must be signed in to change notification settings - Fork 254
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
manual upgrade of rke2 on arm setup gets several pods restarting and alternate between running/crashloopbackoff state #6235
Comments
Am getting inconsistent test results with rc6. Out of 5 manual upgrades, 2 times the pods looked like they were running - after 7 to 9 restarts - and they stayed running for at least 15 mins or so... the other 3 times, i see results as follows:
|
canal logs:
|
This indicates that there are additional amd64 binaries being used on an arm64 system - so more GH Actions ARCH/TARGETARCH problems. Which of the canal containers is that log from? |
|
Verified on master branch with v1.30.2-rc7+rke2r1
|
Issue found on master branch with version v1.30.2-rc5+rke2r1
Environment Details
Infrastructure
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
Config.yaml:
Additional files
Steps to reproduce:
do a manual upgrade on all nodes:
Reproducing Results/Observations:
Pods status for the nginx controllers and snapshot controllers seem to alternate between running/crashloopbackoff and are continuously restarting.
Some of the pod logs:
Expected behavior:
Post upgrade - All pods should be up and running successfully (without restarting several times and heading into a crashloopbackoff. )
The text was updated successfully, but these errors were encountered: