[03:54] <fluvvel> I've installed ubuntu 18 on a new Intel motherboard with secure boot installed (EFI) -all went well, booted, ran etc. Then discovered I needed a custom kernel. Can't seem to reset, reinstall for love nor money
[03:55] <fluvvel> have turned off secure boot and turned on legacy in BIOS but no avail. keeps saying no bootable drive
[03:58] <sarnold> I suggest turning UEFI back on; you can either disable secure boot in the bios or maybe try this mokutil --disable-validation  command listed here https://wiki.ubuntu.com/UEFI/SecureBoot/DKMS  --- or you could sign things, if you wished
[04:02] <fluvvel> ok, will try, think I already did try that but I've deleted the keys from the bios at this stage.
[04:02] <fluvvel> Signing sounds fun, but potentially complicated.
[04:05] <sarnold> yeah it seemed a bit of a hassle to me, I'd probably have to have a huge fleet of machines before I'd want to put in that kind of effort :)
[04:05] <sarnold> two or three.. naaaah
[04:16] <JanC> maybe if you need the security...
[04:20] <fluvvel> what I need is to just wipe and start from scratch
[04:24] <sarnold> heh, that might be quickest
[04:24] <sarnold> but it doesn't feel great, you know?
[06:59] <eandersson> Who do I talk about adding components to OpenStack services? frickler sent me!
[07:00] <eandersson> I added two new services to OpenStack Senlin https://review.opendev.org/#/c/688784/
[07:01] <eandersson> and need to have the Ubuntu packages updated to support them.
[09:18] <frickler> eandersson: most likely adding an issue at https://bugs.launchpad.net/ubuntu/+source/senlin would be helpful, then maybe jamespage or coreycb can take a look
[09:19] <jamespage> eandersson, frickler: yep raise a bug and we'll get to it with the next round of updates
[09:27] <calcmandan> i'm installing a fresh server. manually handling the partitioning. 2 4tb drives. setting root on one, and home on the other. is 500mb suffician for the efi boot partition?
[13:46] <frickler> jamespage: coreycb: another python3 compat issue: openstack-dashboard-common contains some python scripts like /usr/share/openstack-dashboard/manage.py which start with "#!/usr/bin/env python" which fails when python3-django-horizon is installed
[13:47] <frickler> (this is on rocky, didn't double check newer releases yet)
[13:48] <frickler> well the previous should read "... when python3-django-horizon is installed instead of python-django-horizon"
[13:50] <frickler> oh, the post-inst has this code http://paste.openstack.org/show/787165/ and then calls $PYTHON manage.py, likely I can do the same in our automation
[14:15] <coreycb> frickler: is that an issue in your own postinst script or in ours? it looks ok on rocky. that shebang originates from the upstream code and I think it needs to remain as-is until py2 support is dropped.
[14:24] <frickler> coreycb: the issue in our own code that calls manage.py on certain occasions. yes, once py2 is gone, things should be simpler again. the other solution would have been moving those scripts from -common into the python(3)-* pkgs and handle them via /etc/alternatives like some other binaries
[14:24] <frickler> but as I said we can likely work around that
[14:26] <coreycb> frickler: yes alternatives would've been a good approach. alright let me know if you need anything. thanks.
[17:06] <lopta> What software would a person use to deploy Ubuntu Server to a cluster of compute nodes?
[17:11] <lordcirth_> lopta, MaaS, or simply dnsmasq to PXE boot
[17:11] <lopta> brb, phone
[17:32] <lopta> lordcirth_: Thanks