Bug 1309293 - Failed to syncDbRecords after successful live merge because host is down
Summary: Failed to syncDbRecords after successful live merge because host is down
Keywords:
Status: CLOSED DUPLICATE of bug 1309294
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 3.6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-3.6.5
: ---
Assignee: Allon Mureinik
QA Contact: Aharon Canan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-17 12:00 UTC by Ala Hino
Modified: 2016-02-18 11:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-18 11:45:52 UTC
oVirt Team: Storage
Embargoed:
amureini: ovirt-3.6.z?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)

Description Ala Hino 2016-02-17 12:00:50 UTC 
Description of problem:
After successful live merge, if during host goes down after completion of live merge but before calling 'syncDbRecords', flow fails because 'syncDbRecords' calls vdsm to get image info.

This bug is to make sure we remove the call to vdsm outside of 'syncDbRecords'.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. (Lively) remove a snapshot
2. After/before DESTROY_IMAGE_CHECK completes, take shutdown host
3. Update the db fails

Actual results:
Db update fails

Expected results:
Db to be updated with the correct data regarding live merge

Additional info:
Comment 1 Allon Mureinik 2016-02-18 11:45:52 UTC 
This seems like the double-submit issue in bugzilla again. Since bug 1309294 already has some activity, I'm closing this one.

Ala, if this analysis is incorrect, please explain and reopen.

*** This bug has been marked as a duplicate of bug 1309294 ***
Comment 2 Ala Hino 2016-02-18 11:54:35 UTC 
Exactly the same, probably second one created by mistake
Note You need to log in before you can comment on or make changes to this bug.