My version ubuntu server 18.04. Below worked for me:

1. Creating an empty file(/etc/NetworkManager/conf.d/10-globally-
managed-devices.conf)

2. removing the file(10-globally-managed-devices.conf) from /usr/lib

and finally

3. changing Network renderer to NetworkManager in Yaml file.

Yaml file location: /etc/netplan

My yaml was like this:

network:
    ethernets:
      eno1:
       dhcp4: true
    version: 2

Changed to:

network:
 version: 2
 renderer: NetworkManager
 ethernets:
  eno1:
   dhcp4: true


and I change it to:

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1772859

Title:
  Network Manager is not able to manage the devices on Ubuntu 18.04

Status in Ubuntu on IBM z Systems:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid

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
          root@(none):~# nmcli d s
          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/ccwgroup/drivers/qeth/<dev_id>/if_name
      - 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
          
-------------------------------------------------------------------------------------
          0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG         A8 qeth eth0     
        online
          0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000          D0 qeth eth1     
        online

      - output of nmcli c s
          root@(none):~# nmcli c s
          NAME  UUID  TYPE  DEVICE
      
      - output of nmcli d s
          root@(none):~# 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/NetworkManager/conf.d/10-globally-managed-devices.conf) and 
restarting NM,
     solved the issue.
     
  2. Ubuntu(version 17.10): Copying the said 
file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the 
     "unmanaged-devices" to none, resolved the issue.

  * link for reference: https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1638842

  For the latest version(18.04), none of the above solutions worked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to