#12116 Signing fails with error
Closed: Fixed a month ago by kevin. Opened a month ago by zlopez.

NOTE

If your issue is for security or deals with sensitive info please
mark it as private using the checkbox below.

Describe what you would like us to do:


I tried to restart signing today and it failed with:

2024-08-09 11:29:50,451 INFO: Connection from CN=jnsamyak
2024-08-09 11:29:50,469 ERROR: Unexpected exception
Traceback (most recent call last):
  File "/usr/share/sigul/server.py", line 2722, in request_handling_child
    handler.handler(db, conn)
  File "/usr/share/sigul/server.py", line 1439, in cmd_new_key
    conn.authenticate_admin(db)
  File "/usr/share/sigul/server.py", line 584, in authenticate_admin
    user = db.query(User).filter_by(name=user).first()
  File "/usr/lib64/python3.9/site-packages/sqlalchemy/orm/query.py", line 2824, in first
    return self.limit(1)._iter().first()
  File "/usr/lib64/python3.9/site-packages/sqlalchemy/engine/result.py", line 1498, in first
    return self._only_one_row(
  File "/usr/lib64/python3.9/site-packages/sqlalchemy/engine/result.py", line 559, in _only_one_row
    row = onerow(hard_close=True)
  File "/usr/lib64/python3.9/site-packages/sqlalchemy/engine/result.py", line 1386, in _fetchone_impl
    return self._real_result._fetchone_impl(hard_close=hard_close)
  File "/usr/lib64/python3.9/site-packages/sqlalchemy/engine/result.py", line 1801, in _fetchone_impl
    row = next(self.iterator, _NO_ROW)
  File "/usr/lib64/python3.9/site-packages/sqlalchemy/orm/loading.py", line 147, in chunks
    fetch = cursor._raw_all_rows()
  File "/usr/lib64/python3.9/site-packages/sqlalchemy/engine/result.py", line 393, in _raw_all_rows
    return [make_row(row) for row in rows]
  File "/usr/lib64/python3.9/site-packages/sqlalchemy/engine/result.py", line 393, in <listcomp>
    return [make_row(row) for row in rows]
  File "/usr/lib64/python3.9/site-packages/sqlalchemy/sql/sqltypes.py", line 993, in process
    value = bytes(value)
TypeError: string argument without an encoding
2024-08-09 11:29:50,473 ERROR: Child died with status 512

It looks to me like the new keys are maybe not created correctly I don't think that CN=jnsamyak is correct.

When do you need this to be done by? (YYYY/MM/DD)


Asap as it's blocking signing in Fedora


@jnsamyak Could you check this up? I assume it's the keys you created recently. According to the log output the culprit seems to be F43 key.

Okay, so the key creation failed with an I/O error!

Passphrase for the new key (again): 
ERROR: I/O error: EOFError()

So, this is not working and got interrupted, I'm not sure how this might be the cause of it;

What did I do?

sigul new-key --key-admin jnsamyak --key-type gnupg         --gnupg-name-real Fedora         --gnupg-name-comment 43         --gnupg-name-email fedora-43-primary@fedoraproject.org fedora-43

This is likely related to my trying to fix @jnsamyak 's access.

I have cleaned up the previous attempt and tried again. Can you please retry?

I think this is all sorted now...

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

a month ago

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog