Closed freym closed 2 months ago
Hm, never happend here. But the directory '/etc/apt/keyrings' isn't managed by the module puppet-icinga2 neither puppet-icinga.
What kind of version you use for the modules apt and icinga?
The keyring dir is handeld by puppetlabs-apt, see https://github.com/puppetlabs/puppetlabs-apt/blob/e0b3a5db6abb043f106614dffe341f68d88158ab/manifests/keyring.pp#L43
without any owner or group membership. Is there some code around the class declarition?
Sorry my bad. We have set a default in our old Icinga even earlier.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
class { 'icinga2': manage_repos => true, }
What are you seeing
When the module tries to install the apt keyring, puppet aborts because the user/group 'nagios' does not exist on the system.
What behaviour did you expect instead
It should install the apt keyring.
Output log
Any additional information you'd like to impart
I am not a puppet expert but I think the problem is the following: The module sets the default owner/group for all file resources^1. These defaults are apparently used later when configuring the apt keyring directory^2. Perhaps it will be enough if this line is executed a little earlier^3