--Sig_/2+FpI4Cvur605E8SRHVCwXB Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I have oVirt 3.5.x on CentOS 7 hosts. These hosts have updates which include livbirt: libvirt-client x86_64 1.2.17-13.el7_2.5 updates 4= .3 M libvirt-daemon x86_64 1.2.17-13.el7_2.5 updates 5= 85 k libvirt-daemon-config-nwfilter x86_64 1.2.17-13.el7_2.5 updates 1= 22 k libvirt-daemon-driver-interface x86_64 1.2.17-13.el7_2.5 updates 1= 62 k libvirt-daemon-driver-network x86_64 1.2.17-13.el7_2.5 updates 3= 02 k libvirt-daemon-driver-nodedev x86_64 1.2.17-13.el7_2.5 updates 1= 61 k libvirt-daemon-driver-nwfilter x86_64 1.2.17-13.el7_2.5 updates 1= 85 k libvirt-daemon-driver-qemu x86_64 1.2.17-13.el7_2.5 updates 5= 71 k libvirt-daemon-driver-secret x86_64 1.2.17-13.el7_2.5 updates 1= 55 k libvirt-daemon-driver-storage x86_64 1.2.17-13.el7_2.5 updates 3= 28 k libvirt-daemon-kvm x86_64 1.2.17-13.el7_2.5 updates 1= 18 k libvirt-lock-sanlock Is it safe to let yum update these packages while the host has running VMs? in maintenance mode? or not at all? Robert --=20 Senior Software Engineer @ Parsons --Sig_/2+FpI4Cvur605E8SRHVCwXB Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAldum/EACgkQ7/fVLLY1mnj6KQCfWUsVS/OU/98ynUgin2QwEw46 ANsAnjElWFKIhCURI95jsBsCmewxDTgq =Oi3o -----END PGP SIGNATURE----- --Sig_/2+FpI4Cvur605E8SRHVCwXB--
On Sat, Jun 25, 2016 at 5:57 PM, Robert Story <rstory@tislabs.com> wrote:
I have oVirt 3.5.x on CentOS 7 hosts. These hosts have updates which include livbirt:
libvirt-client x86_64 1.2.17-13.el7_2.5 updates 4.3 M libvirt-daemon x86_64 1.2.17-13.el7_2.5 updates 585 k libvirt-daemon-config-nwfilter x86_64 1.2.17-13.el7_2.5 updates 122 k libvirt-daemon-driver-interface x86_64 1.2.17-13.el7_2.5 updates 162 k libvirt-daemon-driver-network x86_64 1.2.17-13.el7_2.5 updates 302 k libvirt-daemon-driver-nodedev x86_64 1.2.17-13.el7_2.5 updates 161 k libvirt-daemon-driver-nwfilter x86_64 1.2.17-13.el7_2.5 updates 185 k libvirt-daemon-driver-qemu x86_64 1.2.17-13.el7_2.5 updates 571 k libvirt-daemon-driver-secret x86_64 1.2.17-13.el7_2.5 updates 155 k libvirt-daemon-driver-storage x86_64 1.2.17-13.el7_2.5 updates 328 k libvirt-daemon-kvm x86_64 1.2.17-13.el7_2.5 updates 118 k libvirt-lock-sanlock
Is it safe to let yum update these packages while the host has running VMs? in maintenance mode? or not at all?
The safest way is to put a host into maintenance before updating. All vms will be migrated to other hosts before the host is deactivated. Some packages like sanlock cannot be updated while host is connected to storage; trying to update them may kill sanlock, which will cause the watchdog to reboot your host, killing your vms. Nir
This is a multi-part message in MIME format. --------------6B148EB764556D45B65FA509 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 06/25/2016 10:57 AM, Robert Story wrote:
I have oVirt 3.5.x on CentOS 7 hosts. These hosts have updates which include livbirt:
libvirt-client x86_64 1.2.17-13.el7_2.5 updates 4.3 M libvirt-daemon x86_64 1.2.17-13.el7_2.5 updates 585 k libvirt-daemon-config-nwfilter x86_64 1.2.17-13.el7_2.5 updates 122 k libvirt-daemon-driver-interface x86_64 1.2.17-13.el7_2.5 updates 162 k libvirt-daemon-driver-network x86_64 1.2.17-13.el7_2.5 updates 302 k libvirt-daemon-driver-nodedev x86_64 1.2.17-13.el7_2.5 updates 161 k libvirt-daemon-driver-nwfilter x86_64 1.2.17-13.el7_2.5 updates 185 k libvirt-daemon-driver-qemu x86_64 1.2.17-13.el7_2.5 updates 571 k libvirt-daemon-driver-secret x86_64 1.2.17-13.el7_2.5 updates 155 k libvirt-daemon-driver-storage x86_64 1.2.17-13.el7_2.5 updates 328 k libvirt-daemon-kvm x86_64 1.2.17-13.el7_2.5 updates 118 k libvirt-lock-sanlock
Is it safe to let yum update these packages while the host has running VMs? in maintenance mode? or not at all?
Robert
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I saw a response where we are supposed to go to maintenance mode and then VMs will migrate but i've got nowhere to migrate to as I'm on a host with hosted Engine and no other host to migrate to. So do I shutdown all VMs and then go to maintenance mode and then update and reboot my host? --------------6B148EB764556D45B65FA509 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <p><br> </p> <br> <div class="moz-cite-prefix">On 06/25/2016 10:57 AM, Robert Story wrote:<br> </div> <blockquote cite="mid:20160625105753.5886ef1d@ispx.vb.futz.org" type="cite"> <pre wrap="">I have oVirt 3.5.x on CentOS 7 hosts. These hosts have updates which include livbirt: libvirt-client x86_64 1.2.17-13.el7_2.5 updates 4.3 M libvirt-daemon x86_64 1.2.17-13.el7_2.5 updates 585 k libvirt-daemon-config-nwfilter x86_64 1.2.17-13.el7_2.5 updates 122 k libvirt-daemon-driver-interface x86_64 1.2.17-13.el7_2.5 updates 162 k libvirt-daemon-driver-network x86_64 1.2.17-13.el7_2.5 updates 302 k libvirt-daemon-driver-nodedev x86_64 1.2.17-13.el7_2.5 updates 161 k libvirt-daemon-driver-nwfilter x86_64 1.2.17-13.el7_2.5 updates 185 k libvirt-daemon-driver-qemu x86_64 1.2.17-13.el7_2.5 updates 571 k libvirt-daemon-driver-secret x86_64 1.2.17-13.el7_2.5 updates 155 k libvirt-daemon-driver-storage x86_64 1.2.17-13.el7_2.5 updates 328 k libvirt-daemon-kvm x86_64 1.2.17-13.el7_2.5 updates 118 k libvirt-lock-sanlock Is it safe to let yum update these packages while the host has running VMs? in maintenance mode? or not at all? Robert </pre> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> I saw a response where we are supposed to go to maintenance mode and then VMs will migrate but i've got nowhere to migrate to as I'm on a host with hosted Engine and no other host to migrate to. So do I shutdown all VMs and then go to maintenance mode and then update and reboot my host?<br> <br> </body> </html> --------------6B148EB764556D45B65FA509--
On Sat, Jun 25, 2016 at 8:51 PM, Brett I. Holcomb <biholcomb@l1049h.com> wrote:
On 06/25/2016 10:57 AM, Robert Story wrote:
I have oVirt 3.5.x on CentOS 7 hosts. These hosts have updates which include livbirt:
libvirt-client x86_64 1.2.17-13.el7_2.5 updates 4.3 M libvirt-daemon x86_64 1.2.17-13.el7_2.5 updates 585 k libvirt-daemon-config-nwfilter x86_64 1.2.17-13.el7_2.5 updates 122 k libvirt-daemon-driver-interface x86_64 1.2.17-13.el7_2.5 updates 162 k libvirt-daemon-driver-network x86_64 1.2.17-13.el7_2.5 updates 302 k libvirt-daemon-driver-nodedev x86_64 1.2.17-13.el7_2.5 updates 161 k libvirt-daemon-driver-nwfilter x86_64 1.2.17-13.el7_2.5 updates 185 k libvirt-daemon-driver-qemu x86_64 1.2.17-13.el7_2.5 updates 571 k libvirt-daemon-driver-secret x86_64 1.2.17-13.el7_2.5 updates 155 k libvirt-daemon-driver-storage x86_64 1.2.17-13.el7_2.5 updates 328 k libvirt-daemon-kvm x86_64 1.2.17-13.el7_2.5 updates 118 k libvirt-lock-sanlock
Is it safe to let yum update these packages while the host has running VMs? in maintenance mode? or not at all?
Robert
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I saw a response where we are supposed to go to maintenance mode and then VMs will migrate but i've got nowhere to migrate to as I'm on a host with hosted Engine and no other host to migrate to. So do I shutdown all VMs and then go to maintenance mode and then update and reboot my host?
In this case you cannot put the host into maintenance, since hosted engine is running on this host. Adding Simone to add more details on hosted engine upgrades. Nir
On 06/25/2016 08:10 PM, Nir Soffer wrote:
On Sat, Jun 25, 2016 at 8:51 PM, Brett I. Holcomb <biholcomb@l1049h.com> wrote:
On 06/25/2016 10:57 AM, Robert Story wrote:
I have oVirt 3.5.x on CentOS 7 hosts. These hosts have updates which include livbirt:
libvirt-client x86_64 1.2.17-13.el7_2.5 updates 4.3 M libvirt-daemon x86_64 1.2.17-13.el7_2.5 updates 585 k libvirt-daemon-config-nwfilter x86_64 1.2.17-13.el7_2.5 updates 122 k libvirt-daemon-driver-interface x86_64 1.2.17-13.el7_2.5 updates 162 k libvirt-daemon-driver-network x86_64 1.2.17-13.el7_2.5 updates 302 k libvirt-daemon-driver-nodedev x86_64 1.2.17-13.el7_2.5 updates 161 k libvirt-daemon-driver-nwfilter x86_64 1.2.17-13.el7_2.5 updates 185 k libvirt-daemon-driver-qemu x86_64 1.2.17-13.el7_2.5 updates 571 k libvirt-daemon-driver-secret x86_64 1.2.17-13.el7_2.5 updates 155 k libvirt-daemon-driver-storage x86_64 1.2.17-13.el7_2.5 updates 328 k libvirt-daemon-kvm x86_64 1.2.17-13.el7_2.5 updates 118 k libvirt-lock-sanlock
Is it safe to let yum update these packages while the host has running VMs? in maintenance mode? or not at all?
Robert
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I saw a response where we are supposed to go to maintenance mode and then VMs will migrate but i've got nowhere to migrate to as I'm on a host with hosted Engine and no other host to migrate to. So do I shutdown all VMs and then go to maintenance mode and then update and reboot my host?
In this case you cannot put the host into maintenance, since hosted engine is running on this host.
Adding Simone to add more details on hosted engine upgrades.
Nir Thanks. That will be a big help.
On Sun, Jun 26, 2016 at 4:14 AM, Brett I. Holcomb <biholcomb@l1049h.com> wrote:
On 06/25/2016 08:10 PM, Nir Soffer wrote:
On Sat, Jun 25, 2016 at 8:51 PM, Brett I. Holcomb <biholcomb@l1049h.com> wrote:
On 06/25/2016 10:57 AM, Robert Story wrote:
I have oVirt 3.5.x on CentOS 7 hosts. These hosts have updates which include livbirt:
libvirt-client x86_64 1.2.17-13.el7_2.5 updates 4.3 M libvirt-daemon x86_64 1.2.17-13.el7_2.5 updates 585 k libvirt-daemon-config-nwfilter x86_64 1.2.17-13.el7_2.5 updates 122 k libvirt-daemon-driver-interface x86_64 1.2.17-13.el7_2.5 updates 162 k libvirt-daemon-driver-network x86_64 1.2.17-13.el7_2.5 updates 302 k libvirt-daemon-driver-nodedev x86_64 1.2.17-13.el7_2.5 updates 161 k libvirt-daemon-driver-nwfilter x86_64 1.2.17-13.el7_2.5 updates 185 k libvirt-daemon-driver-qemu x86_64 1.2.17-13.el7_2.5 updates 571 k libvirt-daemon-driver-secret x86_64 1.2.17-13.el7_2.5 updates 155 k libvirt-daemon-driver-storage x86_64 1.2.17-13.el7_2.5 updates 328 k libvirt-daemon-kvm x86_64 1.2.17-13.el7_2.5 updates 118 k libvirt-lock-sanlock
Is it safe to let yum update these packages while the host has running VMs? in maintenance mode? or not at all?
Robert
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I saw a response where we are supposed to go to maintenance mode and then VMs will migrate but i've got nowhere to migrate to as I'm on a host with hosted Engine and no other host to migrate to. So do I shutdown all VMs and then go to maintenance mode and then update and reboot my host?
In this case you cannot put the host into maintenance, since hosted engine is running on this host.
Adding Simone to add more details on hosted engine upgrades.
Nir
Thanks. That will be a big help.
Didn't test, I think this will work: 1. Shutdown all other VMs (as you already did) 2. Move to global maintenance: hosted-engine --set-maintenance --mode=global 3. Cleanly shutdown engine vm 4. stop HA daemons: service ovirt-ha-agent stop ; service ovirt-ha-broker stop 5. yum update what you need/want 6. Reboot (perhaps not always needed) 7. See that HA daemons started 8. Exit global maintenance: hosted-engine --set-maintenance --mode=none 9. Start engine vm (or see that HA starts it) -- Didi
This is how I upgrade. Works. Dr Christophe Trefois, Dipl.-Ing. Technical Specialist / Post-Doc UNIVERSITÉ DU LUXEMBOURG LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE Campus Belval | House of Biomedicine 6, avenue du Swing L-4367 Belvaux T: +352 46 66 44 6124 F: +352 46 66 44 6949 http://www.uni.lu/lcsb ---- This message is confidential and may contain privileged information. It is intended for the named recipient only. If you receive it in error please notify me and permanently delete the original message and any copies. ----
On 26 Jun 2016, at 08:57, Yedidyah Bar David <didi@redhat.com> wrote:
On Sun, Jun 26, 2016 at 4:14 AM, Brett I. Holcomb <biholcomb@l1049h.com> wrote:
On 06/25/2016 08:10 PM, Nir Soffer wrote:
On Sat, Jun 25, 2016 at 8:51 PM, Brett I. Holcomb <biholcomb@l1049h.com> wrote:
On 06/25/2016 10:57 AM, Robert Story wrote:
I have oVirt 3.5.x on CentOS 7 hosts. These hosts have updates which include livbirt:
libvirt-client x86_64 1.2.17-13.el7_2.5 updates 4.3 M libvirt-daemon x86_64 1.2.17-13.el7_2.5 updates 585 k libvirt-daemon-config-nwfilter x86_64 1.2.17-13.el7_2.5 updates 122 k libvirt-daemon-driver-interface x86_64 1.2.17-13.el7_2.5 updates 162 k libvirt-daemon-driver-network x86_64 1.2.17-13.el7_2.5 updates 302 k libvirt-daemon-driver-nodedev x86_64 1.2.17-13.el7_2.5 updates 161 k libvirt-daemon-driver-nwfilter x86_64 1.2.17-13.el7_2.5 updates 185 k libvirt-daemon-driver-qemu x86_64 1.2.17-13.el7_2.5 updates 571 k libvirt-daemon-driver-secret x86_64 1.2.17-13.el7_2.5 updates 155 k libvirt-daemon-driver-storage x86_64 1.2.17-13.el7_2.5 updates 328 k libvirt-daemon-kvm x86_64 1.2.17-13.el7_2.5 updates 118 k libvirt-lock-sanlock
Is it safe to let yum update these packages while the host has running VMs? in maintenance mode? or not at all?
Robert
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I saw a response where we are supposed to go to maintenance mode and then VMs will migrate but i've got nowhere to migrate to as I'm on a host with hosted Engine and no other host to migrate to. So do I shutdown all VMs and then go to maintenance mode and then update and reboot my host?
In this case you cannot put the host into maintenance, since hosted engine is running on this host.
Adding Simone to add more details on hosted engine upgrades.
Nir
Thanks. That will be a big help.
Didn't test, I think this will work:
1. Shutdown all other VMs (as you already did) 2. Move to global maintenance: hosted-engine --set-maintenance --mode=global 3. Cleanly shutdown engine vm 4. stop HA daemons: service ovirt-ha-agent stop ; service ovirt-ha-broker stop 5. yum update what you need/want 6. Reboot (perhaps not always needed) 7. See that HA daemons started 8. Exit global maintenance: hosted-engine --set-maintenance --mode=none 9. Start engine vm (or see that HA starts it) -- Didi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Upgrading libvirt doesn’t touch running VMs, if there are no active VM operations (start/stop/snapshots/migration). I upgrade libvirt/qemu/vdsm on the fly. Just stop the engine to make sure that nothing will interrupt the upgrade. On 25/06/16 17:57, "users-bounces@ovirt.org on behalf of Robert Story" <users-bounces@ovirt.org on behalf of rstory@tislabs.com> wrote: I have oVirt 3.5.x on CentOS 7 hosts. These hosts have updates which include livbirt: libvirt-client x86_64 1.2.17-13.el7_2.5 updates 4.3 M libvirt-daemon x86_64 1.2.17-13.el7_2.5 updates 585 k libvirt-daemon-config-nwfilter x86_64 1.2.17-13.el7_2.5 updates 122 k libvirt-daemon-driver-interface x86_64 1.2.17-13.el7_2.5 updates 162 k libvirt-daemon-driver-network x86_64 1.2.17-13.el7_2.5 updates 302 k libvirt-daemon-driver-nodedev x86_64 1.2.17-13.el7_2.5 updates 161 k libvirt-daemon-driver-nwfilter x86_64 1.2.17-13.el7_2.5 updates 185 k libvirt-daemon-driver-qemu x86_64 1.2.17-13.el7_2.5 updates 571 k libvirt-daemon-driver-secret x86_64 1.2.17-13.el7_2.5 updates 155 k libvirt-daemon-driver-storage x86_64 1.2.17-13.el7_2.5 updates 328 k libvirt-daemon-kvm x86_64 1.2.17-13.el7_2.5 updates 118 k libvirt-lock-sanlock Is it safe to let yum update these packages while the host has running VMs? in maintenance mode? or not at all? Robert -- Senior Software Engineer @ Parsons
participants (6)
-
Brett I. Holcomb -
Christophe TREFOIS -
Nir Soffer -
Pavel Gashev -
Robert Story -
Yedidyah Bar David