Hello,

There are a number of bugs [1] reported these days about the issue aourd network config of the hosts, when dealing with interfaces manually configured, with bonding and VLANs. These /etc/sysconfig/network-scripts/ifcfg.* files are wiped by vdsm after rebooting.

I see that there are people at Redhat working on these, and some cases were reproduced in lab conditions - and some were not.

I upgraded 3 DC from 3.4.? to 3.5.1, and faced this issue (lost of every network files) in an non-consistent manner.

I finally thought I coped with this problem by adding
net_persistence = ifcfg
to /etc/vdsm/vdsm.conf
and indeed, when restarting vdsmd and the network, files were conserved.

It was before I observed that some action [2] lead to /etc/vdsm/vdsm.conf being renamed into /etc/vdsm/vdsm.conf.some_timestamp and the original one replaced by a very short file with no netcfg persistence at all.

I didn't identified [2]. That could be :
- some actions made by me through the Web UI ?
- service vdsmd restart ?
- reboots ?

I'm sure that some Redhat people know what could be responsible for renaming /etc/vdsm/vdsm.conf into /etc/vdsm/vdsm.conf.some_timestamp, and I wish they are working closely with Dan Kenigsberg and Michael Burman who helped a lot on these issues (or maybe, THEY are the coders responsible for this ?)

[2] :
- https://bugzilla.redhat.com/show_bug.cgi?id=1154399
- https://bugzilla.redhat.com/show_bug.cgi?id=1188251
- and more or less related :
https://bugzilla.redhat.com/show_bug.cgi?id=1134346

--
Nicolas Ecarnot
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to