We still observe this issue.
Sometimes it's just a bunch of errors, but sometimes it fails with segfault which leads to test failure.
Note: more SSH connections used in the test -> more probability to reproduce the issue.
Thus, more nodes in the environment - more chance to hit this bug as well.
We believe it's possible to avoid this bug if we will close SSH connections opened by fuel-qa.
There is method clean_all_connections(), but it is called in resume_environment() only.
Maybe calling this method on tests tear-down/exit will fix the issue.
We still observe this issue.
Sometimes it's just a bunch of errors, but sometimes it fails with segfault which leads to test failure.
Note: more SSH connections used in the test -> more probability to reproduce the issue.
Thus, more nodes in the environment - more chance to hit this bug as well.
This bug is related to known issues: /github. com/paramiko/ paramiko/ issues/ 17 bugs.python. org/issue1856
paramiko: https:/
python: http://
We believe it's possible to avoid this bug if we will close SSH connections opened by fuel-qa. connections( ), but it is called in resume_ environment( ) only.
There is method clean_all_
Maybe calling this method on tests tear-down/exit will fix the issue.