Bug 1145321 - non-responding host is selected as a proxy for fencing operations
Summary: non-responding host is selected as a proxy for fencing operations
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.5.0
Assignee: Eli Mesika
QA Contact: sefi litmanovich
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-22 20:12 UTC by Eli Mesika
Modified: 2016-02-10 19:11 UTC (History)
11 users (show)

Fixed In Version: org.ovirt.engine-root-3.5.0-14
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 17:11:36 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 33220 0 master MERGED core: skip non-responding hosts in proxy selection. Never
oVirt gerrit 33431 0 ovirt-engine-3.5 MERGED core: skip non-responding hosts in proxy selection. Never

Description Eli Mesika 2014-09-22 20:12:26 UTC 
Description of problem:
non-responding host is selected as a proxy for fencing operations 


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


How reproducible:


Steps to Reproduce:
1. Have Host1 with PM and Host2 under cluster C1 
2. Have Host3 under cluster C2 on the same DC as Host 1 and Host2
3. block communication from engine to Host2
4. wait for Host2 to become non-responsive
5. block communication from engine to Host1
6. Host2 is selected as a proxy for fencing operation and only after it fails Host 3 is selected and perform the operation successfully 

Actual results:
non-responding hots Host2 is selected as a proxy

Expected results:
non-responding hosts should be skipped while searching for a proxy
In the scenario above, proxy selection algorithm should return Host3 for the first time

Additional info:
Comment 1 Eyal Edri 2014-10-07 07:13:13 UTC 
this bug status was moved to MODIFIED before engine vt5 was built,
hence moving to on_qa, if this was mistake and the fix isn't in,
please contact rhev-integ
Comment 2 sefi litmanovich 2014-10-14 13:05:13 UTC 
Verified with rhevm-3.5.0-0.14.beta.el6ev.noarch according to description.
Comment 3 Eyal Edri 2015-02-17 17:11:36 UTC 
rhev 3.5.0 was released. closing.
Note You need to log in before you can comment on or make changes to this bug.