[ovirt-users] Update Self-Hosted-Engine - Right Way?

[Taste-Of-IT]

Hello,
sorry that i repeat it, but i dont have the command hosted-engine... Is 
it possible that we talk about different kind of installations? Please 
check yours because i only have the self-hosted engine installed.
Thx

Am 2016-03-04 12:08, schrieb Gianluca Cecchi:
> What I just tested on a lab environment of mine is this below
> 
> Starting situation is single host with CentOS 7.2 and SH Engine on
> CentOS 7.2 deployed from appliance
> Version is 3.6.2.
> Both are updated up to 26/01/16 nad there are 3 VMs running
> 
> - shutdown Vms
> 
> - move host to global maintenance
> On host:
> hosted-engine --set-maintenance --mode=global
> 
> - upgrade engine VM both from 3.6.2 to 3.6.3 and update its CentOS
> packages with:
> On SH Engine:
> yum update "ovirt-engine-setup*"
> yum update
> engine-setup
> 
> - reboot engine VM and verify correct access to web admin gui
> You can verify its console status at this time with something like
> this run on host side:
> hosted-engine --add-console-password --password=mypwd
> /bin/remote-viewer vnc://localhost:5900 &
> 
> NOTE: it seems that nc remote-viewer command doesn't survive the
> reboot... you have to reconnect
> 
> - verify oVirt version is right and all is ok, eg starting a VM and
> accessing its console; then shutdown again the VM
> 
> - move the host to local maintenance
> On host:
> hosted-engine --set-maintenance --mode=local
> 
> - update Host
> On engine VM:
> shutdown -h now
> NOTE: I think this step about engine VM shouldn't be necessary in case
> of multi host environment. Simply you should go host by host with
> these steps up to completing upgrade of your hosts. 
> 
> On host:
> yum update
> reboot
> 
> - Exit maintenance
> On host:
> hosted-engine --set-maintenance --mode=none
> 
> - Verify engine VM starts and access to web admin gui is ok
> 
> - Start your VMs and verify all is ok
> 
> I have just done this and all is ok: all storage domains (ISO, NFS and
> hosted_storage) are up and able to start and manage VMs
> 
> The only "problem" I have seeing is that in Hosts tab, the host is
> still marked for some minutes with a box and tip says "Update
> available".
> But then it goes away (no event regarding this on events pane... just
> wait)..
> 
> HIH,
> Gianluca
> 
> On Fri, Mar 4, 2016 at 11:19 AM, Joop <jvdwege at xs4all.nl> wrote:
> 
>> On 4-3-2016 10:44, Taste-Of-IT wrote:
>>> Hello Simon,
>>> 
>>> i am new with oVirt, but are you sure, that this is the way for
>> the
>>> self-hosted-engine? Because i have no commands with hosted-***.
>> As far
>>> as i understand the engine runs in self-hosted-engine on same
>> host and
>>> therefore there is no way to enter the vm with engine and set it
>> to
>>> maintenance mode.?!
>> If you have only one host and it sounds like it then upgrading is a
>> bit
>> different.
>> hosted-engine command is available on the HOST.
>> Just shutdown all VM's, either way will work if you have
>> ovirt-guest-agent running inside the VM's
>> place hosted-engine in maintenance mode (hosted-engine
>> --set-maintenance
>> --mode=global)
>> ssh, use vnc, into engine
>> yum upgrade if you want to upgrade the system too, else running
>> engine-setup will update only ovirt components.
>> shutdown the engine.
>> yum upgrade your host, reboot your host, once back up, disable
>> maintenance mode (replace global with none)
>> ha-agent and ha-broker will start the engine for you.
>> 
>> Joop
>> 
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users [1]
> 
> 
> 
> Links:
> ------
> [1] http://lists.ovirt.org/mailman/listinfo/users
> 
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users