Bug 1559629 - persistent interface names are wrong for some interfaces
Summary: persistent interface names are wrong for some interfaces
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F28BetaFreezeException
TreeView+ depends on / blocked
 
Reported: 2018-03-22 22:21 UTC by Zbigniew Jędrzejewski-Szmek
Modified: 2018-04-18 16:02 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-18 16:02:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1558027 0 unspecified CLOSED The network.service failed LSB in Fedora Cloud. 2021-02-22 00:41:40 UTC

Internal Links: 1558027

Description Zbigniew Jędrzejewski-Szmek 2018-03-22 22:21:19 UTC
The inadvertent interface name change was fixed in https://github.com/systemd/systemd/commit/8eebb6a9e5.

Version-Release number of selected component (if applicable):
systemd-238-4.fc28

Comment 1 Fedora Blocker Bugs Application 2018-03-22 22:24:08 UTC
Proposed as a Freeze Exception for 28-beta by Fedora user zbyszek using the blocker tracking app because:

 This can potentially break networking. And if machines are set up with this bug present, and then systemd is upgraded to a version without this bug, the interface names will change again. All in all, it's better to fix this as quickly as possible.

Comment 2 Adam Williamson 2018-03-23 01:19:30 UTC
+1 FE for me.

Comment 3 Fedora Update System 2018-03-26 17:19:00 UTC
systemd-238-5.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-037a145d4d

Comment 4 Geoffrey Marr 2018-03-26 19:00:12 UTC
Discussed during the 2018-03-26 blocker review meeting: [1]

The decision to classify this bug as an AcceptedFreezeException was made as this could break many network configurations on upgrade, and upgrades use the stable repositories (not updates-testing), so we should get this fixed in stable ASAP.

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2018-03-26/f28-blocker-review.2018-03-26-16.01.txt

Comment 5 Fedora Update System 2018-03-26 20:52:23 UTC
systemd-238-5.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-037a145d4d

Comment 6 Adam Williamson 2018-03-27 16:11:51 UTC
The fix for this was pulled into the Beta-1.1 (Beta RC1) compose. Can anyone with an affected system confirm the fix in that compose? Thanks.

Comment 7 Zbigniew Jędrzejewski-Szmek 2018-04-18 16:02:23 UTC
Let's close this, since no feedback is apparently coming.


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