Bug 1124442

Summary:	jsonrpc: It should be possible to edit host "advanced" parameters to change rpc
Product:	[Retired] oVirt	Reporter:	Antoni Segura Puimedon <asegurap>
Component:	ovirt-engine-core	Assignee:	Piotr Kliczewski <pkliczew>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.5	CC:	bazulay, bugs, ecohen, gklein, iheim, oourfali, rbalakri, yeylon
Target Milestone:	---
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:	ovirt-3.5.0_rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-17 12:23:40 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 Antoni Segura Puimedon 2014-07-29 13:44:01 UTC

Description of problem:
When upgrading an oVirt setup to 3.5, one of the features that one would like
to setup is the new JSON RPC.

The problem is that once the default cluster has been moved to 3.5
compatibility and the vdsm on the hosts are 4.16.1-0.gita4d9abf, if I put the
hosts in maintenance, going to the "advanced" section of the host editing
dialog does not let me change the communication to jsonrpc

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

vdsm-4.16.1-0.gita4d9abf,
ovirt-engine-3.5.0-0.0.master.20140722232056.git8e1babc.fc19.noarch

How reproducible: 100%


Steps to Reproduce:
0. Put the host in maintenance
1. Upgrade setup from 3.4 to 3.5 (both engine and vdsm machines)
2. Go to the Host edit dialog
3. Tick "advanced parameters"

Actual results:
No possibility to change to json rpc for communication with the host


Expected results:
The same options to set the connectivity to use JSON rpc as when adding a new
host are present


Additional info:
The workaround is to delete the host and add it again, but it is very
cumbersome.

Comment 1 Petr Beňas 2014-09-16 14:02:46 UTC

in vt3.1

Comment 2 Sandro Bonazzola 2014-10-17 12:23:40 UTC

oVirt 3.5 has been released and should include the fix for this issue.