Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPG key isn't required to be present before the repositories #81

Closed
bodgit opened this issue Feb 15, 2019 · 1 comment
Closed

GPG key isn't required to be present before the repositories #81

bodgit opened this issue Feb 15, 2019 · 1 comment
Labels
bug Something isn't working skip-changelog

Comments

@bodgit
Copy link

bodgit commented Feb 15, 2019

The outcome from #72 and #73 means that the GPG key now isn't guaranteed to be imported before the Yum repositories are created which means if I install a package found in these repositories, I get the following errors:

GPG key retrieval failed: [Errno 14] curl#37 - "Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7"

And then a bit further on, I finally see the GPG key get created:

Notice: /Stage[main]/Epel/File[/etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7]/ensure: defined content as '{md5}58fa8ae27c89f37b08429f04fd4a88cc'
Notice: /Stage[main]/Epel/Epel::Rpm_gpg_key[EPEL-7]/Exec[import-EPEL-7]/returns: executed successfully

I agree the original dependency chaining was a bit far reaching, but I think there needs to be something here to keep the resources within the context of this module in the correct order.

@alexjfisher
Copy link
Member

Fixed in #86

@alexjfisher alexjfisher added the bug Something isn't working label Feb 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working skip-changelog
Projects
None yet
Development

No branches or pull requests

2 participants