Bug 1350399 - NPE during compensation on startup
Summary: NPE during compensation on startup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.0.2
: 4.0.2
Assignee: Martin Mucha
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-27 10:49 UTC by Martin Mucha
Modified: 2016-07-27 13:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 13:03:59 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.0.z+
rule-engine: planning_ack+
oourfali: devel_ack+
lsvaty: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 59529 0 ovirt-engine-4.0 NEW core: Remove redundant c'tors 2016-06-27 11:47:43 UTC
oVirt gerrit 59530 0 ovirt-engine-4.0 MERGED core: If command is created to compensate existing business_entity_snapshot records, it should be created with compensat... 2016-07-03 09:48:57 UTC

Description Martin Mucha 2016-06-27 10:49:16 UTC 
Description of problem:
NPE during compensation on startup, caused by not initialized compensation context in command constructor(or elsewhere).

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


How reproducible:
100%


Steps to Reproduce:
1. let some command fail in such way, to have compensation data for next engine start up.
2. perform restart.


Actual results:
NPE.

Expected results:
no NPE.

Additional info:
Comment 1 Martin Perina 2016-07-04 13:09:09 UTC 
I haven't found the patch in ovirt-engine-4.0.1 branch, so moving to 4.0.2
Comment 2 Gil Klein 2016-07-27 13:03:59 UTC 
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA
Note You need to log in before you can comment on or make changes to this bug.