Bug 2222973 - dnf has bug when adding multiple repo gpg keys at once.
Summary: dnf has bug when adding multiple repo gpg keys at once.
Keywords:
Status: POST
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: dnf
Version: 9.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Packaging Maintenance Team
QA Contact: swm-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-14 16:39 UTC by Zach Connor
Modified: 2023-08-16 06:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-162398 0 None None None 2023-07-14 16:40:44 UTC

Description Zach Connor 2023-07-14 16:39:07 UTC
Description of problem:
When trying to add multiple GPG keys while adding a repo using dnf API, only the first GPG key is added.

EXAMPLE:
    base.repos.add_new_repo('foo_repo', conf,
        baseurl=['https://foo/bar'],
        gpgkey=['https://foo/bar/key1','https://foo/bar/key2'],
        gpgcheck=True)

Version-Release number of selected component (if applicable):


How reproducible:
Every time

Steps to Reproduce:
1.Add repo using API and add multiple GPG keys (see example above)
2.Only one GPG key is successfully added

Actual results:
Only one GPG key is added

Expected results:
Multiple GPG keys expected

Additional info:
Bug is already fixed upstream with this pull:
https://github.com/rpm-software-management/dnf/pull/1962


Note You need to log in before you can comment on or make changes to this bug.