/srv/irclogs.ubuntu.com/2021/03/25/#ubuntu-devel.txt

=== jamesh_ is now known as jamesh
=== not_phunyguy is now known as phunyguy
=== not_phunyguy is now known as phunyguy
=== jamesh_ is now known as jamesh
cpaelzerutkarsh2102: doko has asked if you could look at https://launchpad.net/ubuntu/+source/ruby2.7/2.7.2-4ubuntu1 ?09:36
* doko is on leave ...09:37
utkarsh2102cpaelzer: absolutely, the arm64 failure I suppose?10:03
utkarsh2102ah, that and also regression on s390x: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ruby2.710:24
sil2100cpaelzer: hey! I have been poked about a chrony ADT regression for s390x with the new dpkg - was wondering if maybe you or someone from the server team could take a look to see what could be happening there?10:27
cpaelzersil2100: you are the second to ask, it seems to be LTO10:45
cpaelzersil2100: and I'm already on it10:45
sil2100cpaelzer: excellent to hear!10:54
cpaelzersil2100: this case is ugly, it tries to throw red herrings at me in every possible step *sigh*11:18
cpaelzerthanks for the bug filing sil210011:42
cpaelzeryou'll smile when you see al my updates that are incoming to that ... :-)11:42
sil2100cpaelzer: wow, thanks for the detailed investigation! ;)11:54
sil2100This is really a good read11:54
cpaelzersil2100: if you could maybe have a look for silly mistakes on https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/400182 and ack it if ok ?11:59
cpaelzerI'll make cross arch build and cross arch test a requirement for uploading anyway - so consider that covered11:59
utkarsh2102doko: fwiw, this test in ruby-ferret is known to be problematic; we previously hit that on arm64 and it seems now on s390x but unfortunately, I can't seem to reproduce the failure (using canonistack VM); 7/7 passing, no failures :(12:19
utkarsh2102that said, c_paelzer has re-triggered the tests twice on my request. so let's see. (Ik you did already)12:20
utkarsh2102doko: passing both, yay! \o/12:33
sil2100cpaelzer: looking in a moment!12:44
eoli3n_is there a way to make sure that avahi-daemon can't run ? if i remove the package and hold it in my ansible playbook, it seems to come back as dep of another package. If i disable avahi-daemon.socket and avahi-daemon.service, reboot, it is still running...13:45
rbasakeoli3n_: https://askubuntu.com/a/816378/780814:23
rbasakI think you want "mask" rather than "disable".14:24
rbasakYou could also pin avahi-daemon to something negative in apt.14:25
rbasakBut I would investigate why you need a package that depends on it first.14:25
eoli3n_thanks rbasak15:05
eoli3n_xnox i face this again : https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/188223215:55
ubottuLaunchpad bug 1882232 in chromium-browser (Ubuntu Focal) "Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)" [Medium,Fix released]15:55
eoli3n_with desktop iso live system, my ansible playbook hangs, then fail at the task of installing chromium-browser15:56
eoli3n_(just a sec for logs)15:56
xnoxeoli3n_:  fun.15:57
eoli3n_not sure if i would use that word but... :)15:57
xnoxeoli3n_:  where is your playbook running? cause i thought we fixed that, to detect that things are well not running.15:57
eoli3n_in a chroot15:58
eoli3n_i fixed that15:58
eoli3n_s/i/we15:58
eoli3n_s/we/you15:58
eoli3n_:)15:58
xnoxeoli3n_:  however, since that was fixed, we did add preseeding support => so chroot has many snaps things prepopulated.15:58
xnoxeoli3n_:  maybe open a new bug report? and say that this previous bug, has now regressed?15:58
xnoxeoli3n_:  i can't remember what your desired end state was; and what was done to get there.15:59
eoli3n_i don't think that it has regressed15:59
eoli3n_because it is still working with kickstart15:59
eoli3n_and the netboot iso15:59
eoli3n_i just want to install chromium-browser with ansible in a chroot with a ubiquity late command16:00
eoli3n_success command*16:00
xnoxand there is no way today to otherwise tell the installer "and please install these snaps"16:00
xnoxcause in the future we'd need to grow that capability.16:01
xnoxeoli3n_:  yeah, we did changes in focal, that may not result in that working anymore correctly..16:01
xnoxlet me open a new bug report about that.16:01
eoli3n_https://x0.at/BwI.txt16:01
eoli3n_but i don't get what difference between preseeding desktop main iso, and kickstarting netboot iso16:01
xnoxlots16:02
eoli3n_oh ok16:02
xnoxdesktop already has some snaps in partially installed state16:02
eoli3n_but it should concern the package, and not the installer, doesn't it ?16:02
xnoxwhere snapd is paused, at half-preseeded state.16:02
eoli3n_ok ok, you know better :)16:02
xnoxwith many snaps preinstalled.16:02
xnoxthe netboot.iso has no snaps.16:02
xnoxopened https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/192140516:03
ubottuLaunchpad bug 1921405 in chromium-browser (Ubuntu) "preseeded snaps prevent installing chromium-browser deb2snap in chroot, again" [Undecided,New]16:03
eoli3n_you can add the task log in the bug report if you want16:03
eoli3n_you're fast ! thanks again for your help16:04
eoli3n_shouldn't the installer create an efi entry in boot manager automatically ?16:38
=== ijohnson is now known as ijohnson|lunch
xnoxeoli3n_:  yes, no, maybe. it doesn't matter.17:11
xnoxeoli3n_:  it can do it on first boot too.17:11
xnoxeoli3n_:  also, who knows if your firmware honors it.17:11
xnoxif you force it to always netboot, it may ignore BootNext / BootOrder.17:11
eoli3n_at the first boot, i get my firmware configuration screen, if i select my hard drive, then it "creates ubuntu entry" but it doesnt use grubx64.efi17:16
xnoxwhy should it use grubx64.efi ?! =)17:28
xnoxeoli3n:  also sounds like your firmware is buggy, if you want to select a hard drive => if you are in OVMF qemu KVM, did you set bootoder on your drives / network card?17:28
xnoxwe never boot with grub directly.17:29
eoli3n_the firmware is ipxe used by qemu as main one17:29
eoli3n_" if you are in OVMF qemu KVM, did you set bootoder on your drives / network card?" in the firmware ?17:30
eoli3n_nop17:30
eoli3n_problem is that i configured netplan to use networkd for "eth0" and i configured my cmdline in /etc/default/grub17:31
eoli3n_to use old dev names17:31
eoli3n_"18:29 xnox: we never boot with grub directly." I don't understand what you mean17:32
eoli3n_the firmware chainloads grub, then grub loads kernel and initramfs17:32
xnoxfalse17:38
xnoxfirmware should chainload shim, which chainloads grub.17:38
xnoxand shim can choose if it will boot fwupdate, fb, mm, or grub.17:38
xnoxor even reset again.17:39
xnoxeoli3n_:  if you configured things right, there shouln't be a problem. If there is a problem, maybe some of the config is missing.17:39
xnoxeoli3n_:  and i would recommend you to _not_ force eth0 names. Becuase netplan & networked can match on all ethernet device irrespective of how they are named. And it is best to use stable names, rather than eth0.17:40
xnoxeth0 breaks a lot.17:40
eoli3n_stable names on a host is not a stable name on 800 hosts17:41
eoli3n_but why not drop this and configure netplan without hard configure a net card17:42
=== pfsmorigo is now known as Guest8748
xnoxeoli3n:  that's the point. 800 hosts should have 800 different ethernet names, and that should be ok.17:44
=== gusnan_ is now known as gusnan
xnoxeoli3n_:  hi?17:44
xnoxthere are two of you and you had a netsplit?17:44
xnoxeoli3n:  that's the point. 800 hosts should have 800 different ethernet names, and that should be ok.17:44
xnoxfor example, what's your kernel commandline? and did you specify your cmdline changes are `---` such that it gets copied into target too?17:45
eoli3n_xnox something strange happened here :)17:46
eoli3n_BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=cfd0c620-61ab-4887-977c-5138febf933e ro net.ifnames=0 biosdevname=0 ipv6.disable=1 quiet splash17:47
xnoxthere are rolling restarts of freenode at the moment.17:47
xnoxeoli3n_:  is that how you boot the installer, or how you boot the installed system?17:48
xnoxeoli3n_:  looks ok.17:48
eoli3n_ah no17:48
eoli3n_that's how i boot my hosts17:48
xnoxeoli3n_:  how do you boot the installer?17:48
eoli3n_on the first boot17:48
eoli3n_without this17:48
eoli3n_the unmatch is problematic i guess17:49
xnoxwithout what?17:49
eoli3n_net.ifnames=0 biosdevname=017:49
eoli3n_here my installer cmdline : imgargs vmlinuz initrd=initrd rootfstype=nfs netboot=nfs nfsroot=162.38.151.26:/exports/focal-desktop boot=casper ip=dhcp fsck.mode=skip automatic-ubiquity debian-installer/language=fr console-setup/layoutcode=fr console-setup/variantcode=oss url=http://162.38.151.26/preseed/fds/focal-efi.seed quiet17:50
xnoxi expect you to boot the installer as " linux /boot/vmlinuz-xyz ip=dhcp <anything installer related> --- net.ifnames=0 biosdevname=0 ipv6.disable=1 quiet splash17:50
xnox"17:50
eoli3n_ah ok, but i don't get what it does17:50
xnoxbecause then things after "---" will not only be active during the installation, but will also be copied into target's installed system.17:50
eoli3n_ok ! good to know17:50
xnoxsuch that you don't need to manually configure custom kernel cmdline.17:50
eoli3n_where will it be written ?17:51
eoli3n_on the target ?17:51
xnoxcause it's like "my systems need these kernel args and copy them into target too"17:51
xnoxeoli3n_:  i think it like modifies /etc/defaut/grub* something17:51
eoli3n_that's what ansible does17:51
eoli3n_for me17:51
eoli3n_that's the strange part17:51
eoli3n_when i first boot the hard drive in qemu/kvm, then it "creates ubuntu entry" but i runs with shim file17:52
eoli3n_s/i/it17:52
eoli3n_so grub cannot append cmdline17:52
eoli3n_or i misunderstand something17:52
=== themill_ is now known as themill
=== ogra_ is now known as Guest8511

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!