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

[Jason Keltz]

On 02/20/2018 12:17 PM, Michal Skrivanek wrote:
On 19 Feb 2018, at 23:36, Jason Keltz > wrote:


Hi Michal,

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


On 15 Feb 2018, at 16:37, Jason Keltz  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:)
Seemshttps://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.


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


I wasn't really thinking in terms of logs.  I was thinking a database 
field that tracks the ovirt version that created the VM.




 VM Device subtab: (no Cirrus)



so this is a screenshot from VM where the button is grayed out when 
you start it?

Hm..it doesn’t look wrong.


Yes.


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,


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



Sure.. I restarted the VM (called "rs").

engine.log: http://www.eecs.yorku.ca/~jas/ovirt-debug/02202018/engine.log

vdsm log: http://www.eecs.yorku.ca/~jas/ovirt-debug/02202018/vdsm.log

Jason.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[Michal Skrivanek]

> On 19 Feb 2018, at 23:36, Jason Keltz  wrote:
> 
> Hi Michal,
> 
> On 2/15/2018 12:05 PM, Michal Skrivanek wrote:
> 
>>> On 15 Feb 2018, at 16:37, Jason Keltz  
>>>  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)
> 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.

Hi,
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)
> 

so this is a screenshot from VM where the button is grayed out when you start 
it? 
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,

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

Thanks,
michal

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

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

[Jason Keltz]

Hi Michal,

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


On 15 Feb 2018, at 16:37, Jason Keltz  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)
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 
headless,

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

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

[nicolas]

Thanks guys, setting the VM to headless and then removing this option 
seemed to do the trick. Indeed, this VM was created back in 3.6, however 
it had QXL set in options. Seems that despite this something was not 
migrated correctly.


I think I have more machines in this situation, in case the oVirt team 
would like to make some additional tests.


Regards.

El 2018-02-15 19:39, Vineet Khandpur escribió:

Hello.

Just had the same issue

@ 4.1, upgraded to 4.2(.1)

Updated cluster compatibility, then, data centre compatibility

All VMs lost their hardware (NICs (showed attached but unplugged),
disks (status changed to disabled) and console)

Our solution was simply to connect the NICs, activate the disks, then
edit the VM and set Console to headless.

Shut down the VM

Then 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.

Didn't have to delete and re-create anything (although had to perform
the above on all 70+ production hosts including our main web servers
and HA load balancers .. which wasn't fun) ...

Hope this helps someone

vk

On 15 February 2018 at 12:28, John Taylor  wrote:


On Thu, Feb 15, 2018 at 11:54 AM, Michal Skrivanek
 wrote:




On 15 Feb 2018, at 15:58, John Taylor 

wrote:


Hi Nicolas,
I had the same problem and it looked like it was because of some

older

vms (I believe from 3.6) that were configured with console with

video

type of CIRRUS and protocol VNC.


3.6 had cirrus indeed. That should work. Can you somehow confirm

it was really a 3.6 VM and it stopped working in 4.2? The exact
steps are important, unfortunately.




I'm pretty sure they were VMs created in 3.6, but I can't say for
absolute certain.  Sorry.


Tracing it out it showed that the vm  libvirt xml was begin set

to

headless.


do you at least recall what cluster level version it was when it

stopped working? The VM definition should have been changed to VGA
when you move the VM from 3.6 cluster to a 4.0+

I upgraded from 4.1.something and I'm pretty sure at the time the
cluster level was 4.1, and those same VMs were able to get
consoles.
Sorry I can't be more help now. I'll see if I have any notes that
might help me remember.




  I tried different settings but the only thing that seemed
to work was to set them to headless, then reopen config and set

them

to something else.

-John

On Thu, Feb 15, 2018 at 8:48 AM,   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.

Thanks.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users [1]


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users [1]





___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users [1]




Links:
--
[1] http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[Vineet Khandpur]

Hello.
Just had the same issue

@ 4.1, upgraded to 4.2(.1)
Updated cluster compatibility, then, data centre compatibility
All VMs lost their hardware (NICs (showed attached but unplugged), disks
(status changed to disabled) and console)

Our solution was simply to connect the NICs, activate the disks, then edit
the VM and set Console to headless.

Shut down the VM

Then 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.

Didn't have to delete and re-create anything (although had to perform the
above on all 70+ production hosts including our main web servers and HA
load balancers .. which wasn't fun) ...

Hope this helps someone

vk

On 15 February 2018 at 12:28, John Taylor  wrote:

