[Touch-packages] [Bug 1772859] Comment bridged from LTC Bugzilla
--- Comment From sankar...@in.ibm.com 2018-06-07 06:47 EDT--- Hi there, Now Network Manager(NM) is able to manage the devices with the following changes. Change the contents of the file /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf to [keyfile] unmanaged-devices=none from [keyfile] unmanaged-devices=*,except:type:wifi,except:type:wwan and restart NM(service network-manager restart) did the trick. Why it didn't work earlier: We added interfaces to the file /etc/network/interfaces. So NM is not able to manage the interfaces updated in the said file. When we removed the interfaces from the above file, It started working. Is this approach correct ?? -- You received this bug notification because you are a member of Ubuntu Touch seeded 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 eth0ethernet unmanaged -- eth1ethernet 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 - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard 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 eth0ethernet unmanaged -- eth1ethernet 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772859] Comment bridged from LTC Bugzilla
--- Comment From kieni...@de.ibm.com 2018-06-07 03:18 EDT--- "So your system is obviously not an 18.04 default installation from scratch" This is correct. We are not using a standard installation but build an appliance with a minimal footprint. Our build process builds the appliance using debootstrap and we are using a local apt repository with the deb packages from UBUNTU 18.04 as input for debootstrap. So we are basically controlling what packages are installed in our appliances and right now netplan is not included. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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 eth0ethernet unmanaged -- eth1ethernet 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 - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard 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 eth0ethernet unmanaged -- eth1ethernet 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772859] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2018-06-06 14:43 EDT--- Team, We understand Network Manager is good for desktop but not servers. But given the stability NetworkManager is bringing in and ease of use across different operating systems, i assume users are not restricted not to use NetworkManager for servers. The reason being we going with network manager as explained is to reuse the code for all distros. Note : Netplan is not present/installed in our ubuntu. So by default we are expecting network manager to work. root@57fb2571ae8a:~# ls -l /etc | grep netplan root@57fb2571ae8a:~# If we need to start using netplan, probably we have to re-write the code to configure yaml files which can be understood by netplan. So as a workaround, we would like to understand why network manager is failing to manage the devices? This is definitely to do with open issue, https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842 Let me know if more data is needed for analysis, Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded 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 eth0ethernet unmanaged -- eth1ethernet 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 - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard 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 eth0ethernet unmanaged -- eth1ethernet 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772859] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2018-06-06 03:26 EDT--- Team, We understand Network Manager is good for desktop but not servers. But given the stability NetworkManager is bringing in and ease of use across different operating systems, i assume users are not restricted not to use NetworkManager for servers. The reason being we going with network manager as explained is to reuse the code for all distros. Note : Netplan is not present/installed in our ubuntu. So by default we are expecting network manager to work. root@57fb2571ae8a:~# ls -l /etc | grep netplan root@57fb2571ae8a:~# If we need to start using netplan, probably we have to re-write the code to configure yaml files which can be understood by netplan. So as a workaround, we would like to understand why network manager is failing to manage the devices? This is definitely to do with open issue, https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842 Let me know if more data is needed for analysis, Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded 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 eth0ethernet unmanaged -- eth1ethernet 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 - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard 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 eth0ethernet unmanaged -- eth1ethernet 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772859] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2018-06-01 03:11 EDT--- Team, Any update on this issue? This is blocking our experimentation of Network Manager on Ubuntu platform. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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: New Status in network-manager package in Ubuntu: New 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 eth0ethernet unmanaged -- eth1ethernet 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 - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard 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 eth0ethernet unmanaged -- eth1ethernet 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp