Integrity issues with ipsilon #13251

Open
opened 2026-04-02 16:34:47 +00:00 by gwmngilfen · 6 comments
Member

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:

looks like there are integrity errors when adding stuff to the transactions table. This table contains items that were added in 2017. I'm prettysure the oidc transaction is over now.
I should write a script to clean up that table

Logging this so we don't forget it ;)

### 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: > looks like there are integrity errors when adding stuff to the transactions table. This table contains items that were added in 2017. I'm prettysure the oidc transaction is over now. I should write a script to clean up that table Logging this so we don't forget it ;)
Member

I've made some progress on this, I've worked around the two IntegrityError exceptions 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. Only ipsilon01 is fixed / was affected.
I'm keeping an eye on this machine for now.

I've made some progress on this, I've worked around the two `IntegrityError` exceptions 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. Only `ipsilon01` is fixed / was affected. I'm keeping an eye on this machine for now.
Owner

Just a reminder that openid haproxy backend will go away in 2 weeks.

Just a reminder that openid haproxy backend will go away in 2 weeks.
Author
Member

Per update in #13204, we're seeing a ~200x drop in Ipsilon 5xx errors on proxy01, so something is definitely better, nice work @abompard

Per update in #13204, we're seeing a ~200x drop in Ipsilon 5xx errors on proxy01, so something is definitely better, nice work @abompard
Owner

@gwmngilfen Do we want to keep this open?

@gwmngilfen Do we want to keep this open?
Author
Member

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.

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.
Owner

@abompard any news here? can we deploy the fixes in ansible (or via a updated rpm?) and close this out?

@abompard any news here? can we deploy the fixes in ansible (or via a updated rpm?) and close this out?
Sign in to join this conversation.
No milestone
No project
No assignees
4 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#13251
No description provided.