Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2090638

Summary: from time to time we fail on timeout of "Check OVF_STORE volume status" task
Product: [oVirt] ovirt-hosted-engine-setup Reporter: Kobi Hakimi <khakimi>
Component: GeneralAssignee: Asaf Rachmani <arachman>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.6.2CC: bugs, didi, michal.skrivanek, stirabos
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-09 08:50:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kobi Hakimi 2022-05-26 08:30:02 UTC
Description of problem:
from time to time we fail on timeout of "Check OVF_STORE volume status" task


Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup-2.6.3-1.el8ev.noarch
4.5.0.10

How reproducible:
from time to time

Steps to Reproduce:
1. Run the deployment of the hosted engine with restore from file flow or regular flow.

Actual results:
failed because the task "Check OVF_STORE volume status" reach his timeout and the "description['Updated']" still false as you can see:
00:01:41 FAILED - RETRYING: Check OVF_STORE volume status (1 retries left).
00:01:52 failed: [host1.com] (item={'name': 'OVF_STORE', 'image_id': ..., "stdout": "{\n    \"apparentsize\": \"134217728\",\n    \"capacity\": \"134217728\",\n    \"children\": [],\n    \"ctime\": \"1653425433\",\n    \"description\": \"{\\\"Updated\\\":false,\\\"Last Updated\\\":null,\\\"Storage Domains\\\":[{\\\"uuid\\\":\\\...


Expected results:
To increase the timeout to make sure we are not failing because of it from time to time


Additional info:
I remember we saw this issue in the past and we considered this PR:
https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/pull/336
which I copied in:
https://github.com/oVirt/ovirt-ansible-collection/pull/190

Comment 1 Kobi Hakimi 2022-05-26 08:31:34 UTC
related old bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1781102

Comment 4 Michal Skrivanek 2022-05-26 12:46:30 UTC
since it seems related to other hosts restored from backup I doubt it happens on clean install.

Comment 6 Michal Skrivanek 2022-05-26 13:14:02 UTC
errors seem to be cause by bug 1785061 which is still unfixed in 4.3.
Please confirm this problem on a setup with either vdsm-4.30.53 or 4.40+

Comment 7 Kobi Hakimi 2022-05-31 14:27:15 UTC
(In reply to Michal Skrivanek from comment #6)
> errors seem to be cause by bug 1785061 which is still unfixed in 4.3.
> Please confirm this problem on a setup with either vdsm-4.30.53 or 4.40+

I rebuild the same environment with 4.3 and I can see we have in the host:
vdsm-4.30.52-1.el7ev.x86_64
if you want someone to look at this environment I keep it locked for a while :)

Comment 8 Michal Skrivanek 2022-06-01 07:46:01 UTC
there's no need to look at a setup with 4.30.52, if it's not happening with 4.30.53 or 4.4 then we can close this as duplicate of 1785061

Comment 9 Kobi Hakimi 2022-06-01 10:14:44 UTC
as Michal suggested mark it as duplicate

*** This bug has been marked as a duplicate of bug 1785061 ***

Comment 11 Michal Skrivanek 2022-06-09 08:50:39 UTC
I do not see that anything changed, it's still the same duplicate.

please reopen only if you see this issue in an environment consisting only of hosts running that or newer builds.

*** This bug has been marked as a duplicate of bug 1785061 ***