Bug 1559629

Summary:	persistent interface names are wrong for some interfaces
Product:	[Fedora] Fedora	Reporter:	Zbigniew Jędrzejewski-Szmek <zbyszek>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	28	CC:	awilliam, gmarr, lnykryn, msekleta, ssahani, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	AcceptedFreezeException
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-18 16:02:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1469205

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.