This was fixed upstream and included in our stable branch. A cherry-pick
was uploaded to Zesty and all tests were run successfully against it.
I have now uploaded the same thing for xenial and yakkety, they are in
the queue waiting for a SRU team member to approve them.
Once the Xenial SRU is through, I'll update the trusty-backports pocket
with it.
** Changed in: lxc (Ubuntu Yakkety)
Status: Triaged => In Progress
** Changed in: lxc (Ubuntu Xenial)
Status: Triaged => In Progress
** Description changed:
- As in topic. Since the 20161217 rootfs, after upgrade of lxc from
- 2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the lxc-
- android-config service does not start - making the devices unbootable.
+ # SRU
+ ## Rationale
+ LXC 2.0.6 introduced a writability test for /var/lib/lxc which breaks the
corner case of partly-writable systems like the Ubuntu phone.
+ This upload fixes this by changing the test to a simple readability one.
+
+ ## Test case
+ 1) Attempt to run lxc-start with /var/lib/lxc on a read-only filesystem but
/var/lib/lxc/<container> on a writable one.
+ 2) Confirm that the container now starts.
+
+ ## Regression potential
+ This upload only changes the check from read/write to read so the only
consequence of this should be more cases now being allowed. In the case where a
writable /var/lib/lxc is in fact absolutely required for the requested
operation, the operation will still fail, just a bit later and with a slightly
less clear error message (as was the case pre-2.0.6).
+
+
+ # Original report
+ As in topic. Since the 20161217 rootfs, after upgrade of lxc from
2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the
lxc-android-config service does not start - making the devices unbootable.
The syslog only states this:
Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting LXC Android Config and
Container Initialization...
Jan 3 10:50:30 ubuntu-phablet kernel: [ 5.790810] (3)[1:systemd]SLEEP_EN
= 0x1
Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting Light Display Manager...
Jan 3 10:50:30 ubuntu-phablet systemd-udevd[672]: Could not generate
persistent MAC address for ifb0: No such file or directory
Jan 3 10:50:30 ubuntu-phablet systemd-udevd[684]: Could not generate
persistent MAC address for ifb1: No such file or directory
Jan 3 10:50:30 ubuntu-phablet lxc-start[1220]: You lack access to
/var/lib/lxc
Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service:
Control process exited, code=exited status=1
Jan 3 10:50:30 ubuntu-phablet systemd[1]: Failed to start LXC Android Config
and Container Initialization.
Jan 3 10:50:30 ubuntu-phablet systemd[1]: Dependency failed for
force-mtp.service.
Jan 3 10:50:30 ubuntu-phablet systemd[1]: force-mtp.service: Job
force-mtp.service/start failed with result 'dependency'.
Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Unit
entered failed state.
Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Failed
with result 'exit-code'.
This makes all of our frieza and cooler devices useless for testing
purposes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653725
Title:
lxc-android-config not starting on ubuntu-touch/staging/* xenial-based
images after lxc upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1653725/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
