http://bugzilla.opensuse.org/show_bug.cgi?id=1130237
Bug ID: 1130237
Summary: wicked incorrectly reports that eth0 is non-existent
within lxc
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Network
Assignee: bnc-team-screening@forge.provo.novell.com
Reporter: bugs+opensuse@lhpmail.us
QA Contact: qa-bugs@suse.de
Found By: ---
Blocker: ---
Created attachment 800978
--> http://bugzilla.opensuse.org/attachment.cgi?id=800978&action=edit
wicked debug log from journalctl
Host: Proxmox 5.3-11
wicked 0.6.53
Currently, inside a lxc container, wicked has difficulty detecting eth0 device
at least with openSUSE Leap tumbleweed on boot. Remedying this requires calling
ip l s eth0 up. Than magically the network configuration is applied.
Interestingly enough, I am not able to reproduce this behaviour with Leap 15.0.
Here is rootfs I'm currently using:
https://download.lhprojects.net/dl/opensuse-tumbleweed-default_20190322_amd6....
● wicked.service - wicked managed network interfaces
Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor
preset: disabled)
Active: active (exited) since Fri 2019-03-22 13:38:00 UTC; 44min ago
Main PID: 89 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
Memory: 0B
CGroup: /system.slice/wicked.service
Mar 22 13:37:30 ipms systemd[1]: Starting wicked managed network interfaces...
Mar 22 13:38:00 ipms wicked[89]: lo up
Mar 22 13:38:00 ipms wicked[89]: eth0 no-device
Mar 22 13:38:00 ipms systemd[1]: Started wicked managed network interfaces.
# cat /etc/sysconfig/network/ifcfg-eth0
STARTMODE=onboot
BOOTPROTO=static
IPADDR=10.0.2.2/24
# ip a
1: lo: