On Sat, Jun 25, 2016 at 5:57 PM, Robert Story <rst...@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 _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
