Bug 800355 - [ovirt] [vdsm] flow-ID is not used in storage flows
Summary: [ovirt] [vdsm] flow-ID is not used in storage flows
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3.4
Assignee: Douglas Schilling Landgraf
QA Contact:
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-06 11:42 UTC by Haim
Modified: 2016-02-10 17:15 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-25 09:14:46 UTC
oVirt Team: Storage
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 11164 0 None None None Never

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/
Note You need to log in before you can comment on or make changes to this bug.