bonded interface not starting automatically
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
In Progress
|
Medium
|
Revati S Hiremath |
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
ProcVersionSign
Uname: Linux 4.2.0-12-generic x86_64
NonfreeKernelMo
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.
Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/
X: INTERFACE_
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago)
WifiSyslog:
mtime.conffile.
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.
Changed in network-manager (Ubuntu): | |
assignee: | nobody → Revati S Hiremath (rhiremath45) |
Changed in network-manager (Ubuntu): | |
status: | New → In Progress |
Changed in network-manager (Ubuntu): | |
status: | In Progress → Confirmed |
Changed in network-manager (Ubuntu): | |
status: | Confirmed → In Progress |
Changed in network-manager (Ubuntu): | |
importance: | Undecided → Medium |
Looking at the error above... I think I see one issue... in /sys/class/net/, bonding_masters is a file, not a folder.