On 19 Feb 2018, at 23:36, Jason Keltz <jas@cse.yorku.ca> wrote: =20 Hi Michal, =20 On 2/15/2018 12:05 PM, Michal Skrivanek wrote: =20
On 15 Feb 2018, at 16:37, Jason Keltz <jas@cse.yorku.ca> = <mailto:jas@cse.yorku.ca> wrote: =20 On 02/15/2018 08:48 AM, nicolas@devels.es <mailto:nicolas@devels.es> = wrote:
Hi, =20 We upgraded one of our infrastructures to 4.2.0 recently and since =
=20 I changed their compatibility to 4.2 but with no luck, as they're = still disabled. =20 Is there a way to know why is that, and how to solve it? =20 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=3D1528868 = <https://bugzilla.redhat.com/show_bug.cgi?id=3D1528868> (which admittedly was a mesh of a bunch of different issues that = occurred) yeah, that=E2=80=99s not a good idea to mix more issues:) Seems https://bugzilla.redhat.com/show_bug.cgi?id=3D1528868#c26 = <https://bugzilla.redhat.com/show_bug.cgi?id=3D1528868#c26> is the last = one relevant to the grayed out console problem in this email thread. =20 it=E2=80=99s also possible to check "VM Devices=E2=80=9D subtab and =
I believe it was originally a 3.6 VM. Is there anywhere I can verify =
--Apple-Mail=_2C8DBEDD-FB61-492B-BFC4-74C5E95E1F79 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 then some of our machines have the "Console" button greyed-out in the = Admin UI, like they were disabled. 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) 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=E2=80=99t really = keep all the logs forever. Well, you can if you archive them somewhere, = but I guess that=E2=80=99s impractical for such a long time:-D
=20 VM Device subtab: (no Cirrus) <eadpakjggeififdb.png>
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 =
so this is a screenshot from VM where the button is grayed out when you = start it?=20 Hm..it doesn=E2=80=99t look wrong. this one VM left in this state because I had deleted the other VMs and = recreated them one at a time... =20
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 =20 We then had to do a Run-Once which failed Then did a normal Run. =20 Console was available, and all hardware came back fine. =20 ... but I won't try that yet in case you need additional information = from the VM first. =20 Jason.
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--Apple-Mail=_2C8DBEDD-FB61-492B-BFC4-74C5E95E1F79 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br = class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div = class=3D"">On 19 Feb 2018, at 23:36, Jason Keltz <<a = href=3D"mailto:jas@cse.yorku.ca" class=3D"">jas@cse.yorku.ca</a>> = wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""> =20 <meta content=3D"text/html; charset=3Dutf-8" = http-equiv=3D"Content-Type" class=3D""> =20 <div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D""><p class=3D"">Hi = Michal,</p><p class=3D"">On 2/15/2018 12:05 PM, Michal Skrivanek wrote: </p> <blockquote = cite=3D"mid:2EA3B6C6-C3E8-45D8-8ED4-4DF0AE97D279@redhat.com" type=3D"cite"= class=3D""> <blockquote type=3D"cite" class=3D""> <pre wrap=3D"" class=3D"">On 15 Feb 2018, at 16:37, Jason Keltz = <a class=3D"moz-txt-link-rfc2396E" = href=3D"mailto:jas@cse.yorku.ca"><jas@cse.yorku.ca></a> wrote: On 02/15/2018 08:48 AM, <a class=3D"moz-txt-link-abbreviated" = href=3D"mailto:nicolas@devels.es">nicolas@devels.es</a> wrote: </pre> <blockquote type=3D"cite" class=3D""> <pre wrap=3D"" class=3D"">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. </pre> </blockquote> <pre wrap=3D"" class=3D"">Hi Nicolas. I had the same problem with most of my VMs after the upgrade from 4.1 to = 4.2. See bugzilla here: <a class=3D"moz-txt-link-freetext" = href=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D1528868">https://bug= zilla.redhat.com/show_bug.cgi?id=3D1528868</a> (which admittedly was a mesh of a bunch of different issues that = occurred) </pre> </blockquote> <pre wrap=3D"" class=3D"">yeah, that=E2=80=99s not a good idea to = mix more issues:) Seems <a class=3D"moz-txt-link-freetext" = href=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D1528868#c26">https:/= /bugzilla.redhat.com/show_bug.cgi?id=3D1528868#c26</a> is the last one = relevant to the grayed out console problem in this email thread. it=E2=80=99s also possible to check "VM Devices=E2=80=9D 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)</pre> </blockquote> 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.<br = class=3D""></div></div></blockquote><div><br = class=3D""></div>Hi,</div><div>well, we keep the date and who did that, = but we can=E2=80=99t really keep all the logs forever. Well, you can if = you archive them somewhere, but I guess that=E2=80=99s impractical for = such a long time:-D</div><div><br class=3D""><blockquote type=3D"cite" = class=3D""><div class=3D""><div bgcolor=3D"#FFFFFF" text=3D"#000000" = class=3D""> <br class=3D""> VM Device subtab: (no = Cirrus)</div></div></blockquote><blockquote type=3D"cite" class=3D""><div = class=3D""><div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D""> <span = id=3D"cid:part1.802471EC.76DEFB09@cse.yorku.ca"><eadpakjggeififdb.png&g= t;</span><br class=3D""></div></div></blockquote><div><br = class=3D""></div>so this is a screenshot from VM where the button is = grayed out when you start it? </div><div>Hm..it doesn=E2=80=99t = look wrong.</div><div><br class=3D""></div><div><blockquote type=3D"cite" = class=3D""><div class=3D""><div bgcolor=3D"#FFFFFF" text=3D"#000000" = class=3D""> <blockquote = cite=3D"mid:2EA3B6C6-C3E8-45D8-8ED4-4DF0AE97D279@redhat.com" type=3D"cite"= class=3D""> <pre wrap=3D"" class=3D"">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. </pre> </blockquote> 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... <br class=3D""> I will wait to see if you want me to try Vineet's solution of making it headless,<br class=3D""></div></div></blockquote><div><br = class=3D""></div><div>Thanks.</div><div>Can you get engine.log and vdsm = log when you attempt to start that VM ? just the relevant part is = enough.</div><div class=3D""><br class=3D""></div><div = class=3D"">Thanks,</div><div class=3D"">michal</div><div class=3D""><br = class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D""><div= bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D""> <blockquote type=3D"cite" class=3D"">The before bringing it back up, = unchecked headless in the VM<br class=3D""> <br class=3D""> <div class=3D"gmail_default" = style=3D"font-family:monospace,monospace">We then had to do a Run-Once which failed<br class=3D""> </div> <div class=3D"gmail_default" = style=3D"font-family:monospace,monospace">Then did a normal Run.<br class=3D""> <br class=3D""> </div> <div class=3D"gmail_default" = style=3D"font-family:monospace,monospace">Console was available, and all hardware came back fine.<br class=3D""> <br class=3D""> </div> </blockquote> ... but I won't try that yet in case you need additional information from the VM first.<br class=3D""> <br class=3D""> Jason.<br class=3D""> </div> _______________________________________________<br class=3D"">Users = mailing list<br class=3D""><a href=3D"mailto:Users@ovirt.org" = class=3D"">Users@ovirt.org</a><br = class=3D"">http://lists.ovirt.org/mailman/listinfo/users<br = class=3D""></div></blockquote></div><br class=3D""></body></html>= --Apple-Mail=_2C8DBEDD-FB61-492B-BFC4-74C5E95E1F79--