Bug 800355

Summary: [ovirt] [vdsm] flow-ID is not used in storage flows
Product: [Retired] oVirt Reporter: Haim <hateya>
Component: vdsmAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: abaron, acathrow, amureini, bazulay, iheim, mgoldboi, yeylon, ykaul
Target Milestone: ---   
Target Release: 3.3.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-25 09:14:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Haim 2012-03-06 11:42:38 UTC
Description of problem:

due to current design, flow-id (correlation id) is not used in storage flows, such as connectStorage{Server,Pool}, spmStart and so on and so forth.
This is due to design where flow-id implementation is set in api calls, so it only affects vm-life-cycle flows.

please note that engine uses the flow-id in all flows.

Comment 1 Douglas Schilling Landgraf 2013-01-17 19:33:42 UTC
Patch available for review:
http://gerrit.ovirt.org/#/c/11164/