Add new reboot_after_upgrade parameter

This patch add new parameter reboot_after_upgrade, to decide if host
should be rebooted after upgrade.

Change-Id: I04a3dd5df22d885957baf38bd69a7d316faf09fe
Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1539774
Signed-off-by: Ondra Machacek <omachace@redhat.com>

README.md

@@ -21,6 +21,7 @@ Role Variables
 | host_statuses           | [UP]                  | List of host statuses. If a host is in any of the specified statuses then it will be upgraded. |
 | host_names              | [\*]                  | List of host names to be upgraded.        |
 | check_upgrade           | false                 | If true, run check_for_upgrade action on all hosts before executing upgrade on them. If false, run upgrade only for hosts with available upgrades and ignore all other hosts. |
+| reboot_after_upgrade    | true                  | If true reboot hosts after successful upgrade. |
 
 Dependencies
 ------------

defaults/main.yml

@@ -4,6 +4,7 @@ stop_non_migratable_vms: "{{ stop_pinned_to_host_vms | default(false) }}"
 upgrade_timeout: 1200
 cluster_name: Default
 check_upgrade: false
+reboot_after_upgrade: true
 host_statuses:
   - up
 host_names:

library/README.md

@@ -17,3 +17,8 @@ Here is list of updated modules:
 
 - Support the ENV variables for `ovirt_auth`: [PR](https://github.com/ansible/ansible/pull/34878)
   The module will be available in Ansible 2.5.
+
+2. ovirt_hosts.py
+
+- Support `reboot_after_upgrade` parameter in `ovirt_hosts`: [PR](https://github.com/ansible/ansible/pull/35956)
+  The fix will be available in Ansible 2.6.