infra/tickets
24
11
Fork 1
Code Issues 76 Projects Wiki Activity Actions

Authentication issues #13482

New issue
Closed
opened 2026-07-30 17:03:57 +00:00 by kevin · 37 comments
kevin commented 2026-07-30 17:03:57 +00:00
Owner
Copy link

Description of request

Our ipa cluster is fully reinstalled now, but there are still issues we need to sort out:

user facing/high priority:

  • https://accounts.fedoraproject.org is sometimes not allowing people to login. It gives a 'Unauthorized: bad credentials'. This seems sporadic and unclear how many people it effects.
  • fasjson is working, but slow to respond. This can result in things like matrix bots not responding to queries and the like.

internal/lower pri:

  • there are some replication schema errors on ipa01/ipa02 we should fix.
  • many openshift apps are hard coded to use ipa03. I think we can drop this to have them use dns
  • Other things are hard coded to one ipa server, we should try and switch to dns/the cluster
### Description of request Our ipa cluster is fully reinstalled now, but there are still issues we need to sort out: user facing/high priority: * https://accounts.fedoraproject.org is sometimes not allowing people to login. It gives a 'Unauthorized: bad credentials'. This seems sporadic and unclear how many people it effects. * fasjson is working, but slow to respond. This can result in things like matrix bots not responding to queries and the like. internal/lower pri: * there are some replication schema errors on ipa01/ipa02 we should fix. * many openshift apps are hard coded to use ipa03. I think we can drop this to have them use dns * Other things are hard coded to one ipa server, we should try and switch to dns/the cluster
kevin self-assigned this 2026-07-30 17:03:57 +00:00
mwinters commented 2026-07-30 17:48:41 +00:00
Contributor
Copy link

FYI: Retry your login

The FAS lockout threshold has been temporarily increased to allow people to retry their login until it works. The current threshold is 100 failed attempts in 10 minutes.

## FYI: Retry your login The FAS lockout threshold has been temporarily increased to allow people to retry their login until it works. The current threshold is 100 failed attempts in 10 minutes.
kevin commented 2026-07-30 18:10:37 +00:00
Author
Owner
Copy link

I have also readded all the servers to internal dns and redeployed noggin, so accounts may work more reliably now.
We are still looking for the root cause.

I have also readded all the servers to internal dns and redeployed noggin, so accounts may work more reliably now. We are still looking for the root cause.
zlopez commented 2026-07-31 09:05:03 +00:00
Owner
Copy link

There is also IPA web UI authentication issue, do we want separate ticket for that or just add it to this one?

There is also IPA web UI authentication issue, do we want separate ticket for that or just add it to this one?
zlopez commented 2026-07-31 10:33:49 +00:00
Owner
Copy link

Oh, I was able to login now, not sure if I fixed that by #13486 or it is just a coincidence.

Oh, I was able to login now, not sure if I fixed that by https://forge.fedoraproject.org/infra/tickets/issues/13486 or it is just a coincidence.
kevin commented 2026-07-31 17:50:24 +00:00
Author
Owner
Copy link

I have been able to login fine for a while, so I hope that issue is solved/gone.

I think everything is back to normal now... if anyone is seeing any problems, please let us know.

I have been able to login fine for a while, so I hope that issue is solved/gone. I think everything is back to normal now... if anyone is seeing any problems, please let us know.
spot commented 2026-07-31 19:03:11 +00:00
Copy link

So, I can login here, but accounts.fedoraproject.org still says "Unauthorized: bad credentials." I have 2FA enabled, if that makes a difference.

So, I can login here, but accounts.fedoraproject.org still says "Unauthorized: bad credentials." I have 2FA enabled, if that makes a difference.
kevin commented 2026-07-31 19:17:22 +00:00
Author
Owner
Copy link

😢

@abompard any ideas? can we get more verbose logs out of noggin?

😢 @abompard any ideas? can we get more verbose logs out of noggin?
flrnd commented 2026-08-01 09:55:40 +00:00
Copy link

