Issue #2852: [1.24.1] kojira thrown an exception when the user is unknown at the hub - koji

koji

#2852 [1.24.1] kojira thrown an exception when the user is unknown at the hub

Closed: Fixed Nov 8, 2021 by julian8628. Opened May 11, 2021 by frank-mdc.

When using SSL authentication and the user(CN name of the certificate) is unknown, then an python exception is thrown and abrt is triggered.

abrt-cli ls
id 1dabec2c81799b3e9d84365c3bb7abec87d4941b
reason: close(): init.py:2740:_callMethod:koji.AuthError: Unknown user: host.domain
time: Tue 11 May 2021 08:29:03 AM CEST
cmdline: /usr/bin/python3.6 /usr/sbin/kojira --fg --force-lock --verbose
package: koji-utils-1.24.1-1.el8
uid: 0 (root)
count: 1
Directory: /var/spool/abrt/Python3-2021-05-11-08:29:03-2029616

Metadata Update from @tkopecek:
- Custom field Size adjusted to None
- Issue set to the milestone: 1.26

May 11, 2021

mikem commented May 11, 2021

Unknown user: host.domain

Is the username here really "host.domain"

mikem commented May 11, 2021

The "Unknown user" can only happen when LoginCreatesUser is off (which it is by default). This is a perfectly valid option setting, but if you don't let koji create users from valid auth credentials, then you'll need to add the user entries in Koji yourself. See koji add-user.

That said, "host.domain" doesn't seem like a real user name. I suspect the ssl cert you've used for auth is not correct.

frank-mdc commented May 12, 2021

Hi @mikem , yes the user name is the fqdn, because our pki will need this for none human certificates. But this is not an real problem because after adding the user to the hub it will work. The only problem it that the error is thrown as an exception and not logged as an error, so abrt will create an problem report.

Metadata Update from @tkopecek:
- Issue set to the milestone: 1.27 (was: 1.26)

Aug 9, 2021

jcupova commented Oct 26, 2021

PR 3099

Metadata Update from @jcupova:
- Issue tagged with: testing-ready

Oct 27, 2021

Metadata Update from @jobrauer:
- Issue tagged with: testing-done

Nov 5, 2021

julian8628 commented Nov 8, 2021

Commit c7693903 fixes this issue

julian8628 commented Nov 8, 2021

Commit 2118a24e fixes this issue