Monday, 2024-02-05

*** jph0 is now known as jph08:25
*** ralonsoh_ is now known as ralonsoh08:56
opendevreviewElod Illes proposed openstack/project-config master: [relmgt] Update reno when cutting unmaintained branch  https://review.opendev.org/c/openstack/project-config/+/90762610:11
opendevreviewMerged openstack/project-config master: [relmgt] Update reno when cutting unmaintained branch  https://review.opendev.org/c/openstack/project-config/+/90762613:00
bauzasI was getting weird timeouts when accessing review.opendev.org14:04
bauzasnow this is fixed, but some friends (not from work) seem to get the same timeouts that I was having 14:04
bauzasnot sure it's a problem from the server or something about the ISP14:05
fungibauzas: the gerrit server runs in vexxhost, and one of the backbone providers they peer with has been having problems. seems to mostly be affecting transatlantic connections14:17
bauzasahah, thanks for the explanation14:18
bauzasI was indeed thinking about a peering issue14:18
bauzasmy ISP is connected to review.opendev.org thru Cogent, maybe that helps to define which SAs are getting trouble14:22
bauzasAS*14:23
fungiyes, recently cogent has been fine but zayo (formerly abovenet) has been problematic14:23
fungithough it's hard to know for sure where your connections are routed through since they may not be symmertic and a traceroute will only show you the outbound hops14:24
bauzasI just checked with traceroute14:24
bauzasand I saw cogent14:24
bauzasunfortunately when I got my timeout, I haven't checked by traceroute14:24
bauzasbut I can ask priteau to doublecheck14:24
fungipeople may be reaching vexxhost through cogent but then responses may be coming back to them through zayo, but their traceroute will only show the cogent path14:24
bauzashe seems to get the problem14:24
fungiwe can also traceroute back to client ip addresses from the gerrit server to get the other half of the picture14:25
bauzasahah I see14:25
priteauI don't have connectivity issues at all, however I cannot log into Gerrit anymore14:25
bauzasI thought AS peerings were more symmetric but you're making the point14:25
priteauIt says: Provider is not supported, or was incorrectly entered.14:25
bauzaspriteau: can you traceroute review.opendev.org ?14:26
fungipriteau: mmm, that sounds like you're failing to log into the gerrit webui via ubuntuone sso?14:26
bauzaspriteau: my own https://paste.opendev.org/show/bIwgG0AhnWxxfQxTVRJ7/14:26
bauzasfungi: when I got impacted, Gerrit was telling me I needed to reauth14:27
bauzasnow that I'm able to reach it correctly, Gerrit doesn't ask me to refresh my creds14:27
priteaubauzas: Similar trace for the last few hops14:28
fungibauzas: it's not just you. looks like gerrit logins are broken again for everyone14:28
fungipriteau: you i mean14:28
priteauThanks for confirming14:28
priteauGood luckā€¦14:28
bauzassuper strange, because once my connection went back, my token was still valid and I didn't login again14:28
fungii just logged out of the gerrit webui and can't log back in either. we saw this recently. may need to restart gerrit to force obtain another openid handle from ubuntuone14:29
bauzas++14:32
fungino, the last time the association handle we were using changed was 2024-01-23 19:38:03 utc, when forced it to refresh by restarting gerrit. it hasn't changed since then14:43
funginow as i'm testing, the redirect to ubuntuone is timing out, so maybe they're the ones having an issue this time14:47
fungiaha, not us according to the chatter in #launchpad14:49
fungihttps://ubuntu.social/@launchpadstatus14:49
fungihttps://status.canonical.com/14:50
fungiokay, seems to be working again for me now14:54
fungipriteau: try again?14:54
priteauIt's working now, thanks14:54
fungijust glad it wasn't a problem on our end. i was preparing to lose half my day to another openid problem14:55
frickleroutage is still ongoing according to #launchpad, so expect more hickups15:34
fungijoyous15:45
clarkbfungi: I made note of the symptom to check for in the docs update for the hanlde thing. basically we awnt to look for a new handle and then no successful auth attempts afterwards16:14
fungiclarkb: yep, that's what i did, and how i determined that i should check #launchpad for signs of a struggle ;)16:16
clarkbcool just want to make sure that info was available16:16
fungialso that we weren't logging auth failures anywhere i could find this time, i think it wasn't getting that far16:17
clarkbmakes sense if the issue was on the ubuntu side as we won't get the redirect back to gerrit which triggers the failure on our side16:17
*** mtreinish_ is now known as mtreinish18:24
*** dasm is now known as Guest173920:33
*** Guest1739 is now known as dasm20:38

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!