> On 15 Feb 2018, at 16:37, Jason Keltz <j...@cse.yorku.ca> wrote:
> On 02/15/2018 08:48 AM, nico...@devels.es wrote:
>> Hi,
>> We upgraded one of our infrastructures to 4.2.0 recently and since then some 
>> of our machines have the "Console" button greyed-out in the Admin UI, like 
>> they were disabled.
>> I changed their compatibility to 4.2 but with no luck, as they're still 
>> disabled.
>> Is there a way to know why is that, and how to solve it?
>> I'm attaching a screenshot.
> Hi Nicolas.
> I had the same problem with most of my VMs after the upgrade from 4.1 to 4.2.
> See bugzilla here: https://bugzilla.redhat.com/show_bug.cgi?id=1528868
> (which admittedly was a mesh of a bunch of different issues that occurred)

yeah, that’s not a good idea to mix more issues:)
Seems https://bugzilla.redhat.com/show_bug.cgi?id=1528868#c26 is the last one 
relevant to the grayed out console problem in this email thread.

it’s also possible to check "VM Devices” subtab and list the graphical devices. 
If this is the same problem as from Nicolas then it would list cirrus and it 
would be great if you can confirm the conditionas are similar (i.e. originally 
a 3.6 VM)
And then - if possible - describe some history of what happened. When was the 
VM created, when was cluster updated, when the system was upgraded and to what 


> Red Hat was never really able to figure out why, and I think they pretty much 
> just dropped the issue because it seemed like it only happened for me.  In 
> order to resolve it, I had to delete the VMs (not the disk of course), and 
> recreate them, and then I got the console option back.
> It's "good" to see that it's not just me that had this problem. There's a bug 
> to be found there somewhere!!
> Jason.
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

Users mailing list

Reply via email to