** Attachment added: "verify-log.txt: verification of xenial, zesty and artful
per test case in descriptiopn"
https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1728048/+attachment/5037314/+files/verify-log.txt
** Tags removed: verification-needed verification-needed-artful
** Attachment added: "verify-log.txt: verification of xenial, zesty and artful
per test case in descriptiopn"
https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1723183/+attachment/5037313/+files/verify-log.txt
** Tags removed: verification-needed verification-needed-artful
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-initramfs-tools (Ubuntu)
Importance: Undecided => Medium
--
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742479
Title:
Public bug reported:
If manual_cache_clean is set in an instance, then ds-identify will write
'# manual_cache_clean."'
to its config (/run/cloud-init/cloud.cfg).
cloud-init will try to load that file, and will WARN on it not being a
dict.
2018-01-10 15:45:57,282 - util.py[WARNING]: Failed
Well, I went looking to verify this. We got builds out of artful and
xenial today (20180109).
$ usquery maas3-daily --max=1 ftype=boot-initrd arch=amd64 subarch~ga- \
kpackage~generic \
--output-format='%(release)s %(version_name)s %(path)s %(item_url)s' |
while read rel ver path url; do
Well, I do not have 'Sticky keys' enabled now, and I doubt I ever did.
It really felt to me that the lock screen and "everything else" seemed to keep
independent state for shift (or caps lock possibly), and I happened to get them
out of sync.
I'm fine for this bug to expire, but figure I'd at
** Changed in: cloud-utils (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: cloud-utils (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: cloud-utils (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a
** Description changed:
Begin SRU Template ===
[Impact]
Squashfs images published by Ubuntu on http://cloud-images.ubuntu.com
end in '.squashfs' and on http://images.maas.io/ephemeral-v3/
the files are named 'squashfs'.
When you boot an initramfs with rooturl it would
** Changed in: maas-images
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737592
Title:
no zfs module in initramfs
To manage notifications about this bug
The fix that I've applied is to add the '2.5' to the list below.
1.) qemu-nbd --format=raw --connect $DEV $FILE
2.) wait until a 'pid' file appears in /sys/block/$BNAME/pid)
2.5) run 'blockdev --rereadpt' and 'udevadm settle'
3.) wait until $PART_PATH exists
4.) mount $PART_PATH to
** Changed in: cloud-utils (Ubuntu Xenial)
Status: Fix Released => Confirmed
** Changed in: cloud-utils (Ubuntu Bionic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
that had some noise:
=== modified file 'bin/mount-image-callback'
--- bin/mount-image-callback2018-01-03 15:44:47 +
+++ bin/mount-image-callback2018-01-04 18:08:43 +
@@ -284,6 +284,10 @@
debug 1 "connected $img_in ($fmt) ${rwmode} to $nbd. waiting for
device."
this actually seems to fix the issue and I cannot recreate with it in place.
http://paste.ubuntu.com/26320756/
I suspect what this is showing is that we were operating on nbd devices that
existed from a previous run.
--
You received this bug notification because you are a member of Ubuntu
I agree with Robie, yes we can fix lxd to modify file contents in the
guest more than it already does. But that is quite hacky. It would be
equivalent to having cloud-init set manage_etc_hosts to localhost on
lxd.
that does not solve the problem everywhere though.
--
You received this bug
artful and bionic are 'fix-released' as some magic in udev/systemd makes it
work.
It does seem though that maybe running blockdev makes sense there also though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On xenial only:
$ wget
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
$ cp -a xenial-server-cloudimg-amd64-disk1.img disk.img
$ sudo mount-image-callback -v disk.img truewaiting on pidfile for /dev/nbd0 in
/sys/block/nbd0/pid
connected
the recreate script demonstrates failure on xenial, artful and bionic in a VM.
xenial needs a change to mount-image-callback to run 'blockdev' on the nbd
device. i'm not actually sure how i've never seen that bug before.
with the change in place, all 3 can be made to show the issue. artful
and
** Attachment added: "recreate script v2 (support running on xenial)"
https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1741096/+attachment/5031105/+files/test-1741096
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attaching a recreate script with loop included.
It should run correctly just about anywhere, with mount-image-callback
installed.
must be root.
to run with a different/modified mount-image-callback, just add it to your
PATH.
** Attachment added: "recreate script"
marked as cloud-images as that is where the change for nss-myhostname
would be made (i think).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741277
Title:
Not all platforms running cloud-init end
fwiw, its sudo that is causing the roundtrip.
you can certainly come up with reasons to pay a round trip. the infrastructure
then can make changes and each system magically picks them up. its the reason
we don't ship /etc/hosts files around anymore.
all that said, this issue can definitely be
I considered the fact that maybe the partitioned image that test-mic was
creating was somehow invalid. To test that, I modifed mount-image-callback
to set the mount device in MOUNT_DEV, and then did:
cp "$pt1" /tmp/part1.img
cp "$pt2" /tmp/part2.img
mount-image-callback --read-only --part=1
http://paste.ubuntu.com/26315423/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741096
Title:
test-mic can fail / writes to qemu-nbd device do not persist
To manage notifications about this bug
heres another log of /var/log/syslog. http://paste.ubuntu.com/26315330/
I'm not certain if the order of entries in /varlog/syslog can be 100% trusted
or not.
If it can be, then we definitely see oddities.
* mount-image-callback definitly unmounts before running qemu-nbd --disconnect.
* the
I've played a bit. Attached patch here has logging done with logger in
an effort to serialize things.
Then, I have 'go.sh' (see below) that just loops over running test-mic until it
fails.
Then you get bookend messages in /var/log/syslog. I've collected a fail here.
** Patch added:
go.sh looks like
#!/bin/sh
[ "$(id -u)" = "0" ] || { echo "not root" 1>&2; exit 1; }
i=0
while true; do
logger --tag=xtest-mic-$i "start xtest-mic-$i"
echo -n .
{
read up idle out.log 2>&1
logger --tag=xtest-mic-$i "end xtest-mic-$i $r"
[ $r -eq 0 ] || { echo; echo "failed
run like
$ sudo PATH=$PWD/bin:$PATH ./go.sh
failed xtest-mic-3
smoser@milhouse:~/src/cloud-utils/trunk$ cat out.log
19536.67
cat: data.txt: No such file or directory
GPT:
== expected on 1 ==
partition 1
foo1
== found on 1 ==
partition 1
data.txt: cat failed rc=1
19543.86
1
** Attachment
Public bug reported:
### Whats going on here?
## test-mic is a test of mount-image-callback in cloud-image-utils
##
## It populates some disk images and then uses mic to write some
## files (info.txt and data.txt)
## then calls mic again to verify the files are there.
##
## the failure i'm
** Description changed:
Begin SRU Template ===
[Impact]
Squashfs images published by Ubuntu on http://cloud-images.ubuntu.com
end in '.squashfs' and on http://images.maas.io/ephemeral-v3/
the files are named 'squashfs'.
When you boot an initramfs with rooturl it would
** Description changed:
Begin SRU Template
[Impact]
Overlayfs allows a user to mount the root filesystem read-only
and put an overlay over it.
It handles mounting of the root filesystem in the initramfs, and updates
/etc/fstab to account for non-root filesystems and
** Description changed:
Begin SRU Template ===
- [Impact]
+ [Impact]
Squashfs images published by Ubuntu on http://cloud-images.ubuntu.com
end in '.squashfs' and on http://images.maas.io/ephemeral-v3/
the files are named 'squashfs'.
When you boot an initramfs with rooturl it
** Tags removed: verification-donezesty
** Tags added: verification-done-zesty
** Tags removed: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is
** Description changed:
+ Begin SRU Template
+ [Impact]
+ Overlayfs allows a user to mount the root filesystem read-only
+ and put an overlay over it.
+ It handles mounting of the root filesystem in the initramfs, and updates
+ /etc/fstab to account for non-root filesystems and
** Summary changed:
- squashfs url matching is to strict
+ squashfs url matching is too strict
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728048
Title:
squashfs url matching is too strict
To
I'm going to un-tag this bug for sru, as I'm planning on sru-ing a the second
fix.
The change in this bug resulted in the following change in the rendered
/etc/fstab:
- LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults 0 0
+ LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0
I'm going to un-tag this bug for sru, as I'm planning on sru-ing a the second
fix.
The change in this bug resulted in the following change in the rendered
/etc/fstab:
- LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults 0 0
+ LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722668
Title:
Azure: bouncing of network device/publishing of hostname fails on
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/335470
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722668
Title:
Azure: bouncing of network
I just marked xenial explicitly as fixed here. The fix is in all
supported ubuntu releases > trusty.
** Also affects: btrfs-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: btrfs-tools (Ubuntu)
Status: New => Fix Released
** Changed in: btrfs-tools
Dimitri,
What is the fix that you put in? I assume it was to systemd ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734167
Title:
DNS doesn't work in no-cloud as launched by ubuntu
To manage
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
+ Begin SRU Template
+ [Impact]
+ Overlayfs allows a user to mount the root filesystem read-only
+ and put an overlay over it.
+ It handles mounting of the root filesystem in the initramfs, and updates
+ /etc/fstab to account for non-root filesystems and
** Description changed:
+ Begin SRU Template ===
+ [Impact]
+ Squashfs images published by Ubuntu on http://cloud-images.ubuntu.com
+ end in '.squashfs' and on http://images.maas.io/ephemeral-v3/
+ the files are named 'squashfs'.
+
+ When you boot an initramfs with rooturl it would
** Also affects: cloud-initramfs-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-initramfs-tools (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: cloud-initramfs-tools (Ubuntu Zesty)
Importance: Undecided
Status: New
801 - 900 of 11836 matches
Mail list logo
