Bug 1249943 - Failed to power fence host - No route to host
Summary: Failed to power fence host - No route to host
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: Petr Matyáš
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-04 08:22 UTC by Petr Matyáš
Modified: 2015-08-04 12:25 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-04 12:05:15 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
Engine log (9.62 MB, text/plain)
2015-08-04 08:22 UTC, Petr Matyáš
no flags Details

Description Petr Matyáš 2015-08-04 08:22:16 UTC
Created attachment 1058983 [details]
Engine log

Description of problem:
Host is not started automatically after turning it off manually in manager, even though power management is configured properly. However the host can be restarted through the engine's power management.

Version-Release number of selected component (if applicable):
ovirt-engine-3.6.0-0.0.master.20150802181117.git8c45eb7.el6.noarch

How reproducible:
always on my setup

Steps to Reproduce:
1. turn host down
2. wait for engine to try to start the host through power management
3.

Actual results:
host wont start

Expected results:
host starts correctly

Additional info:

Comment 1 Oved Ourfali 2015-08-04 12:05:15 UTC
Host shouldn't be started automatically after they are brought down manually, whether by using the admin portal, or manually.
We only stop/start hosts automatically as part of the fencing mechanism.

Comment 2 Petr Matyáš 2015-08-04 12:19:07 UTC
Well, I was testing if it behaves the same as 3.5 after fencing refactoring, which after manual shutdown of host starts the host automatically, but I suppose that approach changed.

Comment 3 Oved Ourfali 2015-08-04 12:25:09 UTC
It hasn't changed.
I'm highly surprised that it happened before.
Only fencing triggers a flow of:
1. stop host
2. wait for it to be done (determined by power management)
3. start host

Manual stop isn't followed by manual start.


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