-
Notifications
You must be signed in to change notification settings - Fork 81
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
feat: add timeoutSeconds to ManagedChart #929
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: PoAn Yang <[email protected]>
13b14ce
to
45b6c9b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does adding a timeout help to fix the related issue? I'm sure I'm personally missing some knowledge here about managed charts, so please feel free to tell me to RTFM ;-)
A Try w/ Wordaround, upgrade can be triggered and complete. |
The error message is from fleet bundle and fleet is used to run helm command. The default timeout in helm command is 5 minutes, so increasing timeout maybe helpful. I think that this approach may not solve root cause, but it may be a good workaround to reduce the probability of problems occurring. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I can confirm this PR and setting is essential. With debug on fleet-agent, if managedchart does not set a timeout, it uses 0, when there are any hooks, it will fail in below function.
We had below PRs on upgrade path, now with #929, it will solve finally. harvester/harvester#6608
-> with a force param 5
|
Problem:
Solution:
Related Issue:
harvester/harvester#7375
Test plan: