OK. thanks all of you for your help. I'll wait until the new release.
On Wed, Jan 29, 2014 at 7:07 AM, Fabian Deutsch <fabi...@redhat.com> wrote: > Am Mittwoch, den 29.01.2014, 05:02 -0500 schrieb Antoni Segura Puimedon: > > ----- Original Message ----- > > > From: "Fabian Deutsch" <fabi...@redhat.com> > > > To: "Antoni Segura Puimedon" <asegu...@redhat.com> > > > Cc: "Dan Kenigsberg" <dan...@redhat.com>, "Francisco Pérez" > > <fpere...@gmail.com>, amul...@redhat.com, "VDSM Project > > > Development" <vdsm-de...@lists.fedorahosted.org>, users@ovirt.org > > > Sent: Wednesday, January 29, 2014 10:59:43 AM > > > Subject: Re: [vdsm] [Users] ovirtmgmt vanishes after reboot > > > > > > Am Dienstag, den 28.01.2014, 17:42 -0500 schrieb Antoni Segura > > Puimedon: > > > > > > > > We made some more tests with Francisco on #ovirt today and we saw > > that > > > > for some unknown reason, when rebooting the machine the > > > > ifcfg-<YOURNET> > > > > files disappear while the rule-<YOURNET> and route-<YOURNET> stay. > > > > That > > > > happens even when the both ifcfg, rule and route have the correct > > > > entry > > > > in /config/files and are bound to /config/etc/sysconfig/ > > > > > > > > After reboot it returns to eth0 having the connectivity as it was > > > > defined > > > > with the TUI. > > > > > > > > For libvirt networks a bit of the same as for ifcfg files. Before > > > > reboot > > > > /etc/libvirt/qemu/networks is present in /config/files and findmnt > > > > reports > > > > that /etc/libvirt/qemu/networks is a bound mount > > > > of /config/etc/libvirt/qemu/networks. > > > > After reboot it is not the case anymore. > > > > > > > > @Fabian: Do you think there is something on the reboot that > > restores > > > > the > > > > network conf to the TUI settings? > > > > > > Hey Antoni, > > > > > > I vaguely remember that we had a problem with Node removing some > > ifcfg-* > > > files. But this should have been solved in the TestDay iso. > > > > > > What ISO did you use to reproduce this problem? > > > > We reproduced on Francisco's setup, I think it was oVirt node 3.0.1 > > Right. > I believe the bug you are seeing is: > http://gerrit.ovirt.org/#/c/20068/ > > This has been merged into out stable branch, but the release of a new > oVirt Node ISO for 3.3 is pending because of the vdsm-python-cpopen > dependency problem. > > We plan to do a build early next week. > > - fabian >
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users