Bug 967446 - Restarting Host lhprevh01b.pgds.local (Fencing) on Cluster <UNKNOWN>
Summary: Restarting Host lhprevh01b.pgds.local (Fencing) on Cluster <UNKNOWN>
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.4
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: 3.3.0
Assignee: Eli Mesika
QA Contact: Artyom
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-27 07:50 UTC by Daniele
Modified: 2018-12-02 17:24 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-12 14:31:42 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ?
Note You need to log in before you can comment on or make changes to this bug.