[07:54] <foo> I'm looking for a self-hosted system to read all python logs online. Someone suggested Vector. Anyone else want to cast their vote for this? https://vector.dev - got multiple systems pushing logs, I want them in something other than a text file so others can read them/filter them/sort 
[08:00] <frickler> https://grafana.com/oss/loki/ seems to be interesting, but I did't look at it in more detail yet
[08:05] <foo> frickler: thank you, I've heard about grafana
[08:05] <foo> frickler: but didn't consider it for logs, will research
[15:20] <eea> hello all, after habing read through the ubuntu discourse and several other sites and tools... i am not able to get a 20.04 server stood up in an unattended fashion
[15:20] <eea> using cloud-config
[15:20] <eea> looking for advice on how to acheive a working automated install
[15:21] <eea> on bare metal, not using maas
[15:21] <eea> or landscape
[15:38] <rbasak> eea: are you aware of https://ubuntu.com/server/docs/install/autoinstall ?
[15:39] <eea> rbasak: yes
[15:39] <rbasak> Does https://ubuntu.com/server/docs/install/autoinstall-quickstart not work for you?
[15:40] <eea> the only bit i can get to work is adding the user
[15:41] <eea> adding anything else results in installer stopping to ask questions
[15:41] <eea> passes yamllint and cloud-init checks
[15:42] <eea> i guess my real question here is how to best debug this process
[15:43] <eea> my log grok fu is failing me
[15:50] <rbasak> If you follow the quickstart instructions precisely step by step and without any adjustments, does it work?
[15:50] <rbasak> c
[15:53] <znf> how does your user-data look like?
[15:53] <znf> oh wait, cloud-config
[15:53] <znf> that's not the subiquity stuff, is it?
[15:53] <eea> i may be conflating terms
[15:53] <eea> subiquity is the beast i am currently fighting
[15:53] <znf> is this subiquity or the old debian installer?
[15:54] <znf> and which part is failing?
[15:54] <eea> great question, it does not tell me
[15:54] <eea> i will sanitize and post my config in a bit
[15:54] <znf> I'm using this bare-bones: https://pastie.dev/vwrCZq.yaml
[15:54] <znf> but I keep network and storage interactive on purpose
[15:55] <eea> my goal is to.automate both
[15:55] <eea> this installer will be used by very non technical.folk
[15:57] <eea> and all the hardware is identical
[16:00] <eea> even better question... how are the cool kids automating server/desktop deployments today?
[16:00] <eea> is my current issue specific to 20.04 i wonder
[16:22] <elyograg> I am having a problem with ubuntu-bug.  It opens chrome but never goes from the "refresh page every 10 seconds" page to the place where a bug summary can be entered.  Here to find out if I did something wrong or there is something about my server config that is making ubuntu-bug not work.  I did manually open the bug in launchpad, I'm here about the problem with ubuntu-bug itself.
[16:29] <znf> eea, the easiest way is to install a system manually, then copy the generate file
[16:29] <znf> and use that
[16:59] <eea> znf: that was one of my tests, but removing the serial number lines from the drives section broke something
[17:01] <eea> which reminds me... don't think i ran that mod thru the config checker
[17:02] <blackboxsw> eea: seeing autoinstall questions you had about the installer prompting for responses during the install instead of "just doing it".  Can you append the kernel commandline "autoinstall" at your boot menu? That tells autoinstall to do what you have configured with #cloud-config\nautoinstall: directives without waiting for prompts
[17:04] <eea> blackboxsw: i used https://github.com/covertsh/ubuntu-autoinstall-generator and did not double check the kernel params...
[17:04] <blackboxsw> I know in testing some autoinstall: directives myself that if I typo'd the -append kernel commandline, or forgot the "autoinstall" string then the instlaller sits and waits
[17:10] <blackboxsw> I haven't honestly used that script before, though I've seen it. I *looks like" it manipulates the kernel commandline to inject that autoinstall for you in the image From within the running install (if stopped at the installer prompt) you should be able to hit the "help" menu item "enter shell" and cat /proc/cmdline to see if autoinstall was presented there properly
[17:12] <blackboxsw> generally for testing locally, I had justspun up a local python http server with the examples rbasak pointed at from https://ubuntu.com/server/docs/install/autoinstall-quickstart  which allows you to use stock ubuntu server images and present your #cloud-config\nautoinstall: directives from that web service.
[17:14] <konstruktoid> seems easier to use Packer imo
[17:14] <blackboxsw> yet with that approach I mentioned, I had to edit the grub boot menu option with "e" and append the "--- autoinstall ds=nocloud-net;s=http://<IP_OF_YOUR_SERVICE>:<SOME_PORT>/" 
[17:24] <blackboxsw> I've seen examples like https://gitlab.com/kilo40/Packer_templates/-/blob/main/ubuntu-server-jammy.pkr.hcl for packer which look like (through boot_commands) they edit the kernel cmdline through the grub menu to append that autoinstall and ds=nocloud-net type directives as well. Though I haven't gone down that path myself
[17:24] <rbasak> konstruktoid: packer seems to use facilities that aren't expected to be stable, and then packer users complain to us about it when things change. So I wouldn't recommend that.
[17:24] <rbasak> Oh, maybe that's how people use packer, rather than packer itself?
[17:24] <blackboxsw> +1 rbasak on that sentiment... it's a maintenance the user undertakes to try to inject that content automatically
[17:25] <rbasak> Anyway, it seems like it's prone to being done wrong. There's really no need for packer when using Ubuntu, unless you want to use the same pattern for not-Ubuntu as well. We have cloud images which cover the VM use case much better, and for bare metal we have subiquity autoinstall.
[17:27] <konstruktoid> i guess we just have had different experiences then
 "I've seen examples like https..." <- yeah, that is basically the standard way of doing it using packer; one of mine https://github.com/konstruktoid/hardened-images/blob/master/ubuntu-hardened-box.pkr.hcl#L16-L23
[18:52] <eea> well, thanks to all who engaged with me earlier fumbling around with cloud-config
[18:52] <eea> i think i now have a working setup :)
[22:43] <Phibs> Anyone know how this is generated and how I can regenerate it myself since it's old? https://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html