Network Manager is not able to manage the devices on Ubuntu 18.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Invalid
|
Undecided
|
Unassigned | ||
network-manager (Ubuntu) |
Invalid
|
Undecided
|
Ubuntu on IBM Power Systems Bug Triage |
Bug Description
NetworkManager is not able to manage the devices on latest Ubuntu(18.04)
---uname output---
Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux
Machine Type = z14 s390
---Debugger---
A debugger is not configured
---Steps to Reproduce---
1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4).
2. Configure a network device and login to the partition through ssh.
3. Now you can see the following output
DEVICE TYPE STATE CONNECTION
eth0 ethernet unmanaged --
eth1 ethernet unmanaged --
lo loopback unmanaged --
Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x
The userspace tool has the following bit modes: 64-bit
Userspace rpm: NetworkManager --version 1.10.4
Userspace tool obtained from project website: na
Some more information about the issue:
Network device has been configured manually after the image is up from Support Element(SE):
- znetconf -a <dev_id>
- cat /sys/bus/
- ifconfig <interface_name> <ip_address> netmask 255.255.255.0
- route add default gw <gateway_address> <interface_name>
- SSH service has been configured
This helped us to login to the Lpar. In Lpar
- output of znetconf -c
Device IDs Type Card Type CHPID Drv. Name State
- output of nmcli c s
NAME UUID TYPE DEVICE
- output of nmcli d s
DEVICE TYPE STATE CONNECTION
eth0 ethernet unmanaged --
eth1 ethernet unmanaged --
lo loopback unmanaged --
* The above output shows that devices are not managed by nmcli
After some investigation we found couple of suggestions like
1. Ubuntu(version <17.04): Creating an empty file(/etc/
solved the issue.
2. Ubuntu(version 17.10): Copying the said file(10-
"unmanaged-
* link for reference: https:/
For the latest version(18.04), none of the above solutions worked.
tags: | added: architecture-all bugnameltc-168090 severity-critical targetmilestone-inin--- |
Changed in ubuntu: | |
assignee: | nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
affects: | ubuntu → linux (Ubuntu) |
First of all some comments:
- why was znetconf used and not chzdev ?
- I'm a bit puzzled reading about "rpm" in combination with Ubuntu
even if a universe rpm package exists, I assume a network-manager deb package was used, right?
- afaik the network-manager package (that also incl. the nmcli) is a package that belongs to the desktop-packages pocket (need to check this ...)
- is the use of the ip tools (from iproute2) an alternative?