Some env doesn't have enough time to be deployed

[Vasily Gorin]

CI: https://mirantis.testrail.com/index.php?/tests/view/2443245

Test was failed by sys_test timeout (7800sec) - log in CI

After reverting snapshot I have seen that deploying was continuing and has done successful.
I suppose we need to increase timeout for this test (and other tests) or use default timeout of fuel to recognize failure of test case.

[Alexander Kurenyshev (akurenyshev)]

I have talked to V. Sharshov and he said to me that we have not a default timeout for deployment inside Astute scripts and 2 hours should be enough for any our cluster's configuration.
Regarding this test: a normal deploying takes 76,80, 80, 98 minutes for successful runs since 97 build. And if we have timeout for this deployment than something is wrong with it.
I think we should re-assign this bug for library team (plugin has been developed by this team) for further investigation.

[Alexander Kurenyshev (akurenyshev)]

BTW we couldn't start analyze this issue because of this bug https://bugs.launchpad.net/fuel/+bug/1536190 . It's a blocker

[Alexander Kurenyshev (akurenyshev)]

UPD: Bug [0] is fixed now, but the new one [1] has blocked us

[0] https://bugs.launchpad.net/fuel/+bug/1536190
[1] https://bugs.launchpad.net/fuel/+bug/1537386

[Sergey Shevorakov (sshevorakov)]

Sasha, both [0] and [1] are fixed now. Probably now we can proceed fixing 1533234

[Alexander Kurenyshev (akurenyshev)]

This test has been passed for 3 last times and deployment time is ~70 mins. And it's normal behaviour. If test takes more time, then there is some error with product.

I think we could close this bug. Moved to Invalid.