[ovirt-users] latest CentOS libvirt updates safe?

Yedidyah Bar David didi at redhat.com
Sun Jun 26 06:57:51 UTC 2016


On Sun, Jun 26, 2016 at 4:14 AM, Brett I. Holcomb <biholcomb at 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 at 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 at 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



More information about the Users mailing list