Bug 1338843 - Name of migration policy 'safe but not may not converge' is not clear
Summary: Name of migration policy 'safe but not may not converge' is not clear
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.0.0-rc
: 4.0.0
Assignee: Tomas Jelinek
QA Contact: meital avital
Depends On:
TreeView+ depends on / blocked
Reported: 2016-05-23 14:00 UTC by sefi litmanovich
Modified: 2016-08-12 14:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-08-12 14:06:33 UTC
oVirt Team: Virt
michal.skrivanek: ovirt-4.0.0?
rule-engine: planning_ack+
michal.skrivanek: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)
screenshot (2.07 MB, image/png)
2016-05-23 14:00 UTC, sefi litmanovich
no flags Details

System ID Private Priority Status Summary Last Updated
oVirt gerrit 58009 0 master MERGED core: fixed typo in migration policy name 2016-05-25 10:18:47 UTC
oVirt gerrit 58033 0 ovirt-engine-4.0 MERGED core: fixed typo in migration policy name 2016-05-30 08:03:49 UTC

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

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):

How reproducible:

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:

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