| 2016-09-28 16:56:25 |
John Lenton |
bug |
|
|
added bug |
| 2016-09-28 17:07:27 |
Zygmunt Krynicki |
summary |
IT DOESN'T WORK |
prefer "core" rather than "ubuntu-core" if installed |
|
| 2016-09-28 17:10:17 |
Zygmunt Krynicki |
description |
OMG OMG OMG |
The system may run with more than one core snap, by default all snaps should run against the "core" snap but for compatibility the system should fall back to the "ubuntu-core" snap. |
|
| 2016-09-28 17:10:18 |
Zygmunt Krynicki |
snap-confine: milestone |
|
1.0.43 |
|
| 2016-10-04 16:12:59 |
Zygmunt Krynicki |
snap-confine: milestone |
1.0.43 |
1.0.42.1 |
|
| 2016-10-04 16:13:02 |
Zygmunt Krynicki |
snap-confine: status |
Triaged |
Fix Released |
|
| 2016-10-04 16:18:12 |
Zygmunt Krynicki |
description |
The system may run with more than one core snap, by default all snaps should run against the "core" snap but for compatibility the system should fall back to the "ubuntu-core" snap. |
[Impact]
snap-confine uses the "core" snap as the root filesystem of the environment where snap applications execute. In the past that was always "ubuntu-core". The core snap has now been renamed to just "core" and snap-confine needs to handle this case gracefully.
If both snaps are preset (core and ubuntu-core) then core is preferred and used. The apparmor profile was adjusted so that both "core" and "ubuntu-core" names are allowed and internally the code uses two new functions to find the location of the preferred core snap (one in the internal filesystem layout and one in the external filesystem layout)
For more information about the execution environment, please see this article http://www.zygoon.pl/2016/08/snap-execution-environment.html
[Test Case]
The test case can be found here:
https://github.com/snapcore/snap-confine/tree/master/spread-tests/main/core-is-preferred
The test case is ran automatically for each pull request and for each final release. It can be reproduced manually by executing the shell commands listed in the prepare/execute/restore phases manually.
The commands there assume that snapd and snap-confine are installed.
No other additional setup is necessary.
[Regression Potential]
* Regression potential is minimal and mainly depends on what is published to the store as the "core" snap. If the core snap would somehow contain totally bogus content then obviously snaps would cease to work correctly.
[Other Info]
* snap-confine is technically an integral part of snapd which has an SRU exception and is allowed to introduce new features and take advantage of accelerated procedure. For more information see https://wiki.ubuntu.com/SnapdUpdates
== # Pre-SRU bug description follows # ==
The system may run with more than one core snap, by default all snaps should run against the "core" snap but for compatibility the system should fall back to the "ubuntu-core" snap. |
|
| 2016-10-06 16:43:21 |
Andy Whitcroft |
bug task added |
|
snap-confine (Ubuntu) |
|
| 2016-10-06 16:46:37 |
Andy Whitcroft |
snap-confine (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2016-10-06 16:46:39 |
Andy Whitcroft |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-10-06 16:46:44 |
Andy Whitcroft |
bug |
|
|
added subscriber SRU Verification |
| 2016-10-06 16:46:50 |
Andy Whitcroft |
tags |
|
verification-needed |
|
| 2016-10-06 17:47:33 |
Launchpad Janitor |
snap-confine (Ubuntu): status |
New |
Fix Released |
|
| 2016-10-10 09:38:23 |
John Lenton |
tags |
verification-needed |
verification-done |
|
| 2016-10-10 20:20:51 |
Launchpad Janitor |
snap-confine (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-10-10 20:21:34 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