Hi, I'm getting lately 400 Bad request every time I try to log in the first time. As I've observed, the authentication is successful but something in between the flow when tries to redirect back to forge goes wrong, getting the 400 response. Next try always is a 401 and the third time I click sign in, just acts as it nothing happens and let me in.

I also have 2FA

Ive tried with both Firefox and Chrome (with and without extensions)

Hi, I'm getting lately 400 Bad request every time I try to log in the first time. As I've observed, the authentication is successful but something in between the flow when tries to redirect back to forge goes wrong, getting the 400 response. Next try always is a 401 and the third time I click sign in, just acts as it nothing happens and let me in. I also have 2FA Ive tried with both Firefox and Chrome (with and without extensions)
👍 1
catanzaro commented 2026-08-01 12:57:41 +00:00
Copy link

I'm seeing the same behavior as flrnd using Epiphany Tech Preview with WebKitGTK 2.53.4. Most recently, just now:

400 - Bad Request
Invalid transaction id

If the error persists and if you think this is an error, contact Fedora Infra to resolve the problem.

This has been ongoing for several months now.

I'm seeing the same behavior as flrnd using Epiphany Tech Preview with WebKitGTK 2.53.4. Most recently, just now: > 400 - Bad Request >Invalid transaction id > >If the error persists and if you think this is an error, contact Fedora Infra to resolve the problem. This has been ongoing for several months now.
kevin commented 2026-08-01 15:19:04 +00:00
Author
Owner
Copy link

Hi @flrnd and @catanzaro The 400 issue is tracked in #13280

This is about accounts.fedoraproject.org login. Please lets keep issues in one place?

Hi @flrnd and @catanzaro The 400 issue is tracked in https://forge.fedoraproject.org/infra/tickets/issues/13280 This is about accounts.fedoraproject.org login. Please lets keep issues in one place?
👍 1
flrnd commented 2026-08-01 18:04:24 +00:00
Copy link

@kevin sorry! missed that 🙏

@kevin sorry! missed that 🙏
kevin commented 2026-08-01 18:29:48 +00:00
Author
Owner
Copy link

No problem at all... sorry if I came accross grumpy there... Hopefully we can fix this and that bug too.

No problem at all... sorry if I came accross grumpy there... Hopefully we can fix this and that bug too.
❤️ 1
py0xc3 commented 2026-08-03 16:36:37 +00:00
Copy link

I observed two things that are not yet documented, so I add them for the record, although I assume both have limited value:

  1. while Firefox experienced the issue always, I could use accounts.fp.org in Falkon without issues. I tried in Firefox again while I was logged in with Falkon, but the issue remained in Firefox. It also remained after I logged out in Falkon.

  2. after I deleted the cached files of firefox ("temporary cached files and pages" -> I did NOT delete "cookies and site data"), the issue was gone. We'll see if it comes back.

I use a default Firefox from our repos, up to date as of today, 153.0 (64-bit). Security settings are strict (but with "fix major site issues" enabled as recommended) and I have uBlock enabled (I do NOT use noScript at the moment:). Accounts used to work fine in the past with these settings, but I didn't use it for several months I think.

Since I cleared my cache, I can no longer reproduce the issue, but If there is anything specific to test or to document when the issue comes back, let me know.

I observed two things that are not yet documented, so I add them for the record, although I assume both have limited value: 1) while Firefox experienced the issue always, I could use accounts.fp.org in Falkon without issues. I tried in Firefox again while I was logged in with Falkon, but the issue remained in Firefox. It also remained after I logged out in Falkon. 2) after I deleted the cached files of firefox ("temporary cached files and pages" -> I did NOT delete "cookies and site data"), the issue was gone. We'll see if it comes back. I use a default Firefox from our repos, up to date as of today, 153.0 (64-bit). Security settings are strict (but with "fix major site issues" enabled as recommended) and I have uBlock enabled (I do NOT use noScript at the moment:). Accounts used to work fine in the past with these settings, but I didn't use it for several months I think. Since I cleared my cache, I can no longer reproduce the issue, but If there is anything specific to test or to document when the issue comes back, let me know.
zlopez commented 2026-08-05 09:46:05 +00:00
Owner
Copy link

