1:33 p.m.
Hi,
I've got ovirt running on a single host (with hosted-engine). I just
upgraded the engine from 4.0.4 to 4.0.5. That was pretty easy; I just
put the system into global maintenance mode, then yum update, then
engine-setup, then took the host out of maint mode. Easy peasy.
Now, I want to update the host itself. Since it's a single host system
I know I'll need to shut down all the VMs (because there's no place to
migrate them). This means I'll need to shut down the engine VM, too.
That would imply that I can't use the "Update" feature from the ui,
right?
So what IS the process to properly update a single-host host? My guess
is:
* shutdown all the VMs
* go into global maint mode (what IS the difference between global and
local?)
* shutdown the engine/engine VM
* yum update on the host
* restart services (or reboot, I guess)
* bring the system out of maintenance mode
Am I missing a step? Do I need to run hosted-engine --deploy again
similar to how I needed to run "engine-setup" on the engine? Or is
there something else I need to run?
Thanks,
-derek
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
3:34 a.m.
On Thu, Nov 24, 2016 at 8:33 PM, Derek Atkins <derek(a)ihtfp.com> wrote:
Hi,
I've got ovirt running on a single host (with hosted-engine). I just
upgraded the engine from 4.0.4 to 4.0.5. That was pretty easy; I just
put the system into global maintenance mode, then yum update, then
engine-setup, then took the host out of maint mode. Easy peasy.
'took the host out of maint' -> took the engine VM out of maintenance mode:
global maintenance mode means that ovirt-ha-agent (on any hosts) will not
try to check, restart, migrate... the engine VM.
Now, I want to update the host itself. Since it's a single host
system
I know I'll need to shut down all the VMs (because there's no place to
migrate them). This means I'll need to shut down the engine VM, too.
That would imply that I can't use the "Update" feature from the ui,
right?
Yes, correct
So what IS the process to properly update a single-host host? My
guess
is:
* shutdown all the VMs
* go into global maint mode (what IS the difference between global and
local?)
* shutdown the engine/engine VM
* yum update on the host
* restart services (or reboot, I guess)
* bring the system out of maintenance mode
shutdown or hibernate all the other VMs.
set global maintenance mode to avoid ovirt-ha-agent trying to restart the
engine vm
shutdown the engine VM (from the host CLI) with hosted-engine --vm-shutdown
yum update
restart services
bring the system out of global maintenance mode: in a couple of minutes the
HA agent should restart the engine VM
Am I missing a step? Do I need to run hosted-engine --deploy again
similar to how I needed to run "engine-setup" on the engine? Or is
there something else I need to run?
Thanks,
-derek
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
8:53 a.m.
Hi Simone,
On Fri, November 25, 2016 4:34 am, Simone Tiraboschi wrote:
On Thu, Nov 24, 2016 at 8:33 PM, Derek Atkins <derek(a)ihtfp.com>
wrote:
[snip]
> So what IS the process to properly update a single-host host? My
guess
> is:
>
> * shutdown all the VMs
>
* go into global maint mode (what IS the difference between global and
> local?)
> * shutdown the engine/engine VM
> * yum update on the host
> * restart services (or reboot, I guess)
> * bring the system out of maintenance mode
>
shutdown or hibernate all the other VMs.
set global maintenance mode to avoid ovirt-ha-agent trying to restart the
engine vm
shutdown the engine VM (from the host CLI) with hosted-engine
--vm-shutdown
This is in lieu of "shutdown -h now" from the engine VM? (i.e., will this
perform a clean shutdown from within the VM?)
yum update
restart services
So I don't need to run a host equivalent of "engine-setup"? Great.
bring the system out of global maintenance mode: in a couple of
minutes
the
HA agent should restart the engine VM
Perfect. Thanks. I'll go test this shortly.
-derek
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
9:56 a.m.
On Fri, Nov 25, 2016 at 3:53 PM, Derek Atkins <derek(a)ihtfp.com> wrote:
Hi Simone,
On Fri, November 25, 2016 4:34 am, Simone Tiraboschi wrote:
> On Thu, Nov 24, 2016 at 8:33 PM, Derek Atkins <derek(a)ihtfp.com> wrote:
[snip]
>> So what IS the process to properly update a single-host host? My guess
>> is:
>>
>> * shutdown all the VMs
>>
> * go into global maint mode (what IS the difference between global and
>> local?)
>> * shutdown the engine/engine VM
>> * yum update on the host
>> * restart services (or reboot, I guess)
>> * bring the system out of maintenance mode
>>
>
> shutdown or hibernate all the other VMs.
> set global maintenance mode to avoid ovirt-ha-agent trying to restart the
> engine vm
> shutdown the engine VM (from the host CLI) with hosted-engine
> --vm-shutdown
This is in lieu of "shutdown -h now" from the engine VM? (i.e., will this
perform a clean shutdown from within the VM?)
Yes, exactly.
For emergency issue you also have hosted-engine --vm-poweroff to perform an
instant poweroff.
> yum update
> restart services
So I don't need to run a host equivalent of "engine-setup"? Great.
> bring the system out of global maintenance mode: in a couple of minutes
> the
> HA agent should restart the engine VM
Perfect. Thanks. I'll go test this shortly.
-derek
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
10:59 a.m.
HELP!!!
I just did this, but now my storage isn't showing up! According to
"mount", only the HE domain is mounted, but none of my other domains
mounted. Running 'hosted-engine --connect-storage' does not seem to mount
the storage domains.
If I bring the engine up, it still wont access those domains. And indeed,
now the host is showing up as non-responsive to the engine.
on the host, I see:
[root@ovirt-0 ~]# hosted-engine --vm-status
--== Host 1 status ==--
Status up-to-date : True
Hostname : OVIRT-0{.dom.ain}
Host ID : 1
Engine status : {"health": "good",
"vm": "up",
"detail": "up"}
Score : 3400
stopped : False
Local maintenance : False
crc32 : 76ac9280
Host timestamp : 985
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=985 (Fri Nov 25 11:35:39 2016)
host-id=1
score=3400
maintenance=False
state=EngineUp
stopped=False
So the host seems to think the engine is up.
I can't mount the storage from the UI because the engine claims the host
is non-responsive. Not surprisingly, this appears to be due to a
networking issue that I didn't have before the update. Indeed, the engine
can't reach the host, even though I can reach both (and the host can reach
the engine). Did the host update somehow change the iptables
configuration? It doesn't look like it. But I'm not sure why the network
isn't working now when it was working before the update.
So, now what do I do? I suppose I can check my host backup from last
night and see if I can see anything different in the vdsm configs?
There are two problems to solve:
1) Host doesn't mount my storage
2) Engine can't reach host via network.
HELP!
-derek
On Fri, November 25, 2016 9:53 am, Derek Atkins wrote:
Hi Simone,
On Fri, November 25, 2016 4:34 am, Simone Tiraboschi wrote:
> On Thu, Nov 24, 2016 at 8:33 PM, Derek Atkins <derek(a)ihtfp.com> wrote:
[snip]
>> So what IS the process to properly update a single-host host? My guess
>> is:
>>
>> * shutdown all the VMs
>>
> * go into global maint mode (what IS the difference between global and
>> local?)
>> * shutdown the engine/engine VM
>> * yum update on the host
>> * restart services (or reboot, I guess)
>> * bring the system out of maintenance mode
>>
>
> shutdown or hibernate all the other VMs.
> set global maintenance mode to avoid ovirt-ha-agent trying to restart
> the
> engine vm
> shutdown the engine VM (from the host CLI) with hosted-engine
> --vm-shutdown
This is in lieu of "shutdown -h now" from the engine VM? (i.e., will this
perform a clean shutdown from within the VM?)
> yum update
> restart services
So I don't need to run a host equivalent of "engine-setup"? Great.
> bring the system out of global maintenance mode: in a couple of minutes
> the
> HA agent should restart the engine VM
Perfect. Thanks. I'll go test this shortly.
-derek
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
12:02 p.m.
Il 24/Nov/2016 20:34, "Derek Atkins" <derek(a)ihtfp.com> ha scritto:
Hi,
I've got ovirt running on a single host (with hosted-engine). I just
upgraded the engine from 4.0.4 to 4.0.5. That was pretty easy; I just
put the system into global maintenance mode, then yum update, then
engine-setup, then took the host out of maint mode. Easy peasy.
Now, I want to update the host itself. Since it's a single host system
I know I'll need to shut down all the VMs (because there's no place to
migrate them). This means I'll need to shut down the engine VM, too.
That would imply that I can't use the "Update" feature from the ui,
right?
So what IS the process to properly update a single-host host?
It seems you didn't specify the kind of storage you are using...
Anything provided by the host itself or what?
12:43 p.m.
Hi,
On Fri, November 25, 2016 1:02 pm, Gianluca Cecchi wrote:
Il 24/Nov/2016 20:34, "Derek Atkins"
<derek(a)ihtfp.com> ha scritto:
>
> Hi,
>
> I've got ovirt running on a single host (with hosted-engine). I just
> upgraded the engine from 4.0.4 to 4.0.5. That was pretty easy; I just
> put the system into global maintenance mode, then yum update, then
> engine-setup, then took the host out of maint mode. Easy peasy.
>
> Now, I want to update the host itself. Since it's a single host system
> I know I'll need to shut down all the VMs (because there's no place to
> migrate them). This means I'll need to shut down the engine VM, too.
> That would imply that I can't use the "Update" feature from the ui,
> right?
>
> So what IS the process to properly update a single-host host?
It seems you didn't specify the kind of storage you are using...
Anything provided by the host itself or what?
All storage is NFS storage exported by the host itself. i didn't mention
it because it shouldn't have mattered -- the HE export mounted but the
others didn't.. Although it appears this may all have been due to the
network issues between engine and host -- once I added a workaround to
that issue the mounting issues seemed to resolve themselves.
I'm not sure why I'm having this network issue. The engine VM gets an ARP
Redirect and then can't reach the host anymore -- but of course the host
can reach the VM. It's a strange issue that I haven't been able to track
down (but is most likely not related to ovirt).
Thanks,
-derek
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
10:33 p.m.
Hi,
"Derek Atkins" <derek(a)ihtfp.com> writes:
Hi,
All storage is NFS storage exported by the host itself. i didn't mention
it because it shouldn't have mattered -- the HE export mounted but the
others didn't.. Although it appears this may all have been due to the
network issues between engine and host -- once I added a workaround to
that issue the mounting issues seemed to resolve themselves.
I'm not sure why I'm having this network issue. The engine VM gets an ARP
Redirect and then can't reach the host anymore -- but of course the host
can reach the VM. It's a strange issue that I haven't been able to track
down (but is most likely not related to ovirt).
For what it's worth, it did come back after I:
1) worked around a strange networking problem where the engine couldn't
reach the host. I still need to figure out why I'm having this
network issue, where the machines stop being able to communicate. I
don't think this is an ovirt issue, I suspect an ARP issue on my
network.
2) Waited.. it took about 15 minutes to stabilize.
-derek
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
2711
days inactive
2716
days old
7 comments
3 participants
participants (3)
-
Derek Atkins -
Gianluca Cecchi -
Simone Tiraboschi