[Bug 1905412] Re: LVM install broken if other disks have meta-data on the VG name already
I think the issue here is that the guided lvm install always creates a vg named ubuntu-vg -- even if there is already a vg with that name on other disks. Installing over the top of the disk that has the ubuntu-vg vg on it *ought* to work but I wouldn't be that surprised if it didn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905412 Title: LVM install broken if other disks have meta-data on the VG name already To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1905412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907713] Re: aufs support is deprecated and should be handled on upgrade
Hi, docker packaging is maintained at https://github.com/tianon/debian- docker/tree/ubuntu so perhaps you could propose this as a change there? (It's possible we should move this to somewhere with a more generic URL -- or already have, but I don't think so) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907713 Title: aufs support is deprecated and should be handled on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1907713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907713] Re: aufs support is deprecated and should be handled on upgrade
Although there's no reason for the deb's preinst to be checking /var/snap/docker/common/var-lib-docker/aufs surely? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907713 Title: aufs support is deprecated and should be handled on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1907713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1892369] Re: Impossible to skip integrity test for ubuntu-server 20.04.1 iso
On Thu, 25 Feb 2021 at 08:01, Guilherme G. Piccoli < 1892...@bugs.launchpad.net> wrote: > (I needed to > use a VNC connection since by default the images don't output to serial > console, another point to improve if you ask me...) > If you know a way to find out where the serial console _is_ on amd64 that actually works, we're all ears! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892369 Title: Impossible to skip integrity test for ubuntu-server 20.04.1 iso To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1892369] Re: Impossible to skip integrity test for ubuntu-server 20.04.1 iso
People got upset when I suggested that before... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892369 Title: Impossible to skip integrity test for ubuntu-server 20.04.1 iso To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915722] Re: rustc 1.50 and cargo 0.51 will be required by a future version of firefox
So for a status update, rustc is updated to 1.49 in hirsute and I've just uploaded it to the PPA for older releases. So the update to 1.50 and the cargo update to go: unfortunately, Debian has not updated to the versions we need yet so I'll have to do the upstream update myself, which is a bit tedious (especially cargo). We'll get there! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915722 Title: rustc 1.50 and cargo 0.51 will be required by a future version of firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1915722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917590] Re: File integrity check at boot of install media no longer functional
The intent is that the check is done in the background after boot but it seems the service file that should do that is not being installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917590 Title: File integrity check at boot of install media no longer functional To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1917590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922342] Re: HIrsute live session takes ages to boot on BIOS systems
If this is it do with the partition table / flags then it needs to be fixed in debian-cd. You can see the options passed to xorriso here: https://bazaar.launchpad.net/~ubuntu-cdimage/debian- cd/ubuntu/view/head:/tools/boot/impish/boot-amd64 As you can see, it's a bit complicated. The name of the --mbr-force- bootable sounds like it should be adding a partition with a bootable flag... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922342 Title: HIrsute live session takes ages to boot on BIOS systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929129] Re: if cloud-init status is not done, set_installer_password will crash
Oops. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929129 Title: if cloud-init status is not done, set_installer_password will crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1929129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1922342] Re: HIrsute live session takes ages to boot on BIOS systems
On Fri, 21 May 2021 at 02:00, Lucap <1922...@bugs.launchpad.net> wrote: > Yeah it is complicated , when you look at a freshly written USB stick > with gnome disks there is a box you can tick that says Legacy BIOS > bootable , I'm not sure if gnome disks is doing as described below with > the "bios_grub" flag as the link talks about a hardrive so i'm not sure > if it would apply to a USB stick? > That is perhaps setting the bootable flag on the single partition entry in the "protective" MBR, which is AIUI technically a violation of the GPT spec. But if it helps here maybe we should hack it anyway. I'm going to subscribe Thomas Schmitt, xorriso upstream, who knows enormously more than I do about all this stuff. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922342 Title: HIrsute live session takes ages to boot on BIOS systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929129] Re: if cloud-init status is not done, set_installer_password will crash
** Changed in: subiquity (Ubuntu) Status: New => Fix Committed ** Also affects: subiquity Importance: Undecided Status: New ** Changed in: subiquity Status: New => 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/1929129 Title: if cloud-init status is not done, set_installer_password will crash To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1929129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928939] Re: excessive boot time with nothing on screen but blinking cursor (some bios boxes only); ubuntu/lubuntu impish daily
Could you try the server ISOs as well? And maybe attach dmesg output from one of the systems after it has booted oh so slowly? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928939 Title: excessive boot time with nothing on screen but blinking cursor (some bios boxes only); ubuntu/lubuntu impish daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1928939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929150] [NEW] new version fails to start if eth0 not present
Public bug reported: As reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895342, the package currently fails to start if eth0 is not there. eth0 is not there on the autopkgtest runners, so the tests (mostly) fail. ** Affects: suricata (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929150 Title: new version fails to start if eth0 not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/suricata/+bug/1929150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929110] Re: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit
This looks mostly ok but the merge doesn't seem to account for the apport hooks being in debian now -- the changelog still lists it as a difference, the package-hooks dir is in the .dirs files twice, and I think they might be installed twice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929110 Title: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929213] Re: Ubuntu server LVM creates clone partitions and crash installation
Argh what is going on here is that you have two distinct drives with the same WWN. From the UdevDB from the crash report: P: /devices/pci:00/:00:11.0/ata1/host0/target0:0:0/0:0:0:0/block/sda N: sda ... E: ID_WWN=0x5000 ... E: ID_SERIAL=SSDPR-CX400-256-G2_GXA062868 P: /devices/pci:00/:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb N: sdb ... E: ID_WWN=0x5000 ... E: ID_SERIAL=SSDPR-CX400-256-G2_GXA062866 Distinct serial but same wwn. These values end up in the curtin config: - id: disk-sda path: /dev/sda ptable: gpt serial: SSDPR-CX400-256-G2_GXA062868 type: disk wwn: '0x5000' - id: disk-sdb path: /dev/sdb ptable: gpt serial: SSDPR-CX400-256-G2_GXA062866 type: disk wwn: '0x5000' curtin looks up by wwn first (if present) so when processing the action for /dev/sda it actually (at least in the run I looked at) ended up clearing users from /dev/sdb instead. So the vg named "vg0" that was on sda didn't get cleared and then when it tried to create a new vg called vg0, things blew up. I'm not going to bother trying to think of why some of your attempts failed and some succeeded. Your comment "even when only single drive was selected, somehow second(sdb) had clones of partitions from sda." does make sense given this though! What we should do is be more robust to this behaviour (it's not the first time we've seen it). Something needs to notice when drives with the same WWN have different serials and ignore the wwn if that happens, or something along those lines. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929213 Title: Ubuntu server LVM creates clone partitions and crash installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1929213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929213] Re: Ubuntu server LVM creates clone partitions and crash installation
You might also want to yell at your disk vendor a bit I guess :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929213 Title: Ubuntu server LVM creates clone partitions and crash installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1929213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806022] Re: Ubuntu 18.04 server installer does not see existing partitions
** Changed in: subiquity (Ubuntu) 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/1806022 Title: Ubuntu 18.04 server installer does not see existing partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1806022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924575] Re: [21.04] autoinstall reports crashes
This seems to be fixed in impish dailies. ** Changed in: subiquity Status: Fix Committed => Fix Released ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) 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/1924575 Title: [21.04] autoinstall reports crashes To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1924575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924575] Re: [21.04] autoinstall reports crashes
Need to backport the fixes to 20.04 before the point release though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924575 Title: [21.04] autoinstall reports crashes To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1924575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929213] Re: Ubuntu server LVM creates clone partitions and crash installation (invalid wwn is used by udev & probert as well)
I think the reason LVM deploys fail is that there is already a VG with the name that is to be used, which should be deleted but isn't because the installer gets confused about which disk is which. In any case, the source of the problem is clear and the exact symptoms are not that important. We should definitely handle this situation better. (I think arguably the udev rules should such a bogus wwn as well but I don't know as much about how things work at that level). Disk actions can provide three bits of data to find the drive: wwn, serial and path. Currently the installer just uses the first of whichever of these is provided (so in this case, the bogus wwn), but Dimitri suggested that instead it should use all provided fields, which would work much better for this bug at least. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929213 Title: Ubuntu server LVM creates clone partitions and crash installation (invalid wwn is used by udev & probert as well) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1929213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930686] Re: Do not include /dev device node filles in OCI rootfs tarballs
** Also affects: livecd-rootfs (Ubuntu Bionic) 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/1930686 Title: Do not include /dev device node filles in OCI rootfs tarballs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1930686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932564] Re: FilesystemController has no _start_task
This happened because NetworkController.start() raised an exception. The failure mode is pretty bad here, probably a failure in a start() method should crash the whole server? Not sure what the "AttributeError: 'NoneType' object has no attribute 'ref'" stuff is about either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932564 Title: FilesystemController has no _start_task To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1932564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933352] Re: The impish-live-server images fail to boot to subiquity
This is a bug in livecd-rootfs which assumes all base snaps needed for subiquity are already in the filesystem layer, which is no longer true now that lxd is based on core20. ** Changed in: ubuntu-cdimage Status: New => Invalid ** Changed in: subiquity Status: New => Invalid ** Changed in: livecd-rootfs (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/1933352 Title: The impish-live-server images fail to boot to subiquity To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1933352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933711] Re: defining tmpfs /tmp in autoinstall config fails
Ah yeah this makes sense. Should be easy to fix. ** Changed in: subiquity (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/1933711 Title: defining tmpfs /tmp in autoinstall config fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1933711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933711] Re: defining tmpfs /tmp in autoinstall config fails
So https://github.com/canonical/subiquity/pull/993 should fix this. I've built this PR into a snap and pushed it to the edge/pr-993 channel so if you add this to your autoinstall.yaml: refresh-installer: update: yes channel: "edge/pr-993" it should work now. (If your install is offline, you should be able to use https://github.com/mwhudson/livefs-editor to stuff the new snap into an ISO). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933711 Title: defining tmpfs /tmp in autoinstall config fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1933711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933523] Re: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs
Hmm looking into our livecd-rootfs stuff a bit, I'm a bit confused about tty names. We have special handling for sclp_line0 and (on s390x only) ttyS0 but from your logs it seems the tty in z/vm is called ttysclp0, is that correct? Which terminal are you looking at and which can run the subiquity tui? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933523 Title: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1933523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933711] Re: defining tmpfs /tmp in autoinstall config fails
Glad to hear it. The fix should be in the edge channel by now, or pretty soon at least. ** Changed in: subiquity (Ubuntu) Status: Triaged => 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/1933711 Title: defining tmpfs /tmp in autoinstall config fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1933711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933711] Re: defining tmpfs /tmp in autoinstall config fails
And thanks for reporting back! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933711 Title: defining tmpfs /tmp in autoinstall config fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1933711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1933523] Re: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs
On Tue, 29 Jun 2021 at 19:50, Frank Heimes <1933...@bugs.launchpad.net>
wrote:
> Regarding the (main) s390x ttys:
> SCLP line-mode terminal device driver/dev/sclp_line0
> ('Operating Systems Messages')
> SCLP full-screen mode VT220 terminal device driver /dev/ttysclp0
> ('Integrated ASCII console', or z/VM)
>
> Subiquity tui can only run in full-screen, not in line-mode.
>
> There are two "consoles" in case of an LPAR - the "Operating Systems
> Messages" (line-mode) where only low-level console messages are displayed,
> including the installer boot messages that contain the temporary installer
> password,
> and the "Integrated ASCII Console" (the emulated VT220 full-screen-mode)
> where the subiquity tui can run - and is in fact started there
> automatically (this still works and allows to complete an installation).
>
> The z/VM console (by default) uses the 3215 line-mode, for the console
> messages that include temporary installer password, but the Subiquity
> tui can not run there (since it's line-mode), hence a remote ssh
> installation is needed here.
>
> Just notice that all this worked fine in the past - and even with the
> early Impish images (about 06-14-2021 and before) and I do not think
> that things changed that much.
>
> And since paride tried a current impish amd64 ISO image, where the temp
> installer password is also missing,things seems to be platform agnostic
> and should not be cause by any of the special s390x consoles - I think.
>
>
> What's missing is an output like this (see attached example.txt taken from
> a 20.04 installation), that provides lines like:
> "
> "Set the following 'random' passwords"
> installer:x3Z9hgeXCPNDQC8VFeqK
> "
>
So I expect this to no longer be present; basically cloud-init has changed
to make it much harder / impossible to find this password later.
> and
> "
> It is possible to connect to the installer over the network, which
> might allow the use of a more capable terminal and can offer more languages
> than can be rendered in the Linux console.
>
>
> To connect, SSH to installer@10.245.236.14.
>
> You should use the preconfigured password passed to cloud-init.
>
> The host key fingerprints are:
>
> RSA SHA256:YTmNejNSf1OlzQbOcNzkcYrDzqfy9aoT1laAs+oca5k
> ECDSA SHA256:MKGkFuNzdQ3aNBL33bhqapn8clpDD9ZIL2SLr24IDAI
> ED25519 SHA256:NitkBIaBVl97j1E3AXOrQRNrfR89UChEFxbJWnYhtVE
> "
>
This output should still be there though, and that's what we should focus
on figuring out. The serial-getty service running on sclp_line0 is what is
_supposed_ to be producing this output.
I guess you should try this on an LPAR install where you can actually get
into the system: can you post the output of systemctl
status serial-getty@sclp_line0.service? And maybe systemctl
show serial-getty@sclp_line0.service? TIA
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933523
Title:
Temporary installer password and key fingerprints are not printed with
latest impish daily ISOs
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1933523/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933523] Re: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs
Oh, I see the problem: the process that prints the network connection information is running, but does not have its stdout connected to the right place so the output is going nowhere. Easy fix fortunately (easier than figuring out what is going on!) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933523 Title: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1933523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932145] Re: rustc 1.51 and cargo 0.52 required by firefox 91
** Changed in: cargo (Ubuntu) Status: New => Triaged ** Changed in: cargo (Ubuntu Bionic) Status: New => Triaged ** Changed in: cargo (Ubuntu Focal) Status: New => Triaged ** Changed in: cargo (Ubuntu Hirsute) Status: New => Triaged ** Changed in: rustc (Ubuntu) Status: New => Triaged ** Changed in: rustc (Ubuntu Bionic) Status: New => Triaged ** Changed in: rustc (Ubuntu Focal) Status: New => Triaged ** Changed in: rustc (Ubuntu Hirsute) 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/1932145 Title: rustc 1.51 and cargo 0.52 required by firefox 91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1932145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933523] Re: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs
The fix should be in the next images that get built. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933523 Title: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1933523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933523] Re: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs
Yay thanks. Now to get back to backporting this whole mess to focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933523 Title: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1933523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932145] Re: rustc 1.51 and cargo 0.52 required by firefox 91
** Tags added: fr-1484 ** Changed in: rustc (Ubuntu) Status: Triaged => In Progress ** Changed in: rustc (Ubuntu) Assignee: Canonical Foundations Team (canonical-foundations) => Michael Hudson-Doyle (mwhudson) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932145 Title: rustc 1.51 and cargo 0.52 required by firefox 91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1932145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932145] Re: rustc 1.51 and cargo 0.52 required by firefox 91
** Changed in: cargo (Ubuntu) Status: Triaged => 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/1932145 Title: rustc 1.51 and cargo 0.52 required by firefox 91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1932145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932313] Re: Breezy 3.2.0+bzr7543-1 FTBFS
I don't see any evidence this was reverted in 3.9.6 fwiw. Maybe you were thinking of a different change? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932313 Title: Breezy 3.2.0+bzr7543-1 FTBFS To manage notifications about this bug go to: https://bugs.launchpad.net/brz/+bug/1932313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935796] [NEW] intel-graphics-compiler needs sourceful update for llvm 12
Public bug reported: This is keeping intel-opencl-clang and spirv-llvm-translator in proposed. tjaalton: i think intel-graphics-compiler needs a no change rebuild, any reason not to jfdi? mwhudson: against llvm12? won't work, and newer versions aren't any better upstream knows ** Affects: intel-graphics-compiler (Ubuntu) Importance: Undecided Status: New ** Affects: intel-opencl-clang (Ubuntu) Importance: Undecided Status: New ** Affects: spirv-llvm-translator (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: spirv-llvm-translator (Ubuntu) Importance: Undecided Status: New ** Tags added: update-excuse ** Also affects: intel-graphics-compiler (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/1935796 Title: intel-graphics-compiler needs sourceful update for llvm 12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-graphics-compiler/+bug/1935796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924794] Re: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x
Well in the focal -> groovy time we find this change
(http://launchpadlibrarian.net/481474731/initramfs-
tools_0.137ubuntu4_0.137ubuntu5.diff.gz):
# activate non-autoconfigured s390x devices
for dev in $DEVICE $DEVICE6 $IP6 $VLAN_LINK; do
+ # skip $DEVICE which is processed in $VLAN_LINK
+ echo ${VLAN} | grep -q ${dev} && continue
case ${dev} in
enc*)
zdev=${dev#enc}
which I think is just wrong: it's trying to avoid calling chzdev -e on
the encc000.2653 device but it also avoids calling it on encc000 :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924794
Title:
Getting error "ipconfig: no devices to configure" while trying to
autoinstall in a VLAN env on s390x
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1924794/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924794] Re: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x
https://code.launchpad.net/~mwhudson/ubuntu/+source/initramfs-tools/+git /initramfs-tools/+merge/401992 might fix this -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924794 Title: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1924794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925335] Re: subiquity installer : ibmveth disabled by default
wpa_supplicant is not part of the server seed, so by default a server install could only join an unencrypted wifi network, which doesn't seem very useful. There is a chance that we will do the work to make wifi work properly at some point, but we're not there yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925335 Title: subiquity installer : ibmveth disabled by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1925335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926600] Re: Ubuntu server 20.04.2 installer hidden partition problem
The partition is listed under "used devices" because there isn't anything you can do with it. It has to exist though because otherwise grub wont fit -- if you select the partition and then try to "edit" it, there is a blurb about what's going on. ** Changed in: subiquity (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/1926600 Title: Ubuntu server 20.04.2 installer hidden partition problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1926600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924794] Re: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x
Can you try https://people.canonical.com/~mwh/initrd.lp1924794? This is a patched initrd from the 21.04 release ISO, so the other files should also come from that ISO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924794 Title: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1924794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924794] Re: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x
I've uploaded the fix to impish. The bug is present in groovy and hirsute but there's probably no reason to backport the fix -- we are unlikely to make release media for them again... ** Changed in: subiquity Status: New => Invalid ** Changed in: casper (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools Status: New => 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/1924794 Title: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1924794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927654] Re: /snap/subiquity/2393/usr/bin/subiquity-server:KeyError:main:wrapper:log_time:block_meta:meta_custom:mount_handler:mount_apply:fstab_line_for_data:get_volume_spec
The curtin log tail is this:
Running command ['lsblk', '--noheadings', '--bytes', '--pairs',
'--output=ALIGNMENT,DISC-ALN,DISC-GRAN,DISC-MAX,DISC-ZERO,FSTYPE,GROUP,KNAME,LABEL,LOG-SEC,MAJ:MIN,MIN-IO,MODE,MODEL,MOUNTPOINT,NAME,OPT-IO,OWNER,PHY-SEC,RM,RO,ROTA,RQ-SIZE,SIZE,STATE,TYPE,UUID',
'/dev/sda2'] with allowed return codes [0] (capture=True)
volspec: path=/dev/sda2 type=part
An error occured handling 'mount-0': KeyError - 'DEVLINKS'
finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL:
configuring mount: mount-0
TIMED BLOCK_META: 25.187
finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: curtin
command block-meta
Traceback (most recent call last):
File
"/snap/subiquity/2393/lib/python3.6/site-packages/curtin/commands/main.py",
line 202, in main
ret = args.func(args)
File "/snap/subiquity/2393/lib/python3.6/site-packages/curtin/log.py", line 97,
in wrapper
return log_time("TIMED %s: " % msg, func, *args, **kwargs)
File "/snap/subiquity/2393/lib/python3.6/site-packages/curtin/log.py", line 79,
in log_time
return func(*args, **kwargs)
File
"/snap/subiquity/2393/lib/python3.6/site-packages/curtin/commands/block_meta.py",
line 111, in block_meta
return meta_custom(args)
File
"/snap/subiquity/2393/lib/python3.6/site-packages/curtin/commands/block_meta.py",
line 1961, in meta_custom
handler(command, storage_config_dict)
File
"/snap/subiquity/2393/lib/python3.6/site-packages/curtin/commands/block_meta.py",
line 1248, in mount_handler
target=state.get('target'), fstab=state.get('fstab'))
File
"/snap/subiquity/2393/lib/python3.6/site-packages/curtin/commands/block_meta.py",
line 1227, in mount_apply
util.write_file(fstab, fstab_line_for_data(fdata), omode="a")
File
"/snap/subiquity/2393/lib/python3.6/site-packages/curtin/commands/block_meta.py",
line 1154, in fstab_line_for_data
spec = get_volume_spec(fdata.device)
File
"/snap/subiquity/2393/lib/python3.6/site-packages/curtin/commands/block_meta.py",
line 1082, in get_volume_spec
LOG.debug('info[DEVLINKS] = %s', info['DEVLINKS'])
KeyError: 'DEVLINKS'
'DEVLINKS'
which is strange -- maybe we are racing with udev and reading the
partition's udev data while it is still being constructed somehow?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927654
Title:
/snap/subiquity/2393/usr/bin/subiquity-
server:KeyError:main:wrapper:log_time:block_meta:meta_custom:mount_handler:mount_apply:fstab_line_for_data:get_volume_spec
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1927654/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927654] Re: /snap/subiquity/2393/usr/bin/subiquity-server:KeyError:main:wrapper:log_time:block_meta:meta_custom:mount_handler:mount_apply:fstab_line_for_data:get_volume_spec
FWIW, this only seems to happen on hirsute. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927654 Title: /snap/subiquity/2393/usr/bin/subiquity- server:KeyError:main:wrapper:log_time:block_meta:meta_custom:mount_handler:mount_apply:fstab_line_for_data:get_volume_spec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1927654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924794] Re: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x
So the initramfs-tools with the fix has migrated now, the next impish daily should have it (serial 20210511 or later). Would you be able to test to see if that helps? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924794 Title: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1924794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924794] Re: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x
** Changed in: initramfs-tools 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/1924794 Title: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1924794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905412] Re: LVM install broken if other disks have meta-data on the VG name already
Oh that's yet another new bug, but a pretty simple one: https://code.launchpad.net/~mwhudson/curtin/+git/curtin/+merge/401068 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905412 Title: LVM install broken if other disks have meta-data on the VG name already To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1905412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1905412] Re: LVM install broken if other disks have meta-data on the VG name already
On Wed, 14 Apr 2021 at 21:52, Thierry FAUCK <1905...@bugs.launchpad.net> wrote: > I have tested the installation on multipath disk with LVM partition > enabled - and it installed without any problem. > However at reboot I got following messages but that could be related to > other devices: > Volume group "ubuntu-vg" not found > Cannot process volume group ubuntu-vg > > [FAILED] Failed to start Wait for u…omplete Device Initialization. > [ 657.094223] device-mapper: table: 253:78: multipath: error getting > device > [ 658.357618] device-mapper: table: 253:85: multipath: error getting > device > Hm, is this your system with 160+ paths? Maybe something isn't waiting long enough. > and after a while it booted completely and I can check Well if it booted OK it doesn't sound t bad :) Can you attach the journal output? Possibly to a new bug report as I'm pretty sure whatever is going here is not related to the problem this bug was about. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905412 Title: LVM install broken if other disks have meta-data on the VG name already To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1905412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923827] Re: Inconsistent ESP sizes
I have to say I think I spent about 5ms thinking about the size to use in subiquity. I guess it may make sense for subiquity to have a larger default because it is at least possible to imagine other operating systems being installed alongside Ubuntu for its use case, which is not really the case for MAAS or cloud images. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923827 Title: Inconsistent ESP sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1923827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923485] Re: unable to reconize Asgard NVME with short serial
The upstream bug request has a PR that seems to fix the issue already. I guess if it gets accepted upstream we can think about backporting the fix to stable releases in the fullness of time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923485 Title: unable to reconize Asgard NVME with short serial To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1923485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923485] Re: unable to reconize Asgard NVME with short serial
That said, we could fix this issue in curtin by searching for a device with specified serial by just looking through the udev db directly rather than by globbing in /dev/disk/by-id. In fact I thought we already did that! But apparently not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923485 Title: unable to reconize Asgard NVME with short serial To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1923485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915722] Re: rustc 1.50 and cargo 0.51 will be required by a future version of firefox
Oh oops forgot about that. Uploaded now. How serious do you regard the s390x/groovy situation? I'm sure it's fixable but it would be tedious in the extreme I think... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915722 Title: rustc 1.50 and cargo 0.51 will be required by a future version of firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1915722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915722] Re: rustc 1.50 and cargo 0.51 will be required by a future version of firefox
That's what I hoped you would say :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915722 Title: rustc 1.50 and cargo 0.51 will be required by a future version of firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1915722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925335] Re: subiquity installer : ibmveth disabled by default
Subiquity only enables eth* and en* by default. We can add ibmveth* to the list easily enough. (It's unreasonably hard to tell if an interface is a normal wired link vs some virtual or wifi stuff!) ** Changed in: subiquity (Ubuntu) Status: New => Triaged ** Tags added: easy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925335 Title: subiquity installer : ibmveth disabled by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1925335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903716] Re: [20.04.1] VROC - mdadm missing in live-installer ISO
Thanks for confirming. Hopefully there will be progress on VROC at some point (can I contact you for pre-release testing of it?) ** Changed in: subiquity Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903716 Title: [20.04.1] VROC - mdadm missing in live-installer ISO To manage notifications about this bug go to: https://bugs.launchpad.net/mdadm/+bug/1903716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924794] Re: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x
The part of this that doesn't make sense is "ip: can't find device 'encc000'" -- is that device just not appearing in time? It should be chzdev activated just before the initramfs code tries to set up the vlan, maybe it's a race? (is this behaviour consistent?). It's strange that using the nic without a vlan works but there is a bit more time (and a wait for udev, hmm) between the device getting chzdev-ed and used in that case. The code in initramfs-tools hasn't changed at all here between groovy and hirsute so I don't know what's changed. We can always blame the kernel I guess. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924794 Title: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1924794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931531] Re: clisp crashed in impish compiling xindy
So I think what changed to break this was this change in the kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=47ebb09d54856500c5a5e14824781902b3bb738e which I'm pretty sure got backported everywhere. But this is only the base address for dynamic executables. I wonder if it will build if we disable PIE by default... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931531 Title: clisp crashed in impish compiling xindy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clisp/+bug/1931531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931531] Re: clisp crashed in impish compiling xindy
If I disable PIE for ppc64el it builds on my canonistack instance, but all architectures fail to build in my PPA for what seem to be unrelated reasons :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931531 Title: clisp crashed in impish compiling xindy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clisp/+bug/1931531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926137] Re: Error when starting copy to disk due to processes accessing /var/log
** Also affects: casper (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/1926137 Title: Error when starting copy to disk due to processes accessing /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1926137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926137] Re: Error when starting copy to disk due to processes accessing /var/log
I think we should change casper to only (automatically) use a fs with label writable if it's on the same device as the livefs. That may break some use cases but it's definitely the common one. ** Changed in: casper (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/1926137 Title: Error when starting copy to disk due to processes accessing /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1926137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935895] [NEW] update to 4.2-rc1
Public bug reported: We should update to the current upstream rc. It should be fairly simple as most of the patches in the package are backports from upstream anyway. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New ** Tags: fr-1498 ** Tags added: fr-1498 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935895 Title: update to 4.2-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1935895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935969] Re: Ubuntu 20.04.2 LTS installer crash when letting the system determine size of additional LV
Are you enabling encryption in the guided screen? This sort of bug means we are mis-estimating how large the VG is going to be and we've had a few bugs like this in the past but I thought they were mostly fixed. The .crash file from /var/crash would be great help in figuring out what is going on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935969 Title: Ubuntu 20.04.2 LTS installer crash when letting the system determine size of additional LV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1935969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931531] Re: clisp crashed in impish compiling xindy
Ah so the unrelated reasons would be that glibc snapshot I have in that PPA -- clisp with PIE disabled for s390x and ppc64el built fine in a different PPA and then xindy built with the resulting clisp too so I'll upload that. It would be better to fix this properly by choosing better addresses for clisp but well for now it will do. ** Changed in: xindy (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/1931531 Title: clisp crashed in impish compiling xindy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clisp/+bug/1931531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936019] [NEW] please remove armhf binary (ANAIS)
Public bug reported: https://launchpad.net/ubuntu/+source/atlas-ecmwf/0.25.0-2 dropped support for all 32 bit architectures ** Affects: atlas-ecmwf (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936019 Title: please remove armhf binary (ANAIS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atlas-ecmwf/+bug/1936019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936723] Re: glibc regressions on riscv64
I guess https://patches-gcc.linaro.org/patch/57922/ will fix this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936723 Title: glibc regressions on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1936723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936833] Re: package ubuntu-advantage-tools 27.2.1~21.10.1 failed to install/upgrade: installed ubuntu-advantage-tools package post-installation script subprocess returned error exit status 1
** Changed in: ubuntu-advantage-tools (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/1936833 Title: package ubuntu-advantage-tools 27.2.1~21.10.1 failed to install/upgrade: installed ubuntu-advantage-tools package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1936833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936833] Re: package ubuntu-advantage-tools 27.2.1~21.10.1 failed to install/upgrade: installed ubuntu-advantage-tools package post-installation script subprocess returned error exit status 1
You can reproduce this by running "schroot -c impish-amd64 -u root -d /" and then within the chroot, run "apt-get install -y ubuntu-advantage- tools cloud-init". The problem is this bit of the postinst: if command -v "cloud-id" > /dev/null ; then cloud_id=$(cloud-id) fi In this situation, cloud-id is present but errors. One option would be to change this to: cloud_id=$(cloud-id 2>/dev/null || true) Or another would be to make the call to cloud-id conditional on the existence of /run/cloud-init/instance-data.json. Either way this is currently blocking my efforts to work on a minimal layer for the live server ISO so it qualifies as pretty annoying :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936833 Title: package ubuntu-advantage-tools 27.2.1~21.10.1 failed to install/upgrade: installed ubuntu-advantage-tools package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1936833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936833] Re: package ubuntu-advantage-tools 27.2.1~21.10.1 failed to install/upgrade: installed ubuntu-advantage-tools package post-installation script subprocess returned error exit status 1
Here's a PR https://github.com/canonical/ubuntu-advantage- client/pull/1743 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936833 Title: package ubuntu-advantage-tools 27.2.1~21.10.1 failed to install/upgrade: installed ubuntu-advantage-tools package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1936833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936833] Re: package ubuntu-advantage-tools 27.2.1~21.10.1 failed to install/upgrade: installed ubuntu-advantage-tools package post-installation script subprocess returned error exit status 1
Could you upload the fix to impish pretty please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936833 Title: package ubuntu-advantage-tools 27.2.1~21.10.1 failed to install/upgrade: installed ubuntu-advantage-tools package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1936833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937295] Re: Installation hangs on VROC systems during Bionic installs
I'm a bit confused, I wouldn't expect vroc installs to work at all with 18.04.5. Is this after updating to the edge channel or something? ** Package changed: syslinux (Ubuntu) => subiquity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937295 Title: Installation hangs on VROC systems during Bionic installs To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933523] Re: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs
** Also affects: livecd-rootfs (Ubuntu Focal) 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/1933523 Title: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1933523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
** Changed in: subiquity Status: In Progress => Invalid ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released ** Also affects: livecd-rootfs (Ubuntu Focal) 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/1888497 Title: Booting the install system does not always succeed, hence a remote ssh login is not always possible To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1888497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
** Description changed: - From time to time (sporadically and very rarely - maybe in one or two - attempt out of twenty) I face a situation where the installer system (on - s390x) does not boot-up completely. + [impact] + When there is a serial console configured, there was a unit cycle + + serial-getty@$TTY.service -> cloud-final.service -> multi-user.target -> + getty.target -> serial-getty@$TTY.service + + (or something like that) + + Depending on which unit systemd kills to resolve the cycle, this can + result in cloud-init never completing which leads to the subiquity + server waiting forever for it and nothing useful can be done (other than + restarting and hoping for better luck next time). + + Because subiquity itself waits for cloud-init (and this has been true + for a long time now) there is no need for serial-getty@$TTY.service to + wait on cloud-final.service. + + [regression potential] + This change results in shuffling the systemd units around a fair bit, but the new arrangement has been tested in devel for a few months now and works well there. It's also much more straightforward than the current setup. + + [test case] + This is a bit tricky as it's an intermittent failure. Basically, boot the live installer with a serial console configured a bunch of times and (10?) check that the installer starts up properly each time. + + [original description] + From time to time (sporadically and very rarely - maybe in one or two attempt out of twenty) I face a situation where the installer system (on s390x) does not boot-up completely. This happened to me in the past already, but since it happened only one or twice I thought it's due to resource constraints on the system or so. But since I faced it now again on LPAR (before it was on z/VM), I'm opening this ticket now. In the latest case I used the focal daily live image from the 20th of July with installer 20.06.1 (but that also happened with previous versions). The situation is like this: In boot of the installer ends here (LPAR): ... "[ 128.200711] cloud-init[1375]: The key's randomart image is:" "[ 128.200735] cloud-init[1375]: +--[ED25519 256]--+" "[ 128.200758] cloud-init[1375]: |o .ooo |" "[ 128.200781] cloud-init[1375]: |.= . . +. o. .|" "[ 128.200804] cloud-init[1375]: |+ * . . * o.o . |" "[ 128.200826] cloud-init[1375]: |.= o . = = = + |" "[ 128.200849] cloud-init[1375]: |o + . S o +|" "[ 128.200876] cloud-init[1375]: | + o = . . |" "[ 128.200900] cloud-init[1375]: |o + .|" "[ 128.200925] cloud-init[1375]: | o.=. E |" "[ 128.200947] cloud-init[1375]: | .+.o+o. |" "[ 128.200977] cloud-init[1375]: +[SHA256]-+" "[ 138.898906] cloud-init[2217]: Cloud-init v. 20.2-45-g5f7825e2-0ubuntu1~20.04." "1 running 'modules:config' at Wed, 22 Jul 2020 11:27:39 +. Up 138.77 seconds" . "[ 138.898966] cloud-init[2217]: Set the following 'random' passwords" "[ 138.899001] cloud-init[2217]: installer:aecmewaoicnai" or another example (z/VM): ... - ¬ 93.463680| cloud-init¬1282|: +--¬ED25519 256|--+ - ¬ 93.463713| cloud-init¬1282|: !Eo=o ! - ¬ 93.463749| cloud-init¬1282|: !.Bo.o ... o ! - ¬ 93.463782| cloud-init¬1282|: !**.*... o = ! - ¬ 93.463818| cloud-init¬1282|: !*=O o. o . . ! - ¬ 93.463849| cloud-init¬1282|: !**++S! - ¬ 93.463886| cloud-init¬1282|: !§o+..! - ¬ 93.463918| cloud-init¬1282|: !+*o. ! - ¬ 93.463954| cloud-init¬1282|: !.o. ! - ¬ 93.463988| cloud-init¬1282|: !.! - ¬ 93.464028| cloud-init¬1282|: +¬SHA256|-+ + ¬ 93.463680| cloud-init¬1282|: +--¬ED25519 256|--+ + ¬ 93.463713| cloud-init¬1282|: !Eo=o ! + ¬ 93.463749| cloud-init¬1282|: !.Bo.o ... o ! + ¬ 93.463782| cloud-init¬1282|: !**.*... o = ! + ¬ 93.463818| cloud-init¬1282|: !*=O o. o . . ! + ¬ 93.463849| cloud-init¬1282|: !**++S! + ¬ 93.463886| cloud-init¬1282|: !§o+..! + ¬ 93.463918| cloud-init¬1282|: !+*o. ! + ¬ 93.463954| cloud-init¬1282|: !.o. ! + ¬ 93.463988| cloud-init¬1282|: !.! + ¬ 93.464028| cloud-init¬1282|: +¬SHA256|-+ ¬ 104.841438| cloud-init¬2004|: Cloud-init v. 20.2-45-g5f7825e2-0ubuntu1ß20.04. 1 running 'modules:config' at Mon, 20 Jul 2020 10:46:38 +. Up 104.63 seconds - . - ¬ 104.841490| cloud-init¬2004|: Set the following 'random' passwords - ¬ 104.841516| cloud-init¬2004|: installer:U9NJDuvXFw6X2fxG7pP8 + . + ¬ 104.841490| cloud-init¬2004|: Set the following 'random' passwords + ¬ 104.841516| cloud-init¬2004|: installer:U9NJDuvXFw6X2fxG7pP8 But it is not complete at this point. A completed boot of the installer system ends like this: "It is possible to connect to the installer over the network, which" "might allow the use of a more c
[Bug 1933523] Re: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs
** Description changed: - Using the latest Impish daily ISO (timestamp) 2021-06-24 I faced the - situation that I didn't got a temporary installation password not the - key fingerprints at the end of the installer boot-up process. + [impact] + cloud-init no longer puts the password of a user with a RANDOM password anywhere subiquity can find it, so while the password chosen ends up printed to the console, subiquity cannot display it from within the UI as it used to. + + [regression potential] + If something goes wrong here, it's possible that subiquity will no longer be able to display the password for the installer user at all, which will make continuing the install via SSH impossible (this is very important for installing on z/vm) + + [test case] + Make an ISO with this change and boot it and check that the installer password is available in the UI. Make a s390x ISO, boot it in z/vm and check that the installer password is displayed on the console. + + [original description] + Using the latest Impish daily ISO (timestamp) 2021-06-24 I faced the situation that I didn't got a temporary installation password not the key fingerprints at the end of the installer boot-up process. Hence I am not able to perform an installation from remote via ssh. However, subiqity is started at the console (e.g. Integrated ASCII console) and an installation can be successfully completed there, but a console installation is not in all cases possible, for example with z/VM guests. As one can read between the lines I tried this on s390x (Integrated ASCII console and z/VM), but 'paride' tried the same on amd64 and ran into the same symptoms, so it does not seem to be architecture specific. This must have happened recently, since I already was able to do ssh-based Impish installations on s390x in the past (for example with the daily ISO from 06-14-2021). ___ This is not the case for the 20.04 dailies - I can do remote ssh installation with the 20.04 live daily ISOs. ___ With Impish on s390x the kernel parameter 'quiet' is still set by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933523 Title: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1933523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926137] Re: Error when starting copy to disk due to processes accessing /var/log
This should be fixed in the latest impish dailies -- Alfonso, do you still have a way to test this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926137 Title: Error when starting copy to disk due to processes accessing /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1926137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932145] Re: rustc 1.51 and cargo 0.52 required by firefox 91
This is all done now from my side I think. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932145 Title: rustc 1.51 and cargo 0.52 required by firefox 91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1932145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1926137] Re: Error when starting copy to disk due to processes accessing /var/log
The fix is in how the iso is constructed unfortunately, so not trivial to test on focal. If you can link me an iso you've been testing, I should be able to hack the new behavior into it (early next week at this point) On Fri, 23 Jul 2021, 18:25 Alfonso Sanchez-Beato, < 1926...@bugs.launchpad.net> wrote: > On Fri, Jul 23, 2021 at 2:35 AM Michael Hudson-Doyle < > 1926...@bugs.launchpad.net> wrote: > > > This should be fixed in the latest impish dailies -- Alfonso, do you > > still have a way to test this? > > > > Yes, I can reproduce it. I can try the fix if it is available in some > subiquity snap channel. > > > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1926137 > > > > Title: > > Error when starting copy to disk due to processes accessing /var/log > > > > Status in subiquity: > > New > > Status in casper package in Ubuntu: > > Fix Released > > > > Bug description: > > Installation fails when subiquity starts copying to disk due to some > > process accessing /var/log. The full crash log is > > > > https://paste.ubuntu.com/p/Jw4ndyQFzk/ > > > > The error happens only if re-installing on top of an already > > partitioned disk. I am using version 21.04.2+git1.2719c57c. > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/subiquity/+bug/1926137/+subscriptions > > > > > > -- > You received this bug notification because you are subscribed to > subiquity. > https://bugs.launchpad.net/bugs/1926137 > > Title: > Error when starting copy to disk due to processes accessing /var/log > > To manage notifications about this bug go to: > https://bugs.launchpad.net/subiquity/+bug/1926137/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926137 Title: Error when starting copy to disk due to processes accessing /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1926137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937115] Re: Unable to boot/install Impish daily in UEFI boot mode
Well this is a bit strange. Does anyone know when this started? The way the ISO is put together hasn't changed since the hirsute release, so this is probably related to a change in grub2 or shim. The bug was reported less than 24 hours after a new version of grub2 landed which is definitely something that makes one go "hmm". I'll reassign the package there -- this certainly isn't a syslinux problem as that hasn't been used at all to boot ISOs since focal, and afaik never ever when booting via UEFI. ** Package changed: syslinux (Ubuntu) => grub2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937115 Title: Unable to boot/install Impish daily in UEFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1937115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
So I don't have the faintest idea what caused this to start failing but the issue here is in mir: int (*real_open)(char const *path, int flags, mode_t mode); *(void **)(&real_open) = dlsym(RTLD_NEXT, "open"); return (*real_open)(path, flags, mode); The declaration for real_open here does not match that used by the open() function call in umockdev, which uses va_args. This means that the stack frame gcc creates for mir's wrapper does not have space for a parameter save area which the code gcc generates for umockdev assumes it has, and so the stack gets stomped on. So if the prototype in mir is fixed here (also the one for open64) I bet things will start working again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
Martin, right I thought I'd said that in my comment too about the prototype in the header but apparently I only thought it really loudly, or something :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
Simon, no fix has been uploaded yet? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937319] Re: namespace collision on url kernel arg results in downloading iso multiple times
I had a look at the code that does this download and the structure of the APIs used looks to make this kind of sniffing a bit awkward :( Nothing impossible of course but it's not going to be completely trivial either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937319 Title: namespace collision on url kernel arg results in downloading iso multiple times To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1937319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933523] Re: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs
** Changed in: livecd-rootfs (Ubuntu Focal) 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/1933523 Title: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1933523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
** Changed in: livecd-rootfs (Ubuntu Focal) 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/1888497 Title: Booting the install system does not always succeed, hence a remote ssh login is not always possible To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1888497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1902855] Re: two identical disks are only offered as a multipath device
On Thu, 5 Nov 2020 at 21:35, Matthias Klose <1902...@bugs.launchpad.net> wrote: > see also LP: #1871611, failing the install with disabled multipath. > That bug looked very much like the kernel losing its mind. Are you saying you can reproduce it? > However multipath is hard wired into the installer. > The intent is that what mulitpath-tools does on boot is reflected in the installer. If it is disabled by kernel command line or whatever, the disks should not be multipathed. It's possible this is not what happens, but it's not by design. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902855 Title: two identical disks are only offered as a multipath device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1902855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
** Also affects: subiquity Importance: Undecided Status: New ** Changed in: subiquity Status: New => In Progress ** Changed in: subiquity Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893775 Title: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1893775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902855] Re: two identical disks are only offered as a multipath device
*via the kernel command line -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902855 Title: two identical disks are only offered as a multipath device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1902855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902855] Re: two identical disks are only offered as a multipath device
I think there is no doubt that Matthias's disks are bad and the default behaviour is OK, but I would hope that disabling multipath via the kernel would allow an installation as desired. But it seems curtin doesn't quite work this way. Part of the issue IIRC is that the curtin multipath support doesn't assume multipathd is actually running, as for some versions of Ubuntu multipath-tools wasn't included in the environment curtin runs in. I don't think that's true for recent releases, but it might be true for xenial which MAAS presumably still has to support installing... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902855 Title: two identical disks are only offered as a multipath device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1902855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898614] Re: ubuntu server installer serial console not preserved after update
I'm going to mark this incomplete, as far as I can tell the installer restarts on the serial line just fine but I'm certainly interested to hear if you can reproduce the problem or find the logs! ** Changed in: subiquity 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/1898614 Title: ubuntu server installer serial console not preserved after update To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1898614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893818] Re: Several blockprobe errors if trying to install the groovy daily live on LPAR
** 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/1893818 Title: Several blockprobe errors if trying to install the groovy daily live on LPAR To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1893818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878041] Re: installation fails creating user on large multipath system - multipathd show command times out in curtin log with 163 paths
** Also affects: multipath-tools (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/1878041 Title: installation fails creating user on large multipath system - multipathd show command times out in curtin log with 163 paths To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1878041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893818] Re: Several blockprobe errors if trying to install the groovy daily live on LPAR
** Merge proposal linked: https://code.launchpad.net/~mwhudson/curtin/+git/curtin/+merge/392353 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893818 Title: Several blockprobe errors if trying to install the groovy daily live on LPAR To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1893818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901571] Re: rustc 1.47 and cargo 0.47 required by firefox 84
** Changed in: rustc (Ubuntu) Status: New => In Progress ** Changed in: rustc (Ubuntu) Assignee: Canonical Foundations Team (canonical-foundations) => Michael Hudson-Doyle (mwhudson) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901571 Title: rustc 1.47 and cargo 0.47 required by firefox 84 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1901571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907128] Re: Subiquity only provisions half of available space for root logical volume
This is by design. There's not much point in using LVM if you then completely fill up the volume group with a single logical volume -- you can't take snapshots, for example -- and expanding a LV later is much easier than shrinking one. ** Changed in: subiquity (Ubuntu) Status: New => Invalid ** Changed in: subiquity (Ubuntu) Status: Invalid => 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/1907128 Title: Subiquity only provisions half of available space for root logical volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1907128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901817] Re: subiquity installation (on s390x) reusing existing partitions fails with 'Network plugin raised an exception'
** Changed in: subiquity (Ubuntu) Status: New => Invalid ** Changed in: curtin 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/1901817 Title: subiquity installation (on s390x) reusing existing partitions fails with 'Network plugin raised an exception' To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1901817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878596] Re: [Ubuntu 20.04] - Install - problem
** Changed in: subiquity (Ubuntu) Status: Confirmed => In Progress ** Changed in: subiquity (Ubuntu Focal) 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/1878596 Title: [Ubuntu 20.04] - Install - problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1878596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876011] Re: Kernel Panic when dasd-fba device is selected for install
** Changed in: subiquity 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/1876011 Title: Kernel Panic when dasd-fba device is selected for install To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1876011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901571] Re: rustc 1.47 and cargo 0.47 required by firefox 85
So this is in hirsute or the rust-updates PPA now. Need to rebootstrap rustc on 1.47 on riscv but that's not really relevant for this bug. ** Changed in: cargo (Ubuntu) Status: New => Fix Committed ** Changed in: cargo (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: cargo (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: cargo (Ubuntu Focal) Status: New => Fix Committed ** Changed in: cargo (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: rustc (Ubuntu) Status: In Progress => Fix Committed ** Changed in: rustc (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: rustc (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: rustc (Ubuntu Focal) Status: New => Fix Committed ** Changed in: rustc (Ubuntu Groovy) Status: New => 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/1901571 Title: rustc 1.47 and cargo 0.47 required by firefox 85 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1901571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1732368] Re: upgrade to 17.03.2-ce in 16.04+
There is a new upload in UNAPPROVED that is waiting for review from Steve. This version will not migrate so may as well remove it. On Sat, 30 Jun 2018 at 03:32, Łukasz Zemczak <1732...@bugs.launchpad.net> wrote: > Is this being tested? The package has been waiting in the -proposed > pockets for 219 days now. Please perform verification in the nearest > week or I will be removing it from -proposed as per SRU policy. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1732368 > > Title: > upgrade to 17.03.2-ce in 16.04+ > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1732368/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732368 Title: upgrade to 17.03.2-ce in 16.04+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1732368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
