[Puppet - Feature #2198] Install multiple package within a single call to the package manager
Issue #2198 has been updated by Stéphan Gorget. The last update is here : http://github.com/phantez/puppet/tree/features/master/2198 But I guess many changes have be done on resource transactions and the code might have to be update. Feature #2198: Install multiple package within a single call to the package manager http://projects.reductivelabs.com/issues/2198 Author: Stéphan Gorget Status: Needs design decision Priority: Normal Assigned to: Stéphan Gorget Category: transactions Target version: unplanned Affected version: 0.25.0 Keywords: Branch: During the configuration applying process the package manager is called for each package installation. It is possible to reduce the number of calls to the package manager by gathering package installation and delayed some package installation. Naturally, this modification should not break the dependency graph. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #3157] (Unreviewed) puppetdoc should support a site-wide (site.pp) README
Issue #3157 has been reported by Joe McDonagh. Bug #3157: puppetdoc should support a site-wide (site.pp) README http://projects.reductivelabs.com/issues/3157 Author: Joe McDonagh Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Affected version: 0.25.4 Keywords: puppetdoc awesome Branch: This way I could ditch my external wiki for it and stuff it all into a nice README of my autogenerated puppet docs. I talked to Brice about this on the channel and he seemed to think it was a good idea, -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #3158] (Unreviewed) puppetdoc should show a define's full resources like a class
Issue #3158 has been reported by Joe McDonagh. Bug #3158: puppetdoc should show a define's full resources like a class http://projects.reductivelabs.com/issues/3158 Author: Joe McDonagh Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Affected version: 0.25.4 Keywords: puppetdoc, awesome Branch: Right now, puppetdoc only shows a define's arguments. It should show the define's resources just like a class, cause right now you kind of have no idea what the define is actually for by strictly looking at the docs. Also talked to Brice about this one on IRC and he liked it I think. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #3158] (Accepted) puppetdoc should show a define's full resources like a class
Issue #3158 has been updated by James Turnbull. Category set to documentation Status changed from Unreviewed to Accepted Assigned to set to Brice Figureau Brice - let me know if you have time constraints! Bug #3158: puppetdoc should show a define's full resources like a class http://projects.reductivelabs.com/issues/3158 Author: Joe McDonagh Status: Accepted Priority: Normal Assigned to: Brice Figureau Category: documentation Target version: Affected version: 0.25.4 Keywords: puppetdoc, awesome Branch: Right now, puppetdoc only shows a define's arguments. It should show the define's resources just like a class, cause right now you kind of have no idea what the define is actually for by strictly looking at the docs. Also talked to Brice about this one on IRC and he liked it I think. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #3157] (Accepted) puppetdoc should support a site-wide (site.pp) README
Issue #3157 has been updated by James Turnbull. Category set to documentation Status changed from Unreviewed to Accepted Assigned to set to Brice Figureau Target version set to Statler Bug #3157: puppetdoc should support a site-wide (site.pp) README http://projects.reductivelabs.com/issues/3157 Author: Joe McDonagh Status: Accepted Priority: Normal Assigned to: Brice Figureau Category: documentation Target version: Statler Affected version: 0.25.4 Keywords: puppetdoc awesome Branch: This way I could ditch my external wiki for it and stuff it all into a nice README of my autogenerated puppet docs. I talked to Brice about this on the channel and he seemed to think it was a good idea, -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #3155] (Investigating) Strange if statement regex problem, matches fail with Cannot reassign variable 0
Issue #3155 has been updated by James Turnbull.
Category set to RAL
Status changed from Unreviewed to Investigating
Assigned to set to Brice Figureau
Brice - any ideas?
Bug #3155: Strange if statement regex problem, matches fail with Cannot
reassign variable 0
http://projects.reductivelabs.com/issues/3155
Author: Josh Endries
Status: Investigating
Priority: Normal
Assigned to: Brice Figureau
Category: RAL
Target version:
Affected version: 0.25.4
Keywords:
Branch:
I have been doing work on my puppet server itself. I recently changed this:
pre
if ($environment == 'testing') or ($fqdn =~ /repo[1256].nsdl.org/) {
/pre
To this:
pre
if ($environment == 'testing') or ($fqdn =~ /repo[1256].nsdl.org/) or ($fqdn =~
/puppet.nsdl.org/) {
/pre
And Puppet stopped functioning:
pre
puppetd[20829]: Could not retrieve catalog from remote server: Error 400 on
SERVER: Cannot reassign variable 0 at /etc/puppet/manifests/classes/linux.pp:6
on node puppet.nsdl.org
/pre
This was on 0.25.1, but I upgraded to .4 and it still happens. Anything I try
that matches the $fqdn (or $hostname, which I tried) causes this error.
Anything that doesn't match, works fine, e.g. these don't work:
pre
$fqdn =~ /pupp/
$fqdn =~ /puppet/
$fqdn =~ /^puppet\.nsdl\.org$/
$fqdn =~ /(repo[1256]|puppet).nsdl.org/
/pre
These work:
pre
$fqdn == 'puppet.nsdl.org'
$hostname == 'puppet'
/pre
Here is a trace:
pre
14:49:22 r...@puppet.nsdl.org/etc/puppet puppetmasterd --debug --trace
--verbose --no-daemonize
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does
not exist
debug: Puppet::Type::User::ProviderUser_role_add: file roledel does not exist
debug: Failed to load library 'ldap' for feature 'ldap'
debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/puppet.nsdl.org.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/auth.conf]: Autorequiring File[/etc/puppet]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/rrd]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/bucket]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/public_keys/puppet.nsdl.org.pem]: Autorequiring
File[/etc/puppet/ssl/public_keys]
debug: /File[/var/lib/puppet/reports]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/fileserver.conf]: Autorequiring File[/etc/puppet]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/log/puppet/masterhttp.log]: Autorequiring
File[/var/log/puppet]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/manifests/site.pp]: Autorequiring
File[/etc/puppet/manifests]
debug: /File[/etc/puppet/ssl/private_keys/puppet.nsdl.org.pem]: Autorequiring
File[/etc/puppet/ssl/private_keys]
debug: /File[/etc/puppet/manifests]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/yaml]: Autorequiring File[/var/lib/puppet]
debug: Finishing transaction 23650725397220 with 0 changes
debug: /File[/etc/puppet/ssl/ca/ca_crl.pem]: Autorequiring
File[/etc/puppet/ssl/ca]
debug: /File[/etc/puppet/ssl/ca/ca_pub.pem]: Autorequiring
File[/etc/puppet/ssl/ca]
debug: /File[/etc/puppet/ssl/ca/serial]: Autorequiring File[/etc/puppet/ssl/ca]
debug: /File[/etc/puppet/ssl/ca/requests]: Autorequiring
File[/etc/puppet/ssl/ca]
debug: /File[/etc/puppet/ssl/ca/ca_crt.pem]: Autorequiring
File[/etc/puppet/ssl/ca]
debug: /File[/etc/puppet/ssl/ca/signed]: Autorequiring File[/etc/puppet/ssl/ca]
debug: /File[/etc/puppet/ssl/ca/inventory.txt]: Autorequiring
File[/etc/puppet/ssl/ca]
debug: /File[/etc/puppet/ssl/ca/ca_key.pem]: Autorequiring
File[/etc/puppet/ssl/ca]
debug: /File[/etc/puppet/ssl/ca/private]: Autorequiring File[/etc/puppet/ssl/ca]
debug: /File[/etc/puppet/ssl/ca/private/ca.pass]: Autorequiring
File[/etc/puppet/ssl/ca/private]
debug: Finishing transaction 23650724840360 with 0 changes
debug: Using cached certificate for ca, good until Sun Jun 15 16:52:42 UTC 2014
debug: Using cached certificate for ca, good until Sun Jun 15 16:52:42 UTC 2014
[Puppet - Feature #3154] (Accepted) Capability to represent basic/complex datastructures in external nodes
Issue #3154 has been updated by James Turnbull. Category set to RAL Status changed from Unreviewed to Accepted Target version set to Rowlf It is my understanding that hashes at least are probably going to be in Rowlf... Feature #3154: Capability to represent basic/complex datastructures in external nodes http://projects.reductivelabs.com/issues/3154 Author: Michael DeHaan Status: Accepted Priority: Normal Assigned to: Category: RAL Target version: Rowlf Affected version: 0.25.4 Keywords: Branch: User would like to be able to represent arrays and hashes, as well as nested datastructures, in external nodes for use in templating out things such as interface configurations, where these may need to be logically grouped together by interface name, rather than having to do things like eth0_ip_address and so forth. Lists would be great, ideally complex datastructures would be ideal. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Feature #3153] (Accepted) Network interface type
Issue #3153 has been updated by James Turnbull. Category set to network Status changed from Unreviewed to Accepted Assigned to set to Michael DeHaan Mike - all yours in you want to open Pandora's box I'd love to see what's inside... :) Feature #3153: Network interface type http://projects.reductivelabs.com/issues/3153 Author: Michael DeHaan Status: Accepted Priority: Normal Assigned to: Michael DeHaan Category: network Target version: Affected version: 0.25.4 Keywords: networking types Branch: Talking with user, would be nice to be able to model network interface config in Puppet to faciliate easy changes -- OS installers particularly Anaconda do not allow all options. Taking a look at interface modelling in Cobbler will show some of the things we'd like to represent -- including bonding and arbitrarily named interfaces, as well as some examples of kludgy templates for configuring those on RHEL/Fedora. Will take additional work to make something Debian/Ubuntu other friendly. This seems to also require the need to express arbitrary datastructures in external nodes. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Feature #3137] (Accepted) Type for manipulating gconf
Issue #3137 has been updated by James Turnbull. Category set to newfeature Status changed from Unreviewed to Accepted Target version set to unplanned Feature #3137: Type for manipulating gconf http://projects.reductivelabs.com/issues/3137 Author: Andrew Pollock Status: Accepted Priority: Normal Assigned to: Category: newfeature Target version: unplanned Affected version: development Keywords: gconf Branch: Currently we're managing GNOME mandatory policy by carting around a monolithic /etc/gconf/gconf.xml.mandatory/%gonf-tree.xml, which is a bit ghetto. It makes it difficult to have any granularity in what the mandatory policy contains. I was thinking that it'd be cool if Puppet had gconf support directory, so in the DSL, you'd specify that you wanted something set, and it'd run gconftool for you, and make the necessary modifications See also http://live.gnome.org/GnomeScreensaver/FrequentlyAskedQuestions#I.27m_a_systems_administrator.__How_can_I_set_policies_for_all_users_of_my_system.3F -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #3141] (Investigating) Cannot turn off CA in puppetmasterd
Issue #3141 has been updated by James Turnbull. Status changed from Unreviewed to Investigating Assigned to set to Markus Roberts Bug #3141: Cannot turn off CA in puppetmasterd http://projects.reductivelabs.com/issues/3141 Author: Nicholas Veeser Status: Investigating Priority: Normal Assigned to: Markus Roberts Category: SSL Target version: Affected version: 0.25.3 Keywords: Branch: (may be a duplicate) Trying to run a puppetmaster without it being a CA. It keeps trying to be a CA. It does not find the private key for my provided ca.pem bundle, so it removes it and creates another. So this seems to keep my puppetmaster from correctly authenticating its peers. Am I missing something obvious? I found this in the code: puppet/ssl/certificate_authority.rb class Puppet::SSL::CertificateAuthority def self.ca? return false unless Puppet[:ca] return false unless Puppet[:name] == puppetmasterd return true end end Basically I read this as, if this class is used inside of puppetmasterd, then turn on the certificate authority. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #3143] (Investigating) Puppet should correctly support CA trust chains
Issue #3143 has been updated by James Turnbull. Status changed from Unreviewed to Investigating Assigned to set to Markus Roberts Bug #3143: Puppet should correctly support CA trust chains http://projects.reductivelabs.com/issues/3143 Author: Justin Baugh Status: Investigating Priority: Normal Assigned to: Markus Roberts Category: SSL Target version: Affected version: 0.25.4 Keywords: Branch: It would be very, very useful for Puppet to use existing enterprise-deployed PKI systems, rather than relying somewhat on the creation of its own self-signed CA. Here is some background: For a few months, I have been using 0.24.8 in production. I used the techniques described in the wiki (multiple CA certificates) to override the local CA certificate, setting localcacert in puppet.conf to the PEM bundle. This required a slight hack to prevent Puppet from overwriting the file, but it worked and verified correctly. My PKI setup is fairly simple: I have a global root, which has a subordinate network CA, which has signed the Puppet CA (A-B-C). I have recently upgraded to 0.25.4 and this has broken entirely (see http://pastebin.ca/1776458 for a client debug; the server side never sees the request because it doesn't even get that far). I have tried both with a brand new client and an upgrade of an existing one - the errors are the same, failure to validate certificates. From looking at cert_setup in network/http_pool.rb, Puppet will set the ca_file and SSL store as appropriate, but neither of these are seemingly sufficient to verify a trust chain. However, when I commented out usage of the certificate store and CA file (http://pastebin.ca/1776467) and used ca_path instead (set to an OpenSSL-hashed cert dir) containing A,B, and C's PEM files, the verification succeeds, which confuses me greatly. I also tried directly modifying the certificate store passed to the http object to load my certificates directly into the store (via add_file) and this also does not verify. I notice that WEBrick deals with this issue by modifying the SSL context directly (extra_chain_cert). Is it possible for Puppet to do something similar? The property is not directly exposed from http.rb. When I have done testing with Puppet using WEBrick, modifying the appropriate WEBrick code to set the property to the appropriate trust chain (A and B) also works correctly, allowing the verification to succeed. I apologize in advance if if I am overlooking something or doing it wrong. In addition, I am happy to diagnose/debug/investigate this issue, if it is helpful, and write a patch for it if necessary, but my ruby/ruby openssl familiarity is minimal. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #3144] (Needs more information) catalogue generated while --noop taken when error in production
Issue #3144 has been updated by James Turnbull. Category set to plumbing Status changed from Unreviewed to Needs more information Assigned to set to Luke Kanies Priority changed from High to Normal Luke - thoughts? This seems like a bug to me but I can't work out what's happening. Bug #3144: catalogue generated while --noop taken when error in production http://projects.reductivelabs.com/issues/3144 Author: Cedric Jeanneret Status: Needs more information Priority: Normal Assigned to: Luke Kanies Category: plumbing Target version: Affected version: 0.25.4 Keywords: Branch: Hello, I just discovered a nice bug in puppet. we use different environment in our development workflow (say production and toto). While developing in my env (toto), I use to go on the node, and do: puppetd -t --environment toto --noop So far, so good. Unfortunately, there's an error in production (aka default env) (which I'm trying to correct in toto), so that puppet cannot run on production environment. What happens: When puppet's launched via our cronjob (we don't use daemon mode - cron does a simple puppetd -t each 30 minutes) it seems that puppet take the previous catalogue which was successfully ran. In my case, the catalogue generated on toto environment ! What should happen: as previous run was done with --noop, it shouldn't take generated catalogue Is it really normal ? Thank you. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Feature #3153] Network interface type
Issue #3153 has been updated by Michael DeHaan. This should go to unassigned for someone to pick up once we decide the proper release Feature #3153: Network interface type http://projects.reductivelabs.com/issues/3153 Author: Michael DeHaan Status: Accepted Priority: Normal Assigned to: Michael DeHaan Category: network Target version: Affected version: 0.25.4 Keywords: networking types Branch: Talking with user, would be nice to be able to model network interface config in Puppet to faciliate easy changes -- OS installers particularly Anaconda do not allow all options. Taking a look at interface modelling in Cobbler will show some of the things we'd like to represent -- including bonding and arbitrarily named interfaces, as well as some examples of kludgy templates for configuring those on RHEL/Fedora. Will take additional work to make something Debian/Ubuntu other friendly. This seems to also require the need to express arbitrary datastructures in external nodes. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Feature #3153] Network interface type
Issue #3153 has been updated by Peter Meier. there have been once a network type, unfortunately it didn't get any support from someone to fix the outstanding issues, hence it was remove - #1128 Feature #3153: Network interface type http://projects.reductivelabs.com/issues/3153 Author: Michael DeHaan Status: Accepted Priority: Normal Assigned to: Michael DeHaan Category: network Target version: Affected version: 0.25.4 Keywords: networking types Branch: Talking with user, would be nice to be able to model network interface config in Puppet to faciliate easy changes -- OS installers particularly Anaconda do not allow all options. Taking a look at interface modelling in Cobbler will show some of the things we'd like to represent -- including bonding and arbitrarily named interfaces, as well as some examples of kludgy templates for configuring those on RHEL/Fedora. Will take additional work to make something Debian/Ubuntu other friendly. This seems to also require the need to express arbitrary datastructures in external nodes. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Feature #3153] Network interface type
Issue #3153 has been updated by James Turnbull. So my first thoughts are the old code is probably good as a don't do this the same way again guide. I recommend a start from scratch with a new type. I think the first issue is to data model something that works for a variety of platforms, something like: interface name (namevar) interface type (loopback, normal, alias ...?) description ensure (onboot) boot protocol (DHCP/etc) interface number IP address netmask broadcast And then flesh out for Solaris and others. Providers are sufficiently unique that it could be quite a complex exercise. Feature #3153: Network interface type http://projects.reductivelabs.com/issues/3153 Author: Michael DeHaan Status: Accepted Priority: Normal Assigned to: Category: network Target version: Affected version: 0.25.4 Keywords: networking types Branch: Talking with user, would be nice to be able to model network interface config in Puppet to faciliate easy changes -- OS installers particularly Anaconda do not allow all options. Taking a look at interface modelling in Cobbler will show some of the things we'd like to represent -- including bonding and arbitrarily named interfaces, as well as some examples of kludgy templates for configuring those on RHEL/Fedora. Will take additional work to make something Debian/Ubuntu other friendly. This seems to also require the need to express arbitrary datastructures in external nodes. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #3159] (Unreviewed) LDAP groups are being mis-interpretted by RAL
Issue #3159 has been reported by Joel Heenan.
Bug #3159: LDAP groups are being mis-interpretted by RAL
http://projects.reductivelabs.com/issues/3159
Author: Joel Heenan
Status: Unreviewed
Priority: Normal
Assigned to:
Category: RAL
Target version:
Affected version: 0.24.8
Keywords: ldap, ral, centos, rhel, nss
Branch:
It seems puppet is getting confused regarding ldap users and groups
err:
//Node[foo]/class/File[/var/log/httpd]:
Failed to retrieve current state of resource: Could not find group readonly at
/etc/puppet/svn/manifests/common/common.pp:26
[foo ~]# getent group | grep readonly
readonly:*:4002:user1,user2
[foo ~]# ralsh group readonly
group { 'readonly':
ensure = 'absent'
}
Using Centos 5.4 with Xen, and 389 Directory Server. Puppet version
puppet-0.24.8-4.el5. Facter facter-1.5.7-1.el5. NSS ldap nss_ldap-253-22.el5_4.
Is this a known problem? I googled around a bit and found similar
problems but nothing that looked exactly the same.
Thanks
Joel
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://reductivelabs.com/redmine/my/account
--
You received this message because you are subscribed to the Google Groups
Puppet Bugs group.
To post to this group, send email to puppet-b...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-bugs+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #3160] (Unreviewed) Could not intern from pson: source '#Puppet::FileServi' not in PSON!
Issue #3160 has been reported by Rob Terhaar. Bug #3160: Could not intern from pson: source '#Puppet::FileServi' not in PSON! http://projects.reductivelabs.com/issues/3160 Author: Rob Terhaar Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Affected version: 0.25.4 Keywords: Branch: I'm using puppet 25.4 via gem on opensolaris, connecting to a debian puppetmaster which is running the current backported puppetmasterd (v. 0.25.1-2~bpo50+1) All of our Linux machines work correctly with this puppetmaster, however when I try to connect an opensolaris server, i receive the following error when trying to transfer files via puppetmaster's module file server: debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson err: //users::users/User_maker[rterhaar]/File[/export/home/rterhaar/.ssh/authorized_keys2]: Failed to retrieve current state of resource: Could not intern from pson: source '#Puppet::FileServi' not in PSON! Could not retrieve file metadata for puppet:///modules/users/authorized_keys2: Could not intern from pson: source '#Puppet::FileServi' not in PSON! at /etc/puppet/modules/users/manifests/maker.pp:60 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Feature #3161] (Unreviewed) puppetca can only create 1024 bit keys
Issue #3161 has been reported by Joe McDonagh. Feature #3161: puppetca can only create 1024 bit keys http://projects.reductivelabs.com/issues/3161 Author: Joe McDonagh Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Affected version: 0.25.4 Keywords: Branch: There should be an option to create stronger keys, or at least a stronger default. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #3160] (Needs more information) Could not intern from pson: source '#Puppet::FileServi' not in PSON!
Issue #3160 has been updated by James Turnbull. Status changed from Unreviewed to Needs more information Using a later version client with an earlier version master is unlikely to work in most cases or potentially will have unpredictable results. Can you suggest you try with a 0.25.1 client? Bug #3160: Could not intern from pson: source '#Puppet::FileServi' not in PSON! http://projects.reductivelabs.com/issues/3160 Author: Rob Terhaar Status: Needs more information Priority: Normal Assigned to: Category: Target version: Affected version: 0.25.4 Keywords: Branch: I'm using puppet 25.4 via gem on opensolaris, connecting to a debian puppetmaster which is running the current backported puppetmasterd (v. 0.25.1-2~bpo50+1) All of our Linux machines work correctly with this puppetmaster, however when I try to connect an opensolaris server, i receive the following error when trying to transfer files via puppetmaster's module file server: debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson err: //users::users/User_maker[rterhaar]/File[/export/home/rterhaar/.ssh/authorized_keys2]: Failed to retrieve current state of resource: Could not intern from pson: source '#Puppet::FileServi' not in PSON! Could not retrieve file metadata for puppet:///modules/users/authorized_keys2: Could not intern from pson: source '#Puppet::FileServi' not in PSON! at /etc/puppet/modules/users/manifests/maker.pp:60 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Feature #2954] (Ready for Testing) Classes should support attributes
Issue #2954 has been updated by Luke Kanies.
Status changed from Accepted to Ready for Testing
Assigned to set to Markus Roberts
Branch set to luke/tickets/master/2954
I've uploaded my code to my tickets/master/2954 branch.
Note that this branch is based on #3015.
Feature #2954: Classes should support attributes
http://projects.reductivelabs.com/issues/2954
Author: Luke Kanies
Status: Ready for Testing
Priority: Normal
Assigned to: Markus Roberts
Category: language
Target version: Rowlf
Affected version: 0.25.1
Keywords:
Branch: luke/tickets/master/2954
Classes should support statically declared attributes, just like definitions.
It's easy to add the attribute functionality to classes, the only hard part is
the syntax.
I propose that we do a bit of hackery to the grammar and support 'class' as a
resource type, to retain the singleton behaviour:
pre
class foo($var) { ... }
class { foo: var = yayness }
/pre
I think this is a touch confusing, but I don't see another way to do it.
Preferably, all of the attributes would be loaded from an external node tool;
they'd be statically declared there, and if someone just used 'include' with a
class that required attributes that weren't set externally, it would be a
compile error.
Again, set for rowlf, but unlikely to make it in.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://reductivelabs.com/redmine/my/account
--
You received this message because you are subscribed to the Google Groups
Puppet Bugs group.
To post to this group, send email to puppet-b...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-bugs+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #3116] Test failed: to_sym method not found
Issue #3116 has been updated by Luke Kanies. James Turnbull wrote: Which branch/ticket so I can link them? #2954; relation added. Bug #3116: Test failed: to_sym method not found http://projects.reductivelabs.com/issues/3116 Author: James Turnbull Status: Accepted Priority: Normal Assigned to: Luke Kanies Category: testing Target version: Rowlf Affected version: 0.25.4 Keywords: Branch: pre 2) Puppet::Error in 'RDoc::Parser should parse to RDoc data structure' Could not parse for environment production: undefined method `to_sym' for #Puppet::Node::Environment:0x7f673b9a9210 at /etc/puppet/manifests/site.pp:13 grammar.ra:633:in `_reduce_156' grammar.ra:632:in `each' grammar.ra:632:in `_reduce_156' ./spec/integration/util/rdoc/parser.rb:45: ./spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:22:in `run' ./spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:17:in `each' ./spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:17:in `run' /pre Times that by about 150 tests. It seems environment is no longer a string and hence ... fail. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Feature #2759] Reports should provide structured data on events
Issue #2759 has been updated by Luke Kanies. James Turnbull wrote: So am I merging the event_manager branch first? If so, it needs to be rebased also. I just pushed this rebased on master, and you shouldn't need to merge another branch since this one has all of the code. Feature #2759: Reports should provide structured data on events http://projects.reductivelabs.com/issues/2759 Author: Luke Kanies Status: Ready for Testing Priority: High Assigned to: Luke Kanies Category: transactions Target version: Rowlf Affected version: 0.25.1 Keywords: Branch: luke/tickets/master/2759 Reports currently only store log messages, which are somewhat rich -- tags and all -- but provide limited ability to figure out what really happened without parsing log messages. Given that the messages are intentionally optimized for humans, this quickly becomes not so great. Instead, the reports should store the events that result in the logs (including, most likely, the log message itself). This was promised to Ubuntu as a part of providing better machine-readable interfaces. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Feature #2759] Reports should provide structured data on events
Issue #2759 has been updated by Luke Kanies. Assigned to changed from Luke Kanies to James Turnbull Feature #2759: Reports should provide structured data on events http://projects.reductivelabs.com/issues/2759 Author: Luke Kanies Status: Ready for Testing Priority: High Assigned to: James Turnbull Category: transactions Target version: Rowlf Affected version: 0.25.1 Keywords: Branch: luke/tickets/master/2759 Reports currently only store log messages, which are somewhat rich -- tags and all -- but provide limited ability to figure out what really happened without parsing log messages. Given that the messages are intentionally optimized for humans, this quickly becomes not so great. Instead, the reports should store the events that result in the logs (including, most likely, the log message itself). This was promised to Ubuntu as a part of providing better machine-readable interfaces. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #3116] Test failed: to_sym method not found
Issue #3116 has been updated by Luke Kanies. Pretty sure this is fixed in my commit:f12da5d7632eac527e5834ed9523983d8ebd9ffc in my repo. Bug #3116: Test failed: to_sym method not found http://projects.reductivelabs.com/issues/3116 Author: James Turnbull Status: Accepted Priority: Normal Assigned to: Luke Kanies Category: testing Target version: Rowlf Affected version: 0.25.4 Keywords: Branch: pre 2) Puppet::Error in 'RDoc::Parser should parse to RDoc data structure' Could not parse for environment production: undefined method `to_sym' for #Puppet::Node::Environment:0x7f673b9a9210 at /etc/puppet/manifests/site.pp:13 grammar.ra:633:in `_reduce_156' grammar.ra:632:in `each' grammar.ra:632:in `_reduce_156' ./spec/integration/util/rdoc/parser.rb:45: ./spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:22:in `run' ./spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:17:in `each' ./spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:17:in `run' /pre Times that by about 150 tests. It seems environment is no longer a string and hence ... fail. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Feature #2491] (Accepted) The regsubst() function should be able to operate on arrays
Issue #2491 has been updated by James Turnbull.
Status changed from Closed to Accepted
Assigned to changed from Thomas Bellman to James Turnbull
Something is wrong with the commit. Assigned to me to check.
Feature #2491: The regsubst() function should be able to operate on arrays
http://projects.reductivelabs.com/issues/2491
Author: Thomas Bellman
Status: Accepted
Priority: Normal
Assigned to: James Turnbull
Category: functions
Target version: Rowlf
Affected version: 0.25.0rc1
Keywords:
Branch:
It would be nice if one could give an array to regsubst(), and
make it perform the substitution on each element of that array.
One, perhaps non-obvious, use case is to have a definition that
takes an array as parameter, and have it loop over that by
giving it as the name parameter to a helper definition, like
this:
pre
define my_define($param, ...)
{
$x = regsubst($param, .*, $name//\\)
my_define_helper {
$x: ...;
}
...
}
define my_define_helper(...)
{
$n = regsubst($name, '^(.*)//(.*)$', '\1')
$p = regsubst($name, '^(.*)//(.*)$', '\2')
# Do things with $n and $p, which now are the $name and one
# element of $param from my_define, respectively.
}
my_define {
foo: param = [a, b, c], ...;
bar: param = [a, b, c], ...;
}
/pre
One can already do the looping today, but only as long as the
param parameters to My_define[foo] and My_define[bar] doesn't
have any elements in common. (This use case came up in
puppet-users recently, where the poster wanted a definition for
managing PGP keystores, where one parameter would be an array of
keys.
http://groups.google.com/group/puppet-users/browse_thread/thread/d3e85f7869f66ed1)
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://reductivelabs.com/redmine/my/account
--
You received this message because you are subscribed to the Google Groups
Puppet Bugs group.
To post to this group, send email to puppet-b...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-bugs+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Feature #2376] (Accepted) Show inheritence in puppetdoc
Issue #2376 has been updated by James Turnbull. Status changed from Closed to Accepted Checking this one too. Feature #2376: Show inheritence in puppetdoc http://projects.reductivelabs.com/issues/2376 Author: Avi Miller Status: Accepted Priority: Normal Assigned to: James Turnbull Category: documentation Target version: Rowlf Affected version: 0.24.8 Keywords: releasenotes Branch: It would be great if puppetdoc could show child inheritence in nodes, i.e. a heading saying Inherited by and listing the child nodes of a particular node. Or just Children: underneath the Parent heading. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-b...@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
