Puppet users - May 2012 - problem with importing node definitions (2.7.14) [SEC=UNCLASSIFIED]

Hi all,

Doing some work with a puppet 2.7.14 installation to see what''s new and
needs to be changed, however i''m seeing unexpected behavior with my
manifests, so my external node directory isn''t being imported.  This is
on a rhel 5 server with the puppet rpms from yum.puppetlabs.com, but the cilent
machines is based on fc17 beta with 2.7.13 rpm (which is with that version for
now, and has ruby-libs 1.9.3)

First, some appropriate filedumps frome manifests directory:

-------
> cat /etc/puppet/manifests/site.pp
import gfedevws-templates
import ''nodes''

-------
> cat /etc/puppet/manifests/gfedevws-templates.pp
class gfedevws-template {
	notify { "gfedevws-template": }
	include common::puppet-cron
	include gfedevws::puppet-conf
}

-------
> cat /etc/puppet/manifests/nodes.pp
node default {
	include common::puppet-cron
	notify ( "Default node": }
	include gfedevws::puppet-conf
}

#node gfedev-fc17test {
#	include common::puppet-cron
#	notify ( "gfedev in node.pp": }
#	include gfedevws::puppet-conf
#}

import ''gfedevws/*.pp''

-------
> ls /etc/puppet/manifests/gfedevws/
gfedev-fc17test.pp   init.pp

-------
> cat /etc/puppet/manifests/gfedevws/init.pp
import "*"

-------
> cat /etc/puppet/manifests/gfedevws/gfedev-fc17test.pp
node gfedev-fc17test {
	include gfedevws-template
	notify { "gfedevws/gfedev-fc17test" : }
}

-------

Every time I run puppet on the client, it falls through to the default node, or
if I comment out the default node it does nothing.  The one time I uncommented
the gfedev-fc17test node entry in nodes pp it applied that correctly, and
didn''t complain of duplicate node defintion as in previous releases. 
However I''m unable to make it apply the configuration in the imported
gfedevws subdirectory.

I know import is frowned upon, but at this stage its still valid for node
definition/manifests, and should be working correctly, unless i''m
missing something.  All the modules actually used are also correct as far as I
can see.

Is there a way I can check or prove if those files are even being parsed by
puppet?  running my puppetmaster with debug doesn''t seem to trigger
anything useful.

Regards,

Daniel

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

What is the output if you say:
          puppet cert list --all
on the puppet master ?
I am thinking it could be as simple as a typo in the node name.

On May 14, 2012, at 3:15 AM, Daniel Dekok wrote:
> Hi all,
> 
> Doing some work with a puppet 2.7.14 installation to see what''s
new and needs to be changed, however i''m seeing unexpected behavior
with my manifests, so my external node directory isn''t being imported. 
This is on a rhel 5 server with the puppet rpms from yum.puppetlabs.com, but the
cilent machines is based on fc17 beta with 2.7.13 rpm (which is with that
version for now, and has ruby-libs 1.9.3)
> 
> First, some appropriate filedumps frome manifests directory:
> 
> -------
> 
>> cat /etc/puppet/manifests/site.pp
> import gfedevws-templates
> import ''nodes''
> 
> -------
> 
>> cat /etc/puppet/manifests/gfedevws-templates.pp
> class gfedevws-template {
> 	notify { "gfedevws-template": }
> 	include common::puppet-cron
> 	include gfedevws::puppet-conf
> }
> 
> -------
> 
>> cat /etc/puppet/manifests/nodes.pp
> node default {
> 	include common::puppet-cron
> 	notify ( "Default node": }
> 	include gfedevws::puppet-conf
> }
> 
> #node gfedev-fc17test {
> #	include common::puppet-cron
> #	notify ( "gfedev in node.pp": }
> #	include gfedevws::puppet-conf
> #}
> 
> import ''gfedevws/*.pp''
> 
> -------
> 
>> ls /etc/puppet/manifests/gfedevws/
> gfedev-fc17test.pp   init.pp
> 
> -------
> 
>> cat /etc/puppet/manifests/gfedevws/init.pp
> 
> import "*"
> 
> -------
> 
>> cat /etc/puppet/manifests/gfedevws/gfedev-fc17test.pp
> node gfedev-fc17test {
> 	include gfedevws-template
> 	notify { "gfedevws/gfedev-fc17test" : }
> }
> 
> -------
> 
> Every time I run puppet on the client, it falls through to the default
node, or if I comment out the default node it does nothing.  The one time I
uncommented the gfedev-fc17test node entry in nodes pp it applied that
correctly, and didn''t complain of duplicate node defintion as in
previous releases.  However I''m unable to make it apply the
configuration in the imported gfedevws subdirectory.
> 
> I know import is frowned upon, but at this stage its still valid for node
definition/manifests, and should be working correctly, unless i''m
missing something.  All the modules actually used are also correct as far as I
can see.
> 
> Is there a way I can check or prove if those files are even being parsed by
puppet?  running my puppetmaster with debug doesn''t seem to trigger
anything useful.
> 
> Regards,
> 
> Daniel
> 
> -- 
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
> 
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

I hope not, i''ll feel like a right dill
> puppet cert list --all
+ gfedev-fc17test.bom.gov.au (70:B8:34:3D:50:36:D9:F6:C1:C3:4B:D5:3C:55:C3:5B)
+ ho-mantis-op.bom.gov.au    (75:77:30:84:7E:3E:F9:AB:34:3A:18:E4:15:13:6F:FE)
(alt names: DNS:ho-mantis-op.bom.gov.au, DNS:puppet, DNS:puppet.bom.gov.au)

Thanks,

Daniel
________________________________________
From: puppet-users@googlegroups.com [puppet-users@googlegroups.com] On Behalf Of
Dan White [ygor@comcast.net]
Sent: Tuesday, May 15, 2012 9:53 AM
To: puppet-users@googlegroups.com
Subject: Re: [Puppet Users] problem with importing node definitions (2.7.14)
[SEC=UNCLASSIFIED]

What is the output if you say:
          puppet cert list --all
on the puppet master ?
I am thinking it could be as simple as a typo in the node name.

On May 14, 2012, at 3:15 AM, Daniel Dekok wrote:
> Hi all,
>
> Doing some work with a puppet 2.7.14 installation to see what''s
new and needs to be changed, however i''m seeing unexpected behavior
with my manifests, so my external node directory isn''t being imported. 
This is on a rhel 5 server with the puppet rpms from yum.puppetlabs.com, but the
cilent machines is based on fc17 beta with 2.7.13 rpm (which is with that
version for now, and has ruby-libs 1.9.3)
>
> First, some appropriate filedumps frome manifests directory:
>
> -------
>
>> cat /etc/puppet/manifests/site.pp
> import gfedevws-templates
> import ''nodes''
>
> -------
>
>> cat /etc/puppet/manifests/gfedevws-templates.pp
> class gfedevws-template {
>       notify { "gfedevws-template": }
>       include common::puppet-cron
>       include gfedevws::puppet-conf
> }
>
> -------
>
>> cat /etc/puppet/manifests/nodes.pp
> node default {
>       include common::puppet-cron
>       notify ( "Default node": }
>       include gfedevws::puppet-conf
> }
>
> #node gfedev-fc17test {
> #     include common::puppet-cron
> #     notify ( "gfedev in node.pp": }
> #     include gfedevws::puppet-conf
> #}
>
> import ''gfedevws/*.pp''
>
> -------
>
>> ls /etc/puppet/manifests/gfedevws/
> gfedev-fc17test.pp   init.pp
>
> -------
>
>> cat /etc/puppet/manifests/gfedevws/init.pp
>
> import "*"
>
> -------
>
>> cat /etc/puppet/manifests/gfedevws/gfedev-fc17test.pp
> node gfedev-fc17test {
>       include gfedevws-template
>       notify { "gfedevws/gfedev-fc17test" : }
> }
>
> -------
>
> Every time I run puppet on the client, it falls through to the default
node, or if I comment out the default node it does nothing.  The one time I
uncommented the gfedev-fc17test node entry in nodes pp it applied that
correctly, and didn''t complain of duplicate node defintion as in
previous releases.  However I''m unable to make it apply the
configuration in the imported gfedevws subdirectory.
>
> I know import is frowned upon, but at this stage its still valid for node
definition/manifests, and should be working correctly, unless i''m
missing something.  All the modules actually used are also correct as far as I
can see.
>
> Is there a way I can check or prove if those files are even being parsed by
puppet?  running my puppetmaster with debug doesn''t seem to trigger
anything useful.
>
> Regards,
>
> Daniel
>
> --
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

At the risk of making a few pickle jokes, 
puppet is not going to match "gfedev-fc17test.bom.gov.au" to
"node gfedev-fc17test"

Use the full name and apples she''ll be.  (Did I use that correctly ? 
I''m just a sooky Seppo practicing strine)


“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)

----- Daniel Dekok <D.Dekok@bom.gov.au> wrote:
> I hope not, i''ll feel like a right dill
> 
> > puppet cert list --all
> + gfedev-fc17test.bom.gov.au
(70:B8:34:3D:50:36:D9:F6:C1:C3:4B:D5:3C:55:C3:5B)
> + ho-mantis-op.bom.gov.au   
(75:77:30:84:7E:3E:F9:AB:34:3A:18:E4:15:13:6F:FE) (alt names:
DNS:ho-mantis-op.bom.gov.au, DNS:puppet, DNS:puppet.bom.gov.au)
> 
> Thanks,
> 
> Daniel
> ________________________________________
> From: puppet-users@googlegroups.com [puppet-users@googlegroups.com] On
Behalf Of Dan White [ygor@comcast.net]
> Sent: Tuesday, May 15, 2012 9:53 AM
> To: puppet-users@googlegroups.com
> Subject: Re: [Puppet Users] problem with importing node definitions
(2.7.14) [SEC=UNCLASSIFIED]
> 
> What is the output if you say:
>           puppet cert list --all
> on the puppet master ?
> I am thinking it could be as simple as a typo in the node name.
> 
> On May 14, 2012, at 3:15 AM, Daniel Dekok wrote:
> 
> > Hi all,
> >
> > Doing some work with a puppet 2.7.14 installation to see
what''s new and needs to be changed, however i''m seeing
unexpected behavior with my manifests, so my external node directory
isn''t being imported.  This is on a rhel 5 server with the puppet rpms
from yum.puppetlabs.com, but the cilent machines is based on fc17 beta with
2.7.13 rpm (which is with that version for now, and has ruby-libs 1.9.3)
> >
> > First, some appropriate filedumps frome manifests directory:
> >
> > -------
> >
> >> cat /etc/puppet/manifests/site.pp
> > import gfedevws-templates
> > import ''nodes''
> >
> > -------
> >
> >> cat /etc/puppet/manifests/gfedevws-templates.pp
> > class gfedevws-template {
> >       notify { "gfedevws-template": }
> >       include common::puppet-cron
> >       include gfedevws::puppet-conf
> > }
> >
> > -------
> >
> >> cat /etc/puppet/manifests/nodes.pp
> > node default {
> >       include common::puppet-cron
> >       notify ( "Default node": }
> >       include gfedevws::puppet-conf
> > }
> >
> > #node gfedev-fc17test {
> > #     include common::puppet-cron
> > #     notify ( "gfedev in node.pp": }
> > #     include gfedevws::puppet-conf
> > #}
> >
> > import ''gfedevws/*.pp''
> >
> > -------
> >
> >> ls /etc/puppet/manifests/gfedevws/
> > gfedev-fc17test.pp   init.pp
> >
> > -------
> >
> >> cat /etc/puppet/manifests/gfedevws/init.pp
> >
> > import "*"
> >
> > -------
> >
> >> cat /etc/puppet/manifests/gfedevws/gfedev-fc17test.pp
> > node gfedev-fc17test {
> >       include gfedevws-template
> >       notify { "gfedevws/gfedev-fc17test" : }
> > }
> >
> > -------
> >
> > Every time I run puppet on the client, it falls through to the default
node, or if I comment out the default node it does nothing.  The one time I
uncommented the gfedev-fc17test node entry in nodes pp it applied that
correctly, and didn''t complain of duplicate node defintion as in
previous releases.  However I''m unable to make it apply the
configuration in the imported gfedevws subdirectory.
> >
> > I know import is frowned upon, but at this stage its still valid for
node definition/manifests, and should be working correctly, unless i''m
missing something.  All the modules actually used are also correct as far as I
can see.
> >
> > Is there a way I can check or prove if those files are even being
parsed by puppet?  running my puppetmaster with debug doesn''t seem to
trigger anything useful.
> >
> > Regards,
> >
> > Daniel
> >
> > --
> > 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+unsubscribe@googlegroups.com.
> > For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
> >
> 
> --
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
> 
> -- 
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
> 
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On May 15, 7:38 am, Dan White <y...@comcast.net>
wrote:
> At the risk of making a few pickle jokes,
> puppet is not going to match "gfedev-fc17test.bom.gov.au" to
"node gfedev-fc17test"

Really? It used to do.  I''m not yet running the latest Puppet, but all
my certnames are FQDNs, all my node declarations use the nodes'' simple
names, and everything works as expected.


John

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On May 14, 2:15 am, Daniel Dekok <D.De...@bom.gov.au> wrote:
[...]
> Is there a way I can check or prove if those files are even being parsed by
puppet?  running my puppetmaster with debug doesn''t seem to trigger
anything useful.

It is not obvious to me why your code is not working (supposing that
the places where ''('' appears instead of ''{''
are some sort of typo, not
a faithful representation of the actual code).  You should be able to
test whether the manifest is processed, however, by invoking one of
Puppet''s message functions (e.g. notice()) at top level in the
imported manifest, or by declaring a Notify resource there.


John

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

-----Original Message-----
From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On
Behalf Of Dan White
Sent: Tuesday, 15 May 2012 10:38 PM
To: puppet-users@googlegroups.com
Subject: RE: [Puppet Users] problem with importing node definitions (2.7.14)
[SEC=UNCLASSIFIED]

At the risk of making a few pickle jokes, puppet is not going to match
"gfedev-fc17test.bom.gov.au" to "node gfedev-fc17test"

Use the full name and apples she''ll be.  (Did I use that correctly ? 
I''m just a sooky Seppo practicing strine)

Nice first pass on the strine.

Looks like I''ve worked it out, wasn''t to do with the hostname
at all, I did try this suggestion, there was no change to the result.  The
shortname still work as it did in previous versions.

It looks like the import directory of "gfedevws/*.pp" wasn''t
being loaded as it had the same name as a module, so It may have been confused
between that directive and the autoloader?   I ended up chaging the nodes
directory and import to "gfedevws-nodes/*.pp" and viola, its being
imported, and parsing the node definition correctly.

Somewhat obscure, but happy its going along.

Thanks,

Daniel



"Sometimes I think the surest sign that intelligent life exists elsewhere
in the universe is that none of it has tried to contact us."
Bill Waterson (Calvin & Hobbes)

----- Daniel Dekok <D.Dekok@bom.gov.au> wrote:
> I hope not, i''ll feel like a right dill
> 
> > puppet cert list --all
> + gfedev-fc17test.bom.gov.au
(70:B8:34:3D:50:36:D9:F6:C1:C3:4B:D5:3C:55:C3:5B)
> + ho-mantis-op.bom.gov.au   
(75:77:30:84:7E:3E:F9:AB:34:3A:18:E4:15:13:6F:FE) (alt names:
DNS:ho-mantis-op.bom.gov.au, DNS:puppet, DNS:puppet.bom.gov.au)
> 
> Thanks,
> 
> Daniel
> ________________________________________
> From: puppet-users@googlegroups.com [puppet-users@googlegroups.com] On 
> Behalf Of Dan White [ygor@comcast.net]
> Sent: Tuesday, May 15, 2012 9:53 AM
> To: puppet-users@googlegroups.com
> Subject: Re: [Puppet Users] problem with importing node definitions 
> (2.7.14) [SEC=UNCLASSIFIED]
> 
> What is the output if you say:
>           puppet cert list --all
> on the puppet master ?
> I am thinking it could be as simple as a typo in the node name.
> 
> On May 14, 2012, at 3:15 AM, Daniel Dekok wrote:
> 
> > Hi all,
> >
> > Doing some work with a puppet 2.7.14 installation to see
what''s new
> > and needs to be changed, however i''m seeing unexpected
behavior with
> > my manifests, so my external node directory isn''t being
imported.
> > This is on a rhel 5 server with the puppet rpms from 
> > yum.puppetlabs.com, but the cilent machines is based on fc17 beta 
> > with 2.7.13 rpm (which is with that version for now, and has 
> > ruby-libs 1.9.3)
> >
> > First, some appropriate filedumps frome manifests directory:
> >
> > -------
> >
> >> cat /etc/puppet/manifests/site.pp
> > import gfedevws-templates
> > import ''nodes''
> >
> > -------
> >
> >> cat /etc/puppet/manifests/gfedevws-templates.pp
> > class gfedevws-template {
> >       notify { "gfedevws-template": }
> >       include common::puppet-cron
> >       include gfedevws::puppet-conf
> > }
> >
> > -------
> >
> >> cat /etc/puppet/manifests/nodes.pp
> > node default {
> >       include common::puppet-cron
> >       notify ( "Default node": }
> >       include gfedevws::puppet-conf
> > }
> >
> > #node gfedev-fc17test {
> > #     include common::puppet-cron
> > #     notify ( "gfedev in node.pp": }
> > #     include gfedevws::puppet-conf
> > #}
> >
> > import ''gfedevws/*.pp''
> >
> > -------
> >
> >> ls /etc/puppet/manifests/gfedevws/
> > gfedev-fc17test.pp   init.pp
> >
> > -------
> >
> >> cat /etc/puppet/manifests/gfedevws/init.pp
> >
> > import "*"
> >
> > -------
> >
> >> cat /etc/puppet/manifests/gfedevws/gfedev-fc17test.pp
> > node gfedev-fc17test {
> >       include gfedevws-template
> >       notify { "gfedevws/gfedev-fc17test" : } }
> >
> > -------
> >
> > Every time I run puppet on the client, it falls through to the default
node, or if I comment out the default node it does nothing.  The one time I
uncommented the gfedev-fc17test node entry in nodes pp it applied that
correctly, and didn''t complain of duplicate node defintion as in
previous releases.  However I''m unable to make it apply the
configuration in the imported gfedevws subdirectory.
> >
> > I know import is frowned upon, but at this stage its still valid for
node definition/manifests, and should be working correctly, unless i''m
missing something.  All the modules actually used are also correct as far as I
can see.
> >
> > Is there a way I can check or prove if those files are even being
parsed by puppet?  running my puppetmaster with debug doesn''t seem to
trigger anything useful.
> >
> > Regards,
> >
> > Daniel
> >
> > --
> > 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+unsubscribe@googlegroups.com.
> > For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
> >
> 
> --
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
> 
> --
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
> 
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.