[ovirt-users] Console button greyed out (4.2)

Jason Keltz jas at cse.yorku.ca
Mon Feb 19 22:36:09 UTC 2018

Hi Michal,

On 2/15/2018 12:05 PM, Michal Skrivanek wrote:

>> On 15 Feb 2018, at 16:37, Jason Keltz <jas at cse.yorku.ca> wrote:
>> On 02/15/2018 08:48 AM, nicolas at 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)
I believe it was originally a 3.6 VM.  Is there anywhere I can verify 
this info? If not, it would be helpful if oVirt kept track of the 
version that created the VM for cases just like this.

  VM Device subtab: (no Cirrus)

> 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 versions.
All I know is that everything was working fine, then I updated to 4.2, 
updated cluster version, and then most of my consoles were not 
available.  I can't remember if this happened before the cluster upgrade 
or not.  I suspect it was most and not all VMs since some of them had 
been created later than 3.6, and this was  an older one.  I only have 
this one VM left in this state because I had deleted the other VMs and 
recreated them one at a time...
I will wait to see if you want me to try Vineet's solution of making it 
> The before bringing it back up, unchecked headless in the VM
> We then had to do a Run-Once which failed
> Then did a normal Run.
> Console was available, and all hardware came back fine.
... but I won't try that yet in case you need additional information 
from the VM first.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180219/f009a237/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: eadpakjggeififdb.png
Type: image/png
Size: 43283 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180219/f009a237/attachment.png>

More information about the Users mailing list