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

Bug 1338843

Summary: Name of migration policy 'safe but not may not converge' is not clear
Product: [oVirt] ovirt-engine Reporter: sefi litmanovich <slitmano>
Component: BLL.VirtAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED CURRENTRELEASE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: bugs, gklein
Target Milestone: ovirt-4.0.0-rcFlags: michal.skrivanek: ovirt-4.0.0?
rule-engine: planning_ack+
michal.skrivanek: devel_ack+
mavital: testing_ack+
Target Release: 4.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-12 14:06:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description sefi litmanovich 2016-05-23 14:00:21 UTC
Created attachment 1160642 [details]
screenshot

Description of problem:

On ovirt-4.0 new migration policies were added.
One of the is called 'safe but not may not converge'
While the description for the policy seems fine, this name is a bit strange, shouldn't it be 'safe but may not converge'? there seems to be a redundant 'not' in that sentence.

Version-Release number of selected component (if applicable):
ovirt-engine-4.0.0-0.7.master.el7ev.noarch

How reproducible:
always

Steps to Reproduce:
1. open migration sub tab under add/edit cluster

Comment 1 meital avital 2016-08-11 10:59:51 UTC
We change the policy name to ' Minimize downtime', now it is clearer

Comment 2 meital avital 2016-08-11 11:01:42 UTC
Verified on version: 4.0.2.4-0.1.el7ev