Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1732176 - systemd-networkd on Fedora 30 does not work with Linux 5.2
Summary: systemd-networkd on Fedora 30 does not work with Linux 5.2
Keywords:
Status: CLOSED DUPLICATE of bug 1718192
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-22 21:49 UTC by Hristo Venev
Modified: 2019-08-05 21:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-05 21:07:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Hristo Venev 2019-07-22 21:49:47 UTC
Description of problem:
systemd-networkd cannot bring network interfaces up on Linux 5.2 (fails with EINVAL)

Version-Release number of selected component (if applicable):
systemd-241-9.gitb67ecf2.fc30.x86_64

How reproducible:
Fully

Steps to Reproduce:
1. Configure systemd-networkd
2. Install Linux 5.2.2
3. Boot

Actual results:
systemd-networkd fails to bring network interfaces up

Expected results:
systemd-networkd brings network interfaces up

Additional info:
Fixed in systemd commit 4eb086a38712ea98faf41e075b84555b11b54362, systemd-stable 242 commit 8fbc72f45f4aa84889bc8694a9ce662946464c37.

Commit 9f6e82e6eb3b6e73d66d00d1d6eee60691fb702f makes a lot of sense, so consider including it as well. It is also included in systemd-stable 242.

Comment 1 Zbigniew Jędrzejewski-Szmek 2019-08-05 21:07:47 UTC

*** This bug has been marked as a duplicate of bug 1718192 ***


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