=== benpro9 is now known as benpro
=== halvors1 is now known as halvors
[13:56] <icey> hey rafaeldtinoco cpaelzer: https://bugs.launchpad.net/ubuntu/+source/python-rtslib-fb/+bug/1865037 is currently blocking Cinder's autopkgtests, how can we push on getting that fixed sooner rather than later?
[13:56] <ubot3> Launchpad bug 1865037 in python-rtslib-fb (Ubuntu) "make the service fail gracefully if unable to load modules" [High, Triaged]
[14:09] <rafaeldtinoco> icey: I need someone from the server team to take over for this one
[14:09] <rafaeldtinoco> cpaelzer: ^
[14:10] <rbasak> He's out at the moment oo
[14:10] <rbasak> too
[14:10] <rafaeldtinoco> oops
[14:48] <sveinse> Are there any advantages on reinstalling a production server with 20.04 as opposed to upgrading it from 18.04 to 20.04 using do-release-upgrade? E.g. keeping a server clean is a good thing, and doing upgrade will bring some things along with it, right? Any opionions on what you would've done?
[14:55] <rbasak> The best approach is to automate your server deployment so it's reproducible. And ideally you'd also have automated tests to ensure that your automation does what you expect it to do before you deploy it into production. At that point it generally makes sense to redeploy rather than upgrade.
[14:57] <rbasak> The further away you are from that, it might take less effort but you risk more issues in production. So it's all about how that trade-off works in your situation. Eg. how important production uptime is for you, etc.
[16:01] <frickler> another thing to watch out for is additional ppas or other sources, those may break the release-upgrade
[16:03] <sveinse> rbasak: thanks. I agree, reproducability is a good point.
[16:11] <sveinse> I mean testing this deployment starting from an existing 18.04 is one thing. Later recreating a server to 20.04 from scratch would yield something else.
[19:11] <SpaceBass> Hey folks, I am in the process of migrating from one LDAP server to another for authorization. I can successfully getent passwd and list users. But when I try and log in, it cannot create the home directory. But, the home directories are listed in the LDAP server and they are the same as the old LDAP server
[19:11] <SpaceBass> Basically I have the same users with the same UIDs and same directories, but it seems like something isn't working
[19:44] <sarnold> SpaceBass: check the logs of all the moving pieces -- PAM logs on the clients, whatever it you replaced ldap with on the whatever it is you replaced ldap with server, etc
[19:45] <SpaceBass> Thanks! Noticed that getent paswd doesn't show the user directories from the LDAP accounts
[19:46] <SpaceBass> Will try and debug pam
[19:51] <sarnold> getent may by a missing nss library or /etc/nsswitch.conf misconfiguration?
[19:52] <SpaceBass> Hummm I'll double check my nsswitch
[20:01] <SpaceBass> Thanks sarnold ! Problem solved....nss mapping issue
[20:01] <sarnold> SpaceBass: yay :)
[20:34] <daftykins> !cookie | sarnold
[20:34] <ubot3> sarnold: Wow! You're such a great helper, you deserve a cookie!
[20:35] <sarnold> \o/ YAY COOKIES \o/
[20:35] <teward> sarnold actually owes me cookies right now so :P
[20:35] <teward> *takes the cookies from sarnold*
[20:37]  * sarnold notes down .. teward .. cookie thief
[20:39] <teward> *gives sarnold girl scout cookies in place of ubot's inferior cookies*
[20:39] <sarnold> oh man I love those :D
[21:00] <teward> i found the supply source in my township so :P
[21:16] <daftykins> don't even have to have them come door to door eh?