[Desktop-packages] [Bug 1502635] Re: bonded interface not starting automatically
** Changed in: network-manager (Ubuntu) Importance: Undecided => Medium -- 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/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: In Progress Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+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
[Desktop-packages] [Bug 1502635] Re: bonded interface not starting automatically
** Attachment added: "result.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+attachment/4520007/+files/result.png -- 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/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: In Progress Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+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
[Desktop-packages] [Bug 1502635] Re: bonded interface not starting automatically
** Attachment added: "main.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+attachment/4520009/+files/main.png -- 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/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: In Progress Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+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
[Desktop-packages] [Bug 1502635] Re: bonded interface not starting automatically
** Attachment added: "main.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+attachment/4520008/+files/main.png -- 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/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: In Progress Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+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
[Desktop-packages] [Bug 1502635] Re: bonded interface not starting automatically
** Changed in: network-manager (Ubuntu) Status: In Progress => Confirmed -- 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/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: Confirmed Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+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
[Desktop-packages] [Bug 1502635] Re: bonded interface not starting automatically
** Changed in: network-manager (Ubuntu) Status: Confirmed => In Progress -- 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/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: In Progress Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+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
[Desktop-packages] [Bug 1502635] Re: bonded interface not starting automatically
** Changed in: network-manager (Ubuntu) Status: New => In Progress -- 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/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: In Progress Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+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
[Desktop-packages] [Bug 1502635] Re: bonded interface not starting automatically
The patch for the above solution is attached. ** Attachment added: "bugs.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+attachment/4506401/+files/bugs.txt -- 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/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: In Progress Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+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
[Desktop-packages] [Bug 1502635] Re: bonded interface not starting automatically
The attachment "bugs.txt" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: In Progress Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+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
[Desktop-packages] [Bug 1502635] Re: bonded interface not starting automatically
I must be missing it; I see the bugs.txt which looks like output, but I don't see a patch attached? Thanks! -- 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/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: In Progress Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+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
[Desktop-packages] [Bug 1502635] Re: bonded interface not starting automatically
Looking at the error above... I think I see one issue... in /sys/class/net/, bonding_masters is a file, not a folder. -- 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/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: New Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+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
[Desktop-packages] [Bug 1502635] Re: bonded interface not starting automatically
** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Revati S Hiremath (rhiremath45) -- 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/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: New Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+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
