You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the documentation, it is stated that for the yum_repository provider gpgkey option, that "If this option is set, Yum will automatically import the key from the specified URL."
Investigation shows that this is not the case and I cannot find evidence that Chef is downloading GPG keys in the source code.
Chef Version
Chef: 14.13.11
Platform Version
Redhat 7.6
Replication Case
Minimal Chef recipe:
yum_repository 'epel' do
action :create
description 'Fedora EPEL Repository'
metalink 'https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch'
failovermethod 'priority'
gpgcheck true
gpgkey 'http://download.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL'
enabled true
end
Checking the imported rpm keys afterwards will not show the gpg keys added to the system.
Description
In the documentation, it is stated that for the yum_repository provider gpgkey option, that "If this option is set, Yum will automatically import the key from the specified URL."
Investigation shows that this is not the case and I cannot find evidence that Chef is downloading GPG keys in the source code.
Chef Version
Chef: 14.13.11
Platform Version
Redhat 7.6
Replication Case
Minimal Chef recipe:
Checking the imported rpm keys afterwards will not show the gpg keys added to the system.
Reproduced in CentOS on Vagrant, and in a 'real' server running RHEL. Both version 7.6.
The text was updated successfully, but these errors were encountered: