[Bug 1696402] Re: chroot configuration strictly depends on overlayfs

[Launchpad Bug Tracker]

This bug was fixed in the package click -
0.4.46+17.04.20170607.3-0ubuntu1

---------------
click (0.4.46+17.04.20170607.3-0ubuntu1) zesty; urgency=medium

  * Rename the python package this installs from click to click_package.
    (LP: #1693226)
  * Use the correct overlayfs module name for the chroot configuration.
    (LP: #1696402)

 -- Sergio Schvezov <sergio.schvezov at canonical.com>  Wed, 07 Jun 2017
18:53:16 +0000

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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to click in Ubuntu.
https://bugs.launchpad.net/bugs/1696402

Title:
  chroot configuration strictly depends on overlayfs

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Yakkety:
  Fix Released
Status in click source package in Zesty:
  Fix Released

Bug description:
  The kernel changed the module name from overlayfs to overlay, this
  needs to be taken into consideration when creating the chroot.

  [Impact]

  When trying to create the chroot, it fails like this:
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  E: 10mount: mount: wrong fs type, bad option, bad superblock on click-ubuntu-sdk-14.04-armhf,
  E: 10mount:        missing codepage or helper program, or other error
  E: 10mount:
  E: 10mount:        In some cases useful info is found in syslog - try
  E: 10mount:        dmesg | tail or so.
  E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot setup failed: stage=setup-start
  Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little DEB_BUILD_ARCH_ABI
  =base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
  ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf DEB_BUILD_ARCH_BITS=
  64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu DEB_TARGET_GNU_TYPE=arm-linux-gn
  ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm DEB_TARGET_ARCH_CPU=arm DEB_B
  UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little DEB_HOST_ARCH
  _CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
  ERROR

  This makes the autopkgtests fail, so it's blocking bug #1693226.

  [Test Case]

  Run the click autopkgtests.
  Check that there are no errors related to the wrong fs type.

  [Regression Potential]

  Fixing this for artful could make it fail in previous versions.
  However, this was found by the autopkgtests, so as long as the chroot tests pass in the other revisions the fix is correct.

  [Other Info]

  Click is now longer in active development. These tests were failing
  for a long time. In here we are just trying to make a small change on
  the name of the python module so it doesn't conflict with
  python3-click which is in active development and needed by snapcraft
  in bug #1692102.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1696402/+subscriptions