[09:15] <jink> Why doesn't do-release-upgrade offer me 20.04 LTS?  I'm on 18.04.5 LTS and the system is fully up-to-date.
[09:18] <lotuspsychje> jink: the upgrade path sint open yet due some bugs the devs working on
[09:18] <lotuspsychje> jink: keep an eye on: https://discourse.ubuntu.com/t/focal-fossa-20-04-1-lts-point-release-status-tracking/17604
[09:19] <jink> Bedankt weer. ;)
[09:19] <lotuspsychje> np ; ) we assume it will get fixed soon
[09:19] <jink> 👍
[14:19] <KaiH> Hi, which tool can you recommend to use update servers? I use usually aptitude, but heard it's not really good for Ubuntu.
[15:08] <jayjo_> Is using KVM, libvirt,and qemu manually a suitable replacement for production VMs on ubuntu server? Compared to something like proxmox ? I've been trying to virtualize pfsense on a server in a way to that will reboot automatically. I've been able to test with my desktop through other environments, but i'm having a harder time finding non-interactive solutions
[15:12] <cpaelzer> jayjo_: it is perfectly fine to be used just through libvirt/qemu with CLI+XML files
[15:12] <cpaelzer> the amoutn of management stacks on top that you want depends on your preferences
[15:13] <cpaelzer> I mean you can go up to full openstack which underneath still will use the same qemu/libvirt but certainly is quite dfferent :-)
[15:49] <rbasak> jayjo_: in what sense are you considerned that the stack you propose isn't suitable for production VMs?
[15:49] <rbasak> jayjo_: in what sense are you *concerned* that the stack you propose isn't suitable for production VMs?
[15:55] <jayjo_> rbasak: I'm just in the weeds getting things functional. I'm trying to document the init procedure, or get it to an 'always-restart' point
[15:55] <jayjo_> I've used virt-manager, i"m trying to port that method that I had working on a desktop to the ubuntu-server
[15:59] <jayjo_> RHEL uses qemu/kvm as well. Will their resources have diverged from debian/ubuntu? (Just interested in https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/virtualization_administration_guide/index - is there an ubuntu equivalent?)
[16:07] <cpaelzer> jayjo_: every distribution has diverged from upstream a bit as on any package that is so heavily used - but never the less they are still (in terms of docs) used mostly the same
[16:07] <cpaelzer> jayjo_: you can look at the virtualization chapters of https://ubuntu.com/server/docs
[16:08] <cpaelzer> it is not re-explaining every bit of the manpages to make more pages :-), but it is a start
[16:13] <jayjo_> cpaelzer: thanks for your feedback - I appreciate the help
[17:18] <rbasak> cpaelzer: how do you want to triage https://bugs.launchpad.net/qemu/+bug/1894804 ?
[17:24] <rbasak> ahasenack: you triaged https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153 previously and seem to understand the reported problem, but there aren't steps to reproduce given and I don't follow. Mind taking a look please? Is the issue Invalid now that the reporter has confirmed back?
[17:24] <ahasenack> rbasak: yes, local config problem
[17:25] <ahasenack> rbasak: not to say we can't improve it
[17:25] <ahasenack> rbasak: he had a working autofs config, then for unknown reasons installed sssd with its own autofs map, but without configuring it, and that broke his local autofs setup
[17:25] <ahasenack> rbasak: he doesn't know why he had sssd installed
[17:26] <ahasenack> I left it as is because he said we would try an upgrade or fresh install of his apps, and see if something pulled in sssd when it shouldn't
[17:32] <rbasak> ahasenack: maybe Incomplete then, pending his response? Because there's nothing actionable for us to do unless he gets back to us, is there?
[17:33] <ahasenack> well, we could investigate if there is something to be done regarding the interaction of an unconfigured sssd and an existing autofs setup
[17:33] <rbasak> OK thanks. I'll note that then, mark Low and add to the backlog