Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1157372 - [RFE] Introduce Ansible role ovirt-cluster-upgrade, which can perform upgrade of the whole cluster
[RFE] Introduce Ansible role ovirt-cluster-upgrade, which can perform upgrade...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-ansible-roles (Show other bugs)
3.4.0
All Linux
medium Severity medium
: ovirt-4.2.0
: ---
Assigned To: Ondra Machacek
Petr Kubica
: FutureFeature
Depends On: 1462821
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-27 02:42 EDT by Oved Ourfali
Modified: 2018-05-15 14:00 EDT (History)
21 users (show)

See Also:
Fixed In Version: ovirt-ansible-roles-1.1.0-0.el7ev
Doc Type: Enhancement
Doc Text:
The oVirt.cluster-upgrade Ansible role is now available as part of the ovirt-ansible-cluster-upgrade package, which is installed as a dependency of the ovirt-ansible-roles package.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-05-15 13:59:47 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
pkubica: testing_plan_complete+


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1987073 None None None Never
Red Hat Product Errata RHEA-2018:1534 None None None 2018-05-15 14:00 EDT

  None (edit)
Description Oved Ourfali 2014-10-27 02:42:12 EDT
Description of problem:
There is a need to support rolling upgrade through the admin portal, to easy the cluster-upgrade process.
Comment 16 Martin Perina 2017-07-24 03:22:14 EDT
I think we should provide ovirt-ansible-roles package before we can move that to MODIFIED
Comment 18 Martin Perina 2017-09-18 03:17:49 EDT
We have created Ansible role ovirt-cluster-upgrade [1] to perform upgrade of selected cluster. The role is part of ovirt-ansible-roles package [2], which is installed automatically on RHV Manager host so you can find documentation for the role in [3].

To execute this role you need an Ansible playbook which defines required parameters, example of this playbook can be found at [4]. Basic information how to execute a role from ovirt-ansible-roles package can be found at [2].


[1] https://github.com/oVirt/ovirt-ansible/blob/master/roles/ovirt-cluster-upgrade/README.md

[2] /usr/share/doc/ovirt-ansible-roles/README.md

[3] /usr/share/doc/ansible/roles/ovirt-cluster-upgrade/README.md

[4] /usr/share/doc/ovirt-ansible-roles/examples/cluster_upgrade.yml
Comment 19 Petr Kubica 2017-12-19 05:49:43 EST
Verified in
ovirt-ansible-vm-infra-1.1.3-1.el7ev.noarch
ansible-2.4.1.0-1.el7ae.noarch
ovirt-ansible-infra-1.1.2-1.el7ev.noarch
ovirt-ansible-image-template-1.1.3-1.el7ev.noarch
ovirt-ansible-cluster-upgrade-1.1.3-1.el7ev.noarch
ovirt-ansible-roles-1.1.2-1.el7ev.noarch
ovirt-ansible-manageiq-1.1.3-1.el7ev.noarch
Comment 20 eberman 2017-12-19 07:09:43 EST
(In reply to Martin Perina from comment #18)
> We have created Ansible role ovirt-cluster-upgrade [1] to perform upgrade of
> selected cluster. The role is part of ovirt-ansible-roles package [2], which
> is installed automatically on RHV Manager host so you can find documentation
> for the role in [3].
> 
> To execute this role you need an Ansible playbook which defines required
> parameters, example of this playbook can be found at [4]. Basic information
> how to execute a role from ovirt-ansible-roles package can be found at [2].
> 
> 
> [1]
> https://github.com/oVirt/ovirt-ansible/blob/master/roles/ovirt-cluster-
> upgrade/README.md
> 
> [2] /usr/share/doc/ovirt-ansible-roles/README.md
> 
> [3] /usr/share/doc/ansible/roles/ovirt-cluster-upgrade/README.md
> 
> [4] /usr/share/doc/ovirt-ansible-roles/examples/cluster_upgrade.yml

Link dosent work , any chance for another?
Comment 25 errata-xmlrpc 2018-05-15 13:59:47 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHEA-2018:1534

Note You need to log in before you can comment on or make changes to this bug.