Bug 1718790

Summary:	Drop oVirt Node Legacy support in ovirt-engine
Product:	[oVirt] ovirt-engine	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	Host-Deploy	Assignee:	Dana <delfassy>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	---	CC:	bugs, lleistne, mburman, mperina
Target Milestone:	ovirt-4.4.0	Keywords:	CodeChange, DevelBlocker
Target Release:	---	Flags:	pm-rhel: ovirt-4.4+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-20 20:01:00 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:
Bug Depends On:
Bug Blocks:	1455534, 1713605

Description Sandro Bonazzola 2019-06-10 08:29:50 UTC

In order to remove oVirt Node Legacy support from ovirt-host-deploy ( Bug 
 #1713605 ) the oVirt engine should avoid to query for it.
Removing the support in ovirt-host-deploy ends up with a failure during deployment:

 2019-06-10 08:23:38,007+0000 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND       ***Q:STRING CUSTOMIZATION_COMMAND
 2019-06-10 08:23:38,007+0000 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND       **%QEnd: CUSTOMIZATION_COMMAND
 2019-06-10 08:23:38,008+0000 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:RECEIVE    env-get -k VDSM/ovirt-legacy-node
 2019-06-10 08:23:38,008+0000 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND       ***D:VALUE VDSM/ovirt-legacy-node=none:None

Comment 1 Martin Perina 2019-08-21 06:29:00 UTC

*** Bug 1349392 has been marked as a duplicate of this bug. ***

Comment 2 Sandro Bonazzola 2020-05-20 20:01:00 UTC

This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.