apparmor="DENIED" for local build snap

Bug #2036140 reported by JamesLin
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Hypervisor Snap
New
Undecided
Unassigned

Bug Description

If we build snap locally and install it directly on the clean machine, which doesn't have the publish release installed before. We will get error message like this:

```
error: cannot perform the following tasks:
- Start snap "openstack-hypervisor" (unset) services (systemctl command [start snap.openstack-hypervisor.ovs-vswitchd.service] failed with exit status 1: Job for snap.openstack-hypervisor.ovs-vswitchd.service failed because the control process exited with error code.
See "systemctl status snap.openstack-hypervisor.ovs-vswitchd.service" and "journalctl -xeu snap.openstack-hypervisor.ovs-vswitchd.service" for details.
)
```

And we can find some message in dmesg, which shows the apparmor="DENIED" (logs in attachment dmesg.txt)

Revision history for this message
JamesLin (jneo8) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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