I think I fixed the auth issue with IPA web UI. It seems the password max failures was set to 0, and locked user immediately after one failure. I set it to six and it seems to work.

I think I fixed the auth issue with IPA web UI. It seems the password max failures was set to 0, and locked user immediately after one failure. I set it to six and it seems to work.
❤️ 1
kevin commented 2026-08-05 14:49:21 +00:00
Author
Owner
Copy link

Strange. I set that to 100 when we were having problems last week... unless it was a different setting, or somehow got reset?

Strange. I set that to 100 when we were having problems last week... unless it was a different setting, or somehow got reset?
zlopez commented 2026-08-10 11:36:44 +00:00
Owner
Copy link

It was set to 0, before I changed it.

It was set to 0, before I changed it.
zlopez commented 2026-08-10 12:06:31 +00:00
Owner
Copy link

Not sure if that IPA web UI issue is fixed. It's set to 100 again, but my account was locked when I tried to login and have to unlock it to be able to log in.

Not sure if that IPA web UI issue is fixed. It's set to 100 again, but my account was locked when I tried to login and have to unlock it to be able to log in.
kevin commented 2026-08-13 21:22:59 +00:00
Author
Owner
Copy link

Yeah, so I don't think this is actually the problem. When people have said they cannot login I have run 'ipa user-status' on them and also 'ipa user-unlock' and it doesn't seem to matter.

Are folks still seeing this?

I think we need to either get noggin to log more about why it's saying unauthorized and/or match that up to a ipa dirserv log about the access. Would be nice to close this one out..

Yeah, so I don't think this is actually the problem. When people have said they cannot login I have run 'ipa user-status' on them and also 'ipa user-unlock' and it doesn't seem to matter. Are folks still seeing this? I think we need to either get noggin to log more about why it's saying unauthorized and/or match that up to a ipa dirserv log about the access. Would be nice to close this one out..
gotmax23 commented 2026-08-14 03:19:57 +00:00
Copy link

https://accounts.fedoraproject.org is sometimes not allowing people to login. It gives a 'Unauthorized: bad credentials'. This seems sporadic and unclear how many people it effects.

This is still happening. I tried today to log into Noggin and It wasn't working and then I waited a bit to try again and it worked and then I tried to log back in after my session timed out and couldn't again.

> https://accounts.fedoraproject.org is sometimes not allowing people to login. It gives a 'Unauthorized: bad credentials'. This seems sporadic and unclear how many people it effects. This is still happening. I tried today to log into Noggin and It wasn't working and then I waited a bit to try again and it worked and then I tried to log back in after my session timed out and couldn't again.
zlopez commented 2026-08-14 08:06:23 +00:00
Owner
Copy link

I think I found the problem on IPA.

This is what I can see in httpd error_log:

[Fri Aug 14 08:05:02.250703 2026] [:warn] [pid 1988634:tid 1988685] [client 10.16.163.124:41838] failed to set perms (3140) on file (/run/ipa/ccaches/noggin@FEDORAPROJECT.ORG-TuEOnc)!, referer: https://ipa03.rdu3.fedoraproject.org/ipa

There are a lot of errors like this

I think I found the problem on IPA. This is what I can see in httpd error_log: ``` [Fri Aug 14 08:05:02.250703 2026] [:warn] [pid 1988634:tid 1988685] [client 10.16.163.124:41838] failed to set perms (3140) on file (/run/ipa/ccaches/noggin@FEDORAPROJECT.ORG-TuEOnc)!, referer: https://ipa03.rdu3.fedoraproject.org/ipa ``` There are a lot of errors like this
zlopez commented 2026-08-14 09:16:20 +00:00
Owner
Copy link

Found that the ipa-otpd was failing with Aug 14 08:59:56 ipa03.rdu3.fedoraproject.org ipa-otpd[3649437]: bind.c:089: Input/output error: IO error received on bind socket: Can't contact LDAP server and restarted it which fixed the authentication issue I saw on IPA web UI.

