On Wed, 27 Feb 2019 08:52:24 +0200
Juhani Rautiainen <juhani.rautiainen(a)gmail.com> wrote:
On Tue, Feb 26, 2019 at 12:05 PM Dominik Holler
<dholler(a)redhat.com> wrote:
>
> On Mon, 25 Feb 2019 13:46:59 +0200
> Juhani Rautiainen <juhani.rautiainen(a)gmail.com> wrote:
>
> > Hi!
> >
> > I had weird occurence in my two node ovirt cluster today (I have HE).
> > I noticed that one node had ovirtmgmt network unsynchronized. I tried
> > to resynchronize it. This led the node being rebooted by HP ILO. After
> > reboot the node came up with DHCP address. Tried to change it back by
> > fixing ifcfg-ovirtmgmt to original static address.
>
> How did you fix? By ovirt-engine's web UI, REST-API or by modifying a
> config file on the host, or cockpit?
I just copied that ifcfg-ovirtmgmt file from second node and fixed
IP-address to correct one before doing ifdown/ifup. That file had
changed to DHCP so my instinct was trying to correct that one.
Please let oVirt doing the work for you. If you interface to oVirt is
the web UI, please use the dialog "Edit Managment Network: ovirtmgmt"
which opens by clicking on the pencil symbol next to ovirtmgmt in
Compute > Hosts > xxx > Network Interfaces > Setup Host Networks
This will enable oVirt to recognize this change as intended.
>
> If you would share the vdsm.log files containing the relevant flow, this
> would help to understand what happened.
Can I upload these somewhere? I can find the vdsm logs from the
failure time frame. From engine logs I can see that EVENT_ID:
VDS_NETWORKS_OUT_OF_SYNC(1,110) started weeks earlier (February 6th).
The problem really just flared when I noticed it and tried to resync.
There are not old enough vdsm logs to see what happened back then.
This event continues daily so is there anything on vdsm logs which is
connected to that event that I could dig for? Just noticed that this
is pretty much the date I upgraded cluster from 4.2.8 to 4.3.
Maybe no required anymore, since you described very precise what you
did.
Thanks,
Juhani