Replies: 1 comment 1 reply
-
This would best be asked in https://github.com/rancher/system-agent or https://github.com/rancher/rancher. The SUC itself is not responsible for anything done by the upgrade image itself. All it does is schedule jobs based on the plan. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Has anyone ran into an issue where the system-upgrade-controller triggers an upgrade of rancher/wins:v0.5.0, but never completes it? I see several pods on each windows node where it's error'd while attempting to apply an upgrade. When I inspect the pods of the rancher/wins upgrade, I see the following:
From looking at the jobs that get created, it seems like the job is missing a few details to accomplish the upgrade. Since I can't edit the jobs directly, I cloned it to try and see if I could get it to run to completion..
spec
(or to the container) should resolve the issue:Which feels like a bug since it would need to access that file from
c:/host/etc/rancher/wins/config
insteadHow can I modify the controller that keeps creating these jobs? Or should I just do a manual upgrade instead?
Beta Was this translation helpful? Give feedback.
All reactions