Description of problem:
As described in the topic below I also get greyed out icons on VM's, after a couple of refreshed sometimes some buttons are available for usage.
This also happens on the hosts tab it's host specific tabs. Networks is sometimes empty for a host, you need to click around in the tabs, the select tab hangs, some other is selected then where you actually on.
Version-Release number of selected component (if applicable):
Go to the webadmin and click around
Steps to Reproduce:
1. Go to the webadmin
2. Click on VM's
3. Look at the VM buttons
Buttons are greyed out
Buttons should be avaiable
What I also have seen is that when I click on the console of a VM, the .vv file contains a different host than where it's running on.
discussion/more details are in http://lists.ovirt.org/pipermail/users/2013-December/thread.html [look for "Strange UI bug"]
(In reply to Yamakasi from comment #0)
> This also happens on the hosts tab it's host specific tabs. Networks is
> sometimes empty for a host, you need to click around in the tabs, the select
> tab hangs, some other is selected then where you actually on.
I am not sure if the above issue is related to the main VMs issue that was reported here and was also reported and already discussed in .
Moreover, in  it is mentioned that all other tabs are working as expected.
Please note that once there is an exception on the client side, there is no way of knowing how the GUI will behave from that point on. So I suggest to fix the known VM/OsRepository issue first, and then open a separate bug on additional issues, if there are any. Thanks.
 http://lists.ovirt.org/pipermail/users/2013-December/thread.html [look for "Strange UI bug"]
setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
decreasing prio as this happens only when someone modifies osinfo
lowering prio as this happens only after manual removal of OS type from config
There is a problem with the patch that fixed this bug. I just opened a new bug to fix that  for 3.5 target.
FailedQA in ovirt-engine-3.5.0-0.0.master.20140804172041.git23b558e.el6.noarch (rc1).
The Gerrit patch http://gerrit.ovirt.org/23809 was practically reverted in bug 1062344, because it introduces a regression regarding default VM OS selection for x64/ppc archs.
IMHO probably the best solution will be to upload the patch #23809 again, extended by handling the OS architectures, which will also resolve bug 1062344.
It seems bugfix of 1062344 reverted part of the original solution. Posted small patch that should fix that.
oVirt 3.5 has been released and should include the fix for this issue.