https://bugzilla.novell.com/show_bug.cgi?id=843526 https://bugzilla.novell.com/show_bug.cgi?id=843526#c0 Summary: question: network.service enablement (network:wicked:factory/wicked -> factory) Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: fcrozat@suse.com ReportedBy: mt@suse.com QAContact: qa-bugs@suse.de CC: aj@suse.com, ohering@suse.com, werner@suse.com, security-team@suse.de, mfilka@suse.com, kmroz@suse.com, pwieczorkiewicz@suse.com Found By: --- Blocker: --- Until now, the sysconfig network service were enabling itself by default at installation time. Frederic: How should we handle this with wicked? Should we use systemd-presets[-branding-openSUSE] or enable it as before with sysconfig? Currently wicked.spec enables itself if the network.service link (is unset) or points to wicked.service or network.service [=syscofig], that is when it migrates from/replaces sysconfig-network. In a normal installation yast2-network network service is changing to the network service as needed / as specified by the user. But on update or additional install of wicked, yast2-network is not involved and when the spec file does not enable itself as above, there would be no network enabled after reboot... See also obs rq #201154. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.