NetworkManager service crash on recent all snaps images

Bug #1635607 reported by Jonathan Cave
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snappy-hwe-snaps
Fix Released
Critical
Simon Fels

Bug Description

NetworkManager service appears to crash when left running for a period of time on all-snaps images. Result is loss of network address on the interfaces managed.

Running with snapd from master on 20/10/2016.

snap list:
Name Version Rev Developer Notes
bluez 5.37-1 6 canonical -
checkbox-plano 21~s16 1 ce-certification-qa devmode
cloud-led 1 x1 -
core 16.04.1 72 canonical -
modem-manager 1.4.0-1 1 canonical -
network-manager 1.2.2-6 31 canonical -
snapweb 0.21 18 canonical -
stlouis 16.04-1.5 2 canonical -
stlouis-kernel 4.4.0-38-4 1 canonical -
tpm 1.2-3 9 canonical -
uefi-fw-tools 1.1-0.7.2+git 1 canonical -

Revision history for this message
Jonathan Cave (jocave) wrote :
Simon Fels (morphis)
tags: added: network-manager
Simon Fels (morphis)
tags: added: plano-acan
Changed in snappy-hwe-snaps:
importance: Undecided → Critical
assignee: nobody → Simon Fels (morphis)
Revision history for this message
Simon Fels (morphis) wrote :

The relevant part out of the log from above is

Oct 19 13:00:57 localhost NetworkManager[1527]: <warn> [1476882057.1364] settings: couldn't set the system hostname to '10-155-115-54.conference' using hostnamed: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.9" (uid=0 pid=1527 comm="/snap/network-manager/31/usr/sbin/NetworkManager -") interface="org.freedesktop.hostname1" member="SetHostname" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=1319 comm="/lib/systemd/systemd-hostnamed ")
Oct 19 13:00:57 localhost kernel: [ 46.972759] audit: type=1326 audit(1476882057.129:58): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=1527 comm="NetworkManager" exe="/snap/network-manager/31/usr/sbin/NetworkManager" sig=31 arch=c000003e syscall=170 compat=0 ip=0x7f3119a22c17 code=0x0

The seccomp denial makes NetworkManager restart.

Revision history for this message
Simon Fels (morphis) wrote :
Changed in snappy-hwe-snaps:
status: New → In Progress
Revision history for this message
Simon Fels (morphis) wrote :

Asked core team to get the fix in for the final release this week.

Simon Fels (morphis)
Changed in snappy-hwe-snaps:
status: In Progress → Won't Fix
status: Won't Fix → Fix Committed
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.