** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1618572
Title:
apt-key add fails in overlayfs
Status in linux
** No longer affects: cloud-init
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1618572
Title:
apt-key add fails in overlayfs
Status in linux package in Ubuntu:
Confirmed
Status in
This bug was fixed in the package linux - 4.4.0-38.57
---
linux (4.4.0-38.57) xenial; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1620658
* CIFS client: access problems after updating to kernel 4.4.0-29-generic
(LP: #1612135)
- Revert "UBUNTU: SAUCE:
I can confirm that trusty + linux-generic-lts-xenial from -proposed
looks good. I can now run sbuild with a tmpfs overlay, with
4.4.0-36-generic debconf would die with ESTALE during chroot setup.
--
You received this bug notification because you are a member of Kernel
Packages, which is
trusty + linux-virtual-lts-xenial looks good also.
ubuntu@sm-y1:~$ uname -r
4.4.0-38-generic
ubuntu@sm-y1:~$ dpkg -S /boot/vmlinuz-$(uname -r)
linux-image-4.4.0-38-generic: /boot/vmlinuz-4.4.0-38-generic
ubuntu@sm-y1:~$ grep overlay /proc/mounts
overlayroot / overlayfs
I booted a xenial guest as shown in my comment 10, added -proposed and
rebooted into overlayfs
ubuntu@sm-y1:~$ uname -r
4.4.0-38-generic
ubuntu@sm-y1:~$ dpkg -S /boot/vmlinuz-4.4.0-38-generic
linux-image-4.4.0-38-generic: /boot/vmlinuz-4.4.0-38-generic
$ grep overlayroot /proc/mounts
@andres
Please verify that the Xenial and Trusty+hwe-x in -proposed both fix
this problem that you are now seeing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1618572
Title:
apt-key
** Tags added: oil
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1618572
Title:
apt-key add fails in overlayfs
Status in cloud-init:
Confirmed
Status in linux package in Ubuntu:
Ok, I confirm the issue as per previous comment with Trusty+hwe-x
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1618572
Title:
apt-key add fails in overlayfs
Status in cloud-init:
Hi All,
I have come across what seems to be a related issue across the board. This is
not exactly the same way to reproduce but a simple 'apt-get update' shows this:
In Yakkety: http://pastebin.ubuntu.com/23149838/ on 4.4.0-9136-generic
In Xenial: http://pastebin.ubuntu.com/23149864/
Trusty
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1618572
Title:
apt-key add fails in overlayfs
Status in
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1618572
Title:
apt-key add fails in overlayfs
Status in cloud-init:
Confirmed
See: https://lists.ubuntu.com/archives/kernel-
team/2016-September/079879.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1618572
Title:
apt-key add fails in overlayfs
Status in
Ok looks like I have found the underlying cause, a bad port of an
upstream stable patch to our Ubuntu code base. I will send out the fix
shortly.
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
**
Adding a script which can reproduce the problem without the need of
having an active overlayfs-root. Not elegant but does the job.
** Attachment added: "test-ovlmv.sh"
https://bugs.launchpad.net/cloud-init/+bug/1618572/+attachment/4735399/+files/test-ovlmv.sh
--
You received this bug
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1618572
Title:
apt-key add fails in overlayfs
Status
Looking at a test VM the problematic files seem to be present in the
read-only base but then have been at some point deleted. So when the
rename/move is attempted there are whiteout softlinks present in the
overlay.
E.g.:
/media/root-ro/var/lib/cloud/data/status.json
** Attachment added: "atomic_write.py"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618572/+attachment/4733113/+files/atomic_write.py
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Here is some information on how to reproduce this.
I use uvt-kvm, just as an easy way to get a remote system to work with.
I assume that any boot of xenial or yakkety will reproduce the problem.
The failure shows itself in a couple different ways:
a.) original report: apt-key add my.pubkey
This
** Changed in: linux (Ubuntu)
Importance: Medium => High
** Tags removed: kernel-da-key
** Tags added: kernel-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1618572
Title:
20 matches
Mail list logo
