I’m having trouble creating an update for side tag f43-build-side-112655 using https://bodhi.fedoraproject.org/updates/new. When I hit the Submit button, it spins for a second or so and then fails silently. Watching it in Firefox dev tools shows that the response to the POST is an error 500, with the following body:
f43-build-side-112655
<html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html>
If I try to create the update using the Bodhi CLI, I see the same thing:
$ bodhi updates new --type bugfix --bugs 2366373 --request testing --close-bugs --from-tag --notes 'Update abseil-cpp to 20250512.0: https://github.com/abseil/abseil-cpp/compare/20250127.1...20250512.0' f43-build-side-112655 --debug Starting new HTTPS connection (1): id.fedoraproject.org:443 https://id.fedoraproject.org:443 "GET /openidc/.well-known/openid-configuration HTTP/1.1" 200 2750 Starting new HTTPS connection (1): id.fedoraproject.org:443 https://id.fedoraproject.org:443 "POST /openidc/Token HTTP/1.1" 200 321 Starting new HTTPS connection (1): bodhi.fedoraproject.org:443 https://bodhi.fedoraproject.org:443 "GET /oidc/login-token HTTP/1.1" 202 109 https://bodhi.fedoraproject.org:443 "GET /csrf HTTP/1.1" 200 58 https://bodhi.fedoraproject.org:443 "GET /oidc/login-token HTTP/1.1" 202 109 https://bodhi.fedoraproject.org:443 "POST /updates/ HTTP/1.1" 500 141 <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html>
Please help understand why I cannot create a Bodhi update for side tag f43-build-side-112655 and fix or work around the problem.
2025/05/30
No hard deadline, but this side tag will remain open with 18 builds until the problem is resolved, and the likelihood of conflicts will increase the longer the side tag remains open.
There's a database transaction error it was throwing. ;(
I've just scaled the pods down to 0 and back up, can you try again now?
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
Updating this issue with information from the Matrix channel, it seems the problem is most likely due to the NVR of fcitx5-mozc becoming too long: since https://src.fedoraproject.org/rpms/fcitx5-mozc/pull-request/7, it has expanded from fcitx5-mozc-2.30.5618.102-5.20250124gitc0ed34e.s20250101gite5b3425.s20250101gitv3.29.1.fc43 to fcitx5-mozc-2.30.5618.102-7.20250124gitc0ed34e.s20250101gite5b3425.s20250101gitv3.29.1.s20250515git20240722.0.fc43.
fcitx5-mozc
fcitx5-mozc-2.30.5618.102-5.20250124gitc0ed34e.s20250101gite5b3425.s20250101gitv3.29.1.fc43
fcitx5-mozc-2.30.5618.102-7.20250124gitc0ed34e.s20250101gite5b3425.s20250101gitv3.29.1.s20250515git20240722.0.fc43
Both are unreasonable, and I attempted to fix this in https://src.fedoraproject.org/rpms/fcitx5-mozc/pull-request/8, but I am currently still struggling with https://bugzilla.redhat.com/show_bug.cgi?id=2359090.
With https://src.fedoraproject.org/rpms/fcitx5-mozc/pull-request/8, I was able to rebuild fcitx5-mozc as fcitx5-mozc-2.30.5618.102^20250124gitc0ed34e-2.fc43, and then I had no trouble creating a Bodhi update https://bodhi.fedoraproject.org/updates/FEDORA-2025-549a67a167. This confirms the initial theory that the database error was due to the package name being too long. Thank you for the help in understanding the problem here!
fcitx5-mozc-2.30.5618.102^20250124gitc0ed34e-2.fc43
Metadata Update from @music: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)