Integrity issues with ipsilon #13251
Labels
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
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
infra/tickets#13251
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of request
We're getting high rates of 5xx errors on proxy01/10 from HAPtoxy connecting to ipsilon-backend. Discussing with @abompard he noted:
Logging this so we don't forget it ;)
I've made some progress on this, I've worked around the two
IntegrityErrorexceptions that were raised. This has caused a few issues while I was working directly on prod, sorry about that, but it should be working now. Onlyipsilon01is fixed / was affected.I'm keeping an eye on this machine for now.
Just a reminder that openid haproxy backend will go away in 2 weeks.
Per update in #13204, we're seeing a ~200x drop in Ipsilon 5xx errors on proxy01, so something is definitely better, nice work @abompard
@gwmngilfen Do we want to keep this open?
I believe @abompard is waiting for the end of freeze to deploy the fixes permanently via Ansible, so I'd keep it open until then. If I'm wrong and that's out, we can close, yeah.
@abompard any news here? can we deploy the fixes in ansible (or via a updated rpm?) and close this out?