-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Renew dbus connection #2862
Renew dbus connection #2862
Conversation
dd7cc8f
to
56ffd42
Compare
56ffd42
to
7f89c47
Compare
7f89c47
to
65911d9
Compare
@cyphar @kolyshkin |
65911d9
to
75e652f
Compare
b9357d6
to
471ea99
Compare
@kolyshkin |
Hi @kolyshkin, could you have time to take a look this PR. |
PING @kolyshkin |
4a2f7d6
to
a4e640f
Compare
Signed-off-by: Shiming Zhang <[email protected]>
Signed-off-by: Shiming Zhang <[email protected]>
Signed-off-by: Shiming Zhang <[email protected]>
a4e640f
to
0983ca1
Compare
How can I continue to advance this PR? |
@wzshiming I described the idea of retry in place above (#2862 (comment) and #2862 (comment)), and I guess my description was not clear enough. I have took your patches and added retry-in-place on top, please review #2923 |
@kolyshkin |
After the current dbus restarts, legacyManager will always return an error 'dbus: connection closed by user'
This PR fixes when dbus returns this error, try to reconnect to ensure that subsequent calls are normal
xref kubernetes/kubernetes#100328
Please review the changes, if there is no problem, I will to add a test.