Bug 967446

Summary:	Restarting Host lhprevh01b.pgds.local (Fencing) on Cluster <UNKNOWN>
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Daniele <dconsoli>
Component:	ovirt-engine	Assignee:	Eli Mesika <emesika>
Status:	CLOSED NOTABUG	QA Contact:	Artyom <alukiano>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.1.4	CC:	acathrow, bazulay, dconsoli, emesika, iheim, jkt, lpeer, pstehlik, Rhev-m-bugs, yeylon
Target Milestone:	---
Target Release:	3.3.0
Hardware:	All
OS:	All
Whiteboard:	infra
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-08-12 14:31:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniele 2013-05-27 07:50:26 UTC

Description of problem:
Restaring a hypervisors resulted in taks message :-
Restarting Host lhprevh01b.pgds.local (Fencing) on Cluster <UNKNOWN>

Version-Release number of selected component (if applicable):
RHEV 3.1
vdsm-4.10.2-1.8.el6ev

How reproducible:
Not sure yet. Haven't found a pattern.

Steps to Reproduce:
1.
2.
3.

Actual results:
Restarting Host lhprevh01b.pgds.local (Fencing) on Cluster <UNKNOWN>

Expected results:
<UNKNOWN> should be replaced with the host's name.

Additional info:

Comment 1 Eli Mesika 2013-05-27 20:55:32 UTC

Please update with a valid reproducable scenario

Comment 2 Daniele 2013-05-28 10:42:13 UTC

I'm not sure how, since we cannot reproduce yet. A similar issue is being worked on BZ#965617. We're trying to identify a way to reproduce.

Comment 3 Barak 2013-06-30 15:21:16 UTC

Daniele,

Was the fencing proxy selection cluster,DC ?
was lhprevh01b.pgds.local in a local storage DC ? 
Otherwise
   How many hosts were in the cluster where lhprevh01b.pgds.local resided in ?