group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1653725@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package lxc - 2.0.6-0ubuntu1~ubuntu16.10.2

---------------
lxc (2.0.6-0ubuntu1~ubuntu16.10.2) yakkety; urgency=medium

  * Cherry-pick upstream bugfix:
    - 0003-tools-only-check-for-O_RDONLY.patch (LP: #1653725)

 -- Stéphane Graber <stgraber@xxxxxxxxxx>  Wed, 04 Jan 2017 19:51:22
-0500

** Changed in: lxc (Ubuntu Yakkety)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1653725

Title:
  lxc-android-config not starting on ubuntu-touch/staging/* xenial-based
  images after lxc upgrade

Status in Canonical System Image:
  Confirmed
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Triaged
Status in lxc source package in Xenial:
  Fix Committed
Status in lxc source package in Yakkety:
  Fix Released
Status in lxc source package in Zesty:
  Fix Released

Bug description:
  # 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1653725/+subscriptions