Since the timeout bug was fixed (https://tracker.ceph.com/issues/65533)
"Ceph API tests" sometimes fails because vstart.sh command had to be
aborted due to timeout.
Currently, "timeout" is set to 300 seconds which sometimes is not enough
for vstart.sh to run successfully for "Ceph API tests" CI job. 180
seconds usually suffices for vstart.sh to run successfully when used for
CephFS.
Increase value of "timeout" to avoid such failures on "Ceph API tests" CI.
Fixes: https://tracker.ceph.com/issues/65565
Signed-off-by: Rishabh Dave <ridave@redhat.com>
(cherry picked from commit
f779b428689ea245aa0c978732c468860520c609)
(cherry picked from commit
5a8a9df401663ca48b0031104d00ea0e4b636165)
Conflicts:
qa/tasks/vstart_runner.py
- accept the incoming changes
log.info('\nrunning vstart.sh now...')
# usually, i get vstart.sh running completely in less than 100
# seconds.
- remote.run(args=args, env=vstart_env, timeout=(3 * 60))
+ remote.run(args=args, env=vstart_env, timeout=(10 * 60))
log.info('\nvstart.sh finished running')
# Wait for OSD to come up so that subsequent injectargs etc will