Bug 2222973

Summary: dnf has bug when adding multiple repo gpg keys at once.
Product: Red Hat Enterprise Linux 9 Reporter: Zach Connor <zconnor>
Component: dnfAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: POST --- QA Contact: swm-qe
Severity: medium Docs Contact:
Priority: unspecified    
Version: 9.2CC: james.antill, mbanas
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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