Il giorno ven 27 set 2019 alle ore 17:35 Derek Atkins <derek@ihtfp.com> ha scritto:
HI,

On Fri, September 27, 2019 7:23 am, Sandro Bonazzola wrote:
> Il giorno ven 27 set 2019 alle ore 12:55 Derek Atkins <derek@ihtfp.com> ha
> scritto:
>
>> >
>> > Please use the engine to upgrade hosts, there's a command in webadmin
>> > interface for that.
>>
>> I didn't think you could do this in a single-host hosted-engine system?
>> In such a deployment the engine has nowhere to migrate to, so it
>> requires
>> shutting down the whole "data center" in order to upgrade the host.  I
>> didn't think that could be done via the engine?
>>
>> Personally, I still need to upgrade from 4.1.9 / CentOS 7.4!
>>
>
> Single host self hosted engine will require more work.
> You'll need to put the host in global maintenance, turn off the engine,
> yum
> upgrade the host and reboot.
> Then get out of global maintenance and engine VM should get back up and
> running in a few minutes.

Yeah, this is how I've done it in the past.

I'm curious what the steps should be going from 4.1.9 / EL7.4 to 4.3.x /
EL7.7?  I am pretty sure I need some steps along the way (I doubt I can
jump directly from 4.1.9 -> 4.3.x and 7.4 -> 7.7, right).

So should I jump from 7.4/4.1.9 to 7.6/4.2.8 and then from there to
7.7/4.3.6?

4.1 cluster level is still supported by 4.3 engine.
So you can upgrade the engine from 7.4/4.1.9 to 7.6/4.2.8 and then to 7.7/4.3.6 while on the host side you can go straight to 4.3.6/7.7.
Once done, please update cluster level to 4.3.


 

Thanks,

-derek

--
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant



--