fedora-infrastructure

#6971 Staging Bodhi seems to have lost its permission to tag in staging Koji
Closed: Fixed Opened by bowlofeggs.

Closed: Fixed
Reopen Issue
  • Describe what you need us to do:
    I am unable to run a test compose in staging, as the staging Koji is denying staging Bodhi admin access to change the tags on a build. I inserted a log statement to log the reply from Koji, and these are the logs from Bodhi during the compose:
May 22 21:13:49 bodhi-backend01.stg.phx2.fedoraproject.org fedmsg-hub[17952]: [2018-05-22 21:13:49][fedmsg.consumers    INFO]f27-updates-testing Moving kernel-4.16.10-200.fc27 from f27-updates-candidate to f27-updates-testing            
May 22 21:13:49 bodhi-backend01.stg.phx2.fedoraproject.org fedmsg-hub[17952]: [2018-05-22 21:13:49][fedmsg.consumers    INFO]f27-updates-testing [{'faultCode': 1004, 'traceback': ['Traceback (most recent call last):\n', '  File "/usr/share/koji-hub/kojixmlrpc.py", line 325, in multiCall\n    result = self._dispatch(call[\'methodName\'], call[\'params\'])\n', '  File "/usr/share/koji-hub/kojixmlrpc.py", line 308, in _dispatch\n    ret = koji.util.call_with_argcheck(func, params, opts)\n', '  File "/usr/lib/python2.7/site-packages/koji/util.py", line 209, in call_with_argcheck\n    return func(*args, **kwargs)\n', '  File "/usr/share/koji-hub/kojihub.py", line 9411, in moveBuild\n    return self.tagBuild(tag2, build, force=force, fromtag=tag1)\n', '  File "/usr/share/koji-hub/kojihub.py", line 9346, in tagBuild\n    assert_tag_access(tag_id, user_id=None, force=force)\n', '  File "/usr/share/koji-hub/kojihub.py", line 1468, in assert_tag_access\n    raise koji.ActionNotAllowed(reason)\n', 'ActionNotAllowed: tag requires admin permission\n'], 'faultString': 'tag requires admin permission'}]

  • When do you need this? (YYYY/MM/DD)
    Ideally this week, as I plan to release Bodhi 3.8.0 next week and I'd like to be able to test this before releasing.

  • When is this no longer needed or useful? (YYYY/MM/DD)
    When we no longer use Bodhi or Koji.

  • If we cannot complete your request, what is the impact?
    I will be unable to test composing Bodhi in staging.

Metadata Update from @mizdebsk:
- Issue assigned to mizdebsk

Fixed with:

koji=# begin;
BEGIN
koji=# delete from sessions where user_id=4190;
DELETE 4
koji=# delete from users where name='bodhi/bodhi.stg.fedoraproject.org@STG.FEDORAPROJECT.ORG';
DELETE 1
koji=# update users set krb_principal='bodhi/bodhi.stg.fedoraproject.org@STG.FEDORAPROJECT.ORG' where name='bodhi';
UPDATE 1
koji=# commit;
COMMIT

Sync playbook update to prevent regressions during future syncs: https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=0891cde

Metadata Update from @mizdebsk:
- Issue close_status updated to: Fixed
- Issue priority set to: None (was: Waiting on Assignee)
- Issue status updated to: Closed (was: Open)
Metadata

bodhi koji

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.