Public bug reported:

With the switch from out of tree overlayfs to in-tree overlay, sbuild-
launchpad-chroot must be updated to properly detect both of those,
otherwise users end up with a "directory" type chroot that doesn't use
unioning and so looses a few of the useful features provided by this
tool.

# Rationale
New kernel doesn't have a "overlayfs" module, it's now called "overlay".
Both names should be used in the detection code.

# Test case
 - Before upgrade
   - sbuild-launchpad-chroot create -n test -s xenial -a amd64
   - Check that /etc/schroot/chroot.d/test doesn't contain "union-type"
   - sbuild-launchpad-chroot remove -n test
 - After upgrade
   - sbuild-launchpad-chroot create -n test -s xenial -a amd64
   - Check that /etc/schroot/chroot.d/test contains "union-type"
   - sbuild-launchpad-chroot remove -n test

# Regression potential
Not much, this won't affect anyone who has existing chroots, it only affects 
new chroots and re-introduces the behavior that people have been expecting up 
until the time where the overlayfs driver was removed from the kernel.

** Affects: sbuild-launchpad-chroot (Ubuntu)
     Importance: Medium
     Assignee: Stéphane Graber (stgraber)
         Status: Triaged

** Affects: sbuild-launchpad-chroot (Ubuntu Yakkety)
     Importance: Medium
     Assignee: Stéphane Graber (stgraber)
         Status: Triaged

** Affects: sbuild-launchpad-chroot (Ubuntu Zesty)
     Importance: Medium
     Assignee: Stéphane Graber (stgraber)
         Status: Triaged

** Also affects: sbuild-launchpad-chroot (Ubuntu Yakkety)
   Importance: Undecided
       Status: New

** Also affects: sbuild-launchpad-chroot (Ubuntu Zesty)
   Importance: Undecided
       Status: New

** Also affects: sbuild-launchpad-chroot (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: sbuild-launchpad-chroot (Ubuntu Xenial)
       Status: New => Triaged

** Changed in: sbuild-launchpad-chroot (Ubuntu Yakkety)
       Status: New => Triaged

** Changed in: sbuild-launchpad-chroot (Ubuntu Zesty)
       Status: New => Triaged

** Changed in: sbuild-launchpad-chroot (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: sbuild-launchpad-chroot (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: sbuild-launchpad-chroot (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: sbuild-launchpad-chroot (Ubuntu Xenial)
     Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: sbuild-launchpad-chroot (Ubuntu Yakkety)
     Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: sbuild-launchpad-chroot (Ubuntu Zesty)
     Assignee: (unassigned) => Stéphane Graber (stgraber)

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

Title:
  sbuild-launchpad-chroot doesn't detect current overlayfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sbuild-launchpad-chroot/+bug/1652117/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to