Bug 1131545

Summary: SSH Soft Fencing executed even a host does not have PM enabled
Product: [Retired] oVirt Reporter: Jiri Belka <jbelka>
Component: ovirt-engine-coreAssignee: bugs <bugs>
Status: CLOSED NOTABUG QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5CC: acathrow, ecohen, gklein, iheim, oourfali, 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: 2014-08-20 10:20:24 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 Jiri Belka 2014-08-19 14:28:28 UTC
Created attachment 928389 [details]
engine.log

Description of problem:
SSH Soft Fencing executed even a host does not have PM enabled. It seems odd.

Version-Release number of selected component (if applicable):
ovirt-engine-backend-3.5.0-0.0.master.20140804172041.git23b558e.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. stop supervdsmd and vdsmd
2. wait
3.

Actual results:
"restarted" via ssh soft fencing

Expected results:
?? probably nothing, up to sysadmin intervention ??

Additional info:

Comment 1 Jiri Belka 2014-08-19 14:31:48 UTC
fyi i discovered this after:

[root@dell-r210ii-04 ~]# /etc/init.d/vdsmd start
vdsm: already running                                      [  OK  ]
vdsm start                                                 [  OK  ]

...yes, it was up before i tried to start it :)

Comment 2 Oved Ourfali 2014-08-20 10:20:24 UTC
(In reply to Jiri Belka from comment #0)
> Created attachment 928389 [details]
> engine.log
> 
> Description of problem:
> SSH Soft Fencing executed even a host does not have PM enabled. It seems odd.
> 
> Version-Release number of selected component (if applicable):
> ovirt-engine-backend-3.5.0-0.0.master.20140804172041.git23b558e.el6.noarch
> 
> How reproducible:
> 100%
> 
> Steps to Reproduce:
> 1. stop supervdsmd and vdsmd
> 2. wait
> 3.
> 
> Actual results:
> "restarted" via ssh soft fencing
> 
> Expected results:
> ?? probably nothing, up to sysadmin intervention ??
> 
> Additional info:

It is not odd.
When a host is non-responsive we try to do whatever is possible to recover that.
If it doesn't have PM enabled, then the best we can do is try to restart VDSM, which works well a lot of times.

It has nothing to do with PM, and thus it doesn't require it to be configured.