> On 19 Feb 2018, at 23:36, Jason Keltz <j...@cse.yorku.ca> wrote:
> Hi Michal,
> On 2/15/2018 12:05 PM, Michal Skrivanek wrote:
>>> On 15 Feb 2018, at 16:37, Jason Keltz <j...@cse.yorku.ca> 
>>> <mailto:j...@cse.yorku.ca> wrote:
>>> On 02/15/2018 08:48 AM, nico...@devels.es <mailto: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 
>>> <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 
>> <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.

well, we keep the date and who did that, but we can’t really keep all the logs 
forever. Well, you can if you archive them somewhere, but I guess that’s 
impractical for such a long time:-D

>  VM Device subtab: (no Cirrus)
> <eadpakjggeififdb.png>

so this is a screenshot from VM where the button is grayed out when you start 
Hm..it doesn’t look wrong.

>> 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 
> headless,

Can you get engine.log and vdsm log when you attempt to start that VM ? just 
the relevant part is enough.


>> 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.
> Jason.
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

Users mailing list

Reply via email to