Configure hook breaks content interface plug

Bug #1670371 reported by Pat McGowan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Confirmed
Undecided
Unassigned

Bug Description

Start with a working snap which plugs the ubuntu-app-platform interface.
Add a configure hook (meta/hooks/configure) to the snap
The snap will no longer start, and always reports
You need to connect this snap to the ubuntu app platform snap.

Snap interfaces shows the connection.
$ snap --version
snap 2.22.7
snapd 2.22.7
series 16
ubuntu 16.04
kernel 4.4.0-64-generic

Tested on my laptop, have not yet tried on core.

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Running sudo /usr/lib/snapd/snap-discard-ns <snap> fixes it. Sounds related to lp:1645731

Revision history for this message
Kyle Fazzari (kyrofa) wrote :

Confirmed. This is particularly weird considering a few things:

1) The content interface to the ubuntu-app-platform is automatically connected, even if the consumer is --dangerous. I assume this is a slot-side assertion.
2) The configure hook specifically runs _after_ services in the snap, which means confinement (including the content interface since it's automatically connected) should be put together by then.

Changed in snappy:
status: New → Confirmed
Michael Vogt (mvo)
affects: snappy → snapd
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.