Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1444982

Summary:	Host can be moved to maintenance while it there are jobs running on it
Product:	[oVirt] ovirt-engine	Reporter:	Liron Aravot <laravot>
Component:	BLL.Storage	Assignee:	Liron Aravot <laravot>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Kevin Alon Goldblatt <kgoldbla>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1.1	CC:	amureini, bugs, dfodor, tnisan
Target Milestone:	ovirt-4.1.2	Flags:	rule-engine: ovirt-4.1+ amureini: devel_ack+
Target Release:	4.1.2.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: A host which is executing storage jobs may be put into maintenance mode by the engine during the jobs execution - which may lead to unexpected issues. Fix: The engine should block moving a host to maintenance while it's running storage jobs. Result: The engine prevents moving a host which is executing jobs to maintenance till the jobs running on the host ends.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-23 08:18:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Liron Aravot 2017-04-24 16:39:37 UTC

Description of problem:
When a host is running jobs the engine doesn't block moving it to maintenance while the jobs are running.

How reproducible:
Always

Steps to Reproduce:
- Have a 4.1 DC with one host and two or more storage domains.

1. Create a disk (to ease the reproduction make sure that the disk contains data).
2. Move the disk 
3. While the copy_data job is running attempt to switch the host to maintenance.

Expected results:
The engine should block moving the host to maintenance until the jobs running on the host are completed.

Comment 1 Allon Mureinik 2017-04-25 06:47:06 UTC

Liron - this bug may have visible but hard-to-understand effects on user environments in oVirt 4.1/4.1.1.
Can you please add some doctext to it to explain the issue and the fix?
Thanks!

Comment 2 rhev-integ 2017-04-26 10:40:27 UTC

INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[TAG 'ovirt-engine-4.1.2' DOESN'T CONTAIN PATCH 'https://gerrit.ovirt.org/75955']
gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.1.2

For more info please contact: infra

Comment 3 Kevin Alon Goldblatt 2017-05-08 15:23:23 UTC

Verified with the following code:
------------------------------------
ovirt-engine-4.1.2.1-0.1.el7.noarch
rhevm-4.1.2.1-0.1.el7.noarch
vdsm-4.19.12-1.el7ev.x86_64


Verified with the following scenario:
-------------------------------------
Steps to Reproduce:
- Have a 4.1 DC with one host and two or more storage domains.

1. Create a disk on a VM and copy around 1G og data to it (to ease the reproduction make sure that the disk contains data).
2. Move the disk 
3. While the copy_data job is running attempt to switch the host to maintenance >>>> The engine blocks moving the host to maintenance until the jobs running on the host are completed.


Moving to VERIFIED!