koji

#4234 Incorrect operation of Koji PostgreSQL database deleted a user in use, executing delete from users where id=144;
Closed: Fixed by tkopecek. Opened by houlifei.

Closed: Fixed
Reopen Issue

Problem phenomenon：
Error
An error has occurred in the web interface code. This could be due to a bug or a configuration issue.
koji.GenericError: No such build ID: 82345
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/koji/init.py", line 2988, in _callMethod
return self._sendCall(handler, headers, request)
File "/usr/lib/python3.6/site-packages/koji/init.py", line 2885, in _sendCall
raise e
File "/usr/lib/python3.6/site-packages/koji/init.py", line 2881, in _sendCall
return self._sendOneCall(handler, headers, request)
File "/usr/lib/python3.6/site-packages/koji/init.py", line 2931, in _sendOneCall
ret = self._read_xmlrpc_response(r)
File "/usr/lib/python3.6/site-packages/koji/init.py", line 2943, in _read_xmlrpc_response
result = u.close()
File "/usr/lib64/python3.6/xmlrpc/client.py", line 656, in close
raise Fault(**self._stack[0])
xmlrpc.client.Fault:

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/share/koji-web/scripts/index.py", line 1236, in buildinfo
build = server.getBuild(buildID, strict=True)
File "/usr/lib/python3.6/site-packages/koji/init.py", line 2406, in call
return self.func(self.__name, args, opts)
File "/usr/lib/python3.6/site-packages/koji/__init.py", line 2963, in _renew_expired_session
return func(self, args, *kwargs)
File "/usr/lib/python3.6/site-packages/koji/init.py", line 3007, in _callMethod
raise err
koji.GenericError: No such build: 82345

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/share/koji-web/scripts/wsgi_publisher.py", line 389, in handle_request
result = func(environ, **data)
File "/usr/share/koji-web/scripts/index.py", line 1238, in buildinfo
raise koji.GenericError("No such build ID: %i" % buildID)
koji.GenericError: No such build ID: 82345

Problem description: I deleted a user from Koji's PostgreSQL database and executed
delete from users where id=144;
I was prompted to remove many foreign key constraints, such as build, tag, etc. I deleted all the foreign key constraints and executed the command 'alter table build drop constraint build_owner_fkey'; Then the above phenomenon occurred. How to solve this problem is very urgent. I hope to receive a guarantee. Thank you very much!

Users should be never deleted. They can be disabled ("koji disable-user") but not deleted. Of course, they're linked with corresponding builds, etc. The message you've got was right and was trying to block you from causing such damage. Basically, youve' triggered cascading delete which probably took away the build you're mentioning. There is a reason why there is no API for deleting users. I suggest you to look for backup and recover all the data related to the given user.

Metadata Update from @tkopecek:
- Custom field Size adjusted to None

Okay, thank you very much. The issue has been resolved.
The above problem was solved by taking actions to address the following issue. I did not find a good solution and deleted the user, which caused the above problem
koji --user=gtkernel --password=[REDACTED] hello
2024-10-14 19:50:38,204 [ERROR] koji: AuthLockError: User locked by another session
My understanding is that there is currently a Koji client process calling the user to perform Koji related operations, but I am unable to locate the process and restore the user.
Edited by mikem

By default exclusive sessions (locked) are used only by builders. If this user is a builder there is a high chance that it is running. If it is not you can check where it is coming active sessions for the user:

koji call getSessionInfo True gtkernel

It would show you all the active sessions for given user (True will add an ip address from where it is connected)

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

Okay, thank you very much for your response. I have resolved the issue by creating a new user with the same user ID, re associating the table entries, and restoring the data to normal;
The gtkernel user is locked. Use the "koji call getSessionInfo True gtkernel" command you provided to check and then execute the "koji call logout id" to resolve the issue. Thank you very much for your reply.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/4234

Please continue any further discussion there.
Metadata
None
None
None
None
Low
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.