*** 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
Also using Ubuntu 19.04. I attempted the alternative from #34, but it
unfortunately does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318542
Title:
One keystroke goes double when using
*** 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:
: Ubuntu 5.0.0-31.33-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC1: ryan 1936 F pulseaudio
- /dev/snd/controlC0: ryan 1936 F pulseaudi
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ryan 1936 F pulseaudio
/dev/snd/controlC0: ryan 1936 F pulseaudio
Date: Sun Oct 6 17:37:53 2019
InstallationDate: Installed on 2018-05-29 (495 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic B
*** 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
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,
Public bug reported:
The hardware is a desktop computer. Motherboard: ASUS M5A78L-M Plus/USB
(BIOS is the latest 0502), CPU: AMD FX-6300, Graphics: Integrated ATI
Radeon™ HD 3000 GPU, RAM: 16G ECC RAM.
Installation images I have tried: ubuntu-18.04.2-desktop-amd64.iso and
We’ve just dug into this aspect of both Disco and Eoan. Unfortunately,
I don’t know if this ever succeeded on these two releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287040/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287041/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287037/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287039/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287038/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287035/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287036/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287034/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And Bionic for grins:
** Description changed:
Disco and Eoan device is busy after unmounting an ephemeral disk, cannot
format the device until rebooting.
This is blocking all of OpenStack Charms which interact with block
devices (Nova Compute, Ceph, Swift, Cinder), on the Disco and
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287032/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287031/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287027/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287033/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
^ Disco apport above, Eoan to follow:
** Tags added: eoan
** Description changed:
Disco and Eoan device is busy after unmounting an ephemeral disk, cannot
format the device until rebooting.
This is blocking all of OpenStack Charms which interact with block
devices (Nova Compute,
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287028/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287026/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287029/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287030/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected disco ec2-images
** Description changed:
Disco and Eoan device is busy after unmounting an ephemeral disk, cannot
format the device until rebooting.
This is blocking all of OpenStack Charms which interact with block
devices (Nova
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287023/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287025/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287024/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287021/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287022/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287020/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1842751/+attachment/5287019/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
Title:
** Also affects: linux (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/1842751
Title:
[disco] [eoan] After unmount, cannot open /dev/vdb: Device
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
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
Public bug reported:
I'm sorry if I'm reporting this in the wrong place, but the page for
dbusmenu itself (https://bugs.launchpad.net/libdbusmenu) doesn't seem to
allow reporting bugs. After some digging I got the impression that
dbusmenu is actually an Ubuntu-specific package and bugs for it 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
This has already been fixed as of 2.4.48+dfsg-1ubuntu1. I'm not sure why
the upload didn't automatically close the bug.
** Changed in: openldap (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I believe AVC/H.264 is better compression than what is used by the other
options.
I would very much like it if I did not have to select True Color or any of the
other options.
Is there a workaround or plan to make AVC/H.264 usable in Ubuntu 18.04?
I am using the remmina-ppa-team/remmina-next
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.s
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]
601 - 700 of 9549 matches
Mail list logo
