| 2015-09-08 02:29:38 |
宋文武 |
bug |
|
|
added bug |
| 2015-09-08 02:33:06 |
宋文武 |
information type |
Public |
Public Security |
|
| 2015-09-09 13:53:54 |
Marc Deslauriers |
information type |
Public Security |
Public |
|
| 2016-02-01 20:25:40 |
Scott Moser |
cloud-initramfs-tools (Ubuntu): status |
New |
Confirmed |
|
| 2016-02-01 20:25:44 |
Scott Moser |
cloud-initramfs-tools (Ubuntu): importance |
Undecided |
Medium |
|
| 2016-09-22 16:09:12 |
Scott Moser |
bug task added |
|
cloud-utils |
|
| 2016-09-22 16:09:32 |
Scott Moser |
bug task added |
|
cloud-utils (Ubuntu) |
|
| 2016-09-22 16:09:58 |
Scott Moser |
bug task added |
|
cloud-initramfs-tools |
|
| 2016-09-22 16:10:21 |
Scott Moser |
cloud-initramfs-tools: status |
New |
Confirmed |
|
| 2016-09-22 16:10:23 |
Scott Moser |
cloud-utils: status |
New |
Confirmed |
|
| 2016-09-22 16:10:26 |
Scott Moser |
cloud-utils (Ubuntu): status |
New |
Confirmed |
|
| 2016-09-22 16:10:30 |
Scott Moser |
cloud-initramfs-tools: importance |
Undecided |
Medium |
|
| 2016-09-22 16:10:32 |
Scott Moser |
cloud-utils: importance |
Undecided |
Medium |
|
| 2016-09-22 16:10:35 |
Scott Moser |
cloud-utils (Ubuntu): importance |
Undecided |
Medium |
|
| 2016-09-22 16:15:57 |
Scott Moser |
branch linked |
|
lp:~smoser/cloud-initramfs-tools/trunk.overlay |
|
| 2016-09-23 13:19:00 |
Robie Basak |
summary |
overlayroot doesn't work with vanilla kernel |
"overlayfs" no longer exists |
|
| 2016-09-23 13:19:32 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Server Team |
| 2016-09-23 13:57:20 |
Jon Grimm |
bug |
|
|
added subscriber Jon Grimm |
| 2016-09-23 17:57:27 |
Scott Moser |
description |
As mentioned in LP: #1411294, it's now called 'overlay' instead of 'overlayfs'.
Ubuntu had patched the kernel for compatibility.
(The original reporter is @~gpo-9.) |
As mentioned in LP: #1411294, it's now called 'overlay' instead of 'overlayfs'.
Ubuntu had patched the kernel for compatibility.
The Ubuntu kernels as of 4.8 (16.10 kernel) and possibly a bit before no longer have a overlayfs module either. Thus, this is now affecting yakkety.
(The original reporter is @~gpo-9.) |
|
| 2016-09-23 17:57:35 |
Scott Moser |
cloud-initramfs-tools: assignee |
|
Scott Moser (smoser) |
|
| 2016-09-23 17:57:38 |
Scott Moser |
cloud-initramfs-tools: status |
Confirmed |
In Progress |
|
| 2016-09-23 20:06:47 |
Jon Grimm |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-09-23 20:08:51 |
Scott Moser |
bug task added |
|
cloud-utils (Ubuntu Xenial) |
|
| 2016-09-23 20:08:51 |
Scott Moser |
bug task added |
|
cloud-initramfs-tools (Ubuntu Xenial) |
|
| 2016-09-23 20:09:10 |
Scott Moser |
cloud-initramfs-tools (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2016-09-23 20:09:13 |
Scott Moser |
cloud-initramfs-tools (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2016-09-23 20:09:16 |
Scott Moser |
cloud-utils (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2016-09-23 20:09:18 |
Scott Moser |
cloud-utils (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2016-09-23 21:03:59 |
Launchpad Janitor |
branch linked |
|
lp:cloud-initramfs-tools |
|
| 2016-09-23 21:04:21 |
Scott Moser |
cloud-initramfs-tools: status |
In Progress |
Fix Committed |
|
| 2016-09-24 18:57:20 |
Steve Langasek |
cloud-initramfs-tools (Ubuntu Yakkety): status |
Confirmed |
Fix Committed |
|
| 2016-09-24 18:57:23 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-09-24 18:57:25 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2016-09-24 18:57:31 |
Steve Langasek |
tags |
|
verification-needed |
|
| 2016-09-27 19:03:26 |
Scott Moser |
tags |
verification-needed |
verification-done |
|
| 2016-09-27 21:06:04 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/cloud-utils/trunk.lp1493188 |
|
| 2016-09-28 01:18:03 |
Launchpad Janitor |
branch linked |
|
lp:cloud-utils |
|
| 2016-09-28 01:26:31 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/yakkety/cloud-utils/pkg |
|
| 2016-09-28 09:15:35 |
Launchpad Janitor |
cloud-initramfs-tools (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2016-09-28 13:44:40 |
Scott Moser |
cloud-utils: status |
Confirmed |
Fix Committed |
|
| 2016-10-01 10:00:15 |
Launchpad Janitor |
cloud-utils (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2016-11-14 17:28:15 |
Scott Moser |
cloud-initramfs-tools: status |
Fix Committed |
Fix Released |
|
| 2016-11-29 01:32:50 |
Scott Moser |
cloud-initramfs-tools (Ubuntu Xenial): status |
Confirmed |
In Progress |
|
| 2016-11-29 22:17:07 |
Scott Moser |
description |
As mentioned in LP: #1411294, it's now called 'overlay' instead of 'overlayfs'.
Ubuntu had patched the kernel for compatibility.
The Ubuntu kernels as of 4.8 (16.10 kernel) and possibly a bit before no longer have a overlayfs module either. Thus, this is now affecting yakkety.
(The original reporter is @~gpo-9.) |
=== Begin SRU Template ===
[Impact]
The 16.10 kernel dropped a legacy kernel module alias that allowed usage of
the 'overlay' filesystem via name 'overlayfs'. This broke overlayroot as
it explicitly tried to to use 'overlayfs' by name in loading of modules and
also in entry in /etc/fstab.
Without this fix, overlayroot will simply not work on any upstream kernel
or Ubuntu kernel of 16.10 (yakkety) or later.
[Test Case]
Note, not applying proposed as shown in step 3 below will recreate failure.
1.) Start an instance of a cloud image.
2.) get a suitable 4.8 kernel
On 16.10 or later, this is already done. On 16.04, we currently need to
install the kernel team's PPA to get one.
$ sudo apt-add-repository -y ppa:canonical-kernel-team/ppa
$ sudo apt update -q && sudo apt install -y linux-virtual-hwe-16.04-edge </dev/null
3.) Enable proposed and install overlayroot to show fix.
$ rel=$(lsb_release -sc)
$ echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
$ sudo tee /etc/apt/sources.list.d/proposed.list
$ sudo apt update -qy && sudo apt install -qy overlayroot </dev/null
$ dpkg-query --show overlayroot
overlayroot 0.27ubuntu1.3
4.) Enable overlayroot and reboot
$ echo "overlayroot=tmpfs" | sudo tee /etc/overlayroot.local.conf
$ sudo reboot
5.) log back in and look around.
a.) check that 'overlayroot' is in /proc/mounts
$ awk '$1 == "overlayroot" { print $0 }' /proc/mounts
overlayroot / overlay rw,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_ 0 0
b.) check /run/initramfs/overlayroot.log
$ grep success /run/initramfs/overlayroot.log
[success]: configured root with 'tmpfs' using overlay per /dev/vda1/etc/overlayroot.local.conf
6.) try with recurse enabled
Assuming you're on the same system and in an overlayroot, to change the
file necessary, we use overlayroot-chroot.
$ echo overlayroot=tmpfs:recurse=1 | sudo overlayroot-chroot tee /etc/overlayroot.local.conf
$ sudo reboot
7.) log back in and look around.
On an image that has
[Regression Potential]
The most likely regression is just in failure for overlayroot to work.
That was the case 100% of the time on any kernel without 'overlayfs'
filesystem, so this can't really make things worse from that perspective.
Some of the code change was related to fixing another issue, with 'recurse'.
Testing recurse (where not just / is mounted as an overlayroot) is done
above
echo overlayroot=tmpfs:recurse=1 | sudo overlayroot-chroot tee /etc/overlayroot.local.conf
[Other Info]
The full overlayroot/init-bottom/overlayroot can be seen at [1]. The
specific change that fixed the issue is in revision 115 at [2].
[1] http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/overlayroot/scripts/init-bottom/overlayroot
[2] http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/revision/115
=== End SRU Template ===
As mentioned in LP: #1411294, it's now called 'overlay' instead of 'overlayfs'.
Ubuntu had patched the kernel for compatibility.
The Ubuntu kernels as of 4.8 (16.10 kernel) and possibly a bit before no longer have a overlayfs module either. Thus, this is now affecting yakkety.
(The original reporter is @~gpo-9.) |
|
| 2016-11-29 23:12:37 |
Chris Halse Rogers |
cloud-initramfs-tools (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-11-29 23:12:47 |
Chris Halse Rogers |
tags |
verification-done |
|
|
| 2016-11-29 23:12:49 |
Chris Halse Rogers |
tags |
|
verification-needed |
|
| 2016-11-30 15:33:24 |
Scott Moser |
description |
=== Begin SRU Template ===
[Impact]
The 16.10 kernel dropped a legacy kernel module alias that allowed usage of
the 'overlay' filesystem via name 'overlayfs'. This broke overlayroot as
it explicitly tried to to use 'overlayfs' by name in loading of modules and
also in entry in /etc/fstab.
Without this fix, overlayroot will simply not work on any upstream kernel
or Ubuntu kernel of 16.10 (yakkety) or later.
[Test Case]
Note, not applying proposed as shown in step 3 below will recreate failure.
1.) Start an instance of a cloud image.
2.) get a suitable 4.8 kernel
On 16.10 or later, this is already done. On 16.04, we currently need to
install the kernel team's PPA to get one.
$ sudo apt-add-repository -y ppa:canonical-kernel-team/ppa
$ sudo apt update -q && sudo apt install -y linux-virtual-hwe-16.04-edge </dev/null
3.) Enable proposed and install overlayroot to show fix.
$ rel=$(lsb_release -sc)
$ echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
$ sudo tee /etc/apt/sources.list.d/proposed.list
$ sudo apt update -qy && sudo apt install -qy overlayroot </dev/null
$ dpkg-query --show overlayroot
overlayroot 0.27ubuntu1.3
4.) Enable overlayroot and reboot
$ echo "overlayroot=tmpfs" | sudo tee /etc/overlayroot.local.conf
$ sudo reboot
5.) log back in and look around.
a.) check that 'overlayroot' is in /proc/mounts
$ awk '$1 == "overlayroot" { print $0 }' /proc/mounts
overlayroot / overlay rw,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_ 0 0
b.) check /run/initramfs/overlayroot.log
$ grep success /run/initramfs/overlayroot.log
[success]: configured root with 'tmpfs' using overlay per /dev/vda1/etc/overlayroot.local.conf
6.) try with recurse enabled
Assuming you're on the same system and in an overlayroot, to change the
file necessary, we use overlayroot-chroot.
$ echo overlayroot=tmpfs:recurse=1 | sudo overlayroot-chroot tee /etc/overlayroot.local.conf
$ sudo reboot
7.) log back in and look around.
On an image that has
[Regression Potential]
The most likely regression is just in failure for overlayroot to work.
That was the case 100% of the time on any kernel without 'overlayfs'
filesystem, so this can't really make things worse from that perspective.
Some of the code change was related to fixing another issue, with 'recurse'.
Testing recurse (where not just / is mounted as an overlayroot) is done
above
echo overlayroot=tmpfs:recurse=1 | sudo overlayroot-chroot tee /etc/overlayroot.local.conf
[Other Info]
The full overlayroot/init-bottom/overlayroot can be seen at [1]. The
specific change that fixed the issue is in revision 115 at [2].
[1] http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/overlayroot/scripts/init-bottom/overlayroot
[2] http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/revision/115
=== End SRU Template ===
As mentioned in LP: #1411294, it's now called 'overlay' instead of 'overlayfs'.
Ubuntu had patched the kernel for compatibility.
The Ubuntu kernels as of 4.8 (16.10 kernel) and possibly a bit before no longer have a overlayfs module either. Thus, this is now affecting yakkety.
(The original reporter is @~gpo-9.) |
=== Begin SRU Template ===
[Impact]
The 16.10 kernel dropped a legacy kernel module alias that allowed usage of
the 'overlay' filesystem via name 'overlayfs'. This broke overlayroot as
it explicitly tried to to use 'overlayfs' by name in loading of modules and
also in entry in /etc/fstab.
Without this fix, overlayroot will simply not work on any upstream kernel
or Ubuntu kernel of 16.10 (yakkety) or later.
[Test Case]
Note, not applying proposed as shown in step 3 below will recreate failure.
1.) Start an instance of a cloud image.
2.) get a suitable 4.8 kernel
On 16.10 or later, this is already done. On 16.04, we currently need to
install the kernel team's PPA to get one.
$ sudo apt-add-repository -y ppa:canonical-kernel-team/ppa
$ sudo apt update -q && sudo apt install -y linux-virtual-hwe-16.04-edge </dev/null
3.) Enable proposed and install overlayroot to show fix.
$ rel=$(lsb_release -sc)
$ echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
$ sudo tee /etc/apt/sources.list.d/proposed.list
$ sudo apt update -qy && sudo apt install -qy overlayroot </dev/null
$ dpkg-query --show overlayroot
overlayroot 0.27ubuntu1.3
4.) Enable overlayroot and reboot
# remove the cloud-init written mount options for /dev/vdb
# if we do not do this, then /mnt ends up not mounted due to ordering.
$ sudo sed -i.dist s/,x-systemd.requires=cloud-init.service,comment=cloudconfig// /etc/fstab
$ echo "overlayroot=tmpfs" | sudo tee /etc/overlayroot.local.conf
$ sudo reboot
5.) log back in and look around.
a.) check that 'overlayroot' is in /proc/mounts
$ awk '$1 == "overlayroot" { print $0 }' /proc/mounts
overlayroot / overlay rw,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_ 0 0
b.) check /run/initramfs/overlayroot.log
$ grep success /run/initramfs/overlayroot.log
[success]: configured root with 'tmpfs' using overlay per /dev/vda1/etc/overlayroot.local.conf
6.) try with recurse disabled
Assuming you're on the same system and in an overlayroot, to change the
file necessary, we use overlayroot-chroot.
$ echo overlayroot=tmpfs:recurse=0 | sudo overlayroot-chroot tee /etc/overlayroot.local.conf
$ sudo reboot
7.) log back in and look around.
This time the /mnt should not have overlay on it.
$ grep vdb /proc/mounts
/dev/vdb /mnt ext4 rw,relatime,data=ordered 0 0
$ grep overlay /proc/mounts
overlayroot / overlay rw,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_ 0 0
$ cat /etc/overlayroot.local.conf
overlayroot=tmpfs:recurse=0
[Regression Potential]
The most likely regression is just in failure for overlayroot to work.
That was the case 100% of the time on any kernel without 'overlayfs'
filesystem, so this can't really make things worse from that perspective.
Some of the code change was related to fixing another issue, with 'recurse'.
Testing recurse (where not just / is mounted as an overlayroot) is done
above
echo overlayroot=tmpfs:recurse=1 | sudo overlayroot-chroot tee /etc/overlayroot.local.conf
[Other Info]
The full overlayroot/init-bottom/overlayroot can be seen at [1]. The
specific change that fixed the issue is in revision 115 at [2].
[1] http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/overlayroot/scripts/init-bottom/overlayroot
[2] http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/revision/115
=== End SRU Template ===
As mentioned in LP: #1411294, it's now called 'overlay' instead of 'overlayfs'.
Ubuntu had patched the kernel for compatibility.
The Ubuntu kernels as of 4.8 (16.10 kernel) and possibly a bit before no longer have a overlayfs module either. Thus, this is now affecting yakkety.
(The original reporter is @~gpo-9.) |
|
| 2016-11-30 15:33:41 |
Scott Moser |
tags |
verification-needed |
verification-done |
|
| 2016-12-19 16:28:07 |
Launchpad Janitor |
cloud-initramfs-tools (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-12-19 16:28:24 |
Robie Basak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-10-19 16:21:05 |
Scott Moser |
cloud-utils: status |
Fix Committed |
Fix Released |
|
| 2020-09-03 20:46:32 |
Robert C Jennings |
bug |
|
|
added subscriber Robert C Jennings |
| 2020-09-04 16:31:59 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~chad.smith/ubuntu/+source/cloud-utils/+git/cloud-utils/+merge/390318 |
|
| 2020-09-14 14:48:58 |
Scott Moser |
description |
=== Begin SRU Template ===
[Impact]
The 16.10 kernel dropped a legacy kernel module alias that allowed usage of
the 'overlay' filesystem via name 'overlayfs'. This broke overlayroot as
it explicitly tried to to use 'overlayfs' by name in loading of modules and
also in entry in /etc/fstab.
Without this fix, overlayroot will simply not work on any upstream kernel
or Ubuntu kernel of 16.10 (yakkety) or later.
[Test Case]
Note, not applying proposed as shown in step 3 below will recreate failure.
1.) Start an instance of a cloud image.
2.) get a suitable 4.8 kernel
On 16.10 or later, this is already done. On 16.04, we currently need to
install the kernel team's PPA to get one.
$ sudo apt-add-repository -y ppa:canonical-kernel-team/ppa
$ sudo apt update -q && sudo apt install -y linux-virtual-hwe-16.04-edge </dev/null
3.) Enable proposed and install overlayroot to show fix.
$ rel=$(lsb_release -sc)
$ echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
$ sudo tee /etc/apt/sources.list.d/proposed.list
$ sudo apt update -qy && sudo apt install -qy overlayroot </dev/null
$ dpkg-query --show overlayroot
overlayroot 0.27ubuntu1.3
4.) Enable overlayroot and reboot
# remove the cloud-init written mount options for /dev/vdb
# if we do not do this, then /mnt ends up not mounted due to ordering.
$ sudo sed -i.dist s/,x-systemd.requires=cloud-init.service,comment=cloudconfig// /etc/fstab
$ echo "overlayroot=tmpfs" | sudo tee /etc/overlayroot.local.conf
$ sudo reboot
5.) log back in and look around.
a.) check that 'overlayroot' is in /proc/mounts
$ awk '$1 == "overlayroot" { print $0 }' /proc/mounts
overlayroot / overlay rw,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_ 0 0
b.) check /run/initramfs/overlayroot.log
$ grep success /run/initramfs/overlayroot.log
[success]: configured root with 'tmpfs' using overlay per /dev/vda1/etc/overlayroot.local.conf
6.) try with recurse disabled
Assuming you're on the same system and in an overlayroot, to change the
file necessary, we use overlayroot-chroot.
$ echo overlayroot=tmpfs:recurse=0 | sudo overlayroot-chroot tee /etc/overlayroot.local.conf
$ sudo reboot
7.) log back in and look around.
This time the /mnt should not have overlay on it.
$ grep vdb /proc/mounts
/dev/vdb /mnt ext4 rw,relatime,data=ordered 0 0
$ grep overlay /proc/mounts
overlayroot / overlay rw,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_ 0 0
$ cat /etc/overlayroot.local.conf
overlayroot=tmpfs:recurse=0
[Regression Potential]
The most likely regression is just in failure for overlayroot to work.
That was the case 100% of the time on any kernel without 'overlayfs'
filesystem, so this can't really make things worse from that perspective.
Some of the code change was related to fixing another issue, with 'recurse'.
Testing recurse (where not just / is mounted as an overlayroot) is done
above
echo overlayroot=tmpfs:recurse=1 | sudo overlayroot-chroot tee /etc/overlayroot.local.conf
[Other Info]
The full overlayroot/init-bottom/overlayroot can be seen at [1]. The
specific change that fixed the issue is in revision 115 at [2].
[1] http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/overlayroot/scripts/init-bottom/overlayroot
[2] http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/revision/115
=== End SRU Template ===
As mentioned in LP: #1411294, it's now called 'overlay' instead of 'overlayfs'.
Ubuntu had patched the kernel for compatibility.
The Ubuntu kernels as of 4.8 (16.10 kernel) and possibly a bit before no longer have a overlayfs module either. Thus, this is now affecting yakkety.
(The original reporter is @~gpo-9.) |
=== Begin SRU Template ===
[Impact]
The 16.10 kernel dropped a legacy kernel module alias that allowed usage of
the 'overlay' filesystem via name 'overlayfs'. This broke overlayroot as
it explicitly tried to to use 'overlayfs' by name in loading of modules and
also in entry in /etc/fstab.
Without this fix, overlayroot will simply not work on any upstream kernel
or Ubuntu kernel of 16.10 (yakkety) or later.
[Test Case]
Note, not applying proposed as shown in step 3 below will recreate failure.
1.) Start an instance of a cloud image.
2.) get a suitable 4.8 kernel
On 16.10 or later, this is already done. On 16.04, we currently need to
install the kernel team's PPA to get one.
$ sudo apt-add-repository -y ppa:canonical-kernel-team/ppa
$ sudo apt update -q && sudo apt install -y linux-virtual-hwe-16.04-edge </dev/null
3.) Enable proposed and install overlayroot to show fix.
$ rel=$(lsb_release -sc)
$ echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
$ sudo tee /etc/apt/sources.list.d/proposed.list
$ sudo apt update -qy && sudo apt install -qy overlayroot </dev/null
$ dpkg-query --show overlayroot
overlayroot 0.27ubuntu1.3
4.) Enable overlayroot and reboot
# remove the cloud-init written mount options for /dev/vdb
# if we do not do this, then /mnt ends up not mounted due to ordering.
$ sudo sed -i.dist s/,x-systemd.requires=cloud-init.service,comment=cloudconfig// /etc/fstab
$ echo "overlayroot=tmpfs" | sudo tee /etc/overlayroot.local.conf
$ sudo reboot
5.) log back in and look around.
a.) check that 'overlayroot' is in /proc/mounts
$ awk '$1 == "overlayroot" { print $0 }' /proc/mounts
overlayroot / overlay rw,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_ 0 0
b.) check /run/initramfs/overlayroot.log
$ grep success /run/initramfs/overlayroot.log
[success]: configured root with 'tmpfs' using overlay per /dev/vda1/etc/overlayroot.local.conf
6.) try with recurse disabled
Assuming you're on the same system and in an overlayroot, to change the
file necessary, we use overlayroot-chroot.
$ echo overlayroot=tmpfs:recurse=0 | sudo overlayroot-chroot tee /etc/overlayroot.local.conf
$ sudo reboot
7.) log back in and look around.
This time the /mnt should not have overlay on it.
$ grep vdb /proc/mounts
/dev/vdb /mnt ext4 rw,relatime,data=ordered 0 0
$ grep overlay /proc/mounts
overlayroot / overlay rw,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_ 0 0
$ cat /etc/overlayroot.local.conf
overlayroot=tmpfs:recurse=0
[Regression Potential]
The most likely regression is just in failure for overlayroot to work.
That was the case 100% of the time on any kernel without 'overlayfs'
filesystem, so this can't really make things worse from that perspective.
Some of the code change was related to fixing another issue, with 'recurse'.
Testing recurse (where not just / is mounted as an overlayroot) is done
above
echo overlayroot=tmpfs:recurse=1 | sudo overlayroot-chroot tee /etc/overlayroot.local.conf
[Other Info]
The full overlayroot/init-bottom/overlayroot can be seen at [1]. The
specific change that fixed the issue is in revision 115 at [2].
Related bugs:
* bug 1630274 adjusted the mechanism for determining if overlay was supported.
The change to do so is included in the xenial backport for this bug.
[1] http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/overlayroot/scripts/init-bottom/overlayroot
[2] http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/revision/115
=== End SRU Template ===
As mentioned in LP: #1411294, it's now called 'overlay' instead of 'overlayfs'.
Ubuntu had patched the kernel for compatibility.
The Ubuntu kernels as of 4.8 (16.10 kernel) and possibly a bit before no longer have a overlayfs module either. Thus, this is now affecting yakkety.
(The original reporter is @~gpo-9.) |
|
| 2020-09-16 16:37:10 |
Chad Smith |
cloud-initramfs-tools (Ubuntu): status |
Fix Released |
Fix Committed |
|
| 2020-09-16 16:37:14 |
Chad Smith |
cloud-initramfs-tools (Ubuntu): assignee |
|
Chad Smith (chad.smith) |
|
| 2020-09-16 16:37:21 |
Chad Smith |
cloud-initramfs-tools (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2020-09-16 16:37:24 |
Chad Smith |
cloud-initramfs-tools (Ubuntu): assignee |
Chad Smith (chad.smith) |
|
|
| 2020-09-16 16:37:57 |
Chad Smith |
cloud-utils (Ubuntu Xenial): assignee |
|
Chad Smith (chad.smith) |
|
| 2020-09-16 16:38:02 |
Chad Smith |
cloud-utils (Ubuntu Xenial): status |
Confirmed |
Fix Committed |
|
| 2020-09-29 16:46:46 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-09-29 16:46:54 |
Brian Murray |
tags |
verification-done |
verification-needed verification-needed-xenial |
|
| 2020-11-06 22:55:58 |
Chad Smith |
tags |
verification-needed verification-needed-xenial |
verification-done verification-done-xenial |
|
| 2020-11-09 03:14:41 |
Chad Smith |
tags |
verification-done verification-done-xenial |
verification-needed verification-needed-xenial |
|
| 2020-11-09 04:26:04 |
Chad Smith |
tags |
verification-needed verification-needed-xenial |
verification-done verification-done-xenial |
|
| 2020-11-09 17:27:01 |
Joshua Powers |
bug |
|
|
added subscriber Joshua Powers |
| 2020-11-16 12:52:06 |
Launchpad Janitor |
cloud-utils (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
