[ovirt-users] Re: Update hosted engine to 4.3.8 from 4.3.7 questions

2020-02-10 Thread d03
Update successful.  Thanks.  :)
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/FBBMH3BBTSWYDTQZE45DFQQIZWKM6T45/


[ovirt-users] Re: Update hosted engine to 4.3.8 from 4.3.7 questions

2020-02-08 Thread Yedidyah Bar David
On Thu, Feb 6, 2020 at 8:47 PM Strahil Nikolov  wrote:
>
> On February 6, 2020 6:21:02 PM GMT+02:00, d...@bornfree.org wrote:
> >I'd like to update my hosted engine to version 4.3.8 from 4.3.7, but
> >have concerns.
> >
> >First, on the hosted engine, yum reports that several packages are
> >version locked.  Specifically:
> >0:ovirt-engine-webadmin-portal-4.3.8.2-1.el7.*
> >0:ovirt-engine-dwh-4.3.8-1.el7.*
> >0:ovirt-engine-tools-backup-4.3.8.2-1.el7.*
> >0:ovirt-engine-restapi-4.3.8.2-1.el7.*
> >0:ovirt-engine-dbscripts-4.3.8.2-1.el7.*
> >0:ovirt-engine-4.3.8.2-1.el7.*
> >0:ovirt-engine-backend-4.3.8.2-1.el7.*
> >0:ovirt-engine-tools-4.3.8.2-1.el7.*
> >
> >Is this normal and is it okay to proceed with the update?  If it is not
> >normal, what can I do to correct the problem?

As Strahil wrote below, this is normal.

> >
> >Also, what is the correct procedure to update the engine?  Although I
> >tried to read the documentation, I have encountered conflicting
> >documents so I must ask.  Sorry.

Which conflicting documents? You might want to open a github issue
on the documentation. PRs are also most welcome :-)

https://github.com/oVirt/ovirt-site

> >
> >This is how I understand it, but am not confident that it is correct:
> >1. Enable Global HA Maintenance mode.
> >2. On the engine, run # yum update ovirt*

This should work. The docs say "yum update ovirt\*setup\*", which is
"guaranteed" to succeed. "Guaranteed" means that if it fails due to
some conflict, it's considered a bug. If "yum update ovirt*" fails due
to a conflict, it's considered ok (but if it's easy to fix, we'll still
likely fix).

> >3. On the engine, run # engine-setup
> >4. On the engine, run # yum update
> >4. Reboot the hosted engine.  Is "systemctl reboot" acceptable or do I
> >have to do a "hosted-engine --vm-restart" from a host?

Where did you find "--vm-restart"? I do not think we ever had such an option.
You should use 'hosted-engine --vm-shutdown', and after it's down, as you can
verify with 'hosted-engine --vm-status' (and ps auxww | grep qemu), start it
with 'hosted-engine --vm-start'. If you 'reboot' from within the VM, that is
just fine as well, but the vm will remain down until you manually start it
(this is by design, when in global maintenance mode).

As always, if this is a production setup, and especially since it seems like
this is your first upgrade, I recommend to practice first on a test setup (can
be on nested-kvm VMs as hosts, no need for physical machines for this).

Best regards,

> >5. Disable Global HA Maintenance mode.
> >
> >Your expert guidance is much appreciated.
> >___
> >Users mailing list -- users@ovirt.org
> >To unsubscribe send an email to users-le...@ovirt.org
> >Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> >oVirt Code of Conduct:
> >https://www.ovirt.org/community/about/community-guidelines/
> >List Archives:
> >https://lists.ovirt.org/archives/list/users@ovirt.org/message/PAE3EGSMRPJ3SX5UEPXMCUFRT7E5WE3Z/
>
> Version lock is normal, but don't directly use yum.
>
> The correct peocedure  should  be:
> https://www.ovirt.org/documentation/upgrade-guide/chap-Upgrading_from_4.1_to_oVirt_4.2.html
>
> Best Regards,
> Strahil Nikolov
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/2ACPVGJ76JQD6OGSV74I2WKAXSSN7UD3/



-- 
Didi
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2HXSLAZ5Y5QY73V3PDCHIRKYKE7FFL4C/


[ovirt-users] Re: Update hosted engine to 4.3.8 from 4.3.7 questions

2020-02-06 Thread Strahil Nikolov
On February 6, 2020 6:21:02 PM GMT+02:00, d...@bornfree.org wrote:
>I'd like to update my hosted engine to version 4.3.8 from 4.3.7, but
>have concerns.
>
>First, on the hosted engine, yum reports that several packages are
>version locked.  Specifically:
>0:ovirt-engine-webadmin-portal-4.3.8.2-1.el7.*
>0:ovirt-engine-dwh-4.3.8-1.el7.*
>0:ovirt-engine-tools-backup-4.3.8.2-1.el7.*
>0:ovirt-engine-restapi-4.3.8.2-1.el7.*
>0:ovirt-engine-dbscripts-4.3.8.2-1.el7.*
>0:ovirt-engine-4.3.8.2-1.el7.*
>0:ovirt-engine-backend-4.3.8.2-1.el7.*
>0:ovirt-engine-tools-4.3.8.2-1.el7.*
>
>Is this normal and is it okay to proceed with the update?  If it is not
>normal, what can I do to correct the problem?
>
>Also, what is the correct procedure to update the engine?  Although I
>tried to read the documentation, I have encountered conflicting
>documents so I must ask.  Sorry.
>
>This is how I understand it, but am not confident that it is correct:
>1. Enable Global HA Maintenance mode.
>2. On the engine, run # yum update ovirt*
>3. On the engine, run # engine-setup
>4. On the engine, run # yum update
>4. Reboot the hosted engine.  Is "systemctl reboot" acceptable or do I
>have to do a "hosted-engine --vm-restart" from a host?
>5. Disable Global HA Maintenance mode.
>
>Your expert guidance is much appreciated.
>___
>Users mailing list -- users@ovirt.org
>To unsubscribe send an email to users-le...@ovirt.org
>Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>oVirt Code of Conduct:
>https://www.ovirt.org/community/about/community-guidelines/
>List Archives:
>https://lists.ovirt.org/archives/list/users@ovirt.org/message/PAE3EGSMRPJ3SX5UEPXMCUFRT7E5WE3Z/

Version lock is normal, but don't directly use yum.

The correct peocedure  should  be:
https://www.ovirt.org/documentation/upgrade-guide/chap-Upgrading_from_4.1_to_oVirt_4.2.html

Best Regards,
Strahil Nikolov
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2ACPVGJ76JQD6OGSV74I2WKAXSSN7UD3/