[Bug 1123699] libvirt does not start default network automatically
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=1123699 http://bugzilla.suse.com/show_bug.cgi?id=1123699#c24 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(max@suse.com), | |needinfo?(mt@suse.com) | --- Comment #24 from Marius Tomaschewski <mt@suse.com> --- The /etc/resolv.conf is a link to a file in /run/ now (fate#325872) now and when the installer does not create any in advance (e.g. by calling "netconfig update"), /etc/resolv.conf does not exist initially. The first "netconfig update" will create the link or migrate from a previously generated file to link (BTW: "netconfig update -f" enforces the creation, even there is an /etc/resolv.conf file created by something else than netconfig or a link pointing to some another file than netconfig's). This happens while a "netconfig update" executed by ("netconfig modify" inside) wicked or NM while apply of the 1st lease. The wicked or NM service is started in network.target. The network-online.target is pulled & signals that they finished to setup the network. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com