** Tags removed: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750031
Title:
scary/unexpected output in adduser and deluser
To manage notifications about this bug go to:
cloud-images 20180222 do *not* have cloud-initramfs-dyn-netconf or ubuntu-meta
at 1.411.
That is expected as it just wasnt fixed at the time of the build.
Anything newer than 20180222 should have this fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Getting this fixed in cloud-init is tricky.
In ifupdown (/etc/network/interfaces) world, we just took the "global dns"
entries and put them on the loopback device (lo). Since that device would
always be brought up, and never really brought down, it served its purpose.
That is what Ryan tried
>From the install log you can see that we install grub2 at
>2.02~beta2-36ubuntu3.17.
..
Unpacking grub2-common (2.02~beta2-36ubuntu3.17)
..
'dpkg-reconfigure grub-pc' and 'grub-install /dev/vda' are run
And also:
run-parts: executing /etc/kernel/postinst.d/zz-update-grub
Hi.
I've confirmed this fix by using curtin's "vmtest" test harness.
I've applied the attached patch to curtin at 82622f129b.
The patch does:
a.) remove the work arounds we had in place to make zfs root work on xenial.
b.) enable proposed
Then I've run an install of a system that does a
** Attachment added: "first boot console log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1527727/+attachment/5060822/+files/boot-serial.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "installation console log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1527727/+attachment/5060821/+files/install-serial.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've removed the verification-failed-xenial tag.
The problem reported in bug 1750732 may be related to a grub upgrade, but
surely is not related to this specific grub upgrade.
Please see the changes
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750732
Title:
grub package will change the boot order for MaaS deployed system
To manage notifications about this bug
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Released
--
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Released
--
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
I think the issue is:
a.) there is no default locale set in the subiquity installed system.
b.) python3 subprocess is doing a 'decode' for each argument in the
command list.
python2 default encoding *is* supposed to be based on the environment [1],
but python3 default encoding is not. python3 is
I dont think I really agree with this fix.
Adding 'After=local-fs.target' essentially pushes cloud-init to have that same
dependency, which it does not have. We don't really want cloud-init to have to
wait for local-fs.target.
For example see bug 1691489 (and related fallout bug 1717477).
If
It seems to me that each of maas, cloud-init and netplan could do better
here.
a.) maas declares 'global' nameserver/dns info.
this is kind of silly in that such a thing doesn't really exist.
maas has the information necessary to declare the nameserver on the
device with the address that has a
Marked as 'fix-committed' as I pushed to the seed branch.
I need to wait for some server side things to happen before I can upload
ubuntu-meta,
but any ubuntu-meta > 1.411 should have this fix.
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Fix Committed
** Changed in: ubuntu-meta
MAAS is sending a "global" nameserver, and a ethernet device on a bridge.
cloud-init is rendering that nameserver onto the ethernet device rather
than on the bridge or as a "global" entry.
$ cat my.yaml
network:
config: [
{"id": "enp0s25", "type": "physical", "name": "enp0s25",
Hi,
cloud-init has never updated resolv.conf directly.
/etc/resolv.conf in 16.04 is managed via resolvconf through
/etc/network/interfaces.
/etc/resolv.conf in 18.04 is managed via systemd-resolve (netplan ->
systemd-networkd -> systemd-resolve).
Can you provide the content of:
Public bug reported:
I (smoser) removed cloud-initramfs-dyn-netconf from ubuntu-server meta
package. That package provides functionality needed by MAAS and cause bug
1748875. Under that bug we re-added cloud-initramfs-dyn-netconf to the
initramfs that MAAS publishes.
We subsequently saw
Based on Brian's comment, marking wont-fix.
Not the end of the world, just less than ideal.
** Changed in: apport (Ubuntu Xenial)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
adduser and deluser are now printing to stderr 'sent invalidate(passwd)' and
'sent invalidate(group)'.
These are confusing at best and new in bionic.
See below. They do not seem harmful, but not wonderful.
smoser@ubuntu1:~$ sudo adduser guest
Adding user `guest' ...
sent
** Description changed:
1. $ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
2. $ apt-cache policy linux-image-`uname -r`
linux-image-4.13.0-16-generic:
- Installed: 4.13.0-16.19
- Candidate: 4.13.0-16.19
- Version table:
- *** 4.13.0-16.19 500
- 500
Ryan forwarded this to bcache-tools upstream on github.
https://github.com/koverstreet/bcache-tools/pull/1
** Description changed:
[Impact]
* Current users of bcache devices may encounter unreliable device
numbering as the Linux kernel does not guarantee that bcache
minor
** Attachment added: "verification log of xenial"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1581416/+attachment/5056654/+files/verify-1581416-xenial.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
- * Current users of bcache devices may encounter unreliable device
-numbering as the Linux kernel does not guarantee that bcache
-minor numbers are assigned to the same devices at each boot.
-Users who may have used /dev/bcacheN in paths to a
Tetsuo,
Thanks for the info. Removing 'apparmor=0' isn't an option right now both
because MAAS doesn't let you control that and because it is there to work
around other bugs (originally bug 1677336).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: maas (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749246
Title:
[2.3] Image download hardlinks the hwe-*-edge as the generic kernel
** Also affects: bcache-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bcache-tools (Ubuntu)
Status: New => Confirmed
** Changed in: bcache-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: bcache-tools (Ubuntu)
Status: Confirmed => In
Hi. This issue should be fixed in 4.30.
the changelog entry is:
* debian/pollinate.postinst:
- don't try to chown a dir to the user, potentially before the user exists
** Changed in: pollinate (Ubuntu)
Importance: Undecided => High
** Changed in: pollinate (Ubuntu)
Status: New
** Description changed:
OS:Ubuntu Mate 18.04 daily
apport-collect won't work because it's say that i am missing "You need
to run 'sudo apt-get install python3-apport' for apport-collect to
work." But "python3-apport" its installed
work.
apolihron@apolihron-desktop:~$ sudo
** Summary changed:
- apport-collect requires python2 or suggests installing already-installed
python3-apport
+ apport-collect requires python2
** Changed in: apport (Ubuntu)
Status: New => Fix Released
** Changed in: apport (Ubuntu)
Importance: Undecided => Medium
** Also affects:
It happens within 3 minutes of system boot into 4.13 kernel.
2 systems reproduced this. You're lucky to be able to log in before it crashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749221
I've just now got a node back into rescue mode.
then just a simple 'reboot' from an ssh session and it will reboot, pxeboot,
and then be power'd off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, in order to fix an issue where nodes were "stuck" in "exiting
rescue mode", I restarted region and rackd. Next time I put into rescue
mode it booted 4.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
attached is a console log of the system booting while it is in 'Rescue
mode' on the web UI.
** Changed in: maas
Status: Incomplete => New
** Attachment added: "console log of system boot while it is in 'Rescue mode'"
Public bug reported:
When I boot a node into 'rescue mode', it is booting into 4.13 kernel.
the maas has no minimum kernel set (globally) nor does the node.
$ maas crash-and-burn maas get-config name=default_min_hwe_kernel
""
$ maas crash-and-burn nodes read
[
...
"min_hwe_kernel": "",
Yes, it pxe booted, maas passed it IP address, rooturl
i did not (could not) check, but i assume maas passed in its cloud-config
'power_state'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1749221 ***
https://bugs.launchpad.net/bugs/1749221
The collected files here were from a different system.
** Attachment removed: "console log of bibarel and kernel trace"
Public bug reported:
I'm booted into a 16.04 maas rescue environment.
$ apport-collect
You need to run 'sudo apt-get install python-apport' for apport-collect to work.
running the provided command will get me a python2 stack.
python3-apport is already installed.
python3 should be used.
I
Public bug reported:
Booted under maas in rescue mode system console has the attached failure.
First bit is
[ 440.196466] BUG: unable to handle kernel paging request at
fe3ed820
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-generic (not installed)
ProcVersionSignature:
** Attachment added: "full console log into kernel trace"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749221/+attachment/5054369/+files/bibarel-crash-full-console.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Booted under maas in rescue mode system console has the attached failure.
First bit is
[ 440.196466] BUG: unable to handle kernel paging request at
fe3ed820
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-generic (not installed)
ProcVersionSignature:
Public bug reported:
I acquired a node, and put it into rescue mode.
I used the system a bit, and then it hit a kernel crash.
I did a hard reset via ipmi, and expected the system to come back up into
rescue mode.
Instead, the system booted and powered off.
On the console I saw:
[ 55.390845]
Public bug reported:
As ubuntu goes forward, net-tools is looking to be dropped.
Byobu currently depends on net-tools. That code should be replaced by
iproute2.
Related bugs:
* bug 925145: cloud-init Use ip instead of ifconfig and route
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package:
** Description changed:
== Begin SRU Template ==
[Impact]
This release provides both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. Notable changes for Ubuntu stable releases are:
+ -
I just ran into this today:
Setting up avahi-utils (0.7-3.1ubuntu1) ...
dpkg: cycle found while processing triggers:
chain of packages whose triggers are or may be responsible:
gnome-menus -> ufw
packages' pending triggers which are or may be unresolvable:
gnome-menus:
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/337475
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748354
Title:
ec2: systemctl restart
Hi, thanks for the good bug report.
I believe that you should be able to override the datasource provided config
in user-data. Try providing user-data as:
#cloud-config
ssh_pwauth: False
Please let me know if that works for you or not. I do realize that its
unfortunate to have to do that.
Stretch, can you please attach /var/log/cloud-init.log ?
Better would be to attach output of 'cloud-init collect-logs'
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735331
Title:
ec2:
** Description changed:
=== Begin SRU Template ===
[Impact]
Packaging changes caused grub-legacy-ec2 package to install its
kernel post-install and post-rm hooks into
-/etc/kernel/kernel/postinst.d
-/etc/kernel/kernel/postrm.d
+ /etc/kernel/kernel/postinst.d
+
I'm going to mark this 'wont fix' in cloud-initramfs-tools.
and take away cloud-init.
** No longer affects: cloud-init (Ubuntu)
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi, is this still relevant witih 16.04 or 18.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1188756
Title:
No graphical screen and no sound when overlayroot is active
To manage notifications
I'm going to mark this 'wont fix' please feel free to argue if its still
valid and set it back to Confirmed, but please make sure it is still
relevant on 16.04 and recent xen configurations.
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: Confirmed => Won't Fix
--
You received
Hi, is this still relevant with 16.04 and currently supported maas?
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, Is this still relevant with 16.04 or 18.04 ?
** Changed in: cloud-initramfs-tools (Ubuntu)
Importance: Medium => Wishlist
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi, is this still relevant witih 16.04 or 18.04?
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: New => Incomplete
** Changed in: cloud-initramfs-tools (Ubuntu)
Importance: Medium => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: cloud-initramfs-tools (Ubuntu)
Importance: Low => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1499853
Title:
overlayroot should support multiple lowerdir mounts
To
** Changed in: cloud-initramfs-tools (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720036
Title:
Initramfs configuration hook overlayroot sets CRYPTSETUP=1
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Triaged
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in:
** Changed in: cloud-init (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667735
Title:
cloud-init doesn't retry metadata lookups and hangs
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ Packaging changes caused grub-legacy-ec2 package to install its
+ kernel post-install and post-rm hooks into
+/etc/kernel/kernel/postinst.d
+/etc/kernel/kernel/postrm.d
+ rather than
+/etc/kernel/postinst.d
+
** Also affects: cloud-init (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance:
Francis,
Currently nothing is disabling the warning.
You can disable it safely as instructed in the message or by
rm -Rf /var/lib/cloud/warnings
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674861
Verified. on fresh xenial guest in openstack. See below.
$ lsb_release -sc
xenial
$ cat /etc/cloud/build.info
build_name: server
serial: 20180126
$ wget "$url" --progress=dot:giga -O xenial-server-cloudimg-
amd64-disk1.img
$ dpkg -S `which mount-image-callback`
cloud-image-utils:
I've just pushed a commit to cloud-init's upstream packaging for this at [1]
It should get pulled into the next ubuntu Stable Release of cloud-init.
A "cloud-init daily" ppa build should occur tonight and arrive at [2].
You can test that PPA with:
sudo add-apt-repository
** Changed in: curtin
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/1744038
Title:
curtin fails to configure archive in trusty MAAS deployment
To manage
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ mount-image-callback fails to mount images that are qcow2 formatted.
+
+ This function in mount-image-callback works in other Ubuntu releases
+ but not on xenial. The function does succeed some times, but is
+ brittle.
+
+ The
** Description changed:
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
I'm dropping the qemu-nbd. i'm not certain that there is actually
anything that was wrong there.
** No longer affects: qemu (Ubuntu)
--
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:
** Changed in: zfs-linux (Ubuntu)
Status: New => Fix Released
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: zfs-linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: zfs-linux (Ubuntu Xenial)
Status: New =>
I've uploaded just now grub2 (2.02~beta2-36ubuntu3.17) and
grub2-signed (1.66.17) to the xenial SRU queue.
There are currently versions in xenial-proposed for these packages with
fixes for bug 722950 and bug 1708245.
Hopefully after those uploads clear xenial-proposed the fix for this bug will
I've marked this 'Fix Released' in xenial as Ubuntu's package in xenial
at 0.6.5.6-0ubuntu3 which has the fix at [1] as mentioned in comment 29.
Further, my experience with our zfs work in curtin indicates that it is
fixed.
--
Public bug reported:
fresh bionic instance on Azure, I noticed on the console
WARNING Dhcp client is not running.
In fact there is a dhcp client running it is just not isc-dhcp.
See below.
$ systemctl status walinuxagent --no-pager --full
● walinuxagent.service - Azure Linux Agent
Loaded:
** Changed in: cloud-init
Importance: Undecided => Medium
** 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/1707037
Title:
GCE
** Changed in: cloud-init
Importance: Undecided => Medium
** 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/1707039
Title:
GCE
** Changed in: cloud-init
Importance: Undecided => Medium
** 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/1707033
Title:
GCE
A fix for this bug is being SRU to Ubuntu 16.04 and 17.10 under bug
1743618.
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu)
Status: New => Fix Released
** Changed in: curtin (Ubuntu)
Importance: Undecided => Medium
--
You
A fix for this bug is being SRU to Ubuntu 16.04 and 17.10 under bug
1743618.
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu)
Status: New => Fix Released
** Changed in: curtin (Ubuntu)
Importance: Undecided => Medium
--
You
A fix for this bug is being SRU to Ubuntu 16.04 and 17.10 under bug
1743618.
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu)
Status: New => Fix Released
** Changed in: curtin (Ubuntu)
Importance: Undecided => Medium
--
You
A fix for this bug is being SRU to Ubuntu 16.04 and 17.10 under bug
1743618.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744038
Title:
curtin fails to configure archive in trusty MAAS deployment
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu)
Status: New => Confirmed
** Changed in: curtin (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm wondering if you possibly were hitting bug 1744038.
MAAS can declare (and actually, i think *does* declare) both old format
configuration of apt and new format configuration. That would cover
trusty and later. If you declare both, though, there is code in cloud-
init that insists they are
More info that the 13th was the right date.
https://lists.ubuntu.com/archives/ubuntu-announce/2018-January/000227.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743936
Title:
claims zesty is
from the dupe i just filed.
distro info data is wrong for zesty. EOL should be 2018-01-13 not
2018-01-25.
https://wiki.ubuntu.com/Releases says 2018-01-13. And reality shows that
zesty is no longer available in archive.ubuntu.com
http://paste.ubuntu.com/26411461/
--
You received this bug
*** This bug is a duplicate of bug 1743936 ***
https://bugs.launchpad.net/bugs/1743936
** This bug has been marked a duplicate of bug 1743936
claims zesty is supported
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
distro info data is wrong for zesty. EOL should be 2018-01-13 not
2018-01-25.
+
+ https://wiki.ubuntu.com/Releases says 2018-01-13. And reality shows that
+ zesty is no longer available in archive.ubuntu.com
+
+ http://paste.ubuntu.com/26411461/
+
ProblemType:
Public bug reported:
distro info data is wrong for zesty. EOL should be 2018-01-13 not
2018-01-25.
https://wiki.ubuntu.com/Releases says 2018-01-13. And reality shows that
zesty is no longer available in archive.ubuntu.com
http://paste.ubuntu.com/26411461/
ProblemType: Bug
DistroRelease:
Marked as fix-released.
I tested today with 20180115.1 image from bionic.
wget http://cloud-images.ubuntu.com/bionic/20180115.1/bionic-server-
cloudimg-amd64.img -O bionic-server-cloudimg-amd64.img
url="https://smoser.brickies.net/ubuntu/nocloud/;
qemu-system-x86_64 -enable-kvm -m 768 \
-net
@Nate,
there is some suggestions about that in bug 1433761.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1089389
Title:
juju bootstrap fail behind a proxy when a gpg key must be imported
To
closer.
still need artful to be updated. but seems like next build would do that.
$ for f in *-initrd; do echo == $f ==; lsinitramfs $f | grep zfs; done
== artful-20180109-initrd ==
== bionic-20180115.1-initrd ==
lib/modules/4.13.0-25-generic/kernel/zfs
Kryzsztof,
I'm curious why you would use the .vhd file. Is there something
specific that you wanted from it *other* than the format of the disk
image?
If not, then you most likely can just grab the .img file (qcow2) and
use qemu-img to convert it to vhd.
I do realize that converting a disk
Hi,
I'm coming here from bug 1730744.
Is this bug expected to be fixed for 18.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block for much
** Summary changed:
- sru curtin 20180116 - 17.1-5-gfae8ffb1
+ sru curtin 2018-01-16 - 17.1-5-gfae8ffb1
** Summary changed:
- sru curtin 2018-01-16 - 17.1-5-gfae8ffb1
+ sru curtin 2018-01-16 - 17.1-6-g8b145067
** No longer affects: curtin (Ubuntu)
** Changed in: curtin (Ubuntu Xenial)
** Summary changed:
- sru curtin 2018-01016 - 17.1-5-gfae8ffb1
+ sru curtin 20180116 - 17.1-5-gfae8ffb1
** Also affects: curtin (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this
** Tags removed: verification-needed
** Tags added: 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/1735046
Title:
mkfs.btrfs error checking mount status of loop device backing_file
701 - 800 of 11836 matches
Mail list logo
