Thanks for the report.
I suspect subiquity may need to validate the serial value with what's
present in /dev/disk/by-id to ensure that curtin finds the same device
here.
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: curtin
Status: New =>
Netplan in disco has support for dhcp overrides[A], and this is
available in Disco now. Netplan 0.95 is being backported to bionic
which will include this functionality.
Once present, for cloud-init; we will need a few things.
1) cloudinit/sources/helpers/vmware/imc/config_nic.py current
@David generally running on OpenStack, instances already identify
themselves as OpenStack via DMI properties.
It sounds like you've an instance that has failed, please open a new bug
against cloud-init and in there if you could you please run:
$ cloud-init collect-logs
$ sudo sh -c 'cd
** Changed in: curtin (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817964
Title:
sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1
To
)
- - vmtests: network mtu fix-by bump to post 19.04 release
- - vmtest: Fix bug preventing explicit disabling of system_upgrade.
-
- -- Ryan Harper Wed, 27 Feb 2019 16:43:21
ing explicit disabling of system_upgrade.
+
+ -- Ryan Harper Wed, 27 Feb 2019 16:43:21 -0600
+
+ curtin (18.2-0ubuntu1) di
Public bug reported:
This will track an SRU of curtin back to Cosmic, Bionic and Xenial.
** Affects: curtin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => 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/1796917
Title:
cloud-init fails to run on latest cosmic minimal image
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://github.com/lxc/lxd/issues/4656
** Bug watch added: LXD bug tracker #4656
https://github.com/lxc/lxd/issues/4656
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779156
Title:
lxc 'delete'
This still fails on s390x. I've an LPAR with 18.04 and kernel
4.15.0-39-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565029
Title:
bcache doesn't register/recognize devices on s390x
To
ip addr show output:
https://paste.ubuntu.com/p/3gHdFzkrrQ/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815254
Title:
Azure multiple ips prevent access to metadata service
To manage
Public bug reported:
On an instance with a single interface and many private address, the
"primary" address, is not used for outgoing communication as the
source_ipaddr in packets; this prevents communicating with the IMDS
service.
Example metadata:
https://paste.ubuntu.com/p/2y2NBck6VJ/
** Also affects: cloud-init (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
This is still around. Scott wrote up a script to handle cleaning this
up.
https://gist.github.com/smoser/2c78cf54a1e22b6f05270bd3fead8a5c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779156
I've recreated an VM instance that uses the curtin config attached to
this bug.
I can recreate the additional registrations and delete/create of the
dname symlinks to the bcache devices by simply running 'udevadm trigger'
in a loop, and watching, dname directory with inotifywatch (inotifywait
-mr
Public bug reported:
1. # lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
2. # apt-cache policy sosreport
sosreport:
Installed: 3.6-1ubuntu0.18.04.2
Candidate: 3.6-1ubuntu0.18.04.2
Version table:
*** 3.6-1ubuntu0.18.04.2 500
500
After looking at the journal I can conclude a few things.
1) the bcache devices are found and rules run and change events emitted
fairly early during boot
[8.873909] ubuntu kernel: bcache: bch_journal_replay() journal replay done,
673 keys in 35 entries, seq 724
[8.875099] ubuntu
The committed fix did not completely resolve the issue.
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/362352
** Changed in: curtin
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Thanks for the confirmation.
The commit 81bf02ed was not sufficient to fix the issue. We'll be
landing an additional change to ensure that partitions on bcache devices
are recognized as partitions (not as actual bcache devices) as shutting
them down is handled differently.
--
You received this
I spent time looking at a udev debug log and I can confirm that during a
cold plug of the storage subsystem the bcache symlinks (kernel
(/dev/bcache/by-{uuid/label}, dname (/dev/disk/by-dname/)) will be
removed due to how the bcache driver works (it binds a backing and a
cache device) and when
On Mon, Jan 28, 2019 at 9:31 AM Gábor Mészáros
wrote:
> it's affecting one of our customer deployments, running on xenial. I'm
> curious if it's planned to release the fix on xenial, and when.
>
There's a related bug that's also being looked at to confirm if this
resolves issues for them.
Looking at the syslog and kern.log, the kernel has emitted the change
events which trigger the bcache rules, for all 12 devices, each time.
So what remains to understand is whether udevd ran the hook
(69-bcache.rules) and I see no reason it wouldn't.
% grep kernel.*register_bcache
Looking closer at Ubuntu releases:
--
Xenial
--
'zfs' meta package is present, and wants to install:
Note, selecting 'zfsutils-linux' instead of 'zfs'
The following package was automatically installed and is no longer required:
libfreetype6
Use 'sudo apt autoremove' to remove it.
The
Please attach curtin verbose logs and your curtin config.
https://discourse.maas.io/t/getting-curtin-debug-logs/169
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718699
Title:
curtin fails to
On Mon, Jan 14, 2019 at 1:55 PM Thiago Martins
wrote:
> @Ryan,
>
> The working XML file is attached here, with 2048 MB of RAM.
>
> NOTE: This XML was created using Virt-Manager, then, MaaS took it over
> after being "refreshed".
>
Thanks!
If you drop the section (which is what tells libvirt
@Thiago,
Can you attach your guest XML that's working successfully with 2048MB?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes
Public bug reported:
1. Disco
2. probert (0.0.14.2build1)
3. probert --network produces json output
4. probert --network dumps stack trace
root@rharper-d1:~# probert --network
Traceback (most recent call last):
File "/usr/bin/probert", line 62, in
main()
File "/usr/bin/probert", line
Building probert from git tip (HEAD =
8b56d73068ec1f293d3db3b0b44966ede9ed1c94) works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811279
Title:
probert --network throws stacktrace
To
Public bug reported:
1) # lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
2) # apt-cache policy netplan.io
netplan.io:
Installed: 0.36.3
Candidate: 0.40.1~18.04.3
Version table:
0.40.1~18.04.3 500
500 http://archive.ubuntu.com/ubuntu
One other oddity in the xml is the cgroup construction in the "bad"
case.
/machine
>
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This bug is believed to be fixed in cloud-init in version 18.5. 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
This bug is believed to be fixed in cloud-init in version 18.5. 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
This bug is believed to be fixed in cloud-init in version 18.5. 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
I confirmed that the underlying block devices (SAS, NVME) perform the same
on the 4.4 and 4.15 kernels. Roughly 170 IOP/s direct to the SAS device
and 570 IOP/s direct to the bcache infront of the SAS device. The block
scheduler has no effect, due to the use of O_DIRECT.
Public bug reported:
TestIscsiBasic and other Iscsi tests on Cosmic/Disco are failing in
vmtest on jenkins.
- looked some at curtin at iscsi failures cosmic, disco
- 604 was first fail like this.
cosmic 20181204
disco 20181129
** Changed in: curtin (Ubuntu)
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/1807216
Title:
Release 18.2
To manage notifications about this bug go to:
This bug is believed to be fixed in curtin in version 18.2. 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
This bug is believed to be fixed in curtin in version 18.2. 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
This bug is believed to be fixed in curtin in version 18.2. 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
This bug is believed to be fixed in curtin in version 18.2. 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
This bug is believed to be fixed in curtin in version 18.2. 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
This bug is believed to be fixed in curtin in version 18.2. 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
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/360217
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el when
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/360205
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807216
Title:
Release 18.2
To manage notifications
** Description changed:
This bug tracks the release of curtin 18.2
+
+
+ == Changelog ==
+ - Adjust helpers/common to edit GRUB_CMDLINE_LINUX_DEFAULT in place.
+(LP: #1527664)
+ - dname: persistent names based on serial or wwn (LP: #1735839)
+ - Fix bug in is_swap_device if a device
Public bug reported:
This bug tracks the release of curtin 18.2
== Changelog ==
- Adjust helpers/common to edit GRUB_CMDLINE_LINUX_DEFAULT in place.
(LP: #1527664)
- dname: persistent names based on serial or wwn (LP: #1735839)
- Fix bug in is_swap_device if a device was smaller than
On Tue, Dec 4, 2018 at 12:31 PM Mathieu Trudel-Lapierre <
mathieu...@gmail.com> wrote:
> The problem is that DEVTYPE is unreliable at best. Using the MAC of one
> of the member interfaces is fine, but only if you really know what
> you're doing.
>
> I think we're otherwise back to matching by
On Tue, Dec 4, 2018 at 9:31 AM Ryan Harper
wrote:
>
>
> On Tue, Dec 4, 2018 at 6:31 AM Dimitri John Ledkov
> wrote:
>
>> Using systemd 237-3ubuntu10.10
>>
>> Using:
>> [Match]
>> Name=ens3
>> [Network]
>> DHCP=ipv4
>> I
On Tue, Dec 4, 2018 at 10:30 AM Mathieu Trudel-Lapierre <
mathieu...@gmail.com> wrote:
> I disagree.
>
> We'd be working around a real design issue in systemd, rather that
>
While, I agree that having systemd-udev to apply MTU to devices is
less than ideal; I don't see having systemd or networkd
On Tue, Dec 4, 2018 at 6:31 AM Dimitri John Ledkov
wrote:
> Using systemd 237-3ubuntu10.10
>
> Using:
> [Match]
> Name=ens3
> [Network]
> DHCP=ipv4
> IPv6MTUBytes=1600
> [Link]
> MTUBytes=1800
> [DHCP]
> UseMTU=no
> RouteMetric=100
>
Do you put this in the same .network file or .link file?
--
Public bug reported:
When generating a network-config (v1), any routes should be provided under the
scope of a subnet.
For some renderers (eni) using the top-level routes in the config will
'accidentally' work due to ifupdown implementation, however, routes should
instead be scoped under a
Can you collect the following:
Backing device baseline (it's possible the underlying disks regressed
instead of the bcache layer). the same fio randrw test against the
underlying backing device with bcache disabled
And with bcache enabled on both setups before and after tuning:
1) grep -r .
*renderers*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805871
Title:
net renderers miss metric value in per-subnet routes
To manage notifications about this bug go to:
Note, this also affects the eni and sysconfig router as well.
** Summary changed:
- netplan renderer misses metric value in per-subnet routes
+ net renderers miss metric value in per-subnet routes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
When rendering a per-subnet route with a metric, the value is ignored
due to clobbering of the looping variable.
Consider this v1 input:
{
"version": 1,
Public bug reported:
When mounting a complex (raid, lvm) curtin should not use the filesystem
UUID in fstab as it may refer to a member of the array rather than the
filesystem itself. LVM snapshots also retain the same filesystem UUID
which may cause confusing results when rebooting, or possibly
Public bug reported:
dname for disks creates a symlink based on disk properties, like serial
or wwn. In the case that we have disks that are part of a multipath
scenario, then the dname will point to one of many kernel block devices
(sda, sdb, etc) which actually are the same disk.
The dname
v4.13 shows the same search_free stack as 4.14, but doesn't appear to be
fatal (it doesn't result in a hung process nor a block device that
cannot be wiped.
I suspect we've got a new upstream issue since 4.20 didn't fix things.
Re-running 4.20 to see if we had a stack trace, we don't NULL pointer
I also tested v4.15-rc5, which failed with the same stack trace. Then I
returned to 4.14 mainline, and got this one:
[ 953.659489] BUG: unable to handle kernel NULL pointer dereference at
0d40
[ 953.668707] IP:
It took a while, but v4.15-rc6 fails; so we need to move back a bit.
[ 2541.139904] bcache: bcache_device_free() bcache0 stopped
[ 2541.141848] BUG: unable to handle kernel NULL pointer dereference
at 0d38
[ 2541.143813] IP: search_free+0ex01-b6435-e1/5f0x40 [bcache]
[ 2541.145676]
On Mon, Nov 26, 2018 at 11:11 PM Jay Vosburgh
<1671...@bugs.launchpad.net> wrote:
>
> Regarding #2 from comment #19:
>
> As the defined range for the ipv6.mtu is from IPV6_MIN_MTU to the
> device's MTU, and the existing API returns an error if the ipv6.mtu is
> out of range, I think it's
The 4.15.0-39 kernel FAILs:
+ make-bcache -C /dev/sdb
Can't open dev /dev/sdb: Device or resource busy
+ exit 1
Successful runs: 24
root@ubuntu:~# [ 242.655013] INFO: task kworker/3:103:2610 blocked for more
than 120 seconds.
[ 242.665486] Not tainted 4.15.0-39-generic #43~lp1784665
[
It seems there are some limitations to what systemd will do with
IPv6BytesMTU.
1) if LinkLocalAddressing is not disabled, it will clobber any
IPv6BytesMTU value set.
[Network]
LinkLocalAddressing=ipv6
Address=10.10.10.10/24
IPv6MTUBytes=1470
This results in: /proc/sys/net/ipv6/conf//mtu having
4.20-rc3 also fails.
Successful runs: 95
root@ubuntu:~# [ 484.565298] INFO: task kworker/3:206:2091 blocked for more
than 120 seconds.
[ 484.566976] Not tainted 4.20.0-042000rc3-generic #201811182231
[ 484.568069] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
curtin-vmtest-proposed-x-artifacts.tar.xz
** Attachment added: "curtin-vmtest-proposed-x-artifacts.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1795712/+attachment/5213133/+files/curtin-vmtest-proposed-x-artifacts.tar.xz
--
You received this bug notification because you are
maas SRU proposed curtin sru manual testing on bionic artifacts
** Attachment added: "maas SRU proposed curtin sru manual testing on bionic
artifacts"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1795712/+attachment/5213137/+files/maas-SRU-proposed-curtin-sru-manual-bionic.tar.xz
curtin-vmtest-proposed-b-artifacts.tar.xz
** Attachment added: "curtin-vmtest-proposed-b-artifacts.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1795712/+attachment/5213135/+files/curtin-vmtest-proposed-b-artifacts.tar.xz
** Description changed:
== Begin SRU Template ==
curtin-vmtest-proposed-b-console log
** Attachment added: "curtin-vmtest-proposed-b-console log"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1795712/+attachment/5213134/+files/curtin-vmtest-proposed-b-console.log
--
You received this bug notification because you are a member of
curtin-vmtest-proposed-x-console log
** Attachment added: "curtin-vmtest-proposed-x-console log"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1795712/+attachment/5213131/+files/curtin-vmtest-proposed-x-console.log
--
You received this bug notification because you are a member of
OK, I can recreate.
The specific detail is that the bond macaddress matches one of the
physical interfaces and that the bond itself is down at the time of
the apply command.
# netplan apply --debug
WARK: matches: {'by-driver': {}, 'by-mac': {'00:16:3e:2c:4c:e5':
'eth0', '00:16:3e:c3:41:0a':
** Changed in: curtin
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el when partition table is GPT
To manage
On Wed, Oct 31, 2018 at 9:20 AM Scott Moser wrote:
>
> With regard to wiping all prep partitions...
> We do have code that does this in helpers/pt_prep. Ie, the non-storage
> config path does this.
> However, this is kind of a grey line here. If maas wants a partition wiped,
> then MAAS
On Tue, Oct 30, 2018 at 7:35 PM Lee Trager wrote:
>
> Every time I commission the PPC host we have in our CI I always get a
> GPT partitioning table using MAAS 2.4.2+. Looking through the source
> code it appears GPT is always set when creating a new partitioning
> table[1] and when generating
@Andres can you attatch the full config when you run this under beta3
with the MBR config?
>From what I can tell, the prep partition (/dev/sda1) is created fine,
but our wipe clears out the first and last 1M , it's an 8M partition.
This is a curtin bug as you've specified 'wipe: zero' which
Can you do a curtin verbose install with GPT and capture the logs from
that? I don't think mbr should matter, but we do use 'parted' for msdos
partition creation and 'sgdisk' for gpt so there could be some issue
going on here.
--
You received this bug notification because you are a member of
** Changed in: curtin
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el
To manage notifications about this bug go to:
Can you attach the curtin logs?
And do you have logs from the last previous successful run?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el
To manage
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el
To manage notifications
Could you re-apply the KEXEC config changes to the linux-kvm tree build?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799791
Title:
linux-kvm: please support kexec
To manage notifications about
The virtio configuration in this new kernel build changed, can it get
reverted to what the -kvm kernel currently has?
% grep VIRTIO /boot/config-*kvm
CONFIG_BLK_MQ_VIRTIO=y
CONFIG_HW_RANDOM_VIRTIO=y
CONFIG_NET_9P_VIRTIO=y
# CONFIG_RPMSG_VIRTIO is not set
CONFIG_SCSI_VIRTIO=y
CONFIG_VIRTIO=y
Does this fail with other releases? like trusty? I was wondering if
initrd size plays a factor here:
precise/hwe-t: 25M
trusty/hwe-x: 35M
xenial/ga: 39M
xenial/hwe:53M
xenial/edge: 53M
bionic/ga: 55M
cosmic/ga: 57M
That might be faster for you to test than for us to replicate
[0.943808] Unpacking initramfs...
[ 20.690329] Initramfs unpacking failed: junk in compressed archive
[ 20.703673] Freeing initrd memory: 56612K
Looks like the initrd was compromised, possibly a networking hiccup?
Can you confirm the checksums on the source and attempt to download the
URL
I'm unable to recreate with a daily bionic cloud-image on a bionic host
with the same versions.
% sudo apt install uvtool libvirt
% uvt-simplestreams-libvirt -vv sync --source
http://cloud-images.ubuntu.com/daily 'supported=True' arch=amd64 release=bionic
% uvt-kvm create --memory 2048 --cpu 1
The backing image:
/var/lib/libvirt/maas-images/e5d185a9-8ccb-4ca6-959a-bd8eff0ee184
What boot image is that? Can I get a copy of that from maas-images? or
how is it created?
On the node with the vm that fails, can you:
virsh start --console
Assuming it's a normal ubuntu image which has
And /var/log/libvirt/qemu/.log ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
kernel panic
To manage
Can you attach the guest xml and host kernel/qemu/libvirt packages?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
I suspect this reloading of profiles from the core snap has something to
do with the failure.
Oct 11 21:46:42 ubuntu systemd[1]: Mounting Mount unit for core, revision
5548...
Oct 11 21:46:42 ubuntu systemd[1]: Mounted Mount unit for core, revision 5548.
Oct 11 21:46:43 ubuntu snapd[745]:
Looking at this bug:
https://bugs.launchpad.net/snappy/+bug/1665808
As we're in the same maas ephemeral environment; though we get a
slightly different error. However the workaround included:
sudo apt-get install -yu apparmor-utils
sudo aa-complain /usr/lib/snapd/snap-confine
does allow lxd
The error I see is:
Run install hook of "lxd" snap if present
2018-10-10T20:06:30Z ERROR run hook "install": cannot create lock
directory /run/snapd/lock: Permission denied
$ ls -al /run | grep snapd
srw-rw-rw- 1 root root0 Oct 10 20:06 snapd-snap.socket
srw-rw-rw- 1 root root0 Oct 10
** Changed in: curtin
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796968
Title:
attempt to call string 'run_apt_upgrade' when testing proposed
To manage
Tested 0.40.1 from -proposed; things look good here.
root@b1:~# ls -al /etc/netplan/
total 9
drwxr-xr-x 2 root root 4 Oct 4 20:29 .
drwxr-xr-x 87 root root 175 Oct 2 06:36 ..
-rw-r--r-- 1 root root 381 Oct 1 14:53 50-cloud-init.yaml
-rw-r--r-- 1 root root 0 Oct 1 15:16 99-empty.yaml
This SRU has a regression:
https://bugs.launchpad.net/netplan/+bug/1795343
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793309
Title:
Backport netplan.io 0.40 to bionic
To manage notifications
Actually there needs to be changes to netplan to emit the correct
IPV6BytesMtu setting to networkd; and then cloud-init can emit the
correct netplan yaml for that. This feature is on the netplan roadmap
here:
https://trello.com/c/nIjLIRSG/6-support-ipv6-mtu-bytes-configuration
** Also
This may now be a cloud-init bug if the support is there since this is
a network-config v1 -> cloud-init renders netplan.
On Fri, Sep 28, 2018 at 9:12 AM Scott Moser wrote:
>
> Hm...
>
> Our tests show that this is not fixed in cosmic or bionic.
>
>
The comments are unclear what the actual sequence of failure is, but as
comment #4 mentions the tool will automatically listen to the default
port on *ALL* interfaces (0.0.0.0).
If you want to manually create one using the existing default port, you
have to delete the 0.0.0.0 entry before adding
Can we confirm which version of curtin you have installed?
** Changed in: curtin (Ubuntu Trusty)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791006
Title:
Public bug reported:
1) lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
2) $ apt-cache policy bluez
bluez:
Installed: 5.48-0ubuntu3.1
Candidate: 5.48-0ubuntu3.1
Version table:
*** 5.48-0ubuntu3.1 500
500 http://us.archive.ubuntu.com/ubuntu
On Wed, Aug 29, 2018 at 12:01 PM Joseph Salisbury
wrote:
>
> Thanks for digging up this additional information. I'll investigate
> further. While I do that, the v4.19-rc1 kernel is now out. It might be
> worthwhile to give that one a go, and see if the fix was already
> committed to mainline:
501 - 600 of 1546 matches
Mail list logo
