Bug 1090796

Summary:	OVIRT35 - [RFE] Re-work engine ovirt-node host-deploy sequence
Product:	[Retired] oVirt	Reporter:	Oved Ourfali <oourfali>
Component:	ovirt-engine-core	Assignee:	Ravi Nori <rnori>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jiri Belka <jbelka>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.5	CC:	gklein, iheim, jbelka, rbalakri, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-17 12:41:48 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:	989546

Description Oved Ourfali 2014-04-24 07:57:41 UTC

CURRENT IMPLEMENTATION

ovirt-node can be either added like regular host or registered/approved.

Once added, it can only be upgraded.

NEW IMPLEMENTATION

Support two options:

1. ovirt-node upgrade - as in current implementation.

2. ovirt-node reinstall - behaves as host re-install, just perform the host-deploy again.

REASONING

If ovirt-node was reinstalled, or there was other issues like require to re-enroll certificate, there is no need to upgrade node to different version, just to deploy again.

APPENDIXES

While doing this work, please also separate the VdsInstallCommand into two commands, once for installation/reinstallation (both node and host), and one for ovirt-node upgrade. These two logics resides within the same command which is invalid.

Comment 1 Jiri Belka 2014-08-01 09:41:00 UTC

ok as BZ989546.

Comment 2 Sandro Bonazzola 2014-10-17 12:41:48 UTC

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