[Puppet Users] "puppet module generate" using wrong name for directory?

[Dennis Jacobfeuerborn]

Hi,
I'm looking into writing proper modules and starting off with "puppet 
module generate" but it seems the tool uses an invalid name for the 
directory.
When i specify "mymodule" as a name it tells me I need to use a dash 
separated name and when I use "myname-mymodule" then the module
gets generated but using the "mymodule" class as either "mymodule" or 
"myname-mymodule" only results in puppet not being able to find the class.

The fix seems to be to rename the directory to "mymodule". After that the 
"mymodule" class can be used in manifests.
Am I doing something wrong or why does the puppet module tool create 
directories with an invalid name?

Regards,
   Dennis

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Status of bug #8040?

[Dennis Jacobfeuerborn]

Hi,
what plans are in place to deal with bug #8040: 
http://projects.puppetlabs.com/issues/8040

I have some Puppet experience but I'm also looking at Chef and Ansible 
right now in order to determine which configuration management to commit to 
and being able to build and re-use components is a major issue.
Right now this bug seems to make it almost impossible to build non-trivial 
components and the workaround mentioned isn't really useful as a) it means 
you have to lace each and every class with dependencies just to anchor them 
to their parents an b) you will not be able to use components from e.g. 
puppet-forge because they will most likely miss this anchoring as well.

So what is the story here? Is this being worked on in some concrete way or 
is re-usability not something that is considered important in the Puppet 
ecosystem?

Regards,
  Dennis

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Inventory access forbidden

[Dennis Jacobfeuerborn]

Thanks, that was indeed the issue. I just appended it to the file and 
didn't notice the catch-all rule.

On Thursday, July 5, 2012 10:06:10 AM UTC+2, Matthew Burgess wrote:
>
> On Thu, Jul 5, 2012 at 2:52 AM, Dennis Jacobfeuerborn 
>  wrote: 
> > Hi, 
> > I've just set up a puppet server using passenger plus the dashboard and 
> > these parts all work fine but now I have enabled the inventory and added 
> > this to the auth.conf: 
> > 
> > path /facts 
> > auth any 
> > method find, search 
> > allow * 
>
> Where abouts in auth.conf did you place this configuration?  Note that 
> it has to be placed *before* the last stanza in the default config 
> which reads: 
>
> # this one is not strictly necessary, but it has the merit 
> # to show the default policy which is deny everything else 
> path / 
> auth any 
>
> Hope this helps, 
>
> Matt. 
>

-- 
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/-/HYGQ0qx1tCQJ.
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.

[Puppet Users] Inventory access forbidden

[Dennis Jacobfeuerborn]

Hi,
I've just set up a puppet server using passenger plus the dashboard and 
these parts all work fine but now I have enabled the inventory and added 
this to the auth.conf:

path /facts
auth any
method find, search
allow *

The dashboard shows "Could not retrieve facts from inventory service: 403 
"Forbidden"" and in the system log i find this:
Jul  5 03:46:35 puppet2 puppet-master[5221]: Denying access: Forbidden 
request: puppet.local(192.168.2.45) access to /facts/puppet.local [find] at 
line 99
Jul  5 03:46:35 puppet2 puppet-master[5221]: Forbidden request: 
puppet.local(192.168.2.45) access to /facts/puppet.local [find] at line 99

Any ideas why this isn't working?

Regards,
  Dennis

-- 
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/-/OewwSLyyFjEJ.
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.

[Puppet Users] Re: Only write file if copy on master is present

[Dennis Jacobfeuerborn]

I didn't mean to imply that this was your fault and I already knew that the 
puppet support probably was missing because it's quite tricky to implement.
Since I've started looking into writing my own functions and modules and 
get a bit deeper into puppet I might actually look into this myself if I 
find the time. If I make any progress there you can expect a pull request 
for the changes :)

