+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1651406 +++
======================================================================

1. Proposed title of this feature request
Allow Maintenance of Host with Positive Enforcing VM Affinity Rules.

3. What is the nature and description of the request?
Currently by design it is not allowed to break a hard affinity rule to migrate VMs to place host in maintenance mode and it behaves as if 2 or more VMs were pinned to the same host. Request is to allow placing such host in maintenance mode by migrating all VMs.

4. Why does the customer need this? (List the business requirements here)
We are creating an integrated product based on RHHI/RHV which will be installed as part of several isolated networks around the world and the system is expected to work under most extreme circumstances (including, but not limited to, man and nature originating national and international disasters). As such, not all admins/users using the system will be RHV experts so the user experience should be as smooth as possible. The requirement to make affinity rule non-enforcing, then put host to maintenance, then reset the affinity rule back to enforcing has two steps too many that might cause a user to lose time during emergency or, if distracted (which is likely under extreme circumstances), may not remember reset the affinity rule back to enforcing, causing hard-to-find issues later on if the tightly-coupled VMs end up running on separate hosts.

5. How would the customer like to achieve this? (List the functional requirements here)
It must be possible to put a Host to Maintenance even if VMs with Hard Positive VM Polarity are running on it provided that there are resources on other Hosts where they can be migrated, without the admin/user/script needing to tweak Affinity Rules during this operation.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Yes.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
I am not able to find any.

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
Preferably as a part an RHV 4.2 errata but if that is not feasible then as part of RHV 4.3. First half of 2019 is when we ideally would like to have this feature available.

9. Is the sales team involved in this request and do they have any additional input?
No.

10. List any affected packages or components.
ovirt-engine.

11. Would the customer be able to assist in testing this functionality if implemented?
Yes.

(Originally by Ameya Charekar)