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

Bug 892728

Summary: in 3.1 clusters the proxy search algorithm looks for an UP host within the DC and then within the cluster In the GUI it shows the opposite
Product: Red Hat Enterprise Virtualization Manager Reporter: Tareq Alayan <talayan>
Component: ovirt-engine-webadmin-portalAssignee: Eli Mesika <emesika>
Status: CLOSED NOTABUG QA Contact: Pavel Stehlik <pstehlik>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: dyasny, ecohen, iheim, Rhev-m-bugs, ykaul
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-09 00:40:24 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:
Attachments:
Description Flags
screenshot none

Description Tareq Alayan 2013-01-07 17:22:47 UTC 
Description of problem:
In 3.1 cluster, the proxy lookup starts looking for an UP host in DC then goes to lookup for an UP host in cluster

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

Steps to Reproduce:
1. right click on host -> edit
2. click on power management section
3. in the source section we can see that the cluster have more priority 
  
Actual results:
cluster have more priority than DC

Expected results:
DC should be a higher priority since that is the default in 3.1

Additional info:
Comment 1 Tareq Alayan 2013-01-07 17:23:17 UTC 
Created attachment 674185 [details]
screenshot
Comment 2 Eli Mesika 2013-01-08 09:31:01 UTC 
in 3.1 it was agreed to honour the new setting so no difference should be between 3.1 and 3.2 ( since a Host in the cluster is trivially belongs to the DC, backward compatibility is kept)


Closed as NOTABUG
Comment 3 Tareq Alayan 2013-01-08 09:45:11 UTC 
But in 3.1 the default is DC,Cluster.
And in the screen it shows Cluster,DC

it is a confusing.
Comment 4 Tareq Alayan 2013-01-08 14:40:37 UTC 
In this case it will look in the cluster first then DC. 
And it should look in DC then cluster.
I know that the cluster is part of the DC. 
But this way we don't keep the order which means not keeping backwards compatibility. 
I agree it may not cause any damage.
Comment 5 Eli Mesika 2013-01-09 00:40:24 UTC 
Tareq

Please see 
http://wiki.ovirt.org/Talk:HostPMProxyPreferences

It states in the Configuration section :

Not version specific , can be Cluster, DC for both 3.1 & 3.2

This is how it was designed and agreed with PM (Simon G)