Unable to put Host into Maintenance mode
I have a host that is currently reporting down with NO VM's on it or associated with it. However when I attempt to put it into maintenance mode, I get the following error: Host hv-01 cannot change into maintenance mode - not all Vms have been migrated successfully. Consider manual intervention: stopping/migrating Vms: <UNKNOWN> (User: admin) I am running oVirt Engine Version: 3.5.0.1-1.el6 *** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 800.885.8886 x128 | msteele@telvue.com | http://www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www.facebook.com/telvue
--Apple-Mail=_0D201828-9B82-49BD-9A8B-A64A1620B3FA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8
On 15 Feb 2018, at 12:06, Mark Steele <msteele@telvue.com> wrote: =20 I have a host that is currently reporting down with NO VM's on it or = associated with it. However when I attempt to put it into maintenance = mode, I get the following error: =20 Host hv-01 cannot change into maintenance mode - not all Vms have been = migrated successfully. Consider manual intervention: stopping/migrating = Vms: <UNKNOWN> (User: admin) =20 I am running=20 oVirt Engine Version: 3.5.0.1-1.el6
that=E2=80=99s a really old version=E2=80=A6. first confirm there is no running vm on that host (log in there, look = for qemu processes) if not, it=E2=80=99s likely just engine issue, somewhere it lost track = of what=E2=80=99s actually running there - in that case you could try to = restart the host, restart engine. that should help
=20 *** Mark Steele CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 800.885.8886 x128 | msteele@telvue.com <mailto:msteele@telvue.com> | = http://www.telvue.com <http://www.telvue.com/> twitter: http://twitter.com/telvue <http://twitter.com/telvue> | = facebook: https://www.facebook.com/telvue = <https://www.facebook.com/telvue>_________________________________________=
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--Apple-Mail=_0D201828-9B82-49BD-9A8B-A64A1620B3FA 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 15 Feb 2018, at 12:06, Mark Steele <<a = href=3D"mailto:msteele@telvue.com" class=3D"">msteele@telvue.com</a>> = wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div = dir=3D"ltr" class=3D""><div class=3D"gmail_default" style=3D"font-family: = verdana, sans-serif; font-size: small;">I have a host that is currently = reporting down with NO VM's on it or associated with it. However when I = attempt to put it into maintenance mode, I get the following = error:</div><div class=3D"gmail_default" style=3D"font-family: verdana, = sans-serif; font-size: small;"><br class=3D""></div><div = class=3D"gmail_default" style=3D"font-family: verdana, sans-serif; = font-size: small;">Host hv-01 cannot change into maintenance mode - not = all Vms have been=20 migrated successfully. Consider manual intervention: stopping/migrating=20= Vms: <UNKNOWN> (User: admin)<br class=3D""></div><div = class=3D"gmail_default" style=3D"font-family: verdana, sans-serif; = font-size: small;"><br class=3D""></div><div class=3D"gmail_default" = style=3D"font-family: verdana, sans-serif; font-size: small;">I am = running <div class=3D""> <span class=3D"gmail-gwt-InlineLabel">oVirt = Engine Version: 3.5.0.1-1.el6</span> = </div></div></div></div></blockquote><div><br class=3D""></div>that=E2=80=99= s a really old version=E2=80=A6.</div><div><br class=3D""></div><div>first= confirm there is no running vm on that host (log in there, look for = qemu processes)</div><div>if not, it=E2=80=99s likely just engine issue, = somewhere it lost track of what=E2=80=99s actually running there - in = that case you could try to restart the host, restart engine. that should = help</div><div><br class=3D""><blockquote type=3D"cite" class=3D""><div = class=3D""><div dir=3D"ltr" class=3D""><div class=3D""><div = class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div = dir=3D"ltr" class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div = class=3D""><div dir=3D"ltr" class=3D""><div class=3D""><div dir=3D"ltr" = class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div dir=3D"ltr" = class=3D""><div dir=3D"ltr" class=3D""><div class=3D""><br = class=3D""></div><div class=3D""><font face=3D"verdana, sans-serif" = class=3D"">***</font></div><div class=3D""><b style=3D"font-family: = verdana, sans-serif;" class=3D""><font size=3D"2" class=3D"">Mark = Steele</font></b><br class=3D""></div><div class=3D""><font = face=3D"verdana, sans-serif" class=3D""><span style=3D"" class=3D"">CIO = / VP Technical Operations | TelVue Corporation</span></font></div><div = class=3D""><font face=3D"verdana, sans-serif" class=3D""><span = style=3D"font-size: x-small;" class=3D"">TelVue - We Share Your = Vision</span></font></div><div class=3D""><font face=3D"verdana, = sans-serif" class=3D""><span style=3D"font-size: x-small;" = class=3D"">16000 Horizon Way, Suite 100 | Mt. Laurel, NJ = 08054</span></font></div><div class=3D""><font face=3D"verdana, = sans-serif" class=3D""><span style=3D"font-size: x-small;" = class=3D"">800.885.8886 x128 | <a href=3D"mailto:msteele@telvue.com" = target=3D"_blank" class=3D"">msteele@telvue.com</a> | </span><a = href=3D"http://www.telvue.com/" style=3D"font-size:x-small" = target=3D"_blank" class=3D"">http://www.telvue.com</a></font></div><div = class=3D""><font face=3D"verdana, sans-serif" class=3D""><span = style=3D"font-size:x-small" class=3D"">twitter: </span><a = href=3D"http://twitter.com/telvue" style=3D"font-size:x-small" = target=3D"_blank" class=3D"">http://twitter.com/telvue</a><span = style=3D"font-size:x-small" class=3D""> | facebook: </span><a = href=3D"https://www.facebook.com/telvue" style=3D"font-size:x-small" = target=3D"_blank" = class=3D"">https://www.facebook.com/telvue</a></font></div></div></div></d= iv></div></div></div></div></div></div></div></div></div></div> </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=_0D201828-9B82-49BD-9A8B-A64A1620B3FA--
On 02/15/2018 11:10 AM, Michal Skrivanek wrote: ..snippity... with regards to oVirt 3.5
that’s a really old version….
I know I'll catch heat for this, but by "old" you mean like December of 2015? Just trying put things into perspective. Thus it goes with the ancient and decrepit Red Hat Ent. 7.1 days, right? I know, I know, FOSS... the only thing worse than running today's code is running yesterday's. We still run a 3.5 oVirt in our dev lab, btw. But I would not have set that up (not that I would have recommended oVirt to begin with), preferring 3.4 at the time. I would have waited for 3.6. With that said, 3.5 isn't exactly on the "stable line" to Red Hat Virtualization, that was 3.4 and then 3.6. Some people can't afford major (downtime) upgrades every 3-6 months or so. But, arguably, maybe we shouldn't be running oVirt. Maybe it's not designed for "production". I guess oVirt isn't really for production by definition, but many of us are doing so. So... not really a "ding" against oVirt developers, it's just a rapidly moving target with the normal risks that come with that. People just need to understand that. And with that said, the fact that many of us are running those ancient decrepit evil versions of oVirt in production today, is actually a testimony to its quality. Good job devs!
On 15 Feb 2018, at 18:34, Christopher Cox <ccox@endlessnow.com> wrote: On 02/15/2018 11:10 AM, Michal Skrivanek wrote: ..snippity... with regards to oVirt 3.5 that’s a really old version…. I know I'll catch heat for this, but by "old" you mean like December of 2015? Just trying put things into perspective. Thus it goes with the ancient and decrepit Red Hat Ent. 7.1 days, right? Hehe. It’s not about using it, rather I was referring to the fact that we stopped developing it, stopped fixing even critical security issues. Same for 3.6, and 4.0. I know, I know, FOSS... the only thing worse than running today's code is running yesterday's. Well, there is only a limited amount of resources you can devote to actively maintain branches/releases We typically do that for two versions, covering roughly 1,5 years We still run a 3.5 oVirt in our dev lab, btw. But I would not have set that up (not that I would have recommended oVirt to begin with), preferring 3.4 at the time. I would have waited for 3.6. With that said, 3.5 isn't exactly on the "stable line" to Red Hat Virtualization, that was 3.4 and then 3.6. Some people can't afford major (downtime) upgrades every 3-6 months or so. That’s why we do not really require it and still support 3.6 cluster compat in 4.2, so that does give you longer time to update. And even the cluster upgrades are rolling, we do not require any real downtime other than for rebooting individual VMs and some spare capacity to migrate workloads to during host upgrade. But, arguably, maybe we shouldn't be running oVirt. Maybe it's not designed for "production". I guess oVirt isn't really for production by definition, but many of us are doing so. So... not really a "ding" against oVirt developers, it's just a rapidly moving target with the normal risks that come with that. People just need to understand that. Absolutely. People should understand the difference between a GA and a zstream update 6 months later. Every sw has bugs. But I would argue we do actually have quite a long supported versions, when compared to a $random project. And then yes, we do have a longer support for Red Hat Virtualization, but again in general I would doubt you can find many similar commercial products being _actively_ supported for more than few years And with that said, the fact that many of us are running those ancient decrepit evil versions of oVirt in production today, is actually a testimony to its quality. Good job devs! Thanks! _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Feb 15, 2018 7:35 PM, "Christopher Cox" <ccox@endlessnow.com> wrote: On 02/15/2018 11:10 AM, Michal Skrivanek wrote: ..snippity... with regards to oVirt 3.5
that’s a really old version….
I know I'll catch heat for this, but by "old" you mean like December of 2015? Just trying put things into perspective. Thus it goes with the ancient and decrepit Red Hat Ent. 7.1 days, right? I know, I know, FOSS... the only thing worse than running today's code is running yesterday's. We still run a 3.5 oVirt in our dev lab, btw. But I would not have set that up (not that I would have recommended oVirt to begin with), preferring 3.4 at the time. I would have waited for 3.6. With that said, 3.5 isn't exactly on the "stable line" to Red Hat Virtualization, that was 3.4 and then 3.6. Red Hat doesn't support 3.x anymore, unless its 3.6 with specific subscription that extends its support. Some people can't afford major (downtime) upgrades every 3-6 months or so. But, arguably, maybe we shouldn't be running oVirt. Maybe it's not designed for "production". 3.4,5,6 are minor releases of 3.x. The same way that 4.1 and 4.2 are minor releases of 4.x. I agree that with lots of changing landscape (for example, the move from EL6 to EL7) and with the number of features introduced, they don't seem that minor. But there's an ongoing effort to both keep backwards compatibility as well continously improve quality - which regretfully, requires updating from time to time. I guess oVirt isn't really for production by definition, but many of us are doing so. So... not really a "ding" against oVirt developers, it's just a rapidly moving target with the normal risks that come with that. People just need to understand that. And with that said, the fact that many of us are running those ancient decrepit evil versions of oVirt in production today, is actually a testimony to its quality. Good job devs! Or a warning sign that upgrade is not yet easy as it should be. I believe we've improved the experience and quality of the upgrade flow over time, but we can certainly do a better job. I also think there are two additional factors : 1. Don't fix what ain't broken - it works, why bother? Not much the oVirt community can do here. 2. Newer versions do not provide enough incentive to upgrade. This is a tougher one - I believe they do, both in terms of quality as well as new features that bring value to different use-cases. However, we may not be doing enough 'marketing' work around them, or they are not documented well enough, etc. Y. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
So - to get this back on track - I was able to remove the host entirely from HostedEngine using ovirt-shell - but now cannot add it back for the same reason as not being able to add ANY hosts to this cluster (there is another email thread on this): *** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 800.885.8886 x128 | msteele@telvue.com | http://www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www.facebook.com/telvue On Fri, Feb 16, 2018 at 3:30 PM, Yaniv Kaul <ykaul@redhat.com> wrote:
On Feb 15, 2018 7:35 PM, "Christopher Cox" <ccox@endlessnow.com> wrote:
On 02/15/2018 11:10 AM, Michal Skrivanek wrote: ..snippity... with regards to oVirt 3.5
that’s a really old version….
I know I'll catch heat for this, but by "old" you mean like December of 2015? Just trying put things into perspective. Thus it goes with the ancient and decrepit Red Hat Ent. 7.1 days, right?
I know, I know, FOSS... the only thing worse than running today's code is running yesterday's.
We still run a 3.5 oVirt in our dev lab, btw. But I would not have set that up (not that I would have recommended oVirt to begin with), preferring 3.4 at the time. I would have waited for 3.6.
With that said, 3.5 isn't exactly on the "stable line" to Red Hat Virtualization, that was 3.4 and then 3.6.
Red Hat doesn't support 3.x anymore, unless its 3.6 with specific subscription that extends its support.
Some people can't afford major (downtime) upgrades every 3-6 months or so. But, arguably, maybe we shouldn't be running oVirt. Maybe it's not designed for "production".
3.4,5,6 are minor releases of 3.x. The same way that 4.1 and 4.2 are minor releases of 4.x. I agree that with lots of changing landscape (for example, the move from EL6 to EL7) and with the number of features introduced, they don't seem that minor. But there's an ongoing effort to both keep backwards compatibility as well continously improve quality - which regretfully, requires updating from time to time.
I guess oVirt isn't really for production by definition, but many of us are doing so.
So... not really a "ding" against oVirt developers, it's just a rapidly moving target with the normal risks that come with that. People just need to understand that.
And with that said, the fact that many of us are running those ancient decrepit evil versions of oVirt in production today, is actually a testimony to its quality. Good job devs!
Or a warning sign that upgrade is not yet easy as it should be. I believe we've improved the experience and quality of the upgrade flow over time, but we can certainly do a better job.
I also think there are two additional factors : 1. Don't fix what ain't broken - it works, why bother? Not much the oVirt community can do here. 2. Newer versions do not provide enough incentive to upgrade. This is a tougher one - I believe they do, both in terms of quality as well as new features that bring value to different use-cases. However, we may not be doing enough 'marketing' work around them, or they are not documented well enough, etc. Y.
_______________________________________________ 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
Michal, Thank you for the response. - there are no qemu processes running - the server has been rebooted several times - the engine has been rebooted several times The issue persists. I'm not sure where to look next. *** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 800.885.8886 x128 | msteele@telvue.com | http://www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www.facebook.com/telvue On Thu, Feb 15, 2018 at 12:10 PM, Michal Skrivanek < michal.skrivanek@redhat.com> wrote:
On 15 Feb 2018, at 12:06, Mark Steele <msteele@telvue.com> wrote:
I have a host that is currently reporting down with NO VM's on it or associated with it. However when I attempt to put it into maintenance mode, I get the following error:
Host hv-01 cannot change into maintenance mode - not all Vms have been migrated successfully. Consider manual intervention: stopping/migrating Vms: <UNKNOWN> (User: admin)
I am running oVirt Engine Version: 3.5.0.1-1.el6
that’s a really old version….
first confirm there is no running vm on that host (log in there, look for qemu processes) if not, it’s likely just engine issue, somewhere it lost track of what’s actually running there - in that case you could try to restart the host, restart engine. that should help
*** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 <https://maps.google.com/?q=16000+Horizon+Way,+Suite+100+%7C+Mt.+Laurel,+NJ+08054&entry=gmail&source=g> 800.885.8886 x128 <(800)%20885-8886> | msteele@telvue.com | http:// www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www. facebook.com/telvue _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Thursday, February 15, 2018 1:14:44 PM EST Mark Steele wrote:
Michal,
Thank you for the response.
- there are no qemu processes running - the server has been rebooted several times - the engine has been rebooted several times
The issue persists. I'm not sure where to look next.
Have you tried right clicking on the host, and select 'Confirm Host has been rebooted' that is basically telling the engine that the host is fenced, and you should be able to put it into maintenance mode. It will ask confirmation but we know the host has been rebooted and nothing is running.
*** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 800.885.8886 x128 | msteele@telvue.com | http://www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www.facebook.com/telvue
On Thu, Feb 15, 2018 at 12:10 PM, Michal Skrivanek <
michal.skrivanek@redhat.com> wrote:
On 15 Feb 2018, at 12:06, Mark Steele <msteele@telvue.com> wrote:
I have a host that is currently reporting down with NO VM's on it or associated with it. However when I attempt to put it into maintenance mode, I get the following error:
Host hv-01 cannot change into maintenance mode - not all Vms have been migrated successfully. Consider manual intervention: stopping/migrating Vms: <UNKNOWN> (User: admin)
I am running oVirt Engine Version: 3.5.0.1-1.el6
that’s a really old version….
first confirm there is no running vm on that host (log in there, look for qemu processes) if not, it’s likely just engine issue, somewhere it lost track of what’s actually running there - in that case you could try to restart the host, restart engine. that should help
*** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 <https://maps.google.com/?q=16000+Horizon+Way,+Suite+100+%7C+Mt.+Laurel,+N J+08054&entry=gmail&source=g> 800.885.8886 x128 <(800)%20885-8886> | msteele@telvue.com | http:// www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www. facebook.com/telvue _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I have with no joy. Question: Can I restart the HostedEngine with running VM's without negatively impacting them? *** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 800.885.8886 x128 | msteele@telvue.com | http://www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www.facebook.com/telvue On Thu, Feb 15, 2018 at 1:41 PM, Alexander Wels <awels@redhat.com> wrote:
On Thursday, February 15, 2018 1:14:44 PM EST Mark Steele wrote:
Michal,
Thank you for the response.
- there are no qemu processes running - the server has been rebooted several times - the engine has been rebooted several times
The issue persists. I'm not sure where to look next.
Have you tried right clicking on the host, and select 'Confirm Host has been rebooted' that is basically telling the engine that the host is fenced, and you should be able to put it into maintenance mode. It will ask confirmation but we know the host has been rebooted and nothing is running.
*** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 800.885.8886 x128 | msteele@telvue.com | http://www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www.facebook.com/telvue
On Thu, Feb 15, 2018 at 12:10 PM, Michal Skrivanek <
michal.skrivanek@redhat.com> wrote:
On 15 Feb 2018, at 12:06, Mark Steele <msteele@telvue.com> wrote:
I have a host that is currently reporting down with NO VM's on it or associated with it. However when I attempt to put it into maintenance mode, I get the following error:
Host hv-01 cannot change into maintenance mode - not all Vms have been migrated successfully. Consider manual intervention: stopping/migrating Vms: <UNKNOWN> (User: admin)
I am running oVirt Engine Version: 3.5.0.1-1.el6
that’s a really old version….
first confirm there is no running vm on that host (log in there, look
for
qemu processes) if not, it’s likely just engine issue, somewhere it lost track of what’s actually running there - in that case you could try to restart the host, restart engine. that should help
*** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 <https://maps.google.com/?q=16000+Horizon+Way,+Suite+100+% 7C+Mt.+Laurel,+N J+08054&entry=gmail&source=g> 800.885.8886 x128 <(800)%20885-8886> | msteele@telvue.com | http:// www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www. facebook.com/telvue _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Yes you can. On Feb 15, 2018 23:09, "Mark Steele" <msteele@telvue.com> wrote:
I have with no joy.
Question: Can I restart the HostedEngine with running VM's without negatively impacting them?
*** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 800.885.8886 x128 <800%20885%208886> | msteele@telvue.com | http:// www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www. facebook.com/telvue
On Thu, Feb 15, 2018 at 1:41 PM, Alexander Wels <awels@redhat.com> wrote:
On Thursday, February 15, 2018 1:14:44 PM EST Mark Steele wrote:
Michal,
Thank you for the response.
- there are no qemu processes running - the server has been rebooted several times - the engine has been rebooted several times
The issue persists. I'm not sure where to look next.
Have you tried right clicking on the host, and select 'Confirm Host has been rebooted' that is basically telling the engine that the host is fenced, and you should be able to put it into maintenance mode. It will ask confirmation but we know the host has been rebooted and nothing is running.
*** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 800.885.8886 x128 | msteele@telvue.com | http://www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www.facebook.com/telvue
On Thu, Feb 15, 2018 at 12:10 PM, Michal Skrivanek <
michal.skrivanek@redhat.com> wrote:
On 15 Feb 2018, at 12:06, Mark Steele <msteele@telvue.com> wrote:
I have a host that is currently reporting down with NO VM's on it or associated with it. However when I attempt to put it into maintenance mode, I get the following error:
Host hv-01 cannot change into maintenance mode - not all Vms have been migrated successfully. Consider manual intervention:
stopping/migrating
Vms: <UNKNOWN> (User: admin)
I am running oVirt Engine Version: 3.5.0.1-1.el6
that’s a really old version….
first confirm there is no running vm on that host (log in there, look for qemu processes) if not, it’s likely just engine issue, somewhere it lost track of what’s actually running there - in that case you could try to restart the host, restart engine. that should help
*** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 <https://maps.google.com/?q=16000+Horizon+Way,+Suite+100+%7C +Mt.+Laurel,+N J+08054&entry=gmail&source=g> 800.885.8886 x128 <(800)%20885-8886> | msteele@telvue.com | http:// www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www. facebook.com/telvue _______________________________________________ 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
Using the ovirt-shell, I find that there are no vms assigned to this host: [oVirt shell (connected)]# list vms --query "host=hv-01" So I'm now looking to see where the host is reporting back to the engine that it has migrations in progress. Anyone know where to look for that? Thanks! *** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 800.885.8886 x128 | msteele@telvue.com | http://www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www.facebook.com/telvue On Thu, Feb 15, 2018 at 4:35 PM, Alex K <rightkicktech@gmail.com> wrote:
Yes you can.
On Feb 15, 2018 23:09, "Mark Steele" <msteele@telvue.com> wrote:
I have with no joy.
Question: Can I restart the HostedEngine with running VM's without negatively impacting them?
*** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 <https://maps.google.com/?q=16000+Horizon+Way,+Suite+100+%7C+Mt.+Laurel,+NJ+08054&entry=gmail&source=g> 800.885.8886 x128 <800%20885%208886> | msteele@telvue.com | http:// www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www.facebook .com/telvue
On Thu, Feb 15, 2018 at 1:41 PM, Alexander Wels <awels@redhat.com> wrote:
On Thursday, February 15, 2018 1:14:44 PM EST Mark Steele wrote:
Michal,
Thank you for the response.
- there are no qemu processes running - the server has been rebooted several times - the engine has been rebooted several times
The issue persists. I'm not sure where to look next.
Have you tried right clicking on the host, and select 'Confirm Host has been rebooted' that is basically telling the engine that the host is fenced, and you should be able to put it into maintenance mode. It will ask confirmation but we know the host has been rebooted and nothing is running.
*** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
800.885.8886 x128 | msteele@telvue.com | http://www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www.facebook.com/telvue
On Thu, Feb 15, 2018 at 12:10 PM, Michal Skrivanek <
michal.skrivanek@redhat.com> wrote:
On 15 Feb 2018, at 12:06, Mark Steele <msteele@telvue.com> wrote:
I have a host that is currently reporting down with NO VM's on it or associated with it. However when I attempt to put it into maintenance mode, I get the following error:
Host hv-01 cannot change into maintenance mode - not all Vms have been migrated successfully. Consider manual intervention: stopping/migrating Vms: <UNKNOWN> (User: admin)
I am running oVirt Engine Version: 3.5.0.1-1.el6
that’s a really old version….
first confirm there is no running vm on that host (log in there, look for qemu processes) if not, it’s likely just engine issue, somewhere it lost track of what’s actually running there - in that case you could try to restart the host, restart engine. that should help
*** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054 <https://maps.google.com/?q=16000+Horizon+Way,+Suite+100+%7C+Mt.+Laurel,+NJ+08054&entry=gmail&source=g> <https://maps.google.com/?q=16000+Horizon+Way,+Suite+100+%7C +Mt.+Laurel,+N J+08054&entry=gmail&source=g> 800.885.8886 x128 <(800)%20885-8886> | msteele@telvue.com | http:// www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www. facebook.com/telvue _______________________________________________ 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
participants (7)
-
Alex K -
Alexander Wels -
Christopher Cox -
Mark Steele -
Michal Skrivanek -
Reznikov Alexei -
Yaniv Kaul