Description of problem: After upgrading a RHEV environment from 3.1 to 3.2, the sources values 'cluster' and 'dc' in the Power Management tab while editing an existing host in the environment are not shown, only are being displayed while adding a new host in the environment. Version-Release number of selected component (if applicable): rhevm-3.2.5-0.49.el6ev.noarch RHEV Hypervisor - 6.5 - 20131204.0.3.2.el6_5 vdsm-4.10.2-27.0.el6ev How reproducible: 100% Steps to Reproduce: 1. Upgrade a RHEV-M from 3.1 to 3.2 2. Add a new host into the DC/Cluster 3. Edit the existing and the new host and search for 'cluster' and 'dc' options in the Power Management tab. Actual results: The existing hosts can't see the 'cluster' and 'dc' options in the Power Management tab. Only the new added host can see them. Expected results: All the hosts in the environment should be able to use this new feature while upgrading from 3.1 to 3.2
(In reply to Javier Coscia from comment #0) > Description of problem: > Expected results: > All the hosts in the environment should be able to use this new feature > while upgrading from 3.1 to 3.2 Just to make it clear, the absence of the Cluster and DC values for installed Hosts means that it still will get the default which is "cluster,dc) , that means that even installed Hosts will look first foir proxy in the Cluster and then in the DC. So, the only affect of this bug is the ability to sort the "Cluster,DC" values as "DC, Cluster"
This bug is referenced in ovirt-engine-3.4.0-beta3 logs. Moving to ON_QA
Verified. 1) installed ovirt-3.3.4 2) added host with pm and configured pm 3) updated to ovirt-3.4.0-0.11beta3 4) edit host - power management - dc and cluster options appear as expected 5) engine_20140226134338=# select vds_name,pm_proxy_preferences from vds_static; vds_name | pm_proxy_preferences ----------+---------------------- rose07 | cluster,dc (1 row)
*** Bug 922778 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0506.html