> On Thu, Feb 15, 2018 at 11:54 AM, Michal Skrivanek
>  wrote:
> >
> >
> >> On 15 Feb 2018, at 15:58, John Taylor  wrote:
> >>
> >> Hi Nicolas,
> >> I had the same problem and it looked like it was because of some older
> >> vms (I believe from 3.6) that were configured with console with video
> >> type of CIRRUS and protocol VNC.
> >
> > 3.6 had cirrus indeed. That should work. Can you somehow confirm it was
> really a 3.6 VM and it stopped working in 4.2? The exact steps are
> important, unfortunately.
> >
>
> I'm pretty sure they were VMs created in 3.6, but I can't say for
> absolute certain.  Sorry.
>
> >> Tracing it out it showed that the vm  libvirt xml was begin set to
> >> headless.
> >
> > do you at least recall what cluster level version it was when it stopped
> working? The VM definition should have been changed to VGA when you move
> the VM from 3.6 cluster to a 4.0+
>
> I upgraded from 4.1.something and I'm pretty sure at the time the
> cluster level was 4.1, and those same VMs were able to get consoles.
> Sorry I can't be more help now. I'll see if I have any notes that
> might help me remember.
>
> >
> >>  I tried different settings but the only thing that seemed
> >> to work was to set them to headless, then reopen config and set them
> >> to something else.
> >>
> >> -John
> >>
> >> On Thu, Feb 15, 2018 at 8:48 AM,   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.
> >>>
> >>> Thanks.
> >>> ___
> >>> Users mailing list
> >>> Users@ovirt.org
> >>> http://lists.ovirt.org/mailman/listinfo/users
> >>>
> >> ___
> >> Users mailing list
> >> Users@ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/users
> >>
> >>
> >
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[John Taylor]

On Thu, Feb 15, 2018 at 11:54 AM, Michal Skrivanek
 wrote:
>
>
>> On 15 Feb 2018, at 15:58, John Taylor  wrote:
>>
>> Hi Nicolas,
>> I had the same problem and it looked like it was because of some older
>> vms (I believe from 3.6) that were configured with console with video
>> type of CIRRUS and protocol VNC.
>
> 3.6 had cirrus indeed. That should work. Can you somehow confirm it was 
> really a 3.6 VM and it stopped working in 4.2? The exact steps are important, 
> unfortunately.
>

I'm pretty sure they were VMs created in 3.6, but I can't say for
absolute certain.  Sorry.

>> Tracing it out it showed that the vm  libvirt xml was begin set to
>> headless.
>
> do you at least recall what cluster level version it was when it stopped 
> working? The VM definition should have been changed to VGA when you move the 
> VM from 3.6 cluster to a 4.0+

I upgraded from 4.1.something and I'm pretty sure at the time the
cluster level was 4.1, and those same VMs were able to get consoles.
Sorry I can't be more help now. I'll see if I have any notes that
might help me remember.

>
>>  I tried different settings but the only thing that seemed
>> to work was to set them to headless, then reopen config and set them
>> to something else.
>>
>> -John
>>
>> On Thu, Feb 15, 2018 at 8:48 AM,   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.
>>>
>>> Thanks.
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[Michal Skrivanek]

> On 15 Feb 2018, at 16:37, Jason Keltz  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 
versions.

Thanks,
michal


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

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

[Michal Skrivanek]

> On 15 Feb 2018, at 15:58, John Taylor  wrote:
> 
> Hi Nicolas,
> I had the same problem and it looked like it was because of some older
> vms (I believe from 3.6) that were configured with console with video
> type of CIRRUS and protocol VNC.

3.6 had cirrus indeed. That should work. Can you somehow confirm it was really 
a 3.6 VM and it stopped working in 4.2? The exact steps are important, 
unfortunately.

> Tracing it out it showed that the vm  libvirt xml was begin set to
> headless.

do you at least recall what cluster level version it was when it stopped 
working? The VM definition should have been changed to VGA when you move the VM 
from 3.6 cluster to a 4.0+

>  I tried different settings but the only thing that seemed
> to work was to set them to headless, then reopen config and set them
> to something else.
> 
> -John
> 
> On Thu, Feb 15, 2018 at 8:48 AM,   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.
>> 
>> Thanks.
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[Jason Keltz]

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)
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

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

[John Taylor]

Hi Nicolas,
I had the same problem and it looked like it was because of some older
vms (I believe from 3.6) that were configured with console with video
type of CIRRUS and protocol VNC.
Tracing it out it showed that the vm  libvirt xml was begin set to
headless.  I tried different settings but the only thing that seemed
to work was to set them to headless, then reopen config and set them
to something else.

-John

On Thu, Feb 15, 2018 at 8:48 AM,   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.
>
> Thanks.
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[nicolas]

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.

Thanks.___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users