|
Bugzilla – Full Text Bug Listing |
| Summary: | Please enable networkd in the systemd package | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Markos Chandras <mchandras> |
| Component: | Basesystem | Assignee: | Franck Bui <fbui> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | astieger, lnussel, sweet_f_a, systemd-maintainers |
| Version: | Leap 42.3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Markos Chandras
2017-12-05 14:47:00 UTC
Hi Markos, Since Ludwig is fine with this, I'll do this change and both 42.2 and 42.3 will ship networkd. However networkd will be still disabled by default. Cheers. Maintenance is not fine with this for Leap 42.2/42.3. (In reply to Andreas Stieger from comment #2) > Maintenance is not fine with this for Leap 42.2/42.3. Hi Andreas, Could you explain why maintenance is not happy with it? Do you also oppose to a separate systemd-networkd subpackage which is not pulled in by default by the systemd one? (In reply to Markos Chandras from comment #3) > Could you explain why maintenance is not happy with it? That is openSUSE Maintenance I might add, and I may just be the standard stance based on the information given. Basically I am concerned about the introduction of this into Leap 42.x without proper integrating this with the other network management things. Overall I think such a change may be better suited for Leap 15, which is what Ludwig may have meant. I mean, there was probably a reason why this was not shipped in SLE 12 and Leap? Do you intend to fork the Leap 42.x package from SLE for this? Do you intend to bring through SLE maintenance? > Do you also oppose to a separate systemd-networkd subpackage > which is not pulled in by default by the systemd one? Not much different here, it would be off either way unless systemd magically starts such things. Would not make much sense though to introduce a new package to then merge it again in TW and 15. You can make a change to SUSE:SLE-12-SP2:Update/system that enables building of systemd-networkd. Whether you make this a conditional or a subpackage that is shipped in Leap but not SLE I will leave to you. Once this update is imported into Leap maintenance, systemd-networkd will be available in Leap, with the understanding that it remains off by default. networkd has been enabled on Leap distros eventually, see: https://build.suse.de/package/rdiff/home:fbui:systemd:SLE-12-SP2/systemd?linkrev=base&rev=214 So it should be part of the next update of systemd. Closing. SUSE-SU-2018:0546-1: An update that solves one vulnerability and has 5 fixes is now available. Category: security (moderate) Bug References: 1057974,1068588,1071224,1071311,1075801,1077925 CVE References: CVE-2017-18078 Sources used: SUSE Linux Enterprise Software Development Kit 12-SP3 (src): systemd-228-150.32.1 SUSE Linux Enterprise Software Development Kit 12-SP2 (src): systemd-228-150.32.1 SUSE Linux Enterprise Server for Raspberry Pi 12-SP2 (src): systemd-228-150.32.1 SUSE Linux Enterprise Server 12-SP3 (src): systemd-228-150.32.1 SUSE Linux Enterprise Server 12-SP2 (src): systemd-228-150.32.1 SUSE Linux Enterprise Desktop 12-SP3 (src): systemd-228-150.32.1 SUSE Linux Enterprise Desktop 12-SP2 (src): systemd-228-150.32.1 SUSE CaaS Platform ALL (src): systemd-228-150.32.1 OpenStack Cloud Magnum Orchestration 7 (src): systemd-228-150.32.1 openSUSE-SU-2018:0560-1: An update that solves one vulnerability and has 5 fixes is now available. Category: security (moderate) Bug References: 1057974,1068588,1071224,1071311,1075801,1077925 CVE References: CVE-2017-18078 Sources used: openSUSE Leap 42.3 (src): systemd-228-44.1, systemd-mini-228-44.1 FYI this networkd feature was IMHO totally unnecessary for a maintenance update and introduced a real annoying bug #1085062 which forced me to manually repair 3 files on each of our 20 machines ... |