I wonder, how this could be fixed by QA guys?
We have implemented the workaround - the master node restart if this problem occurs, but all these jobs failed after restart with the same error: no route to host.
It seems that problem should be investigated and solved by developers.
I wonder, how this could be fixed by QA guys?
We have implemented the workaround - the master node restart if this problem occurs, but all these jobs failed after restart with the same error: no route to host.
It seems that problem should be investigated and solved by developers.