Bug 922778

(In reply to Netbulae from comment #0)
Is that still occuring
If so, please attach 

1) screenshots
2) engine.log

may be related to https://bugzilla.redhat.com/show_bug.cgi?id=1048356
but anyway the fencing in that case should be still working 
closing that as the reporter not provided the requested data

Created attachment 881736 [details]
DC and Cluster still blank in fresh 3.4 install

I installed a fresh 3.4 and added two nodes with power management enabled. De dialog is blank as can be seen in the screenshot. The test button reports everything "Ok"

Please provide the output of the following queries :

1) select vds_name, pm_proxy_preferences from vds_static;


2) select * from schema_version where script ilike '%proxy_preferences%';


Thanks

engine=# select vds_name, pm_proxy_preferences from vds_static;
 vds_name | pm_proxy_preferences 
----------+----------------------
 node1 | 
 node2 | 
(2 rows)

engine=# select * from schema_version where script ilike '%proxy_preferences%';
 id  | version  |                        script                        |             checksum             | installed_by |         started_at         |          ended_at          |   state   | current | comment 
-----+----------+------------------------------------------------------+----------------------------------+--------------+----------------------------+----------------------------+-----------+---------+---------
  19 | 03020180 | upgrade/03_02_0180_add_pm_proxy_preferences.sql      | 832f8501fabdad9fe9f3523567223c83 | engine       | 2014-03-28 11:50:01.150114 | 2014-03-28 11:50:01.412819 | INSTALLED | f       | 
 207 | 03040570 | upgrade/03_04_0570_set_proxy_preferences_default.sql | ad0d2f486704100ec927a59b93c83d56 | engine       | 2014-03-28 11:50:38.002931 | 2014-03-28 11:50:38.028549 | INSTALLED | f       | 
(2 rows)

Can you please paste the result of the following query as well, thanks :

select * from vdc_options where option_name ilike 'FenceProxyDefaultPreferences';

engine=# select * from vdc_options where option_name ilike 'FenceProxyDefaultPreferences';
 option_id |         option_name          | option_value | version 
-----------+------------------------------+--------------+---------
        63 | FenceProxyDefaultPreferences | cluster,dc   | general
(1 row)

managed to reproduce , reopening

Sorry, my mistake 

I had tested 

1) Creating a new Host

2) Editing an existing host with no PM defined

When the New/edit Host popup displayed I had in the "Source" field a list of two items : "cluster" and "dc"

Can you please describe the full scenario you are doing since I am not able to get an empty "source" list

These are all the steps:

Clean Centos 6.5 install
yum update
reboot
install repo's
yum install ovirt-engine
engine-setup

install ovirt node iso from pxe
login with admin
enable dhcp
connect to ovirt-engine
exit

login to ovirt engine web interface
approve node, enable power management, fill in power management required fields
approve node2, enable power management, fill in power management required fields

That's it, I haven't done anything else with this install yet.

I'll do it again tomorrow as I have to check some things for other issues.

Any updates ?

I did a fresh install but have exactly the same issue. The source is blank on both power management tabs, but the test button works ok.

Created attachment 883503 [details]
Node2 power management dialog

Still blank

(In reply to Netbulae from comment #13)
> Created attachment 883503 [details]
> Node2 power management dialog
> 
> Still blank

please run the following on your database and let me know if you see the values after doing that and restart the oVirt engine 

> update vds_static set pm_proxy_preferences = 'cluster,dc' where pm_enabled;

Created attachment 884121 [details]
screenshot after pm_proxy_preferences update

It looks ok now

update vds_static set pm_proxy_preferences = 'cluster,dc' where pm_enabled;
UPDATE 1

Was resolved as part of BZ 1048356 resolving
Since this was a fix in one of the upgrade scrips, it affects only upgrades done after the fix was merged
A specific work-around was suggested and worked to workaround this problem manually (see comment 14 and comment 15)

*** This bug has been marked as a duplicate of bug 1048356 ***