Open aleksbykov opened 11 months ago
Is this similar to https://github.com/scylladb/scylladb/issues/14004
I.e. can you see if we are getting SSH bad packet length ?
It looks so, rerun job again failed. i will check the logs for issue #14004
Issue reproduced again during: https://argus.scylladb.com/test/97a03f7d-fd85-468c-8c23-a465f7693243/runs?additionalRuns[]=8c1c057d-6956-4151-80c5-2fc102687cee
But on this time "sshd complains on Bad packet length" error was not found in logs.
Is it possible, that drain process could restart network interface or somehow close all connections to host?
@aleksbykov if it's a scylla issue, please move your report to scylla and let's close this one.
Prerequisites
Versions
Logs
Description
during upgrade node, nodetool command
nodetool drain
executed. But the command raise exception and terminate job if network exception happened:Steps to Reproduce
issue reproduced rarely. Latest was happened: https://argus.scylladb.com/test/3f60c813-ab37-4cea-b400-21e8d4fc6dc9/runs?additionalRuns[]=927b91e5-b96c-46e1-ae7e-a68f2510e9ed
as work around we need catch such exception/ or don't raise exception and use warning