Bug 846227

Summary: Wrong correlation id in events for deactivate host action
Product: Red Hat Enterprise Virtualization Manager Reporter: Elena <edolinin>
Component: ovirt-engine-restapiAssignee: Juan Hernández <juan.hernandez>
Status: CLOSED CURRENTRELEASE QA Contact: Elena <edolinin>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: dyasny, ecohen, hateya, iheim, mpastern, Rhev-m-bugs, sgrinber, srevivo, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: si16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 20:02:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Elena 2012-08-07 08:33:10 UTC
When adding Correlation-Id header to deactivate host action request it doesn't returned correcly by related event.

api/hosts/456c4a30-e065-11e1-8552-07ecb740587d/deactivate
headers={'Correlation-Id': 1061}

got in event of this request:
<correlation_id>5fdec853</correlation_id>

For activate host action the corrent correlated id is returned in events.

Comment 1 Juan Hernández 2012-08-22 12:48:58 UTC
The reason for this is that the API uses the MaintananceNumberOfVdss backend command, but this doesn't propagate the correlation id to the MaintananceVds commands that it runs internally. The proposed solution is available here:

http://gerrit.ovirt.org/7412

Comment 2 Juan Hernández 2012-08-23 16:19:19 UTC
The proposed change has been merged upstream:

http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=89bbeb2308405a5e3de4424254ece16e8fee3575

Comment 4 Elena 2012-09-02 09:42:18 UTC
Verified in rhevm-sdk-3.1.0.7-1.el6ev.noarch.rpm