Bug 1539774

Summary:	[RFE] Add variable about not rebooting the host after upgrade
Product:	[oVirt] ovirt-ansible-collection	Reporter:	Petr Kubica <pkubica>
Component:	cluster-upgrade	Assignee:	Ondra Machacek <omachace>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kubica <pkubica>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	1.1.3	CC:	lveyde, mperina, nicolas
Target Milestone:	ovirt-4.2.2	Keywords:	FutureFeature
Target Release:	---	Flags:	rule-engine: ovirt-4.2? pkubica: testing_plan_complete? rule-engine: planning_ack? rule-engine: devel_ack+ rule-engine: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-ansible-cluster-upgrade-1.1.5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-29 11:18:17 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 Petr Kubica 2018-01-29 15:14:49 UTC

Description of problem:
By default engine will reboot all host after upgrade. In webadmin this behavior can be changed. Role should provide a variable about rebooting/not rebooting the hosts too 

Version-Release number of selected component (if applicable):
ovirt-ansible-cluster-upgrade-1.1.3-1.el7ev.noarch
ansible-2.4.1.0-1.el7ae.noarch

Comment 1 Petr Kubica 2018-03-07 14:55:01 UTC

Verified in
ansible-2.5.0-0.3.rc1.el7ae.noarch
ovirt-ansible-cluster-upgrade-1.1.5-1.el7ev.noarch

Comment 2 Sandro Bonazzola 2018-03-29 11:18:17 UTC

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 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.

Comment 3 Nicolas Ecarnot 2018-04-09 13:51:19 UTC

For the record, one can modify the .yml playbook by adding :

reboot_after_upgrade: true/false

Details in /usr/share/doc/ovirt-ansible-cluster-upgrade-1.1.6/README.md