Check OVF_STORE volume status: Try 10 minutes

[kobihk]

we still face this issue that the timeout reached and we failed because we didn't got the expected results
but when looking into the machine few minutes later we see that we have the volume status results:

22:45:16 TASK [ovirt.ovirt.hosted_engine_setup : Check OVF_STORE volume status] *********
22:45:17 changed: [example.com] => (item={'name': 'OVF_STORE', 'image_id': 'aabbcc', 'id': 'ddeeff'})
22:45:17 FAILED - RETRYING: Check OVF_STORE volume status (12 retries left).
22:45:28 FAILED - RETRYING: Check OVF_STORE volume status (11 retries left).
22:45:39 FAILED - RETRYING: Check OVF_STORE volume status (10 retries left).
22:45:50 FAILED - RETRYING: Check OVF_STORE volume status (9 retries left).
22:46:01 FAILED - RETRYING: Check OVF_STORE volume status (8 retries left).
22:46:11 FAILED - RETRYING: Check OVF_STORE volume status (7 retries left).
22:46:22 FAILED - RETRYING: Check OVF_STORE volume status (6 retries left).
22:46:33 FAILED - RETRYING: Check OVF_STORE volume status (5 retries left).
22:46:44 FAILED - RETRYING: Check OVF_STORE volume status (4 retries left).
22:46:55 FAILED - RETRYING: Check OVF_STORE volume status (3 retries left).
22:47:06 FAILED - RETRYING: Check OVF_STORE volume status (2 retries left).
22:47:16 FAILED - RETRYING: Check OVF_STORE volume status (1 retries left).

[ovirt-infra]

Hello contributor, thanks for submitting a PR for this project!

I am the bot who triggers "standard-CI" builds for this project.
As a security measure, I will not run automated tests on PRs that are not from white-listed contributors.

In order to allow automated tests to run, please ask one of the project maintainers to review the code and then do one of the following:

1. Type ci test please on this PR to trigger automated tests for it.
2. Type ci add to whitelist on this PR to trigger automated tests for it and also add you to the contributor white-list so that your future PRs will be tested automatically. ( keep in mind this list might be overwritten if the job XML is refreshed, for permanent whitelisting, please follow ovirt dynamic plugin improvements #3 option )
3. If you are planning to contribute to more than one project, maybe it's better to ask them to add you to the project organization, so you'll be able to run tests for all the organization's projects.

[kobihk]

This PR is the same as the closed PR oVirt/ovirt-ansible-hosted-engine-setup#336

[mnecas]

ci add to whitelist

[michalskrivanek]

seems to work properly as is