Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1070674

Summary:

Provide informations about fencing in RHEV-M

Product:

Red Hat Enterprise Virtualization Manager

Reporter:

Fabian Deutsch <fdeutsch>

Component:

ovirt-engine

Assignee:

Eli Mesika <emesika>

Status:

CLOSED CURRENTRELEASE

QA Contact:

sefi litmanovich <slitmano>

Severity:

unspecified

Docs Contact:

Priority:

unspecified

Version:

unspecified

CC:

aberezin, bazulay, emesika, gklein, iheim, lpeer, oourfali, pstehlik, rbalakri, Rhev-m-bugs, yeylon

Target Milestone:

---

Target Release:

3.5.0

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

infra

Fixed In Version:

org.ovirt.engine-root-3.5.0-9

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2015-02-17 17:09:27 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:

Bug Depends On:

1090520

Bug Blocks:

1142923, 1156165

Attachments:

Description	Flags
engine log	none

Description Fabian Deutsch 2014-02-27 10:56:07 UTC

Description of problem:
Currently it's not obvious why a fencing event occucred.

To give the user a hint it would be better to display/gather more informations about the fencing events.

This would also help GSS to analyze the incident.

Comment 1 Barak 2014-04-13 11:50:34 UTC

Eli please make sure we have the folowing in the event log:
- host enetered connecting status (+ timeout calculated)
- host became non-responsive
- all the fencing attempts (including the proxy selected)

Ar

Comment 2 Barak 2014-04-24 07:36:58 UTC

*** Bug 1090520 has been marked as a duplicate of this bug. ***

Comment 3 sefi litmanovich 2014-08-21 12:33:23 UTC

attempt to verify with ovirt-engine-3.5.0-0.0.master.20140804172041.git23b558e.el6.noarch.

1. install 2 hosts, at least 1 with pm.
2. stop network for host with pm.
3.verify all the messages as described in comment #1 are issued.

failed:

regarding the new message added in this patch:

VDS_HOST_NOT_RESPONDING_CONNECTING=Host ${VdsName} is not responding. It will stay in Connecting sta
te for a grace period of ${Seconds} seconds and after that an attempt to fence the host will be issu
ed.

the message appears in engine.log but not issued in events in ui.

from engine.log:

2014-08-21 14:54:30,194 WARN  [org.ovirt.engine.core.vdsbroker.VdsManager] (DefaultQuartzScheduler_Worker-69) Host {hostname} is not responding. It will stay in Connecting state for a grace period of $120 seconds and after that an attempt to fence the host will be issued.

Comment 4 sefi litmanovich 2014-08-21 12:34:07 UTC

Created attachment 929190 [details]
engine log

Comment 5 sefi litmanovich 2014-09-10 10:07:21 UTC

Verified with rhevm-3.5.0-0.10.master.el6ev.noarch.

1. install 2 hosts, at least 1 with pm.
2. stop network for host with pm.
3. all the messages as described in comment #1 were issued on audit log and appeared in ui as well as engine.log.

Comment 6 Eyal Edri 2015-02-17 17:09:27 UTC

rhev 3.5.0 was released. closing.