Bug 1249943

Summary: Failed to power fence host - No route to host
Product: [Retired] oVirt Reporter: Petr Matyáš <pmatyas>
Component: ovirt-engine-coreAssignee: bugs <bugs>
Status: CLOSED NOTABUG QA Contact: Petr Matyáš <pmatyas>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.6CC: bugs, ecohen, gklein, lsurette, oourfali, rbalakri, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-04 12:05:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Engine log none

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.