*** This bug is a duplicate of bug 1841321 ***
https://bugs.launchpad.net/bugs/1841321
Hello,
Thanks for taking the time to file a bug and help make Ubuntu better.
This looks like a duplicate of bug #1841321
This should be fixed in the latest snap of subiquity, you can test out
the latest
@Dan Thanks for reading closer that I did.
** Changed in: curtin (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847257
Title:
In Eoan, link_in_boot
*** This bug is a duplicate of bug 1841697 ***
https://bugs.launchpad.net/bugs/1841697
Thanks for filing the bug. This is fixed in ew the latest cloud-init in
19.10; in the short-term, you can workaround the failure by removing
/etc/cloud/cloud.cfg/d/90_dpkg.cfg and optionally re-running
This was an release-branch only issue; it did not affect upstream cloud-
init.
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Eoan)
** Changed in: curtin (Ubuntu)
Importance: Undecided => Medium
** Changed in: curtin (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847058
Title:
MAAS
I'm marking the curtin task invalid; it's likely that the subiquity
task is invalid as well; it appears to be something with the live image
build. If you find out that there's something wrong with curtin itself,
please re-open the curtin task and mark it New.
** Changed in: curtin (Ubuntu)
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840928
Title:
FFE: include changes to enable ssh access sooner during boot
To manage
Curtin hasn't made any changes here; but I suspect the workload on the
target machine which created the thin lv's has left metadata that curtin
doesn't yet know how to clear. As a workaround for now, you can use the
MAAS disk-erasure to clear the volumes before attempting to deploy.
the UUID is already bound to the device mapper device:
% cat fstab
UUID=50e5271d-665f-4edb-a023-e2f744679751 / ext4 defaults 0 0
UUID=5d9f777b-c102-4d8f-b4f5-56195c4ae21c /home ext4 defaults,nofail 0 0
% cat ls_al_byuuid
total 0
drwxr-xr-x 2 root root 120 Oct 8 14:37 .
drwxr-xr-x 8 root root
@thinktwo nothing missing, the fix is entirely in systemd. Please open
a new bug and put in your steps so we can track down what's going wrong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815254
What's the bad path if we don't specify the mpath device name?
** Changed in: curtin (Ubuntu)
Importance: Undecided => Medium
** Changed in: curtin (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
commit 08bf6ff7c6dd919bb420f610d2b427ce161d6096
Author: Dimitri John Ledkov
Date: Thu Apr 11 18:29:03 2019 +
Setup kernel-img.conf like base-installer/live-installer did.
LP: #1534162
Should we remove it entirely, or only on target_release E and newer?
Or can we tell
The example config and docs don't mention VTOC; the mention of MBR and
DOS is not correct at all. The curtin dasd code, checks for vtoc; which
currently will fail schema validation; I'll put up a branch to fix docs
and schema for curtin right now.
** Changed in: curtin (Ubuntu)
Importance:
Actually, this isn't right; For DASD, we need to specify 'vtoc'.
storage:
version: 1
config:
*** This bug is a duplicate of bug 1840524 ***
https://bugs.launchpad.net/bugs/1840524
2019-10-03 17:52:22,159 curtin:1156 Validation error:
'eui.ace42e00954452d62ee4ac01' is not valid under any of the given
schemas in
{
"id": "disk-nvme0n1",
"path": "/dev/nvme0n1",
"serial":
This can be reproduced in an LXD Eoan container:
lxc launch ubuntu-daily:eoan e1
lxc exec e1
cat > /etc/netplan/50-cloud-init.yaml << EOF
network:
version: 2
ethernets:
eth0:
dhcp4: false
mtu: 1500
vlans:
eth0.2667:
id: 2667
@Dan/Chad I suggest we skip-by this bug number on the eoan vlan test
case;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846232
Title:
vmtests: test_ip_output failing in vlan tests on eoan
To
This looks to be related to networkd:
https://github.com/systemd/systemd/pull/12574/commits
Which is automatically added 4 bytes to base interface MTU, even though
we're explicitly setting mtu to 1500 on base interface and vlan.
** Also affects: systemd (Ubuntu)
Importance: Undecided
The _real_ concern is:
do you get the _same_ ID_SERIAL value with and without the sg3-utils-
udev package installed?
Can you compare: /dev/disk/by-id/*https://bugs.launchpad.net/bugs/1833618
Title:
failing to deploy Ubuntu Disco
To manage notifications about this bug go to:
@Rafael,
the critical path would be to check the output from:
udevadm info --query=all --name=/dev/sd[cd] | grep -i serial
ID_SERIAL does not get set on Disco where we have sg3-utils package
install, which adds the s3g-utils-udev package, and includes the rules
file 55-scsi-sg3_id.rules.
This
** Changed in: curtin (Ubuntu)
Status: New => 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/1845611
Title:
Install fails on ppc64el (unrecognized partition table: 'mac')
To
This needs fixing in curtin.
** Also 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.
https://bugs.launchpad.net/bugs/1845611
Title:
Install fails on ppc64el
2019-09-26 21:11:56,148 block-discover:96 probing failed restricted=True
Traceback (most recent call last):
File
"/snap/subiquity/1196/lib/python3.6/site-packages/subiquity/controllers/filesystem.py",
line 93, in _probed
self.model.load_probe_data(storage)
File
Thanks! I can confirm this fixes the issue we found:
root@ubuntu:/# apt-cache policy efivar
efivar:
Installed: 37-2ubuntu2
Candidate: 37-2ubuntu2
Version table:
*** 37-2ubuntu2 500
500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844320
Title:
efibootmgr -v UiAppCould not parse device path
To manage notifications about this bug go to:
A quick hack shows that if we export after unmount. I'd like to
understand if we we need/should use import -f, however, curtin can now
ensure it exports pools it has created at the end of install.
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Changed in: curtin
Curtin hasn't ever run zfs export on the pools; so either something else
did this previously, or it wasn't a requirement.
I can see if adding a zfs export on the pool works around the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
On Eoan, efibootmgr -v output fails with error "UiAppCound not parse
device path"; this succeeds on Disco and Bionic.
root@ubuntu:/# efivar --name 8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot
--print
GUID: 8be4df61-93ca-11d2-aa0d-00e098032b8c
Name: "Boot"
Attributes:
On Thu, Sep 12, 2019 at 5:00 PM Patricia Domingues <
patricia.doming...@canonical.com> wrote:
> Ryan,
> Sorry for delay, we had a BMC issue and it required a manual intervention
> to fix it.
> I've tested Eoan in that machine and it also fails, it doens't show the
> same curtin error as Disco
MAAS QA Results for Disco
** Attachment added: "sru-proposed-cloudinit-disco.zip"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1841099/+attachment/5287795/+files/sru-proposed-cloudinit-disco.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs,
MAAS QA Results for Bionic
** Attachment added: "sru-proposed-cloudinit-bionic.zip"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1841099/+attachment/5287794/+files/sru-proposed-cloudinit-bionic.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs,
MAAS QA Results for Xenial
** Attachment added: "sru-proposed-cloudinit-xenial.zip"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1841099/+attachment/5287793/+files/sru-proposed-cloudinit-xenial.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs,
On Tue, Sep 3, 2019 at 9:31 AM Andrew Cloke
wrote:
> @Ryan, do you know if the Server team looks after sg3-utils-udev, or
> should we be chasing the Foundations team to look into this?
>
Not quite sure, I'll follow up.
Also, Patricia, can you try an Eoan install to see if this is maybe fix in
It's actually the sg3-utils-udev package which provides new udev rules
to inquery about scsi device's ID_SERIAL.
** Also affects: sg3-utils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for filing a bug. This is something that cloud-init should
consider providing in the package.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a
err, on Eoan, I used ipv6-mtu 6000.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671951
Title:
networkd should allow configuring IPV6 MTU
To manage notifications about this bug go to:
See comment #20; ipv6 mtu is 1280 -> DEVICE_MTU.
I'm testing something in the middle now.
On Eoan with:
network:
version: 2
ethernets:
ens3:
addresses: [10.5.0.16/16]
gateway4: 10.5.0.1
dhcp4: false
match:
I tested with your single-file approach and that also fails. Note that
bionic now has systemd 237, so maybe something is missing (or regressed)
?
$ apt-cache policy systemd
systemd:
Installed: 237-3ubuntu10.26
Candidate: 237-3ubuntu10.26
Version table:
*** 237-3ubuntu10.26 500
500
I launched a bionic image on serverstack, updated the netplan.io to
proposed, modified the network config to set ipv6-mtu to 6000 and
rebooted.
root@b-test-ipv6-mtu:~# apt-cache policy netplan.io
netplan.io:
Installed: 0.98-0ubuntu1~18.04.1
Candidate: 0.98-0ubuntu1~18.04.1
Version table:
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => 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/1841697
Title:
Upgrade corrupts 90_dpkg.cfg
To manage notifications about
As a workaround, you can ensure that you have a space before and after
the list:
datasource_list: [ ConfigDrive, None ]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841697
Title:
Upgrade
The cloud-init.config dpkg parser has this sed line which doesn't like
the brackets without spaces:
sed -n -e /^datasource_list:/!d -e s/datasource_list:[ \[]*// -e s,
\]$,, -e p /etc/cloud/cloud.cfg.d/90_dpkg.cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks for filing a bug.
I can recreate this using your config file. It appears to be related to
the shell parsing of that value, if you leave a space before the start
of the list and the end like so:
diff -u /etc/cloud/cloud.cfg.d/90_dpkg.cfg.bad
/etc/cloud/cloud.cfg.d/90_dpkg.cfg
---
Thanks for filing the bug.
Can you provide the netplan you used?
Also, if possible, could you run:
mkdir /etc/systemd/system/systemd-networkd.service.d/
echo -e "[Service]\nEnvironment=SYSTEMD_LOG_LEVEL=debug" >
/etc/systemd/system/systemd-networkd.service.d/10-debug.conf
Reboot and then
On Mon, Aug 26, 2019 at 4:05 AM Tobias Koch <1834...@bugs.launchpad.net>
wrote:
> > (Odds are that whatever causes it to be recreated later in boot would be
> > blocked by cloud-init waiting.)
>
> But that's not happening. The instance does boot normally, the only
> service degraded is cloud-init
** Changed in: curtin (Ubuntu)
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/1841321
Title:
Curtin Fails to Validate Storage Config with Crucial P1 NVMe
Thanks for filing the bug.
A "quickfix" would involve getting into the installer shell, manually
patching the curtin python source on the instance, and then re-running
the install. I've not poked around inside the installer so I'm not sure
where the the subiquity snap keeps curtin. If you do
On Fri, Aug 23, 2019 at 10:21 AM Dan Watkins
wrote:
> Looking at the comment timestamps, Dan probably didn't see my comment,
> but to reiterate: all the events we expect to be processed _are_
> processed, the issue is that when they are processed they don't always
> end up with the correct
On Fri, Aug 23, 2019 at 10:00 AM Dan Streetman
wrote:
> > Dan had put a udevadm settle in this spot like so
> >
> > def get_size(filename)
> >util.subp(['udevadm', 'settle'])
> >os.open()
>
> if you know you've just changed (e.g.) /dev/sda, possibly its kernel-
> generated udev
Overnight testing of the revised deployment configuration has no errors,
200 runs completed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784665
Title:
bcache: bch_allocator_thread(): hung task
The sequence is:
exec growpart
exec sgdisk --info # read-only
exec sgdisk --pretend # read-only
exec sgdisk --backup # read-only copy
# modification of disk starts
exec sgdisk --move-second-header \
--delete=PART \
--new=PART \
--typecode
Also, I had some confusion earlier about what kernel I was testing.
apt-cache policy shows the package version 4.15.0.59.61, however that's
the meta package, the actual kernel is the .66 one.
# dpkg --list | grep linux-image
ii linux-image-4.15.0-59-generic 4.15.0-59.66
Finally, I did verify xenial proposed with our original test. I had
over 100 installs with no issue.
@Jason
Have you had any runs on Xenial or Disco? (or do you not test those)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've adjusted my bionic testing with the simpler configuration. I
cannot reproduce the failure so far. I'll leave this running over
night.
I suspect there's something else going on baremetal that we can't
reproduce in a VM.
--
You received this bug notification because you are a member of
Public bug reported:
This FFE covers changes to cloud-init which will enable a configured
instance to re-order portions of startup to allow ssh access to an
instance sooner.
The set of changes will include
- updated systemd cloud-init-generator to trigger platform specific systemd
unit
I've verified that disco-proposed linux-virtual kernel succeeds our
test-case (curtin-nvme). I've 50 installs with no issue.
root@ubuntu:~# apt-cache policy linux-virtual
linux-virtual:
Installed: 5.0.0.26.27
Candidate: 5.0.0.26.27
Version table:
*** 5.0.0.26.27 500
500
Public bug reported:
1) # lsb_release -rd
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
2) root@e1:~# apt-cache policy secureboot-db
secureboot-db:
Installed: 1.5
Candidate: 1.5
Version table:
*** 1.5 500
500 http://archive.ubuntu.com/ubuntu
I've verified that bionic-proposed linux-virtual kernel succeeds our
test-case (curtin-nvme). I've 50 installs with no issue.
ubuntu@ubuntu:~$ apt-cache policy linux-virtual
linux-virtual:
Installed: (none)
Candidate: 4.15.0.59.61
Version table:
4.15.0.59.61 500
500
On Thu, Aug 15, 2019 at 11:56 AM Sherry Hurwitz <1839...@bugs.launchpad.net>
wrote:
> It is similar in that a property is missing so the dictionary errors out
> but in this case the error is in probert in the storage.py in the
> blockdev probe. when all the devices in in the block subsystem are
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: Expired => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832381
This looks related:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839529
Title:
Live-server installation fails to install on
On Mon, Aug 5, 2019 at 1:19 PM Ryan Harper
wrote:
>
>
> On Mon, Aug 5, 2019 at 8:01 AM Andrea Righi
> wrote:
>
>> Ryan, I've uploaded a new test kernel with the fix mentioned in the
>> comment before:
>>
>> https://kernel.ubuntu.com/~arighi/LP-17962
On Mon, Aug 5, 2019 at 8:01 AM Andrea Righi
wrote:
> Ryan, I've uploaded a new test kernel with the fix mentioned in the
> comment before:
>
> https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-56.62~lp1796292+4/
>
> I've performed over 100 installations using curtin-nvme.sh
> (install_count =
Trying the first kernel without the change event sauce also fails:
[ 532.823594] bcache: run_cache_set() invalidating existing data
[ 532.828876] bcache: register_cache() registered cache device nvme0n1p2
[ 532.869716] bcache: register_bdev() registered backing device vda1
[ 532.994355]
I tried the +3 kernel first, and I got 3 installs and then this hang:
[ 549.828710] bcache: run_cache_set() invalidating existing data
[ 549.836485] bcache: register_cache() registered cache device nvme1n1p2
[ 549.937486] bcache: register_bdev() registered backing device vdg
[ 550.018855]
** Changed in: curtin (Ubuntu)
Status: Fix Committed => 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/1772618
Title:
btrfs-tools is dead, long live btrfs-progs
To manage
Reproducer script
** Attachment added: "curtin-nvme.sh"
https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Thu, Aug 1, 2019 at 10:15 AM Andrea Righi
wrote:
> Thanks Ryan, this is very interesting:
>
> [ 259.411486] bcache: register_bcache() error /dev/vdg: device already
> registered (emitting change event)
> [ 259.537070] bcache: register_bcache() error /dev/vdg: device already
> registered
Public bug reported:
Installing into a chroot without /run mounted, grub's os-prober calls
into lvs for details and it waits a very long time. I believe this is
fixed upstream:
https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=3ebce8dbd2d9afc031e0737f8feed796ec7a8df9
1. Eoan
2. lvm2
ubuntu@ubuntu:~$ uname -r
4.15.0-56-generic
ubuntu@ubuntu:~$ cat /proc/version
Linux version 4.15.0-56-generic (arighi@kathleen) (gcc version 7.4.0 (Ubuntu
7.4.0-1ubuntu1~18.04.1)) #62~lp1796292 SMP Thu Aug 1 07:45:21 UTC 2019
This failed on the second install while running bcache-super-show
On Mon, Jul 29, 2019 at 11:35 AM Richard Laager
wrote:
> What was the expected behavior from your perspective?
>
> The ZFS utilities are useless without a ZFS kernel module. It seems to
> me that this is working fine, and installing the ZFS utilities in this
> environment doesn’t make sense.
>
Public bug reported:
1. Eoan
2. http://archive.ubuntu.com/ubuntu eoan/main amd64 zfs-initramfs amd64
0.8.1-1ubuntu7 [23.1 kB]
3. ZFS rootfs rpool is mounted at boot
4. Booting an image with a rootfs rpool:
[0.00] Linux version 5.2.0-8-generic (buildd@lgw01-amd64-015) (gcc
version
Public bug reported:
In MAAS (ephemeral environment) or LXD where no kernel package is
currently installed; installing the zfsutils-linux package will pull in
a kernel package from the zfs-modules dependency.
1) # lsb_release -rd
Description:Ubuntu Eoan Ermine (development branch)
Release:
I think the question is; why don't we log to syslog by default. I think
historically cloud-init is run in many OSes which may or maynot have
syslog capabilities so it defaults to writing it's own log directly.
At least for local testing, it's easy enough to update
** Also 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.
https://bugs.launchpad.net/bugs/1837217
Title:
[partition reuse] can't create new partitions in an already
** Changed in: curtin
Status: New => 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/1819034
Title:
[FFE] add s390x dasd, zkey and additional dm-crypt support fixes
To manage
I'm marking the cloud-init task invalid; I don't believe cloud-init did
anything wrong; but please set the task back to New if you have new
information showing that cloud-init didn't do something quite right.
** Changed in: cloud-init
Status: New => Invalid
--
You received this bug
Hi, I don't believe this is a cloud-init bug. Cloud-init wrote the two
certificate files requested.
2018-05-02 08:55:00,913 - stages.py[DEBUG]: Running module ca-certs () with
frequency once-per-instance
2018-05-02 08:55:00,914 - handlers.py[DEBUG]: start:
init-network/config-ca-certs:
This bug is believed to be fixed in curtin in version 19.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: In Progress => Fix Released
--
You received this bug notification because you are a member of
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => 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/1833192
Title:
Disco manual verification that installing curtin from -proposed does not
pull in probert package.
** Attachment added: "disco-manual-verification.txt"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1831757/+attachment/5277194/+files/disco-manual-verification.txt
** Tags removed:
Cosmic manual verification that installing curtin from -proposed does
not pull in probert package.
** Attachment added: "cosmic-manual-verification.txt"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1831757/+attachment/5277193/+files/cosmic-manual-verification.txt
--
You received
Bionic manual verification that installing curtin from -proposed does
not pull in probert package.
** Attachment added: "bionic-manual-verification.txt"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1831757/+attachment/5277192/+files/bionic-manual-verification.txt
--
You received
Xenial manual verification that installing curtin from -proposed does
not pull in probert package.
** Attachment added: "xenial-manual-verification.txt"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1831757/+attachment/5277191/+files/xenial-manual-verification.txt
--
You received
The newer kernel went about 16 runs and then popped this:
[ 2137.810559] md: md0: resync done.
[ 2296.795633] INFO: task python3:11639 blocked for more than 120 seconds.
[ 2296.800320] Tainted: P O 4.15.0-55-generic
#60+lp1796292+1
[ 2296.805097] "echo 0 >
Andrea, thanks for the updated kernels.
On the first one, I got 23 installs before I ran into an issue; I'll
test the newer kernel next.
https://paste.ubuntu.com/p/2B4Kk3wbvQ/
[ 5436.870482] BUG: unable to handle kernel NULL pointer dereference at
09b8
[ 5436.873374] IP:
Disco manual verification that installing curtin from -proposed does not
pull in probert package.
** Attachment added: "Disco manual verification that installing curtin from
-proposed does not pull in probert package."
n ubuntu only
-
- -- Ryan Harper Wed, 05 Jun 2019 13:46:57 -0500
+ == changelog ==
+
+ curtin (19.1-7-g37a7a0f4-0ubuntu1~19.04.1) disco; urgency=medium
+
+ * New upstream snapshot.
+ - vmtests: determine block name via dname w
Cosmic manual verification that installing curtin from -proposed does
not pull in probert package.
** Attachment added: "Cosmic manual verification that installing curtin from
-proposed does not pull in probert package."
Bionic manual verification that installing curtin from -proposed does
not pull in probert package.
** Attachment added: "Bionic manual verification that installing curtin from
-proposed does not pull in probert package."
Xenial vmtest console log from rerunning tests that timed out.
** Attachment added: "Xenial vmtest console log from rerunning tests that timed
out."
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275697/+files/curtin-vmtest-proposed-x-diglett-console.log
--
You received this
Xenial vmtest console log
** Attachment added: "Xenial vmtest console log"
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275695/+files/curtin-vmtest-proposed-x-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Xenial vmtest artifacts from rerunning tests that timed out.
** Attachment added: "Xenial vmtest artifacts from rerunning tests that timed
out."
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275696/+files/curtin-vmtest-proposed-x-diglett-artifacts.tar.xz
--
You received this
Xenial vmtest artifacts
** Attachment added: "Xenial vmtest artifacts"
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275693/+files/curtin-vmtest-proposed-x-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Disco vmtest artifacts from rerunning tests that timed out.
** Attachment added: "Disco vmtest artifacts from rerunning tests that timed
out."
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275691/+files/curtin-vmtest-proposed-d-diglett-artifacts.tar.xz
--
You received this
Disco vmtest console log
** Attachment added: "Disco vmtest console log"
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275690/+files/curtin-vmtest-proposed-d-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Disco vmtest console-log from rerunning tests that timed out.
** Attachment added: "Disco vmtest console-log from rerunning tests that timed
out."
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275692/+files/curtin-vmtest-proposed-d-diglett-console.log
--
You received this bug
Cosmic vmtest artifacts from rerunning tests that timed out.
** Attachment added: "Cosmic vmtest artifacts from rerunning tests that timed
out."
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275686/+files/curtin-vmtest-proposed-c-diglett-artifacts.tar.xz
--
You received this
Bionic vmtest artifacts from repeating tests that timed out.
** Attachment added: "Bionic vmtest artifacts from repeating tests that timed
out."
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275683/+files/curtin-vmtest-proposed-b-diglett-console.log
--
You received this bug
Cosmic vmtest console log
** Attachment added: "Cosmic vmtest console log"
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275685/+files/curtin-vmtest-proposed-c-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
301 - 400 of 1546 matches
Mail list logo
