[ovirt-users] ovirt minor upgrades for nodes via GUI or CLI?

Matthias Leopold matthias.leopold at meduniwien.ac.at
Wed Apr 26 08:20:59 UTC 2017



Am 2017-04-25 um 07:36 schrieb Yedidyah Bar David:
> On Mon, Apr 24, 2017 at 5:41 PM, Matthias Leopold
> <matthias.leopold at meduniwien.ac.at> wrote:
>>
>>
>> Am 2017-04-24 um 16:37 schrieb Yedidyah Bar David:
>>>
>>> On Mon, Apr 24, 2017 at 5:28 PM, Matthias Leopold
>>> <matthias.leopold at meduniwien.ac.at> wrote:
>>>>
>>>> hi,
>>>>
>>>> i'm still testing ovirt 4.1.
>>>>
>>>> i installed engine and 2 nodes in vanilla centos 7.3 hosts with
>>>> everything
>>>> that came from
>>>> http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm
>>>>
>>>> i regularly checked for updates in the engine host OS with "yum update"
>>>> (is
>>>> there a gui option for this?). it obviously got an ovirt update from
>>>> version
>>>> 4.1.0 to 4.1.1.1 already some time ago.
>>>>
>>>> i regularly checked for updates in the nodes via the ovirt web gui
>>>> (installation - check for upgrade). there where package updates available
>>>> and installed in the past so i thought that everything was fine.
>>>>
>>>> now i checked with "yum check-update" in the nodes OS shell and noticed
>>>> that
>>>> ovirt-release41 is still on 4.1.0 and there are 81 packages available for
>>>> update (from centos base _and_ ovirt repos including ovirt-release41
>>>> itself). ovirt gui tells me 'no updates found'.
>>>
>>>
>>> I think this function only checks for specific packages, not everything
>>> yum reports.
>>>
>>>>
>>>> why didn't these updates get installed? is it because of the
>>>> ovirt-release41
>>>> update? do i have to do this manually with yum?
>>>
>>>
>>> ovirt-release41 itself is not one of these packages, and should in
>>> principle
>>> be considered "another package" (just like any other package you installed
>>> on your machine).
>>>
>>> Which packages does yum say you have updates for?
>>
>>
>> firts my repos, to be sure:
>>
>> # yum repolist
>> ...
>> Repo-ID                                        Repo-Name:
>> Status
>> base/7/x86_64                                  CentOS-7 - Base
>> 9.363
>> centos-opstools-testing/x86_64                 CentOS-7 - OpsTools - testing
>> repo                                          448
>> centos-ovirt-common-candidate/x86_64           CentOS-7 - oVirt common
>> 198
>> centos-ovirt41-candidate/x86_64                CentOS-7 - oVirt 4.1
>> 95
>> extras/7/x86_64                                CentOS-7 - Extras
>> 337
>> ovirt-4.1/7                                    Latest oVirt 4.1 Release
>> 455
>> ovirt-4.1-centos-gluster38/x86_64              CentOS-7 - Gluster 3.8
>> 181
>> ovirt-4.1-epel/x86_64                          Extra Packages for Enterprise
>> Linux 7 - x86_64                           11.550
>> ovirt-4.1-patternfly1-noarch-epel/x86_64       Copr repo for patternfly1
>> owned by patternfly                                 2
>> updates/7/x86_64                               CentOS-7 - Updates
>> 1.575
>> virtio-win-stable                              virtio-win builds roughly
>> matching what was shipped in latest RHEL            4
>> repolist: 24.208
>>
>> # yum check-update
>> ...
>> NetworkManager.x86_64                                   1:1.4.0-19.el7_3
...
>> util-linux.x86_64 2.23.2-33.el7_3.2                           updates
>
> Looks ok to me. Please check the upgrade guide for details:
>
> http://www.ovirt.org/documentation/upgrade-guide/chap-Updates_between_Minor_Releases/
>
> It wasn't updated for 4.1 but the principles remain the same.
>
> Best,
>

thank you very much. i should have looked at the docs first

regards
matthias


More information about the Users mailing list