Bug 1317248 - Add host name as header to JsonRpcUtils
Summary: Add host name as header to JsonRpcUtils
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 3.6.3.2
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ovirt-3.6.5
: 3.6.5.1
Assignee: Eldad Marciano
QA Contact: Eldad Marciano
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-13 10:16 UTC by Eldad Marciano
Modified: 2016-04-21 14:40 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-04-21 14:40:29 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-3.6.z+
mgoldboi: planning_ack+
mperina: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 39888 0 master MERGED construct jsonrpc with identifier name. 2016-03-30 15:33:08 UTC
oVirt gerrit 55501 0 ovirt-engine-3.6.5 MERGED construct jsonrpc with identifier name. 2016-04-01 07:10:37 UTC
oVirt gerrit 55502 0 ovirt-engine-3.6 MERGED construct jsonrpc with identifier name. 2016-03-31 12:32:01 UTC
oVirt gerrit 55521 0 master MERGED core: Fix formatting in JsonRpcUtils 2016-03-31 19:49:46 UTC

Description Eldad Marciano 2016-03-13 10:16:15 UTC 
Description of problem:
when working with ovirt-vdsmfake with many hosts we have to use header name in order to identify the hostname for establishing correct channels.



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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Yaniv Kaul 2016-03-13 21:17:26 UTC 
Is that a bug? A feature request?
Comment 2 Martin Perina 2016-03-16 13:02:01 UTC 
It's a feature request, but it's important only for fake-vdsm as normal vdsm will completely ignore this new information sent from engine. Since vdsm ignores it completely, QA don't need to test this patch.

Patcch is already posted and waiting to be merged.

Scale team needs it for 3.6 scale testing, so that's why it's targeted to 3.6
Comment 3 Mike McCune 2016-03-28 23:13:32 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Note You need to log in before you can comment on or make changes to this bug.