diff options
| author | Stefano Brivio <sbrivio@redhat.com> | 2025-06-04 18:23:13 +0200 |
|---|---|---|
| committer | Stefano Brivio <sbrivio@redhat.com> | 2025-06-06 10:46:40 +0200 |
| commit | 754c6d728686c5d115bd97c628d53733776dd711 (patch) | |
| tree | 89d74da6d0b937e97041b705dbbbc4954d746ee8 /doc | |
| parent | a2088fef360ee262c19186470d63875b32f80917 (diff) | |
| download | passt-754c6d728686c5d115bd97c628d53733776dd711.tar passt-754c6d728686c5d115bd97c628d53733776dd711.tar.gz passt-754c6d728686c5d115bd97c628d53733776dd711.tar.bz2 passt-754c6d728686c5d115bd97c628d53733776dd711.tar.lz passt-754c6d728686c5d115bd97c628d53733776dd711.tar.xz passt-754c6d728686c5d115bd97c628d53733776dd711.tar.zst passt-754c6d728686c5d115bd97c628d53733776dd711.zip | |
flow, repair: Proper error handling for missing passt-repair helper on target2025_06_06.754c6d7
If the target doesn't have a connected passt-repair helper,
repair_wait() sets a timeout and forcibly calls accept4(), but if the
timeout expires, we don't report any error and proceed as if we had a
connected helper.
Later, in repair_flush(), sendmsg() will fail for each flow we try to
migrate with EBADF, and we'll handle that gracefully, but it makes no
sense to even try, and it also leads to noise in the logs.
Similarly to how we handle a missing repair helper in
flow_migrate_repair_all(), propagate timeout and other errors through
repair_wait(), and don't attempt to migrate flows if repair_wait()
failed.
Fixes: c8b520c0625b ("flow, repair: Wait for a short while for passt-repair to connect")
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions