2. I guess that when I recently 'reinstalled' the host from UI, the old teamports' ifcfg-<DEVICENAME> was moved to ifcfg-<DEVICENAME>-1 and the original file was left empty.
3. When the system rebooted, network.service rereads all ifcfg-* files and starts the team0 , but when NetworkManager reads the empty files - he alters the /etc/resolv.conf which leads to out-of-sync status.

Still, this is only theory and as ovirt3  has no team device (plain gluster arbiter) - I'm not sure how close  is this one.

Best Regards,
Strahil Nikolov

On Nov 2, 2019 09:50, Strahil Nikolov <hunter86_bg@yahoo.com> wrote:

I saw the hint in the Cluster's tab and then on each host. I had to put the host back to maintenance in order to sync it again.

Logs attached .

Best Regards,

Strahil Nikolov

В четвъртък, 31 октомври 2019 г., 16:12:53 ч. Гринуич+2, Dominik Holler <dholler@redhat.com> написа:

On Thu, Oct 31, 2019 at 10:06 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:

Il giorno gio 31 ott 2019 alle ore 09:45 Strahil Nikolov <hunter86_bg@yahoo.com> ha scritto:

Hi Sandro,

I have just updated to latest release candidate (2 clusters in total - 1 AMD , 1 Intel).

The only issue observed is that after patching every host's ovirtmgmt (I have another one that has none of the 4 roles which was OK) is out of sync and has to be synced before removing maintenance.

Still the system was accessible.

Can you guide me which log reports the out-of-sync in order to further investigate.

+Miguel Duarte de Mora Barroso , +Dominik Holler can you please help here?

 

Do you remember if there was a hint shown as a tooltip if you hover the
mouse pointer over ovirtmgmt in
"Compute > Hosts > xxx > Network Interfaces > Setup Host Networks"
?

Are you able to share the vdsm.log and engine.log after the  ovirtmgmt?