fedora-infrastructure

#5520 koji-stage user 'm8y' is getting Postgress database error (please fix that)
Closed: Fixed Opened by lkocman.

Closed: Fixed
Reopen Issue

Hello team,

I was just discovering why our module-build system doesn't work and figured out that we can't even authenticate. Could you please fix that? koji-prod works.




[fedora@modularity ~ []]$ koji hello # this is koji-stage instance

Fault: : error \'ERROR: duplicate key value violates unique \
constraint "users_pkey"\nDETAIL: Key (id)=(3652) already exists.\n\' in \'INSERT INTO users (id, name, usertype, status, krb_principal)\n VALUES (3652, \'m8y\', 0, 0, NULL)\''>




KOJI PROD # ALSO LOL UTF-8



[fedora@modularity koji.conf.d []]$ koji --profile koji-prod hello

UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 1: ordinal not in range(128)

[fedora@modularity koji.conf.d []]$ koji --profile koji-prod hello

UnicodeEncodeError: 'ascii' codec can't encode characters in position 1-2: ordinal not in range(128)

[fedora@modularity koji.conf.d []]$ koji --profile koji-prod hello

hallo, m8y!



You are using the hub at http://koji.fedoraproject.org/kojihub

Authenticated via client certificate /home/fedora/.fedora.cert

I'm looking into this.

'INSERT INTO users (id, name, usertype, status, krb_principal)\n VALUES (3652, \'m8y\', 0, 0, NULL)\'

Should it be using "users" here as postgresql has its own users registry/table ?

So, this is likely related to me changing the db setup in staging, but I hope it's fixable. :)

The db in staging was made from a new production snapshot from a day or two ago and has had our playbooks/manual/staging-sync/templates/koji-reset-staging.sql run on it.
It's also running now a BDR replication setup with 2 masters.

I hope the issue here is that this user was not setup in prod or added to our reset-staging sql and we just need to re-add them. It might be there's some problem caused by the replication however.

Happy to help look into it...

Figured it out.

There was an old ~/.fedora/fedora_session on the client.

When the database was swapped out by kevin, the the old session no longer existed, but koji didn't handle it well.

Should be able to close this issue now.

Whew. :joy: I was worried my replication broke something.

Thanks.

@kevin changed the status to Fixed
Metadata
None
None
None
None
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.