[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Launchpad Bug Tracker]

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

---
lxc (2.0.6-0ubuntu1~ubuntu16.04.2) xenial; urgency=medium

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

 -- Stéphane Graber   Wed, 04 Jan 2017 19:52:32
-0500

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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 Released
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/ 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Launchpad Bug Tracker]

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   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 Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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/ 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Stéphane Graber]

The verification of the Stable Release Update for lxc has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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/ 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Paul Larson]

I was able to test this on a m10 tablet. The fix seems to have gone
through to the cooler image I was trying to test - r13 in ubuntu-
touch/staging/bq-aquaris-pd.en, and now no longer hangs on install.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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 Committed
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/ 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Andy Whitcroft]

Hello Łukasz, or anyone else affected,

Accepted lxc into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/2.0.6-0ubuntu1~ubuntu16.10.2 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

** Changed in: lxc (Ubuntu Xenial)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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 Committed
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/ 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Łukasz Zemczak]

Thanks! Greatly appreciated guys. I'll kick a test xenial image as soon
as it's available.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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:
  In Progress
Status in lxc source package in Yakkety:
  In Progress
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/ 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Stéphane Graber]

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/ 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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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:
  In Progress
Status in lxc source package in Yakkety:
  In Progress
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/ 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: [

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 2.0.6-0ubuntu5

---
lxc (2.0.6-0ubuntu5) zesty; urgency=medium

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

 -- Stéphane Graber   Wed, 04 Jan 2017 14:11:45
-0500

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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:
  Triaged
Status in lxc source package in Yakkety:
  Triaged
Status in lxc source package in Zesty:
  Fix Released

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Stéphane Graber]

** Also affects: lxc (Ubuntu Zesty)
   Importance: High
 Assignee: Christian Brauner (cbrauner)
   Status: Fix Committed

** Also affects: lxc-android-config (Ubuntu Zesty)
   Importance: High
   Status: New

** Also affects: lxc (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: lxc-android-config (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: lxc (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: lxc-android-config (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** No longer affects: lxc-android-config (Ubuntu)

** Changed in: lxc (Ubuntu Yakkety)
   Status: New => Triaged

** Changed in: lxc (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: lxc (Ubuntu Yakkety)
   Importance: Undecided => High

** Changed in: lxc (Ubuntu Xenial)
   Importance: Undecided => High

** Also affects: lxc (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: lxc (Ubuntu Trusty)
   Status: New => Triaged

** Changed in: lxc (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: lxc (Ubuntu Xenial)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: lxc (Ubuntu Yakkety)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** No longer affects: lxc-android-config (Ubuntu Xenial)

** No longer affects: lxc-android-config (Ubuntu Yakkety)

** No longer affects: lxc-android-config (Ubuntu Zesty)

** Changed in: lxc (Ubuntu Trusty)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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 Committed
Status in lxc source package in Trusty:
  Triaged
Status in lxc source package in Xenial:
  Triaged
Status in lxc source package in Yakkety:
  Triaged
Status in lxc source package in Zesty:
  Fix Committed

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Christian Brauner]

** Changed in: lxc (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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 Committed
Status in lxc-android-config package in Ubuntu:
  New

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Christian Brauner]

** Changed in: lxc (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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:
  In Progress
Status in lxc-android-config package in Ubuntu:
  New

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Stéphane Graber]

Thanks. I think the problem is a newly introduced check for path
writeability which is harmless and in fact, potentially useful in just
about all cases but the weird Ubuntu Phone case where / is read-only,
confusing that check.

@Christian: Can you look into fixing this? I suspect we only really care
about being able to access the path, not so much about being able to
write to it. So it may make sense to change the check in all our tools
to simply check for read rights.

** Changed in: lxc (Ubuntu)
 Assignee: (unassigned) => Christian Brauner (cbrauner)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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:
  New
Status in lxc-android-config package in Ubuntu:
  New

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Łukasz Zemczak]

Looking at my krillin from the recovery, /var/lib/lxc looks like this:
Access: (0700/drwx--)  Uid: (0/root)   Gid: (0/root)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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:
  New
Status in lxc-android-config package in Ubuntu:
  New

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Stéphane Graber]

What are the permissions on /var/lib/lxc on such devices?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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:
  New
Status in lxc-android-config package in Ubuntu:
  New

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Jean-Baptiste Lallement]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

** Changed in: canonical-devices-system-image
Milestone: None => x1

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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:
  New
Status in lxc-android-config package in Ubuntu:
  New

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp