sbuild-launchpad-chroot doesn't detect current overlayfs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sbuild-launchpad-chroot (Ubuntu) |
Fix Released
|
Medium
|
Stéphane Graber | ||
Yakkety |
Fix Released
|
Medium
|
Stéphane Graber | ||
Zesty |
Fix Released
|
Medium
|
Stéphane Graber |
Bug Description
With the switch from out of tree overlayfs to in-tree overlay, sbuild-
# 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-
- Check that /etc/schroot/
- sbuild-
- After upgrade
- sbuild-
- Check that /etc/schroot/
- sbuild-
# 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.
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: | nobody → Stéphane Graber (stgraber) |
Changed in sbuild-launchpad-chroot (Ubuntu Yakkety): | |
assignee: | nobody → Stéphane Graber (stgraber) |
Changed in sbuild-launchpad-chroot (Ubuntu Zesty): | |
assignee: | nobody → Stéphane Graber (stgraber) |
no longer affects: | sbuild-launchpad-chroot (Ubuntu Xenial) |
This probably should be SRUed to xenial at some point too, but right now xenial's schroot appears to be lacking support for the "overlay" union-type.