Bug 1539761 - [RFE] changing cluster into maintenance only with special parameter
Summary: [RFE] changing cluster into maintenance only with special parameter
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-ansible-collection
Classification: oVirt
Component: cluster-upgrade
Version: 1.1.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.2.2
: ---
Assignee: Ondra Machacek
QA Contact: Petr Kubica
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-29 14:53 UTC by Petr Kubica
Modified: 2018-03-29 11:01 UTC (History)
2 users (show)

Fixed In Version: ovirt-ansible-cluster-upgrade-1.1.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-29 11:01:01 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.2?
pkubica: testing_plan_complete?
rule-engine: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-ansible-cluster-upgrade pull 15 0 None None None 2018-02-13 12:40:47 UTC

Description Petr Kubica 2018-01-29 14:53:03 UTC 
Description of problem:
Now role is changing cluster into maintenance in every time when admin runs an update. It prevents to other users to run any non-HA VMs in upgraded cluster.

From point of view of providing infrastructure as service to end users, the service (virtualization service) should be available all time. 

If admin needs safe upgrade - prevent to other users to run any non-HA VMs, there should be a variable: safe_upgrade: yes (for example) 

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:53:59 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:01:01 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.
Note You need to log in before you can comment on or make changes to this bug.