I unfortunately didn't found the root cause of this, but this would explain the Bad credentials error as the OTP didn't work correctly.

Found that the `ipa-otpd` was failing with `Aug 14 08:59:56 ipa03.rdu3.fedoraproject.org ipa-otpd[3649437]: bind.c:089: Input/output error: IO error received on bind socket: Can't contact LDAP server` and restarted it which fixed the authentication issue I saw on IPA web UI. I unfortunately didn't found the root cause of this, but this would explain the `Bad credentials` error as the OTP didn't work correctly.
kevin commented 2026-08-14 17:14:58 +00:00
Author
Owner
Copy link

Interesting. Does everyone who was seeing this have a otp enrolled? I think they might?

Note that ipa-otpd is setup as a systemd 'socket', so it listens for requests and then fires up the service. That service is sometimes getting that error. Explains why it might work after a while as the service times out and has to get started again from the socket.

I guess we need to file a ipa bug here and ask for help... I couldn't find anything already existing from a search.

All 3 ipa servers have those errors, so I don't think it's anything specific to ipa03.

And... I was able to hit the 'cannot login to the ipa web ui' issue... and otpd was working, it just rejected me:

Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: request rece
ived
Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: user query s
tart
Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: user query e
nd: uid=kevin,cn=users,cn=accounts,dc=fedoraproject,dc=org
Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: bind start: 
uid=kevin,cn=users,cn=accounts,dc=fedoraproject,dc=org
Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: bind end: In
valid credentials
Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: sent: 0 data
: 20
Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: ..sent: 20 d
ata: 20
Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: response sent: Access-Reject

