Bug 920112

Summary: [Power Management] There is no notification on event tab about what proxy is selected to fence a host
Product: Red Hat Enterprise Virtualization Manager Reporter: Tareq Alayan <talayan>
Component: ovirt-engineAssignee: Eli Mesika <emesika>
Status: CLOSED CURRENTRELEASE QA Contact: Tareq Alayan <talayan>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: acathrow, dyasny, emesika, iheim, lpeer, pstehlik, Rhev-m-bugs, sgrinber, yeylon, ykaul, yzaslavs
Target Milestone: ---   
Target Release: 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: sf13 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 Tareq Alayan 2013-03-11 11:15:30 UTC
Description of problem:
User is not aware of what host has been selected to be a proxy to fence a host.

Version-Release number of selected component (if applicable):
sf9

How reproducible:
always

Steps to Reproduce:
1. have an up and running env with 2 hosts at least with pm configured 
2. restart one of the hosts

Actual results:
on event tab you will see a message like : Host XXXX was restarted by vdcadmin.
  
Expected results:
"Host XXXX was restarted by vdcadmin, Host YYYY was selected as a fencing proxy".
  
Additional info:
This is of course very important when there are more than 2 hosts and many clusters.

Comment 1 Yair Zaslavsky 2013-03-17 08:28:51 UTC
Restart is composed from stop + start.
Two internal FenceBase commands (StopVDS,StartVDS) are invoked.
I think that we should use the VdcReturnValue object, and put on it the host that is used as the proxy agent (which is calculated at FenceExecutor.findVdsToFence).

Comment 4 Tareq Alayan 2013-04-09 09:08:59 UTC
verified

Comment 5 Itamar Heim 2013-06-11 08:59:35 UTC
3.2 has been released

Comment 6 Itamar Heim 2013-06-11 08:59:35 UTC
3.2 has been released

Comment 7 Itamar Heim 2013-06-11 08:59:35 UTC
3.2 has been released

Comment 8 Itamar Heim 2013-06-11 09:01:08 UTC
3.2 has been released

Comment 9 Itamar Heim 2013-06-11 09:30:38 UTC
3.2 has been released