http://bugzilla.opensuse.org/show_bug.cgi?id=1136927

Bug ID: 1136927 Summary: [Build 20190528] System does not use same network names after update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/945719/modules/check _network/steps/3 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: dimstar@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: ---

## Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-update_Leap_15.0_cryptlvm@uefi fails in [check_network](https://openqa.opensuse.org/tests/945719/modules/check_network/steps/3)

## Test suite description Upgrade scenario with cryptlvm for Leap 15.0. Maintainer: riafarov.

## Reproducible

Fails since (at least) Build [20190528](https://openqa.opensuse.org/tests/945450)

## Expected result

Last good: [20190527](https://openqa.opensuse.org/tests/943840) (or more recent)

## Further details

Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?distri=opensuse&machine=uefi&am...)

So far, we kept the network name from an openSUSE Leap 15.x update (using eth0) to Tumbleweed, in order to have 'least surprise' for the user.

With the update to dracut 0.49+git... this seems to have gotten lost: as can be seen in the referenced job run, the system now uses an ens4 network interface name (and as a consequence has no valid network configuration, as /etc/sysconfig/network only has a config for eth0)

This is critical, as a remote-upgraded system will not be accessible without network interfaces coming up