#8466 Bodhi 5 leaking connections
Closed: Fixed 3 months ago by kevin. Opened 4 months ago by pbrobinson.

While working from Australia bodhi is almost unusable via cli and the web interface pretty much times out every time.

$ fedpkg update
Could not execute update: Could not generate update request: ServerError(https://bodhi.fedoraproject.org/updates/, 504, Error returned from json module while processing b'https://bodhi.fedoraproject.org/updates/': b'Expecting value: line 1 column 1 (char 0)'
b"<html><body>

504 Gateway Time-out

\nThe server didn't respond in time.\n</body></html>\n") A copy of the filled in template is saved as bodhi.template.last

a 'fedpkg update' will often require 2-3+ attempts to get an update, the web interface to edit an update for adding bugs, or updating the metadata description basically times out and doesn't update it but doesn't provide a useful error either.

Can you try again now? This might be an issue we have been trying to fix all week. ;(

I just restarted the bodhi web pods... which usually clears up the issue (for a while).

That did work, I've been trying for 4 hours to get that submitted. It was extremely frustrating :-/

So the issue isn't with latency or you being in Australia. The issue is that bodhi, openshift, or the DB is leaking database connections and so goes into longer and longer la-la land. [All examinations of the items seem to point to the next thing in the stack as being the problem so it is probably a little of all 3.]

Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: bodhi, database

4 months ago

Metadata Update from @cverna:
- Issue assigned to cverna

4 months ago

Can you try again now? This may have been related to all our koji/bodhi/rabbitmq issues and should be over now...

As @abompard mentioned there is a high possibility that the problem we have experienced with Bodhi was related to #8477.

I propose to close this ticket since Bodhi is working as expected now.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 months ago

Login to comment on this ticket.

Metadata