Package: puppet Version: 3.7.2-1 Severity: normal Tags: upstream Hi maintainer,
We normally use `kill -USR1` on the puppet agent process to trigger an agent run without restarting the process. When attempting this on jessie (rather than wheezy), a run is not triggered, and the following is logged to syslog: > Nov 14 21:10:48 eruption puppet-agent[21975]: Caught USR1; calling reload > Nov 14 21:10:48 eruption puppet-agent[12969]: Could not autoload > puppet/indirector/node/rest: current thread not owner > Nov 14 21:10:48 eruption puppet-agent[12969]: Unable to fetch my node > definition, but the agent run will continue: > Nov 14 21:10:48 eruption puppet-agent[12969]: Could not autoload > puppet/indirector/node/rest: current thread not owner > Nov 14 21:10:48 eruption puppet-agent[12969]: Could not autoload > puppet/feature/external_facts: current thread not owner > Nov 14 21:10:48 eruption puppet-agent[12969]: Failed to apply catalog: Could > not autoload puppet/feature/external_facts: current thread not owner This is upstream bug PUP-1635: https://tickets.puppetlabs.com/browse/PUP-1635 The bug is also present when we use the Puppetlabs APT repository (rather than the Debian jessie archive), which contains version 3.7.3-1puppetlabs1 of puppet. Many thanks, Chris -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages puppet depends on: ii init-system-helpers 1.21 ii puppet-common 3.7.2-1 ii ruby 1:2.1.0.4 ii ruby2.1 [ruby-interpreter] 2.1.4-1 puppet recommends no packages. Versions of packages puppet suggests: pn etckeeper <none> pn puppet-el <none> pn vim-puppet <none> -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
