/srv/irclogs.ubuntu.com/2024/08/07/#launchpad.txt

=== guruprasad changed the topic of #launchpad to: Launchpad DB upgrade underway - some downtime is expected | Help contact: ruinedyourlife (07:00-15:00 UTC) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad"
=== graber1 is now known as graber
=== graber1 is now known as graber
=== guruprasad changed the topic of #launchpad to: Launchpad DB upgrade complete - please report any issues | Help contact: ruinedyourlife (07:00-15:00 UTC) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad"
=== graber1 is now known as graber
antoninHi, I land here because I cannot login in https://launchpad.net/hugin despite an account created severals days ago. (Error ID: OOPS-1ee7b440bb69ca18943eb6579d2854cd). I then succeeded login in https://help.launchpad.net/ without finding where to post my error id. Can anyone help me ? Thank you.08:31
guruprasadantonin, checking08:56
guruprasadantonin, there was a Launchpad account auto-created with your email address while importing bugs from an external bug tracker. That was causing an error with the creation of your current account. I have merged the two now and you should be able to log in.09:02
antoninHi, I land here because I cannot login in https://launchpad.net/hugin despite an account created severals days ago. (Error ID: OOPS-1ee7b440bb69ca18943eb6579d2854cd). I then succeeded login in https://help.launchpad.net/ without finding where to post my error id. Can anyone help me ? Thank you.09:08
antoninWonderfull snap @guruprasad. Thank you very much.09:09
antonin((sorry I played with the mouse wheel over the text input before submitting, which took a previous message))09:10
=== graber1 is now known as graber
cjwatsonGood to see the PostgreSQL 12 upgrade being completed!14:21
cjwatsonI'd tried to get as far as I could on that before I left, but just ran out of time ...14:22
guruprasadcjwatson, we just reaped the benefits of all your hard work and with wgrant running the show, everything was straightforward.14:38
guruprasadNow, we have a mandate to upgrade to the new Postgres charms and to Postgres 16 asap and that is going to be a challenge that we have to deal with.14:39
guruprasadOne of the reasons for that being the ability of the new charms to help avoid downtime. I don't know any details regarding this and need to check with wgrant and the team.14:40
cjwatsonguruprasad: new charm> lol, good luck, I always thought that was infeasible17:14
cjwatsonat the very least you'd probably have to get onto an even newer pg version first17:14
guruprasadThis is not the first tiem I am hearing similar feedback about the new charm :)17:20
guruprasad*time17:20
guruprasadBut unfortunately, we can no longer rely on "Colin/William said so" and will have to do our research and go back with actual technical reasons as to why we cannot use it, if there are issues with the new charm.17:21
guruprasad"Colin/William said so"> those were great times ;)17:21
cjwatsonyeah, I'm not surprised Mark was able to force it now18:06
cjwatsonmaybe the charm's authors will eventually listen to the need for some manual control18:06
cjwatsonI'd suggest making very sure of the state of DB backups (including point-in-time recovery) first!18:07

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