Bug 963726 - Dracut does not include 70-persistent-net.rules
Summary: Dracut does not include 70-persistent-net.rules
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Fabian Vogt
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-27 08:46 UTC by Fabian Vogt
Modified: 2016-01-27 13:32 UTC (History)
6 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Fabian Vogt 2016-01-27 08:46:54 UTC 
For various reasons, dracut does not include 70-persistent-net.rules.
This is not necessary on "normal" TW systems as those use predictable network names by default ("enp25s0", "wlp3s1").
When upgrading from 13.2 or Leap 42.1, it is required to include the rules file as the network interfaces don't get the same names as before the upgrade, breaking the network configuration both inside the initrd and after fully booting.
This is even more important due to another bug that network support is included by default.

The file was included once, but that patch got reverted shortly afterwards, due to bug 886669.
Comment 1 Jiri Bohac 2016-01-27 13:26:28 UTC 
Why would you need the rules file in the initramfs? As explained in bsc#886669, this has several problems.

It should suffice to have the file in the installed root filesystem.
And during the upgrade it stays there, so it should work. What exactly is the problem?
Comment 2 Fabian Vogt 2016-01-27 13:32:01 UTC 
(In reply to Jiri Bohac from comment #1)
> Why would you need the rules file in the initramfs? As explained in
> bsc#886669, this has several problems.
> 
> It should suffice to have the file in the installed root filesystem.
> And during the upgrade it stays there, so it should work. What exactly is
> the problem?

bug 960669 is the rather big problem.