Bug#1060084: puppet-agent: Resource type 'Cron' was not found, even after puppet-module-puppetlabs-cron-core installed
OK, folks, I may have some interesting things (including an [ugly] workaround). 1. The original puppet-7.23.0 code does not mention '/usr/share/puppet' *at all*. 2. The 0001-Adjust-default-paths.patch Debian patch includes: - '$codedir/modules:/opt/puppetlabs/puppet/modules' + '$codedir/modules:/usr/share/puppet/modules' - '/opt/puppetlabs/puppet/vendor_modules' + '/usr/share/puppet/vendor_modules' (looks good) 3. The puppet cron module (and others...) ends up visible in /usr/share/puppet/modules 4. My run under 'strace' *NEVER* looks at '/usr/share/puppet/modules' (!) but it *does* look at '/usr/share/puppet/vendor_modules' 5. Doing a comparable 'strace'd run, but using only puppetlabs client and server (the current 7.x bullseye code), it *NEVER* looks at '/opt/puppetlabs/puppet/modules' (!) but it *does* look at '/opt/puppetlabs/puppet/vendor_modules'. 6. The puppetlabs code puts these core modules in 'vendor_modules', witness: $ ls /opt/puppetlabs/puppet/vendor_modules augeas_core host_core scheduled_task sshkeys_core zfs_core cron_coremount_core selinux_coreyumrepo_core zone_core (In '/opt/puppetlabs/puppet/modules/'? - nothing) 7. (Workaround) If I copy the debian-12-bookworm 'modules' to 'vendor_modules', e.g. cd /usr/share/puppet/modules rsync -a --itemize-changes . ../vendor_modules/. then... things work as expected(!). If you want to most-closely mirror the puppetlabs version, the cron (mount, host, ...) modules should go in vendor_modules. If they're going to stay in modules, something needs to get puppet-agent to *look* there -- something the puppetlabs code does not seem to do. Can anyone point to *any* debian-12-bookworm Puppet installation that can do 'cron' (mount, host, etc.) resources? I might, of course, be missing something... Regards to all, Will
Bug#1060084: [Pkg-puppet-devel] Bug#1060084: puppet-agent: Resource type 'Cron' was not found, even after puppet-module-puppetlabs-cron-core installed
Antoine Beaupré wrote: > Is there any specific reason why you feel this should be adressed in a > different bug report than the above? Hi, Antoine -- stumbling into the "bug"? again, I realized it was probably more likely a puppet agent bug, not the cron_core module. My understanding of the Debian bugs process is very slight. But I know it is a wondrously good thing! Regards to all, Will
Bug#1060084: puppet-agent: Resource type 'Cron' was not found, even after puppet-module-puppetlabs-cron-core installed
Package: puppet-agent Version: 7.23.0-1 Severity: important Dear Maintainer, (This is a more detailed version of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054664 ) Did: apt install puppet-agent puppetserver puppetdb Ended up with, inter alia: ii puppet-agent7.23.0-1 ii puppet-module-puppetlabs-augeas-core1.1.2-1 ii puppet-module-puppetlabs-cron-core 1.1.0+dfsg1-1 ii puppet-module-puppetlabs-host-core 1.1.0-1 ii puppet-module-puppetlabs-mount-core 1.0.4+dfsg1-2 ii puppet-module-puppetlabs-selinux-core 1.2.0-1 ii puppet-module-puppetlabs-sshkeys-core 2.3.0-1 ii puppetdb7.12.1-3 ii puppetserver7.9.5-2 Invoked puppet-agent against a "legacy" server: /usr/bin/puppet agent --server parple-pup1.parple.org --test --certname=parple-pup2.parple.org --environment=prodnew --diff_args=-U1 --noop --debug It received "work" from the server, and started doing things, until it needed 'Cron'... (the debugging log just before that...): Debug: /Package[apticron]: Provider apt does not support features install_only; not managing attribute install_only Debug: /Package[logrotate]: Provider apt does not support features targetable; not managing attribute command Debug: /Package[logrotate]: Provider apt does not support features install_only; not managing attribute install_only Error: Failed to apply catalog: Resource type 'Cron' was not found The full debugging info gives no hint of what it is failing to find, or what might not be working like expected. Puppet without 'cron' resources is of, uh, limited value. Thanks for your help, or any insight. Will -- System Information: Debian Release: 12.4 APT prefers stable APT policy: (900, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.2.0-39-generic (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages puppet-agent depends on: ii adduser3.134 ii debconf [debconf-2.0] 1.5.82 ii facter 4.3.0-2 ii hiera 3.10.0-1 ii init-system-helpers1.65.2 ii ruby 1:3.1 ii ruby-augeas1:0.5.0+gem-1 ii ruby-concurrent1.1.6+dfsg-5 ii ruby-deep-merge1.1.1-2 ii ruby-semantic-puppet 1.0.4-1 ii ruby-shadow2.5.1-1 ii ruby-sorted-set1.0.3-3 Versions of packages puppet-agent recommends: ii augeas-tools 1.14.0-1 ii debconf-utils 1.5.82 ii lsb-release12.0-1 ii ruby-selinux 3.4-1+b6 Versions of packages puppet-agent suggests: pn hiera-eyaml ii puppet-module-puppetlabs-augeas-core 1.1.2-1 ii puppet-module-puppetlabs-cron-core 1.1.0+dfsg1-1 ii puppet-module-puppetlabs-host-core 1.1.0-1 ii puppet-module-puppetlabs-mount-core1.0.4+dfsg1-2 ii puppet-module-puppetlabs-selinux-core 1.2.0-1 ii puppet-module-puppetlabs-sshkeys-core 2.3.0-1 pn puppet-module-puppetlabs-stdlib ii ruby-hocon 1.3.1-2 pn ruby-msgpack -- debconf information excluded
Bug#1054664: puppet-module-puppetlabs-cron-core: after installing, still get: Resource type 'Cron' was not found
Package: puppet-module-puppetlabs-cron-core Version: 1.1.0+dfsg1-1 Severity: normal Dear Maintainer, Installed 'puppet-agent'. Then, when running my years-old puppet-agent- invoking script, I got: ... Info: Loading facts Error: Failed to apply catalog: Resource type 'Cron' was not found (I expected the Puppet agent to proceed normally.) I then 'apt install'ed puppet-module-puppetlabs-cron-core and... got the exact same result. I've done 'apt install puppet-agent' straight off apt.puppetlabs.com for years, and haven't seen this. (I would prefer straight Debian, of course.) Not clear (to me) what's wrong. My understanding from reading the Puppet docs is that 'cron' is no longer builtin to Puppet, but the module is still normally considered an integral part of Puppet. Thank you for your efforts. -- System Information: Debian Release: 12.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.2.0-35-generic (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