So, not convinced this is the issue... :(

Interesting. Does everyone who was seeing this have a otp enrolled? I think they might? Note that ipa-otpd is setup as a systemd 'socket', so it listens for requests and then fires up the service. That service is sometimes getting that error. Explains why it might work after a while as the service times out and has to get started again from the socket. I guess we need to file a ipa bug here and ask for help... I couldn't find anything already existing from a search. All 3 ipa servers have those errors, so I don't think it's anything specific to ipa03. And... I was able to hit the 'cannot login to the ipa web ui' issue... and otpd was working, it just rejected me: ``` Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: request rece ived Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: user query s tart Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: user query e nd: uid=kevin,cn=users,cn=accounts,dc=fedoraproject,dc=org Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: bind start: uid=kevin,cn=users,cn=accounts,dc=fedoraproject,dc=org Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: bind end: In valid credentials Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: sent: 0 data : 20 Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: ..sent: 20 d ata: 20 Aug 14 17:11:30 ipa03.rdu3.fedoraproject.org ipa-otpd[7609]: kevin@FEDORAPROJECT.ORG: response sent: Access-Reject ``` So, not convinced this is the issue... :(
py0xc3 commented 2026-08-14 17:54:48 +00:00
Copy link

Interesting. Does everyone who was seeing this have a otp enrolled? I think they might?

Yes, I have OTP enabled (but not sure if I'm still affected as I didn't use accounts.fp since my last post)

> Interesting. Does everyone who was seeing this have a otp enrolled? I think they might? Yes, I have OTP enabled (but not sure if I'm still affected as I didn't use accounts.fp since my last post)
zlopez commented 2026-08-18 13:18:32 +00:00
Owner
Copy link

In case of IPA web UI it usually helps me to just do ipa user-unlock, but I'm not sure if accounts.fedoraproject.org is the same problem and I'm also not sure why the account get locked in first place.

EDIT: One idea crossed my mind, isn't there some grace period after giving the wrong login credentials before it will let you try again.

In case of IPA web UI it usually helps me to just do `ipa user-unlock`, but I'm not sure if accounts.fedoraproject.org is the same problem and I'm also not sure why the account get locked in first place. EDIT: One idea crossed my mind, isn't there some grace period after giving the wrong login credentials before it will let you try again.
mwinters commented 2026-08-18 15:30:30 +00:00
Contributor
Copy link

Does everyone who was seeing this have a otp enrolled?

I have OTP enrolled.

isn't there some grace period after giving the wrong login credentials before it will let you try again

This could be exacerbating things, though there has definitely been some amount of false "bad credentials" happening. I use 1Password, so zero opportunity to typo anything. (Unless someone is trying to brute force my password and locking my account! Clankers?)

> Does everyone who was seeing this have a otp enrolled? I have OTP enrolled. > isn't there some grace period after giving the wrong login credentials before it will let you try again This could be exacerbating things, though there has definitely been some amount of false "bad credentials" happening. I use 1Password, so zero opportunity to typo anything. (Unless someone is trying to brute force my password and locking my account! Clankers?)
kevin commented 2026-08-18 19:51:55 +00:00
Author
Owner
Copy link

So, I went down this path too, but everytime I (or someone else) was having problems logging in and I checked with 'ipa user-status ' it said they were not locked, and 'ipa user-unlock' didn't seem to do anything. ;(

As far as the time limits, I set them to 10 seconds a while ago, and the number of failed logins is 100...

So, if it is this thing, it's acting in a way that doesn't seem as described.

So, I went down this path too, but everytime I (or someone else) was having problems logging in and I checked with 'ipa user-status <user>' it said they were not locked, and 'ipa user-unlock' didn't seem to do anything. ;( As far as the time limits, I set them to 10 seconds a while ago, and the number of failed logins is 100... So, if it is this thing, it's acting in a way that doesn't seem as described.
gotmax23 commented 2026-08-20 18:02:24 +00:00
Copy link

Do we know for sure if this issue only affects users with 2FA enabled or if that's a red herring? If this is 2FA related, it would be ideal to have it sorted before the provenpackager 2FA flag date at the end of September.

(EDIT: If it helps, I also have 2FA enabled and hit this again today)

Do we know for sure if this issue only affects users with 2FA enabled or if that's a red herring? If this is 2FA related, it would be ideal to have it sorted before the provenpackager 2FA flag date at the end of September. (EDIT: If it helps, I also have 2FA enabled and hit this again today)
zlopez commented 2026-08-21 06:49:56 +00:00
Owner
Copy link

We are not sure, but it looks like a common pattern.

We are not sure, but it looks like a common pattern.
ngompa commented 2026-08-23 17:43:56 +00:00
Copy link

I can log into accounts, but I can no longer log into id.fedoraproject.org or id.centos.org since enabling 2FA OTPs. I now persistently get 401 errors.

I can log into accounts, but I can no longer log into id.fedoraproject.org or id.centos.org since enabling 2FA OTPs. I now persistently get 401 errors.
kevin commented 2026-08-24 18:11:18 +00:00
Author
Owner
Copy link

Huh, thats different and the first report we have seen of that. By "log into id.fedoraproject.org or id.centos.org" you mean you try and log into some application, you don't have a kerberos ticket and it redirects to id to ask your credentials?

What application was it?
What error did it give? just incorrect password?

If you do have a valid kerberos ticket does it log you in?

Huh, thats different and the first report we have seen of that. By "log into id.fedoraproject.org or id.centos.org" you mean you try and log into some application, you don't have a kerberos ticket and it redirects to id to ask your credentials? What application was it? What error did it give? just incorrect password? If you _do_ have a valid kerberos ticket does it log you in?
ngompa commented 2026-08-24 20:48:53 +00:00
Copy link

@kevin wrote in #13482 (comment):

Huh, thats different and the first report we have seen of that. By "log into id.fedoraproject.org or id.centos.org" you mean you try and log into some application, you don't have a kerberos ticket and it redirects to id to ask your credentials?

Yup.

What application was it? What error did it give? just incorrect password?

Three applications so far: RHBZ. GitLab.com. Dist-Git.

I get "authentication failure" today, but yesterday I got "unauthorized".

If you do have a valid kerberos ticket does it log you in?

Yes, but this is not applicable on my phone or my Mac.

@kevin wrote in https://forge.fedoraproject.org/infra/tickets/issues/13482#issuecomment-1345338: > Huh, thats different and the first report we have seen of that. By "log into id.fedoraproject.org or id.centos.org" you mean you try and log into some application, you don't have a kerberos ticket and it redirects to id to ask your credentials? Yup. > What application was it? What error did it give? just incorrect password? Three applications so far: RHBZ. GitLab.com. Dist-Git. I get "authentication failure" today, but yesterday I got "unauthorized". > If you _do_ have a valid kerberos ticket does it log you in? Yes, but this is not applicable on my phone or my Mac.
kevin commented 2026-08-24 22:02:08 +00:00
Author
Owner
Copy link

So, this thing turned out to be sssd on ipsilon01 being in a bad state. I am guessing that it worked for people who it had cached info for, but not for anyone else. :( I think it was caused by the ipa02 re-sync, but not sure of that. In any case, restarting sssd on ipsilon01 seems to have fixed that.

(But will not I am pretty sure fix the sporadic problems logging into accounts / ipa web ui)

So, this thing turned out to be sssd on ipsilon01 being in a bad state. I am guessing that it worked for people who it had cached info for, but not for anyone else. :( I think it was caused by the ipa02 re-sync, but not sure of that. In any case, restarting sssd on ipsilon01 seems to have fixed that. (But will not I am pretty sure fix the sporadic problems logging into accounts / ipa web ui)
zlopez commented 2026-08-25 08:42:53 +00:00
Owner
Copy link

So I reinstalled ipa02 and ipa03, hopefully that will make the ipa cluster more stable. Let's see if that helps with this issue as well.

So I reinstalled ipa02 and ipa03, hopefully that will make the ipa cluster more stable. Let's see if that helps with this issue as well.
kevin commented 2026-08-25 20:56:49 +00:00
Author
Owner
Copy link

I've tweaked some things on ipsilon01 to avoid the bad state ( I hope ).

If folks see any issues now, can you please let us know? (and which exact issue?)

Reminder, the issues are:

  1. Cannot login to accounts.fedoraproject.org (I have not seen reports of this since the ipa cluster was all back)
  2. Cannot login to applications via dialog at id.fedoraproject.org (the ipsilon thing I hopefully fixed/mitigated)
  3. 400 or 401's when trying to login to applications
I've tweaked some things on ipsilon01 to avoid the bad state ( I hope ). If folks see any issues now, can you please let us know? (and which exact issue?) Reminder, the issues are: 1. Cannot login to accounts.fedoraproject.org (I have not seen reports of this since the ipa cluster was all back) 2. Cannot login to applications via dialog at id.fedoraproject.org (the ipsilon thing I hopefully fixed/mitigated) 3. 400 or 401's when trying to login to applications
kevin commented 2026-08-31 18:58:12 +00:00
Author
Owner
Copy link

I've seen no reports in the last 5 days. If anyone is still seeing something, please let us know.

I'll keep this open for a bit more to gather more issues if any.

I've seen no reports in the last 5 days. If anyone is still seeing something, please let us know. I'll keep this open for a bit more to gather more issues if any.
zlopez commented 2026-09-01 09:23:32 +00:00
Owner
Copy link

Maybe it helped when I reinstalled the ipa02 and ipa03 again with you tweaking the ipsilon01.

Maybe it helped when I reinstalled the ipa02 and ipa03 again with you tweaking the ipsilon01.
kevin commented 2026-09-01 22:07:20 +00:00
Author
Owner
Copy link

Yeah, I think so...

I guess I am going to close this now.

Please report any new issues.

Yeah, I think so... I guess I am going to close this now. Please report any new issues.
kevin closed this issue 2026-09-01 22:07:21 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
announcement

Archived

  
anubis
Issues related to anubis

  
authentication
Authentication related issues

  
aws
Issues related to Amazon Web Services

  
backlog
Tasks that will take longer then ~4 hours to do

Archived

  
blocked
Issue is blocked

Archived

  
bodhi
Issues with Bodhi

  
ci
Continuous Integration

  
cloud
Items in FedoraInfraCloud or COmmunishift

  
communishift
issues/questions about os.edorainfracloud.org ( Community OpenShift)

  
copr
COPR system (run by other team)

  
database
Issues related to databases

  
day-to-day
These are small self contained tasks that are part of normal operations, but are async from sprint planning.

  
dc-move
Items related to datacenter move

Archived

  
deprecated
Tools which Infrastructure may not be able to fix

Archived

  
dev
Tasks requiring some dev work

  
discourse
outsourced tool

  
dns
Changes or problems with DNS

  
downloads
rsync,dl.fp.o,AWS,torrents

  
easyfix

Archived

  
epel
Issues relating to epel

Archived

  
firmitas

   
forgejo_migration
Request migration to the new forge

  
Gain
High
 task that gets us a lot / is important / makes many people happy

Archived

  
Gain
Low
 tasks that gets us little / isn't very important / makes only 1 person or few happy

Archived

  
Gain
Medium
 task that gets us some / is somewhat important / makes some people happy

Archived

  
gitlab

   
greenwave
Issues with greenwave

  
hardware
Problem is with Fedora Infrastructure Owned/Leased Hardware

  
help wanted

   
high-trouble
task that is complex/long/difficult

Archived

  
koji
Issues with the build system

  
koschei
Items needing Koschei team

  
lists
issues with lists

  
low-trouble
task that is easy/short

Archived

  
medium-trouble
task that is medium complex / difficult

Archived

  
mirrorlists
Way to tell systems where downloads are

  
monitoring

   
Needs investigation

   
odcs
On Demand Compose Service issues

Archived

  
OpenShift
Issues with OpenShift

  
ops
ops problem now...

Archived

  
outage

   
packager_workflow_blocker
Blocks the packager workflow

Archived

  
pagure
Issues with pagure.io

  
permissions
Items which need permissions set in outside tools

  
Priority
Needs Review
 Priority of Needs Review

Archived

  
Priority
Next Meeting
 Priority of Next Meeting

Archived

  
Priority
🔥 URGENT 🔥
 Priority of 🔥 URGENT 🔥

Archived

  
Priority
Waiting on Assignee
 Priority of Waiting on Assignee

Archived

  
Priority
Waiting on External
 Priority of Waiting on External

Archived

  
Priority
Waiting on Reporter
 Priority of Waiting on Reporter

Archived

  
rabbitmq
issues with the message broker

  
release-monitoring
release-monitoring.org (Anitya)

  
releng
For problems which should be in the releng ticket system

Archived

  
request-for-resources

   
s390x
The secondary architecture hardware and problems related with it

  
security

   
SMTP
Email issues outside of lists (DMARC, SPF, aliases)

  
sprint-0

Archived

  
sprint-1

Archived

  
src.fp.o
Issues related to src.fedoraproject.org

  
staging
Issues in staging

  
unfreeze
Patches to be applied after freeze is lifted

  
waiverdb
Issues with waiverdb

  
websites-general
General items with a website focus

  
wiki
Issues with the Wiki

  
Backlog Status
Needs Review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
High
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
 Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
 Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
 Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt
Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
 Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
 Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
 User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
announcement
anubis
authentication
aws
backlog
blocked
bodhi
ci
cloud
communishift
copr
database
day-to-day
dc-move
deprecated
dev
discourse
dns
downloads
easyfix
epel
firmitas
forgejo_migration
Gain
High
Gain
Low
Gain
Medium
gitlab
greenwave
hardware
help wanted
high-trouble
koji
koschei
lists
low-trouble
medium-trouble
mirrorlists
monitoring
Needs investigation
odcs
OpenShift
ops
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
release-monitoring
releng
request-for-resources
s390x
security
SMTP
sprint-0
sprint-1
src.fp.o
staging
unfreeze
waiverdb
websites-general
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint ( 2026-08-24 to 2026-09-06)
Assignees
Clear assignees
No assignees
kevin
9 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
infra/tickets#13482
No description provided.