On Monday, April 23, 2012 3:57:08 PM UTC+2, matti wrote:
>
> Hi,
>
> On Monday, 23 April 2012 13:59:00 UTC+1, Dennis Jacobfeuerborn wrote:
>
>> Thanks, this looks like it will do the trick. The lack of puppet:// 
>> support probably means I will have to hard-code a path to a directory 
>> somewhere but that shouldn't be to big of a deal.
>>
> [...]
>
> Apologies for that :-(
>
> Adding support for "puppet://" is quite tricky (there is a lot going on 
> under-the-hood with this one), and I never have the time to do it (unless 
> somebody is willing to help out and/or sponsor).
>
> For the time being, please bare with fully-qualified paths ...
>
> KW 
>

-- 
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/-/NAMjjrnooXwJ.
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.

[Puppet Users] Re: Only write file if copy on master is present

[Dennis Jacobfeuerborn]

Thanks, this looks like it will do the trick. The lack of puppet:// support 
probably means I will have to hard-code a path to a directory somewhere but 
that shouldn't be to big of a deal.

On Sunday, April 22, 2012 8:49:50 PM UTC+2, matti wrote:
>
> Hi,
>
> On Sunday, 22 April 2012 02:15:19 UTC+1, Dennis Jacobfeuerborn wrote:
>  
> [...]
>
>> The twist I need to add though is that I only want to do this if a copy 
>> of that file for the node exists on the server. If this file doesn't
>>
> exists then I want puppet to not replace the file on the client and not 
>> restart the service.
>>
>> Is there a way to accomplish this sort of conditional execution?
>>
>
> Have a look on: 
> https://github.com/kwilczynski/puppet-functions/blob/master/lib/puppet/parser/functions/exists.rb
>  
>
> Maybe it will be of any use to you in this case.
>
> KW
>

-- 
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/-/5HEbo-N91H8J.
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.

[Puppet Users] Only write file if copy on master is present

[Dennis Jacobfeuerborn]

Hi,
I'm trying to find a way to configure the firewall on centos systems using 
puppet by copying the /etc/sysconfig/iptables file and restarting the 
iptables service.
That part is simple to accomplish. The twist I need to add though is that I 
only want to do this if a copy of that file for the node exists on the 
server. If this file doesn't
exists then I want puppet to not replace the file on the client and not 
restart the service.

Is there a way to accomplish this sort of conditional execution?

Regards,
  Dennis

-- 
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/-/oAUk_tpcqooJ.
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.

[Puppet Users] Re: Bug #9388 prevents us from upgrading to 2.7.x

[Dennis Jacobfeuerborn]

Good news, thanks! Bug #9388 should probably be closed or more correctly be 
marked as a duplicate of bug 
#9109so that the people watching 
that bug know the problem is fixed.

Regards,
  Dennis

-- 
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/-/vXv_uIDW5_IJ.
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.

[Puppet Users] Bug #9388 prevents us from upgrading to 2.7.x

[Dennis Jacobfeuerborn]

Hi,
can somebody who understands the puppet codebase take a look at bug #9388?
I isolated the problem and it seems that the yaml cache files are not 
properly updated when mongrel is used.
Cody Robertson added the the switch from GET to POST/PUT between 2.6.x and 
2.7.x might be the problem and that the POST/PUT code might not update the 
cache files while the "old" GET code does.

Given that 2.7.x is considered stable I'm getting a bit nervous that such a 
bug is still present and we are basically stuck on an outdated version.

Regards,
  Dennis

-- 
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/-/zd298i0fS2sJ.
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.

[Puppet Users] puppet fails to retrieve catalog

[Dennis Jacobfeuerborn]

Hi,
I've got a problem where clients apparently randomly lose the ability to 
retrieve catalogs.
This is what I end up seeing in the log:

puppet-agent[26510]: Starting Puppet client version 2.6.6
puppet-agent[26510]: Could not retrieve catalog from remote server: 
puppet-agent[26510]: Using cached catalog
puppet-agent[26510]: Could not retrieve catalog; skipping run

Notice that no actual reason is given which makes finding the cause 
difficult. This also happened with 0.25.5 and I upgraded both the server and 
one client hoping that this would fix things or at least provide a proper 
error message but that didn't work.

Strangely enough when I run "tcpdump -i eth0 port 8140" on the client in 
order to see if the client manages to communicate with the server this 
apparently fixes the problem and the client can retrieve catalogs again.

Any ideas on how the fix this problem?

Regards,
  Dennis

-- 
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.

Re: [Puppet Users] Re: puppet 2.6.4 installation options for redhat/centos

[Dennis Jacobfeuerborn]

Do you plan to bring these builds into Koji to make them more visible?

Regards,
  Dennis

-- 
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.

[Puppet Users] Re: Client no longer reads catalog

[Dennis Jacobfeuerborn]

Wow, apparently running a "tcpdump -nn port 8140" un-wedges puppet and 
brings things back to normal. Problem is that I have no clue how or why 
running a tcpdump could possibly matter here even though it apparently does. 
Does anyone have an idea what might be going on here?

Regards,
  Dennis

-- 
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.

[Puppet Users] Client no longer reads catalog

[Dennis Jacobfeuerborn]

Hi,
One of my machines has started to refuse reading the catalog from the 
server. The log shows the following:

Mar 16 15:36:42 wmembf10 puppetd[7411]: Starting Puppet client version 
0.25.5
Mar 16 15:36:46 wmembf10 puppetd[7411]: Could not retrieve catalog from 
remote server: 
Mar 16 15:36:46 wmembf10 puppetd[7411]: Using cached catalog
Mar 16 15:36:46 wmembf10 puppetd[7411]: Could not retrieve catalog; skipping 
run

Server and Client are both version 0.25.5. An identical System (wmembf09) 
has no such problems and updates the configuration just fine.
Since I don't get any indication what the problem could be I'm at a loss 
what to do about this. Any ideas?

Regards,
  Dennis

-- 
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.