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
Example is: yum::config { 'gpgcheck': ensure => 1, }
What are you seeing
Starting in RHEL 8, a new major release of yum, now known as dnf, was released. As part of this change, /etc/yum.conf is no longer directly responsible for configuring the package manager settings. The legacy file /etc/yum.conf is kept as a symbolic link to the new package manager configuration file /etc/dnf/dnf.conf.
When using yum::config, the symlink at /etc/yum.conf is removed and a new regular file is created in its place. This new file will not be read by dnf, since it only looks at /etc/dnf/dnf.conf by default (can override with dnf -c <config file> option).
Before puppet agent -t run: [root@client ~]# ls -l /etc/yum.conf lrwxrwxrwx. 1 root root 17 Nov 2 01:35 /etc/yum.conf -> /etc/dnf/dnf.conf
After puppet agent -t run: [root@client ~]# ls -l /etc/yum.conf -rw-r--r--. 1 root root 99 Nov 2 01:26 /etc/yum.conf
What behaviour did you expect instead
/etc/yum.conf symbolic link should be kept. [root@client ~]# ls -l /etc/yum.conf lrwxrwxrwx. 1 root root 17 Nov 2 01:35 /etc/yum.conf -> /etc/dnf/dnf.conf
The module should either:
modify the target of the symbolic link, rather than the symbolic link itself (similar to sed --follow-symlinks)
add an option to change the location of the package manager configuration file (e.g., RHEL7 => /etc/yum.conf, RHEL8 => /etc/dnf/dnf.conf)
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Any yum::config option will cause the issue.
Example is:
yum::config { 'gpgcheck':
ensure => 1,
}
What are you seeing
Starting in RHEL 8, a new major release of yum, now known as dnf, was released. As part of this change, /etc/yum.conf is no longer directly responsible for configuring the package manager settings. The legacy file /etc/yum.conf is kept as a symbolic link to the new package manager configuration file /etc/dnf/dnf.conf.
When using
yum::config
, the symlink at /etc/yum.conf is removed and a new regular file is created in its place. This new file will not be read by dnf, since it only looks at /etc/dnf/dnf.conf by default (can override withdnf -c <config file>
option).Before
puppet agent -t
run:[root@client ~]# ls -l /etc/yum.conf
lrwxrwxrwx. 1 root root 17 Nov 2 01:35 /etc/yum.conf -> /etc/dnf/dnf.conf
After
puppet agent -t
run:[root@client ~]# ls -l /etc/yum.conf
-rw-r--r--. 1 root root 99 Nov 2 01:26 /etc/yum.conf
What behaviour did you expect instead
/etc/yum.conf symbolic link should be kept.
[root@client ~]# ls -l /etc/yum.conf
lrwxrwxrwx. 1 root root 17 Nov 2 01:35 /etc/yum.conf -> /etc/dnf/dnf.conf
The module should either:
sed --follow-symlinks
)puppet-yum/manifests/config.pp
Line 39 in 099c488
Output log
Any additional information you'd like to impart
The text was updated successfully, but these errors were encountered: