librados/watch_notify: reconnect after socket injection#45825
librados/watch_notify: reconnect after socket injection#45825yuriw merged 2 commits intoceph:masterfrom
Conversation
badone
left a comment
There was a problem hiding this comment.
This looks good so far but could you remove "?next_issue_id=52488" from the tracker link in the commit message and change "socket injection" to "socket failure injection". Please also take a look at the comment I left on the tracker regarding expanding this solution to cover more of the known failure cases.
For some tests, if socket failure injection cause watch to fail, we can re-watch using the error callback Fixes: https://tracker.ceph.com/issues/45868 Signed-off-by: Nitzan Mordechai <nmordec@redhat.com>
When socket failure injection or any delay that time out watch we need reconnect the watch using the error callback to reconnect Fixes: https://tracker.ceph.com/issues/47025 Signed-off-by: Nitzan Mordechai <nmordec@redhat.com>
20e6e39 to
d2c5d7a
Compare
I added another commit to handle another known issue with test |
|
jenkins test api |
|
Failures, unrelated: Details: |
|
@NitzanMordhai perhaps similar logic can be applied for this Tracker: https://tracker.ceph.com/issues/45721. Let me know if you have any thoughts! |
For some tests, if socket failure injection cause watch to fail, we can re-watch using the error callback
Fixes: https://tracker.ceph.com/issues/45868
Signed-off-by: Nitzan Mordechai nmordec@redhat.com
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windows