Bug 1650342 - systemd-networkd support in RHEL 8
Summary: systemd-networkd support in RHEL 8
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: 8.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
Keywords: Reopened
Depends On:
Blocks: 1623566
TreeView+ depends on / blocked
Reported: 2018-11-15 22:09 UTC by Morten Stevens
Modified: 2019-05-07 19:49 UTC (History)
15 users (show)

Clone Of:
Last Closed: 2018-11-26 10:11:22 UTC

Attachments (Terms of Use)

Description Morten Stevens 2018-11-15 22:09:23 UTC
Description of problem:

RHEL 8 beta should support systemd-networkd since it's already shipped with RHEL 7.

Actually, there is no support for systemd-networkd?

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1. dnf provides networkctl
2. systemctl enable systemd-networkd

Actual results:

dnf provides networkctl

Last metadata expiration check: 0:05:31 ago on Thu 15 Nov 2018 10:58:58 PM CET.
Error: No Matches found

# systemctl enable systemd-networkd
Failed to enable unit: Unit file systemd-networkd.service does not exist.

# networkctl
bash: networkctl: command not found...

Expected results:

systemd-networkd should be available

Comment 1 Michal Sekletar 2018-11-16 09:37:05 UTC
(In reply to Morten Stevens from comment #0)

> RHEL 8 beta should support systemd-networkd since it's already shipped with
> RHEL 7.

In RHEL-7 we shipped it in Optional channel, hence it was not officially supported. We decided to remove it for a couple for reasons,
  * networkd is not mature enough and is somewhat poorly maintained upstream
  * networkd is still missing management interfaces (DBUS interface)
  * RHEL's default network configuration tool is NetworkManager and we didn't want to send mixed signals to users
  * RHEL-8 was supposed to be as small as possible in terms of packages
  * we didn't see too much networkd usage (even experimental) in RHEL-7

Comment 2 Robert Scheck 2018-11-25 21:47:30 UTC
Given we raised multiple GSS tickets for systemd-networkd for RHEL 7, that
were even only more or less handled by Red Hat, because it's not in the base
channel, we definitely want to see systemd-networkd in RHEL 8. Reasons are
quite simple: systemd-networkd is smaller than NetworkManager (which is just
bloated on packaging level when looking to dependencies), which perfectly
fine for semi-static simple network configurations in virtual machines or
containers, especially given the fact that network-scripts are now marked as
deprecated (which otherwise would also do the job perfectly). Honestly, the
lack of DBUS interface in systemd-networkd is not an issue for us (it even
fits with our expectation of simple semi-static network configurations).

Comment 3 Robert Scheck 2018-11-25 21:49:58 UTC
Cross-filed case 02260325 at the Red Hat customer portal.

Comment 4 Lukáš Nykrýn 2018-11-26 09:58:02 UTC
I am sorry, but we don't plan to include the systemd-networkd in rhel8.

The main reason is that rhel is a stable distribution and including multiple components that aims to do the same things basically doubles our testing scenarios.

In rhel7 we have custom shell scripts in initrd, initscripts, NetworkManager and systemd-networkd (in optional channel), that are able to set up a network connection. And that complicates the maintenance.

We have agreed that we want to standardise on NM in all the scenarios, so we plan to remove/deprecate all the other solutions.

For your setup, I would encourage you to look into the "configure-and-quit" option for NM.

Also, I don't agree with the claim that it has too many dependencies, just for my curiosity, I have installed a minimal container on F29 (systemd passwd dnf fedora-release vim-minimal) and try to add the NM. The only packages it installed were NetworkManager, NetworkManager-libnm, libndp and polkit-libs.

Comment 5 RHEL Product and Program Management 2018-11-26 10:11:22 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.

Comment 6 Robert Scheck 2018-11-26 15:47:27 UTC
I am sorry, but I hereby request reopening this request given comment #5
happened without any possibility for us for a business justification via GSS.

Comment 12 Phil 2019-03-13 13:08:43 UTC
I'd prefer to be able to decide for myself what kind of network configuration to use. NetworkManager may be great for desktops but I don't want it on my servers. I understand the need to reduce the amount of supported packages and to define a standard on how Redhat's customers should set up their network, though.
Is there maybe a way for Redhat of providing systemd-networkd via an unsupported channel for us die-hards?

Comment 13 Jan Synacek 2019-03-18 08:53:58 UTC
(In reply to Phil from comment #12)
> Is there maybe a way for Redhat of providing systemd-networkd via an
> unsupported channel for us die-hards?

Currently, no. I may create a copr build in the future, though, if the demand is high enough. Or, if you feel brave enough, it shouldn't be really hard to grab the source rpm, modify the spec file a bit and build it locally.

Comment 14 Fred F 2019-03-20 09:37:31 UTC
Programming network interfaces through DBUS/nmcli is super nasty in managed environments. With systemd-networkd you just drop a plaintext file in /etc, which is definitely what you want on a fully managed system.

I know that NetworkManager can also be partially configured through text files, but the text file "API" is not considered stable. If you guys don't want to support networkd officially please at least ship a rpm through an unsupported channel.

Comment 16 Jan Synacek 2019-03-28 11:39:25 UTC
An unofficial repository with unsupported packages with systemd-networkd enabled can be found at


Comment 17 Zach Villers 2019-04-15 02:32:17 UTC
I'd be interested to know how many large installations use NetworkManager vs disabling it and using network scripts. If Network scripts are further deprecated in RHEL 8, I imagine there will be a slower transition. We run upwards of 9K servers at $work, mostly VMs and none of them have NetworkManager enabled (7.3-7.6).

Comment 18 Pat Riehecky 2019-04-24 13:27:42 UTC
I will echo some of the other thoughts here.

Our plan was to move from legacy network scripts to networkd.  We are not using NetworkManager at this time.

Note You need to log in before you can comment on or make changes to this bug.