Can you undo the change in foreman, see if the problem goes away, then
reimplement the change and see if the problem comes back? That would go a
long way toward isolating the cause.
On Thursday, October 6, 2016, wrote:
>
>
> On Wednesday, October 5, 2016 at 2:32:37 PM UTC-5,
On Wednesday, October 5, 2016 at 2:32:37 PM UTC-5, re-g...@wiu.edu wrote:
>
> I installed the puppet module saz-rsyslog from puppet forge.
> I use The Foreman to configure nodes. The Foreman is used by puppet via
> configuration [master] "external_nodes" "/etc/puppet/node.rb"
>
> Since the
On Thursday, October 6, 2016 at 8:27:40 AM UTC-5, jcbollinger wrote:
>
>
>
> On Wednesday, October 5, 2016 at 2:32:37 PM UTC-5, re-g...@wiu.edu wrote:
>>
>> I installed the puppet module saz-rsyslog from puppet forge.
>> I use The Foreman to configure nodes. The Foreman is used by puppet via
>>
On Wednesday, October 5, 2016 at 4:15:21 PM UTC+2, jcbollinger wrote:
>
>
>
> On Tuesday, October 4, 2016 at 6:55:36 AM UTC-5, Prunk Dump wrote:
>>
>> Hello puppet users !
>>
>> My problem is simple. I use the following classes in three different
>> stages (setup/main/runtime) :
>>
>> class {
On Wednesday, October 5, 2016 at 3:58:38 PM UTC-5, Rob Nelson wrote:
>
> RG, typically the Duplication declaration message is followed by some
> indicator of the file where it is duplicated and the line number. Are you
> receiving that information and maybe snipped it off the end of the
On Wednesday, October 5, 2016 at 2:32:37 PM UTC-5, re-g...@wiu.edu wrote:
>
> I installed the puppet module saz-rsyslog from puppet forge.
> I use The Foreman to configure nodes. The Foreman is used by puppet via
> configuration [master] "external_nodes" "/etc/puppet/node.rb"
>
> Since the
It was just an example to reproduce it.
On Thursday, October 6, 2016 at 12:49:11 PM UTC+3, Rob Nelson wrote:
>
> I do not know that a workaround is needed. I believe that when a package
> is upgraded, the old and new versions should show up in the logs already,
> so the notify may not be
I do not know that a workaround is needed. I believe that when a package is
upgraded, the old and new versions should show up in the logs already, so
the notify may not be needed.
On Thursday, October 6, 2016, Erez Zarum wrote:
> Ok, so the workaround is to use a variable
Ok, so the workaround is to use a variable (set default), if that fails,
try the fact.
Thanks!
On Thursday, October 6, 2016 at 10:45:26 AM UTC+3, R.I. Pienaar wrote:
>
>
>
> - Original Message -
> > From: "Erez Zarum"
> > To: "puppet-users"
- Original Message -
> From: "Erez Zarum"
> To: "puppet-users"
> Sent: Thursday, 6 October, 2016 09:40:44
> Subject: [Puppet Users] Facts and Resource relationships
> I'm not sure if it's a bug or an expected behavior.
>
> I have
I'm not sure if it's a bug or an expected behavior.
I have written a simple fact for a module that returns a version of a
binary file, it executes: "binary --version" and then parses the version,
no issues there, it works.
The issue i am having is relying on this fact in case the binary file
11 matches
Mail list logo