Bug 1114253

+++ This bug was initially created as a clone of Bug #1054778 +++

Description of problem:

When you shut down a host in a data center with no other host, you are
unable to start it using the configured power management in ovirt.
Version-Release number of selected component (if applicable):

ovirt-engine 3.3.2 on EL 6

How reproducible:
shut down a host in a datacenter with a single host (e.g. "init 0" on a shell)

Steps to Reproduce:
1. shut down a host e.g. in a local storage DC
2. the host becomes "non responsive"
3. try to start the host via the configured powermanagement

Actual results:

Error while executing action:

hostname:

    There is no other Host in the Data Center that can be used to test the Power Management settings.

Expected results:

the hosts starts, there is no test of power management necessary.

Additional info:

no other action helps to circumvent this test:
put host in maintenance, confirm manually host has been rebooted.

you end up with the failing power management test (why should it test it with
another host in the first place?)

Related Bug: BZ1053434

--- Additional comment from Itamar Heim on 2014-01-17 12:56:07 EST ---

my first instinct was this was similar to bug 837539, but its not.

the engine doesn't perform fence operations from the engine rather from another host in the cluster/dc, hence needs "another running host" (by asking vdsm on the other host to call the fence script)

eli, maybe until we can do this from engine, we can allow doing this from a host not in same DC?
(wouldn't work for an engine with really only a single host, but for most use cases should be good enough?)

--- Additional comment from Eli Mesika on 2014-01-26 10:30:23 EST ---

(In reply to Itamar Heim from comment #1)

> eli, maybe until we can do this from engine, we can allow doing this from a
> host not in same DC?
> (wouldn't work for an engine with really only a single host, but for most
> use cases should be good enough?)

Yes, we have now the pm_proxy_preferences field that is set by default to "cluster,DC" maybe we can support that by adding "other" such that in hosts that have this value set to "cluster,DC,other" we will search for proxy in other DCs

--- Additional comment from Itamar Heim on 2014-02-13 13:31:06 EST ---

pushing to target release 3.5, assuming its not planned for 3.4 at this point...

--- Additional comment from Eli Mesika on 2014-04-07 16:19:18 EDT ---

We will address for 3.5 only the option to look for proxy outside the DC where the host is located and try to use other DCs

This will be done by adding to the pm_proxy_preferences field which is defaulted now to "cluster,DC" another option named otherDC.
(The pm_proxy_preferences value is available via the UI Host New/Edit PM TAB in the field named "source" , in the API it is under <pm_proxies>)

The default will stay "cluster,DC" and the admin can change this value per host using the API