On Thu, Jan 10, 2013 at 3:18 PM, iamauser <tapas.sara...@gmail.com> wrote:
> Running puppet agent with a blank node default didn't throw any error and
> prints out the notification. I get this message when puppet agent runs on
> 'node_name'.
>
> Notice: I AM DEFAULTing...
> Notice: /Stage[main]//Node[default]/Notify[I AM DEFAULTing...]/message:
> defined 'message' as 'I AM DEFAULTing...'
>
> I tried to give another notify message in one of the classes
> (dyd::agents), but it didn't print that out. So it is definitely not
> considering the policies defined in that class.
>
> Just to note, without the ENC, include dyd::agents in site.pp works and
> propagate the policies and prints the notification.
>
>
>
Ahh,
I think I see something. Looking at this:
---
environment: production
classes:
defaultcls:
dyd::agents:
It looks like the classes are being listed as hashes without values, and
not as an array of class names. How are you generating this YAML? It
should be displaying like:
---
environment:
classes:
- defaultcls
- dyd::agents
(note the dashes) When you ORIGINALLY gave us the output, it was being
output correctly, but when you pasted the output when you run the ENC as
the puppet user, it seems to be incorrect. ENCs can pass parameters for
class declarations like so:
---
environment: production
classes:
defaultcls:
parameter: value
dyd::agents:
parameter: value
...but the fact that you're not passing parameters may be messing with
Puppet (I'm going off the top of my head without validating this, so please
someone else speak up if what I'm saying is not entirely true).
-Thanks
>
>
>
> On Thursday, January 10, 2013 5:02:08 PM UTC-6, Gary Larizza wrote:
>
>>
>>
>>
>> On Thu, Jan 10, 2013 at 2:56 PM, iamauser <tapas....@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Here is the output. Sorry I didn't get it the first time :)
>>>
>>> ]# su -s /bin/sh puppet -c "/usr/local/bin/enclassifier node_name"
>>> ---
>>> environment: production
>>> classes:
>>> defaultcls:
>>> dyd::agents:
>>>
>>
>> Cool. Okay, so you said initially that site.pp exists, but it's blank -
>> there's no default node at all. Have you tried creating a blank default
>> node declaration (or one with a simple notify statement) to debug what's
>> going on? I'd do that next just to rule out a missing default node causing
>> issues (I know there was a bug awhile back where Puppet threw a fit
>> whenever it didn't find a default node declaration, but I can't remember
>> how it was resolved).
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/dcC_pakJNe0J.
>
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
--
Gary Larizza
Professional Services Engineer
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
