Jira (PUP-1928) puppet's idea of /etc/hosts management does not match real world use
Title: Message Title
steve foster commented on an issue
Re: puppet's idea of /etc/hosts management does not match real world use
We're currently working around the issue by using a module which keys on the IP:
https://forge.puppetlabs.com/uol/host6
Its based on the host type from core puppet.
Add Comment
Puppet / PUP-1928
puppet's idea of /etc/hosts management does not match real world use
Here is a valid extract from an {{/etc/hosts}} files on a RHEL box: {noformat} 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 {noformat} Here is the code to make puppet add these entries: {noformat} host { 'localhost': ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this
Jira (PUP-2801) 'puppetca' needs feature to remove (/revoke) a pending certificate signing request
Title: Message Title cristi falcas commented on an issue Re: 'puppetca' needs feature to remove (/revoke) a pending certificate signing request thank you, it's working Add Comment Puppet / PUP-2801 'puppetca' needs feature to remove (/revoke) a pending certificate signing request It is not possible to remove a pending certificate signing request with 'puppetca --revoke $fqdn': pre [root@X puppet]# puppetca --list rhel32bit.x.local [root@X puppet]# puppetca --revoke rhel32bit.x.local rhel32bit.x.local notice: Revoked certificate with serial # Inventory of signed certificates err: Could not call revoke: Cannot convert i... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-717) PR (129): Auto enable strict_variables for unit tests when puppet 3.5 - mcanevet
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-717 PR (129): Auto enable strict_variables for unit tests when puppet 3.5 - mcanevet Issue Type: Task Assignee: Unassigned Created: 19/Jun/14 2:51 AM Labels: github module Priority: Normal Reporter: gepetto-bot Auto enable strict_variables for unit tests when puppet 3.5 Author: Mickal Canvet mickael.cane...@camptocamp.com Company: camptocamp Github ID: mcanevet Pull Request 129 Discussion Pull Request 129 File Diff Pull Request Description (webhooks-id: d36ea6038d62fd448dcaa608d2ca6141)
Jira (PUP-2738) Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-2738 Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2389) Create ruby 2.0 branch for x64 in puppet-win32-ruby
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2389 Create ruby 2.0 branch for x64 in puppet-win32-ruby Change By: Rob Reynolds Weneedtovendorx64versionsofruby2.0,andinstalltheappropriatesetsofgemsintobothbranches.Ruby2.1isnotyetreleasedonWindows. Theworkhereincludes:#create2.0.0-x64branch#vendorruby2.0.0-p545(x64)fromrubyinstaller.orgORneweriftheyreleaseapatchedversion#upgrade/installgemsforx64versions#upgrade/removegemsin1.9.3branchaswell(actuallynotsurewe'dneedtoremovethem) Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-592) Add swapfree/swapsize facts for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-592 Add swapfree/swapsize facts for OpenBSD Issue Type: Improvement Affects Versions: 2.0.2 Assignee: Jasper Lievisse Adriaanse Created: 19/Jun/14 6:19 AM Priority: Normal Reporter: Jasper Lievisse Adriaanse OpenBSD lacks support for the swapsize and swapfree facts. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title Aaron Zauner commented on an issue Re: puppet parser validate - no output when everything's ok +1 Add Comment Puppet / PUP-2341 puppet parser validate - no output when everything's ok Running `puppet parser validate init.pp` returns nothing on the command line when there are no errors. Please consider adding a message like OK or No Parse Error that indicates to the user that the file(s) passed parser validation. This comes up for discussion at almost every fundamentals class I teach, where someone asks So I see no output, is t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-592) Add swapfree/swapsize facts for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse commented on an issue Re: Add swapfree/swapsize facts for OpenBSD Actually, it seems they were already present but totally broken. https://github.com/puppetlabs/facter/pull/698 Add Comment Facter / FACT-592 Add swapfree/swapsize facts for OpenBSD OpenBSD lacks support for the swapsize and swapfree facts. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-716) HTTP API gets stuck
Title: Message Title Erik Daln commented on an issue Re: HTTP API gets stuck The config is fairly standard: /etc/puppetdb/conf.d# cat *.ini # See README.md for more thorough explanations of each section and # option. [global] # Store mq/db data in a custom directory vardir = /var/lib/puppetdb # Use an external logback config file logging-config = /etc/puppetdb/logback.xml [command-processing] # How many command-processing threads to use, defaults to (CPUs / 2) # threads = 4 # Maximum amount of disk space (in MB) to allow for ActiveMQ persistent message storage # store-usage = 102400 # Maximum amount of disk space (in MB) to allow for ActiveMQ temporary message storage # temp-usage = 51200 [database] # For the embedded DB: org.hsqldb.jdbcDriver # For PostgreSQL: org.postgresql.Driver # Defaults to embedded DB classname = org.postgresql.Driver # For the embedded DB: hsqldb # For PostgreSQL: postgresql # Defaults to embedded DB subprotocol = postgresql # For the embedded DB: file:/path/to/database;hsqldb.tx=mvcc;sql.syntax_pgs=true # For PostgreSQL: //host:port/databaseName # Defaults to embedded DB located in vardir/db subname = //lon3-puppetdbdb-b1.lon3.spotify.net:5432/puppetdb # Connect as a specific user # username = foobar username = puppetdb # Use a specific password # password = foobar password = --- # How often (in minutes) to compact the database # gc-interval = 60 gc-interval = 60 # Number of seconds before any SQL query is considered 'slow'; offending # queries will not be interrupted, but will be logged at the WARN log level. log-slow-statements = 10 report-ttl = 14d syntax_pgs = true node-ttl = 7d node-purge-ttl = 1d conn-keep-alive = 45 conn-lifetime = 0 conn-max-age = 60 [jetty] # Hostname to list for clear-text HTTP. Default is localhost #host = localhost host = localhost # Port to listen on for clear-text HTTP. port = 8080 ssl-host = lon3-puppetdb-a1.lon3.spotify.net ssl-port = 8081 # keystore = /etc/puppetdb/ssl/keystore.jks # truststore = /etc/puppetdb/ssl/truststore.jks # key-password = --- # trust-password = --- ssl-key = /etc/puppetdb/ssl/private.pem ssl-cert = /etc/puppetdb/ssl/public.pem ssl-ca-cert = /etc/puppetdb/ssl/ca.pem [repl] # Set to true to enable the remote REPL enabled = false # Either nrepl or swank or telnet type = nrepl # What port the REPL should listen on port = 8082 Add Comment
Jira (PDB-716) HTTP API gets stuck
Title: Message Title Erik Daln updated an issue PuppetDB / PDB-716 HTTP API gets stuck Screenshot of the dashboard. The load average on the host is around 3 (24 core host). And it drops to 0 when it gets stuck. Change By: Erik Daln Attachment: puppetdbdashboard.tiff Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-465) LinuxMint support is missing in facter stable/facter-2
Title: Message Title Charlie Sharpsteen commented on an issue Re: LinuxMint support is missing in facter stable/facter-2 Kylo Ginsberg Was there a Pull Request or merge commit that resolved this issue? Add Comment Facter / FACT-465 LinuxMint support is missing in facter stable/facter-2 Detection of the LinuxMint distro is present in master, but missing in stable (2.0.1) and facter-2 (2.1.0). This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2806) puppet module generate ignores ERB files beginning with a dot
Title: Message Title
Ryan Coleman commented on an issue
Re: puppet module generate ignores ERB files beginning with a dot
Trey Dockendorf, thanks for your bug report.
I'm just trying to wrap my ahead around the core problem. What's in .fixtures.yml.erb and how do you use the templating system during the module build process?
Add Comment
Puppet / PUP-2806
puppet module generate ignores ERB files beginning with a dot
When using 'puppet module generate' with a custom skeleton directory, any files prefixed with a dot (for example, .fixtures.yml.erb) are ignored by the 'populate_erb_templates' method. Example: After running 'puppet module generate treydock-munge' using a custom skeleton directory. {code} $ ls -la treydock-munge/ total 112 drwxr-xr-x 18 tr...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit
Jira (PUP-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title Ryan Coleman updated an issue Puppet / PUP-2781 'puppet module generate' create not compatible metadata.json with forge Thank you Marcin Brański for the report. Change By: Ryan Coleman Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2532) parameter lookup produces screwy result for default values
Title: Message Title Henrik Lindberg commented on an issue Re: parameter lookup produces screwy result for default values Yet another approach is to assign the default values up front - but that is a much bigger change, and affects how / where the default values are applied. Discussion and a decision is needed before work can start on this. Add Comment Puppet / PUP-2532 parameter lookup produces screwy result for default values When the future parser lookup resource parameter evaluates and there is no parameter value set by the evaluated manifest logic at that point, the evaluator then looks up the default value for that parameter. This unfortunately looks up the default value as seen from the perspective of the lookup resource parameter scope/context, and not the context... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title Aaron Armstrong updated an issue Puppet / PUP-2781 'puppet module generate' create not compatible metadata.json with forge Change By: Aaron Armstrong Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2806) puppet module generate ignores ERB files beginning with a dot
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2806 puppet module generate ignores ERB files beginning with a dot Change By: Charlie Sharpsteen Assignee: TreyDockendorf Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-593) Facter assumes that route is in the path
Title: Message Title
Josh Cooper created an issue
Facter / FACT-593
Facter assumes that route is in the path
Issue Type:
Bug
Assignee:
Eric Sorenson
Created:
19/Jun/14 9:20 AM
Fix Versions:
2.1
Priority:
Normal
Reporter:
Josh Cooper
Acceptance tests are failing on rhel7 when trying to evaluate dhcp_servers fact:
q6mzikqnvnd9urf (agent) $ env RUBYLIB=/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-puppet/lib:${RUBYLIB} PATH=/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH} facter
SCRIPT CALLED
Could not retrieve fact='dhcp_servers', resolution='anonymous': undefined method `scan' for nil:NilClass
Add Comment
Jira (FACT-568) Run specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Facter / FACT-568 Run specs against windows ruby 2.0 x64 Change By: Josh Cooper Sprint: Week2014- 7 6 - 2 18 to2014- 7 6 - 9 25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-593) Facter assumes that route is in the path
Title: Message Title Josh Cooper updated an issue Facter / FACT-593 Facter assumes that route is in the path Change By: Josh Cooper Sprint: Week2014-6-18to2014-6-25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-593) Facter assumes that route is in the path
Title: Message Title Josh Cooper updated an issue Facter / FACT-593 Facter assumes that route is in the path Change By: Josh Cooper Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-593) Facter assumes that route is in the path
Title: Message Title Josh Cooper updated an issue Facter / FACT-593 Facter assumes that route is in the path Change By: Josh Cooper Assignee: EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-593) Facter assumes that route is in the path
Title: Message Title Adrien Thebo assigned an issue to William Hopper Facter / FACT-593 Facter assumes that route is in the path Change By: Adrien Thebo Assignee: WilliamHopper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2808) generate is too safe (false sense security)
Title: Message Title
Rodney Beede created an issue
Puppet / PUP-2808
generate is too safe (false sense security)
Issue Type:
Improvement
Assignee:
Unassigned
Created:
19/Jun/14 10:19 AM
Priority:
Minor
Reporter:
Rodney Beede
Original Estimate:
1 minute
Remaining Estimate:
1 minute
Taken from https://projects.puppetlabs.com/issues/5481 (Export to JIRA button didn't work).
The generate[1] function is too safe. We should encourage people to do safe things and perhaps log warnings when they do not, but we should not keep people from running commands that we deem to be unsafe.
An example is given that shows it is possible to bypass the intended restriction/protection of this command.
BEGIN QUOTE
First let me point out a workaround: generate(“/bin/sh”, “-c”, “/usr/bin/uptime | /usr/bin/awk ‘ {print $3}
’ | cut -d, -f1”)
Second, let me say that this workaround demonstrates that the safety built into this command is completely and totally worthless right now. However I suspect that the original attempt at safety was misguided anyway. What’s the issue that we’re protecting from?
Jira (PUP-2727) Reserved keywords conflict with resource type parameters
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2727 Reserved keywords conflict with resource type parameters Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1299) Deprecate and eliminate magic parameter array handling
Title: Message Title Andy Parker updated an issue Puppet / PUP-1299 Deprecate and eliminate magic parameter array handling Change By: Andy Parker Sprint: Week2014-6- 25 18 to2014- 7 6 - 2 25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1299) Deprecate and eliminate magic parameter array handling
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1299 Deprecate and eliminate magic parameter array handling Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-714) Exported resource relationship woes
Title: Message Title
Zach Leslie commented on an issue
Re: Exported resource relationship woes
I will try to replicate this in a testing environment with the minimal amount of setup and code around it. We'll see where this takes us.
Add Comment
PuppetDB / PDB-714
Exported resource relationship woes
Consider the following. {code} @@concat::fragment { bacula-client-${::fqdn}: target = '/etc/bacula/conf.d/client.conf', content = template('bacula/client.conf.erb'), tag = bacula-${bacula::params::bacula_director}, } {code} The above resource exports a fragment from a node to be backed up. For those familiar with the fragmen...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-717) PR (129): Auto enable strict_variables for unit tests when puppet 3.5 - mcanevet
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-717 PR (129): Auto enable strict_variables for unit tests when puppet 3.5 - mcanevet Change By: Kenneth Barber Component/s: Module Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2755) Move iterative functions to 4x function API
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2755 Move iterative functions to 4x function API Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1299) Deprecate and eliminate magic parameter array handling
Title: Message Title
Andy Parker commented on an issue
Re: Deprecate and eliminate magic parameter array handling
This isn't actually fixed. I think what Erik Daln was seeing was that in 3.5 you are able to reference the value of a resource property which will show up as the unmunged value. However, that doesn't reach the code path that is actually causing the issue.
The section of code identified in the description is only used when the catalog is being converted from one form to another (this is part of the parser catalog to ral catalog conversion). At that point the single element array parameter values are stripped down to just the scalar value of the single element of the array.
In the example of exec with an single element environment array, I instrumented the code and found that it was still being stripped.
I agree with Henrik that this isn't the kind of thing that we can warn about since there is no action that a user can take. However, I think we can simply put a conditional around the transformation and leave it at that.
Add Comment
Puppet / PUP-1299
Deprecate and eliminate magic parameter array handling
Puppet's parser will automatically de-arrayify single element arrays for parameters (and properties). See `lib/puppet/parser/resource.rb` {code} result[p] = if v.is_a?(Array) and v.length == 1 v[0] else v end {code} As a result when writing a custom type, the parameter...
This message was sent by Atlassian JIRA
Jira (PUP-1299) Deprecate and eliminate magic parameter array handling
Title: Message Title Andy Parker assigned an issue to Unassigned Puppet / PUP-1299 Deprecate and eliminate magic parameter array handling Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2557) Deprecate and remove node inheritance
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2557 Deprecate and remove node inheritance Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-717) PR (129): Auto enable strict_variables for unit tests when puppet 3.5 - mcanevet
Title: Message Title gepetto-bot commented on an issue Re: PR (129): Auto enable strict_variables for unit tests when puppet 3.5 - mcanevet Pull request Auto enable strict_variables for unit tests when puppet 3.5 has been closed. Add Comment PuppetDB / PDB-717 PR (129): Auto enable strict_variables for unit tests when puppet 3.5 - mcanevet h2. Auto enable strict_variables for unit tests when puppet 3.5 * Author: Mickal Canvet mickael.cane...@camptocamp.com * Company: camptocamp * Github ID: [mcanevet|https://github.com/mcanevet] * [Pull Request 129 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/129] * [Pull Request 129 File Diff|https://github.com/puppetlabs/p... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2727) Reserved keywords conflict with resource type parameters
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-2727 Reserved keywords conflict with resource type parameters Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1057) Remove 'collect' and 'select' iterative function stubs
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1057 Remove 'collect' and 'select' iterative function stubs Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-465) LinuxMint support is missing in facter stable/facter-2
Title: Message Title Kurt Wall commented on an issue Re: LinuxMint support is missing in facter stable/facter-2 Peter Huene Was there a PR or merge that resolved this issue? Add Comment Facter / FACT-465 LinuxMint support is missing in facter stable/facter-2 Detection of the LinuxMint distro is present in master, but missing in stable (2.0.1) and facter-2 (2.1.0). This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2304) Implement requirements support for the PMT
Title: Message Title Ryan Coleman commented on an issue Re: Implement requirements support for the PMT I'm not convinced this is a slam-dunk. Not unlike operating systems, it's difficult to make this decision at the end-point receiving the module. What if the master is running a newer version than the agents? The opposite could be true. Less importantly, the author could have been very narrow in their _expression_ (Puppet 3.1 and no more) but it could totally work with Puppet 3.2, 3.3, 3.4, etc. Will the author be expected to update for each release in order to enable better default behavior? The work we did on PE compatibility for PE 3.2 taught me that we're stretching the balance of convenience and usability. Add Comment Puppet / PUP-2304 Implement requirements support for the PMT We should implement support for validated (at install time) requirements for modules, particularly for Puppet and Facter. As an example, if a release of module is published with a 'puppet' requirement and the current Puppet version does not fall in that range PMT should refuse to install that release. This behaviour can be bypassed with the --ignore-r... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-465) LinuxMint support is missing in facter stable/facter-2
Title: Message Title Peter Huene commented on an issue Re: LinuxMint support is missing in facter stable/facter-2 Added links to both. Add Comment Facter / FACT-465 LinuxMint support is missing in facter stable/facter-2 Detection of the LinuxMint distro is present in master, but missing in stable (2.0.1) and facter-2 (2.1.0). This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2078) Puppet module install --force does not re-install dependencies
Title: Message Title
Ryan Coleman commented on an issue
Re: Puppet module install --force does not re-install dependencies
Oh '--force', you do all the things.
Now that we have individual flags for the things that --force also does, like ignoring requirements and dependencies, should we:
a) reduce the scope of what --force actually does to Force overwrite of existing module, if any.
or
b) document its implicit override of other logic and leave it as a giant lever.
Thoughts Pieter van de Bruggen Alex Dreyer?
Thanks for the ticket Werner Buck.
Add Comment
Puppet / PUP-2078
Puppet module install --force does not re-install dependencies
Installing a module from forge on the commandline with --force does not (re)install its dependencies. installing normally {code} $ puppet module install puppetlabs-ntp Notice: Preparing to install into /etc/puppet/modules ... Notice: Downloading from https://forge.puppetlabs.com ... Notice: Installing -- do not interrupt ... /etc/puppet/modules ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-700) java.io.IOException: Frame size larger than max allowed 100 MB
Title: Message Title
Kenneth Barber updated an issue
PuppetDB / PDB-700
java.io.IOException: Frame size larger than max allowed 100 MB
Change By:
Kenneth Barber
Weareseeingthefollowingbacktraceappearingafterpuppetdbrunningfor~5-15Minutes,forcingustorestartpuppetdbprettyoftentokeepitworking.Afterarestartoutstandingqueuedtasksareappliedwithoutproblemsatall.Ithinktheproblemwasintroducedwiththeupgradto2.0.0,butduetoaddingalargishnumberofnewhostsataboutthesametimeI'mnot100%sureaboutthat. {code} 014-06-0416:25:28,323ERROR[o.a.a.b.r.c.AbstractStoreCursor]org.apache.activemq.broker.region.cursors.QueueStorePrefetch@66ed66e4:com.puppetlabs.puppetdb.commands,batchResetNeeded=false,storeHasMessages=true,size=2207,cacheEnabled=false-Failedtofillbatchjava.lang.RuntimeException:java.io.IOException:Framesizeof194MBlargerthanmaxallowed100MBatorg.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:280)~[puppetdb.jar:na]atorg.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:113)~[puppetdb.jar:na]atorg.apache.activemq.broker.region.cursors.StoreQueueCursor.reset(StoreQueueCursor.java:157)[puppetdb.jar:na]atorg.apache.activemq.broker.region.Queue.doPageInForDispatch(Queue.java:1766)[puppetdb.jar:na]atorg.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:1995)[puppetdb.jar:na]atorg.apache.activemq.broker.region.Queue.iterate(Queue.java:1488)[puppetdb.jar:na]atorg.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122)[puppetdb.jar:na]atorg.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43)[puppetdb.jar:na]atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[na:1.7.0_55]atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[na:1.7.0_55]atjava.lang.Thread.run(Thread.java:744)[na:1.7.0_55]Causedby:java.io.IOException:Framesizeof194MBlargerthanmaxallowed100MBatorg.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:277)~[puppetdb.jar:na]atorg.apache.activemq.store.kahadb.KahaDBStore.loadMessage(KahaDBStore.java:1016)~[puppetdb.jar:na]atorg.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore$4.execute(KahaDBStore.java:556)~[puppetdb.jar:na]atorg.apache.kahadb.page.Transaction.execute(Transaction.java:769)~[puppetdb.jar:na]atorg.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.recoverNextMessages(KahaDBStore.java:545)~[puppetdb.jar:na]atorg.apache.activemq.store.ProxyMessageStore.recoverNextMessages(ProxyMessageStore.java:106)~[puppetdb.jar:na]atorg.apache.activemq.broker.region.cursors.QueueStorePrefetch.doFillBatch(QueueStorePrefetch.java:97)~[puppetdb.jar:na]atorg.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:277)~[puppetdb.jar:na]...10commonframesomitted {code}
Jira (PUP-1186) puppet module tool on windows will (sometimes) create a PaxHeader directory
Title: Message Title Ryan Coleman updated an issue Puppet / PUP-1186 puppet module tool on windows will (sometimes) create a PaxHeader directory If this bug is still relevant, I've raised it to Major and would like to see a fix in 3.x. Change By: Ryan Coleman Priority: Normal Major Fix Version/s: future Fix Version/s: 3.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title Pieter van de Bruggen updated an issue Puppet / PUP-2781 'puppet module generate' create not compatible metadata.json with forge Change By: Pieter van de Bruggen Sprint: July2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2738) Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-2738 Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2578) Adjustments for new OpenBSD service provider
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2578 Adjustments for new OpenBSD service provider Change By: Adrien Thebo Sprint: Week2014-6-18to2014-6-25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2578) Adjustments for new OpenBSD service provider
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2578 Adjustments for new OpenBSD service provider Change By: Adrien Thebo Story Points: 1 Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title
Pieter van de Bruggen commented on an issue
Re: 'puppet module generate' create not compatible metadata.json with forge
Pull request ready for review: https://github.com/puppetlabs/puppet/pull/2784
Add Comment
Puppet / PUP-2781
'puppet module generate' create not compatible metadata.json with forge
When one generate module by puppet it automaticlly adds version_range instead of version_requirement which is required to publish module {code} dependencies: [ { name: puppetlabs-stdlib, version_range: = 1.0.0 } ] {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2578) Adjustments for new OpenBSD service provider
Title: Message Title
Adrien Thebo commented on an issue
Re: Adjustments for new OpenBSD service provider
Merged into master in ced666d.
Add Comment
Puppet / PUP-2578
Adjustments for new OpenBSD service provider
After some more testing of @xaque208 new service provider I ran into an issue where a service from packages like: service {'puppetboard': enable = true } would end up with the following in /etc/rc.conf.local: puppetboard_flags= This breaks the script, as it has sets it's local daemon_flags which are then overridden by the flags from rc.conf...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2809) PMT does not provide a way to see the latest available version of a module
Title: Message Title Ryan Coleman moved an issue Puppet / PUP-2809 PMT does not provide a way to see the latest available version of a module Change By: Ryan Coleman Workflow: Forge Platform Workflow Issue Type: Bug Improvement Key: FORGE PUP - 194 2809 Project: Puppet Forge Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2809) PMT does not provide a way to see the latest available version of a module
Title: Message Title Ryan Coleman updated an issue Puppet / PUP-2809 PMT does not provide a way to see the latest available version of a module Change By: Ryan Coleman Assignee: RyanColeman Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2809) PMT does not provide a way to see the latest available version of a module
Title: Message Title Ryan Coleman updated an issue Puppet / PUP-2809 PMT does not provide a way to see the latest available version of a module Thanks Carthik. Moving this ticket into PUP and linking to a related ticket, marking for consideration in 4.x Change By: Ryan Coleman Component/s: PMT Fix Version/s: 4.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2738) Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-2738 Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-392) Validate win32 gems on x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Validate win32 gems on x64
win32console in colors.rb should be made optional based on whether we are in ruby 1.9 or not.
Add Comment
Puppet / PUP-392
Validate win32 gems on x64
Some of the win32 gems that we use contain native code and will need to be validated that they run on x64 systems. The current set of gems is in https://github.com/puppetlabs/puppet/blob/master/ext/project_data.yaml. It currently includes {code} ffi: '1.9.0' sys-admin: '1.5.6' win32-api: '1.4.8' win32-dir: '~ 0.4.3' ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2738) Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer
Title: Message Title Josh Cooper commented on an issue Re: Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer Merged in ea94dfa44b and 99680f25b Add Comment Puppet / PUP-2738 Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer As of the merge for PUP-2657, we've noticed some intermittent test failures (in both CI and locally) in semi-random locations. The merge commit is as follows: https://github.com/puppetlabs/puppet/commit/d38153bd712167e2777bdd4c63d37e2e8d1cdb39 The commit itself has been reviewed and it doesn't seem to have issues itself, but it's likely it's trigge... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1186) puppet module tool on windows will (sometimes) create a PaxHeader directory
Title: Message Title Josh Cooper commented on an issue Re: puppet module tool on windows will (sometimes) create a PaxHeader directory Ryan Coleman Yes it it is still an issue, however, it is only an issue if you package a module on a non-Windows box using a version of tar that creates the PaxHeader. Add Comment Puppet / PUP-1186 puppet module tool on windows will (sometimes) create a PaxHeader directory In Puppet 3.2 the module tool started using minitar when the tar executable is not present. It turns out that minitar does not understand the [PAX](http://en.wikipedia.org/wiki/Pax_(Unix)) format. An example of a module that was created with this is [liamjbennet/win_facts v0.0.1](https://forge.puppetlabs.com/liamjbennett/win_facts/0.0.1). When that mod... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (HI-276) Hiera should list deep_merge as an optional gem dependency somewhere
Title: Message Title Rob Reynolds created an issue Hiera / HI-276 Hiera should list deep_merge as an optional gem dependency somewhere Issue Type: Bug Assignee: Release Engineering Components: RE Created: 19/Jun/14 1:59 PM Priority: Normal Reporter: Rob Reynolds https://github.com/puppetlabs/hiera/blob/stable/lib/hiera/backend.rb#L5 There is nowhere in the gemfile or in the project_data.yaml that deep_merge is expressed as a dependency for Hiera. My understanding is that it is an optional dependency. Add Comment
Jira (HI-276) Hiera should list deep_merge as an optional gem dependency somewhere
Title: Message Title Rob Reynolds updated an issue Hiera / HI-276 Hiera should list deep_merge as an optional gem dependency somewhere Change By: Rob Reynolds https://github.com/puppetlabs/hiera/blob/stable/lib/hiera/backend.rb#L5Thereisnowhereinthegemfileorintheproject_data.yamlthatdeep_mergeisexpressedasadependencyforHiera.Myunderstandingisthatitisanoptionaldependency. Iseeboth1.0.0and1.0.1werereleasedonthesamedate,yetinourpuppet-win32-rubydirectory,weareusingthe1.0.0dependency.Noideawhythatis... Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-283) Improve agent error reporting
Title: Message Title Daniel Dreier commented on an issue Re: Improve agent error reporting I made a trivial pull request to improve documentation on this command, but I think the issue can probably be closed at this point. Please re-open if you feel like further work is needed. Add Comment Puppet / PUP-283 Improve agent error reporting When a Puppet run fails for whatever reason (catalog compilation failure/timeout, etc..), it would be nice to have this cause of failure be available as a field in the submitted report. If this was available then one would be able to introspect on it to see the reason for a failed Puppet run, without having to parse the logs field and perform some regex ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-283) Improve agent error reporting
Title: Message Title Nate Wolfe commented on an issue Re: Improve agent error reporting Daniel Dreier Oops, I think you got the wrong ticket Add Comment Puppet / PUP-283 Improve agent error reporting When a Puppet run fails for whatever reason (catalog compilation failure/timeout, etc..), it would be nice to have this cause of failure be available as a field in the submitted report. If this was available then one would be able to introspect on it to see the reason for a failed Puppet run, without having to parse the logs field and perform some regex ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2738) Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer
Title: Message Title Rob Reynolds commented on an issue Re: Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer Ha, looks like I was pointed to an incorrect commit. Add Comment Puppet / PUP-2738 Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer As of the merge for PUP-2657, we've noticed some intermittent test failures (in both CI and locally) in semi-random locations. The merge commit is as follows: https://github.com/puppetlabs/puppet/commit/d38153bd712167e2777bdd4c63d37e2e8d1cdb39 The commit itself has been reviewed and it doesn't seem to have issues itself, but it's likely it's trigge... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2557) Deprecate and remove node inheritance
Title: Message Title Andy Parker commented on an issue Re: Deprecate and remove node inheritance After looking over this, I can sympathize with wanting to make the use of the future parser as easy as possible in puppet 3.7, but it prevents it from being a true preview of what will be available in puppet 4. I'm kicking this back to convert it to being an error in puppet 3.7 when the future parser is enabled. Add Comment Puppet / PUP-2557 Deprecate and remove node inheritance Node inheritance causes a large number of complications and ambiguities that make understanding puppet code difficult. There is very little reason to use it since much more effective reuse can be achieved using classes and defined types. On the next 3 series puppet that is using the current parser: the system must issue a deprecation warning when it en... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to
Jira (PUP-2087) Puppet does not implicitly convert string to integer
Title: Message Title
Daniel Dreier commented on an issue
Re: Puppet does not implicitly convert string to integer
This issue is from 2012 and appears not to apply to current versions of puppet.
There are two separate parts to this issue. First, there's the question of whether quoted strings in variables are converted to numbers for arithmetic operators. Here are the tests I can on the latest puppet master (3.6.2):
$quoted_number = '5'
$multiplication_result_quoted = $quoted_number * 2
notice(${quoted_number} * 2 = ${multiplication_result_quoted})
$unquoted_number = 5
$multiplication_result_unquoted = $unquoted_number * 2
notice(${quoted_number} * 2 = ${multiplication_result_unquoted})
$division_result_quoted = $quoted_number / 2
notice(${quoted_number} / 2 = ${division_result_quoted})
$division_result_unquoted = $unquoted_number / 2
notice(${quoted_number} / 2 = ${division_result_unquoted})
$addition_result_quoted = $quoted_number + 2
notice(${quoted_number} + 2 = ${addition_result_quoted})
$addition_result_unquoted = $unquoted_number + 2
notice(${quoted_number} + 2 = ${addition_result_unquoted})
$subtraction_result_quoted = $quoted_number - 2
notice(${quoted_number} - 2 = ${addition_result_quoted})
$subtraction_result_unquoted = $unquoted_number - 2
notice(${quoted_number} - 2 = ${addition_result_unquoted})
$modulo_result_quoted = $quoted_number % 2
notice(${quoted_number} % 2 = ${modulo_result_quoted})
$modulo_result_unquoted = $unquoted_number % 2
notice(${quoted_number} % 2 = ${modulo_result_unquoted})
The result I got was the following, as expected:
[vagrant@poss-head-centos vagrant]$ puppet apply test.pp
Notice: Scope(Class[main]): 5 * 2 = 10
Notice: Scope(Class[main]): 5 * 2 = 10
Notice: Scope(Class[main]): 5 / 2 = 2
Notice: Scope(Class[main]): 5 / 2 = 2
Notice: Scope(Class[main]): 5 + 2 = 7
Notice: Scope(Class[main]): 5 + 2 = 7
Notice: Scope(Class[main]): 5 - 2 = 7
Notice: Scope(Class[main]): 5 - 2 = 7
Notice: Scope(Class[main]): 5 % 2 = 1
Notice: Scope(Class[main]): 5 % 2 = 1
Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.04 seconds
Notice: Finished catalog run in 0.11 seconds
However, the linked serverfault post contains a somewhat different test case:
$ip_array = split($ipaddress, '.')
$odd_ip = $ip_array[3] % 2
if $odd_ip == 1 {
notice(is odd)
}
That code does indeed cause an error, but the cause of the error is that the . in the split is not escaped, so puppet is actually correct in asserting that $odd_ip is not a number. It work as expected with the period escaped properly:
$ip_array = split($ipaddress, '[.]')
$odd_ip = $ip_array[3] % 2
if $odd_ip == 1 {
notice(is odd)
}
Jira (PUP-2786) `puppet cert list ca` returns an error on a working puppet installation
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-2786 `puppet cert list ca` returns an error on a working puppet installation Change By: Daniel Dreier Affects Version/s: 3.6.2 Affects Version/s: 2.7.23 Affects Version/s: 3.4.3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-2341 puppet parser validate - no output when everything's ok Change By: Daniel Dreier Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title
Daniel Dreier commented on an issue
Re: puppet parser validate - no output when everything's ok
Recategorized from bug to improvement because no output on success is the expected behavior of most *nix tools. If this is implemented, I think it would be best to add to a --verbose flag, or at least a --quiet flag to suppress it, because it would create a lot of unnecessary noise as default behavior.
For example, my rake tests involve something along the lines of find -name '*.pp' -exec puppet validate {} \; – meaning that an OK message on output would be repeated dozens or hundreds of times on a larger project.
Add Comment
Puppet / PUP-2341
puppet parser validate - no output when everything's ok
Running `puppet parser validate init.pp` returns nothing on the command line when there are no errors. Please consider adding a message like OK or No Parse Error that indicates to the user that the file(s) passed parser validation. This comes up for discussion at almost every fundamentals class I teach, where someone asks So I see no output, is t...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2810) Beaker fails to copy config.yml when failure occurs early
Title: Message Title
Josh Cooper commented on an issue
Re: Beaker fails to copy config.yml when failure occurs early
This is coming from acceptance/Rakefile in puppet, not beaker:
def preserve_configuration(final_options, options_file)
if (hosts_file = config || final_options[:hosts_file]) hosts_file !~ /preserved_config/
cp(hosts_file, log/latest/config.yml)
generate_config_for_latest_hosts
end
mv(options_file, log/latest)
end
Add Comment
Puppet / PUP-2810
Beaker fails to copy config.yml when failure occurs early
The acceptance job fails during the ntp step (the first command in the test run), and tries to copy config.yml, but the destination directory doesn't exist: {noformat} You can reproduce this run with: /home/jenkins/workspace/Puppet-Acceptance-Future-Parser-master-vcloud-and-github/label/acc-coord/platform/win2008r2/acceptance/.bundle/gems/ruby/1.8/bi...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2810) Puppet acceptance Rakefile fails to copy config.yml when failure occurs early
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2810 Puppet acceptance Rakefile fails to copy config.yml when failure occurs early Change By: Josh Cooper Summary: Beaker PuppetacceptanceRakefile failstocopyconfig.ymlwhenfailureoccursearly Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2810) Beaker fails to copy config.yml when failure occurs early
Title: Message Title Josh Cooper moved an issue Puppet / PUP-2810 Beaker fails to copy config.yml when failure occurs early Change By: Josh Cooper Workflow: Engineering Platform Workflow Key: QENG PUP - 826 2810 Project: QualityEngineering Puppet Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2810) Beaker fails to copy config.yml when failure occurs early
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2810 Beaker fails to copy config.yml when failure occurs early Change By: Josh Cooper Assignee: QE Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-283) Improve agent error reporting
Title: Message Title Jason Antman commented on an issue Re: Improve agent error reporting To throw in some customer perspective here, FWIW: 1) I largely agree with what Christopher Price said. 2) There's a finite amount of information available from the agent about why a failure occurred. In most cases (i.e. excluding --profile) it's actually a pretty small amount of data. I don't see a compelling reason to not expose all of that in the reports themselves. If PE decides not to surface all of it to the user, oh well - I'm sure there are people other than myself that want as much detail as possible available to custom report processors, analytics, etc. and just because the PE UX team doesn't want to utilize it, doesn't mean the data should be thrown out (and yes, anything that exists only in a local text log file is, IMO, thrown out). 3) This is a seriously killer issue at the moment for those of us using PuppetDB and our own analytics and reporting (i.e. not the Dashboard) who want actually find out what happened on a node (or on a hundred nodes) without having to dig through logs. Add Comment Puppet / PUP-283 Improve agent error reporting When a Puppet run fails for whatever reason (catalog compilation failure/timeout, etc..), it would be nice to have this cause of failure be available as a field in the submitted report. If this was available then one would be able to introspect on it to see the reason for a failed Puppet run, without having to parse the logs field and perform some regex ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-335) Revisit how facter detects GCE instances
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Facter / FACT-335 Revisit how facter detects GCE instances Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-593) Facter assumes that route is in the path
Title: Message Title
William Hopper commented on an issue
Re: Facter assumes that route is in the path
I've got a pull request up ready for review at https://github.com/puppetlabs/facter/pull/699
Add Comment
Facter / FACT-593
Facter assumes that route is in the path
Acceptance tests are failing on rhel7 when trying to evaluate {{dhcp_servers}} fact: {noformat} q6mzikqnvnd9urf (agent) $ env RUBYLIB=/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-puppet/lib:${RUBYLIB} PATH=/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH} facter SCRIPT CALLED Could not retrieve fact='dhcp_servers', resolution='a...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title Aaron Zauner commented on an issue Re: puppet parser validate - no output when everything's ok I don't entirely get why not output at all on success is the expected behavior of unix tools? That may be true for simple things like rm, cp and so forth but a parser? not really. how about just writing to stderr? Add Comment Puppet / PUP-2341 puppet parser validate - no output when everything's ok Running `puppet parser validate init.pp` returns nothing on the command line when there are no errors. Please consider adding a message like OK or No Parse Error that indicates to the user that the file(s) passed parser validation. This comes up for discussion at almost every fundamentals class I teach, where someone asks So I see no output, is t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (FACT-353) some facts do not work with locales set
Title: Message Title
Adrien Thebo commented on an issue
Re: some facts do not work with locales set
Merged in 413e2b7.
Add Comment
Facter / FACT-353
some facts do not work with locales set
facter does not clean locale environment variables prior to executing commands and sometimes falls over the localized output. I'm not sure whether this is relevant for facter being executed by puppet, but it makes debugging a lot harder. For example with the macaddress fact {code} root@mail:~# facter | grep mac Could not retrieve macaddress: undefine...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title Daniel Dreier commented on an issue Re: puppet parser validate - no output when everything's ok On reflection, it looks like my use case would readily be satisfied by simply passing validate a large list of files. I'd still like a --quiet option for use in scripts, and purely from an aesthetic perspective I like the traditional no output on success, but I can definitely see why it has the potential to be confusing. Add Comment Puppet / PUP-2341 puppet parser validate - no output when everything's ok Running `puppet parser validate init.pp` returns nothing on the command line when there are no errors. Please consider adding a message like OK or No Parse Error that indicates to the user that the file(s) passed parser validation. This comes up for discussion at almost every fundamentals class I teach, where someone asks So I see no output, is t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title Henrik Lindberg commented on an issue Re: puppet parser validate - no output when everything's ok The Unix philosophy relevant here is succeed silently, fail noisily. Don't think that is something we want to go against. The puppet validation can easily be wrapped in your own script and print ok if it exits with 0. Add Comment Puppet / PUP-2341 puppet parser validate - no output when everything's ok Running `puppet parser validate init.pp` returns nothing on the command line when there are no errors. Please consider adding a message like OK or No Parse Error that indicates to the user that the file(s) passed parser validation. This comes up for discussion at almost every fundamentals class I teach, where someone asks So I see no output, is t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-2557) Deprecate and remove node inheritance
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-2557 Deprecate and remove node inheritance Change By: Andy Parker Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2557) Deprecate and remove node inheritance
Title: Message Title Henrik Lindberg commented on an issue Re: Deprecate and remove node inheritance PR-2788 merged to master: f54911e Add Comment Puppet / PUP-2557 Deprecate and remove node inheritance Node inheritance causes a large number of complications and ambiguities that make understanding puppet code difficult. There is very little reason to use it since much more effective reuse can be achieved using classes and defined types. On the next 3 series puppet that is using the current parser: the system must issue a deprecation warning when it en... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2557) Deprecate and remove node inheritance
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2557 Deprecate and remove node inheritance Change By: Henrik Lindberg Nodeinheritancecausesalargenumberofcomplicationsandambiguitiesthatmakeunderstandingpuppetcodedifficult.Thereisverylittlereasontouseitsincemuchmoreeffectivereusecanbeachievedusingclassesanddefinedtypes.Onthenext3seriespuppetthatisusingthecurrentparser:thesystemmustissueadeprecationwarningwhenitencountersinheritsinanodestatement.Forthefutureparser(3seriesandin4)inheritsonanodeisanerror. UPDATE:Thefinaldecisionistomake3.7(current)issueawarning,andthat3.7(future)raisesanerror.Thistomakethe3.7futureascloseaspossibletowhatwillbereleasedin4.0. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1394) NFS on Fedora 20 requires both path and device
Title: Message Title
Daniel Dreier commented on an issue
Re: NFS on Fedora 20 requires both path and device
I just tried to reproduce this on Fedora 20 x86_64 with puppet 3.6.2 on ruby 2.0.0p353 . I'm using the following manifest:
mount { '/mnt/foo':
ensure = 'mounted',
device = 'localhost:/export',
fstype = 'nfs',
options = 'rw,intr,soft,context=system_u:object_r:var_log_t:s0',
atboot = true,
}
I created a /etc/export containing:
/export *(rw,sync,no_root_squash,no_all_squash)
I created /exports/foo and put a test file in it, then started NFS
systemctl start rpcbind.service
systemctl start nfs-server.service
systemctl start nfs-lock.service
systemctl start nfs-idmap.service
systemctl restart nfs-server.service
When I ran the manifest above, I got the following /etc/fstab entry created:
localhost:/export /mnt/foo nfs rw,intr,soft,context=system_u:object_r:var_log_t:s0 0 0
It mounted to /mnt/foo as expected, both using puppet and by hand. SELinux is set to enforcing.
Can you share more details about how you're able to reproduce the issue you're running into? Do the settings I described cause the issue to happen for you?
Add Comment
Puppet / PUP-1394
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title
Henrik Lindberg commented on an issue
Re: puppet parser validate - no output when everything's ok
or just do like this: {code] puppet parser validate foo.pp --parser future; if test $? -eq 0; then echo 'ok'; fi
Add Comment
Puppet / PUP-2341
puppet parser validate - no output when everything's ok
Running `puppet parser validate init.pp` returns nothing on the command line when there are no errors. Please consider adding a message like OK or No Parse Error that indicates to the user that the file(s) passed parser validation. This comes up for discussion at almost every fundamentals class I teach, where someone asks So I see no output, is t...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title Henrik Lindberg commented on an issue Re: puppet parser validate - no output when everything's ok I am closing this as won't fix since puppet follows the unix philosophy. I don't think adding a --verbose flag with the only purpose of printing ok if there were no errors is very valuable. For any real development flow it is far better to test the entire catalog and using rspec to do this. Any parse/validation errors will then also be caught. Alternatively, you can trigger the compilation of the catalog which also catches issues with files not being found and the effect of hiera use, reading files, as well as evaluation errors, circular dependencies, etc. etc. One alternative is also to use puppet master compile to produce a catalog (then you will get lots of output when it is ok, and errors otherwise. Add Comment Puppet / PUP-2341 puppet parser validate - no output when everything's ok Running `puppet parser validate init.pp` returns nothing on the command line when there are no errors. Please consider adding a message like OK or No Parse Error that indicates to the user that the file(s) passed parser validation. This comes up for discussion at almost every fundamentals class I teach, where someone asks So I see no output, is t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1299) Deprecate and eliminate magic parameter array handling
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1299 Deprecate and eliminate magic parameter array handling Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title Aaron Zauner commented on an issue Re: puppet parser validate - no output when everything's ok `puppet master compile` makes sense. thanks for your reasoning - i'm fine with that. Add Comment Puppet / PUP-2341 puppet parser validate - no output when everything's ok Running `puppet parser validate init.pp` returns nothing on the command line when there are no errors. Please consider adding a message like OK or No Parse Error that indicates to the user that the file(s) passed parser validation. This comes up for discussion at almost every fundamentals class I teach, where someone asks So I see no output, is t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1428) No such file or directory error with ssh_authorized_keys
Title: Message Title
Daniel Dreier commented on an issue
Re: No such file or directory error with ssh_authorized_keys
This was originally reported against 2.7.14. About two years ago, the original reporter figured out what the matter was: I was mounting my tmp folder to another volume and that folder was not writable. I did not know that puppet writes to /tmp. Should we display a warning if tmp cannot be written to? The error message, in its current form, is not easy to debug.
As of puppet 3.6.2, error messages for a read-only /tmp are more descriptive. For the following test manifest, and given a loopback filesystem mounted read-only to /tmp, we get the output below:
ssh_authorized_key { 'daniel':
key = 'testkey',
type = ssh-rsa,
user = 'daniel',
require = User['daniel'],
}
user { 'daniel':
ensure = 'present',
managehome = true,
}
[root@poss-head-centos ~]# puppet apply test.pp
Warning: Future reserved word: type. Either choose a different name or quote the string, if possible. In /root/test.pp:3. See http://links.puppetlabs.com/reserved-words-4
(at /puppetlabs/puppet/lib/puppet/parser/lexer.rb:615:in `warn_if_reserved')
Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.34 seconds
Error: Could not set 'present' on ensure: Read-only file system - /tmp/puppet20140619-9394-rzb8kx.lock at 11:/root/test.pp
Error: Could not set 'present' on ensure: Read-only file system - /tmp/puppet20140619-9394-rzb8kx.lock at 11:/root/test.pp
Wrapped exception:
Read-only file system - /tmp/puppet20140619-9394-rzb8kx.lock
Error: /Stage[main]/Main/User[daniel]/ensure: change from absent to present failed: Could not set 'present' on ensure: Read-only file system - /tmp/puppet20140619-9394-rzb8kx.lock at 11:/root/test.pp
Notice: /Stage[main]/Main/Ssh_authorized_key[daniel]: Dependency User[daniel] has failures: true
Warning: /Stage[main]/Main/Ssh_authorized_key[daniel]: Skipping because of failed dependencies
Notice: Finished catalog run in 0.09 seconds
Given the fact that the original issue was essentially misconfiguration exacerbated by a confusing error message, and the error message is much more descriptive now, I think this issue can safely be closed.
Add Comment
Jira (PUP-2087) Puppet does not implicitly convert string to integer
Title: Message Title Henrik Lindberg commented on an issue Re: Puppet does not implicitly convert string to integer There are a number of issues with number/string conversion in puppet 3x. The parser and evaluator of puppet is about to be replaced (in 4.0) with what is now available when you use --parser future. If you are into testing details of the language, it is valuable to also test with --future parser. In the future parser there is a distinction between numbers and strings, but conversion will still take place from string to number when doing arithmetic (it even does it correctly, and reports relevant errors). Add Comment Puppet / PUP-2087 Puppet does not implicitly convert string to integer I refer to my post on serverfault (http://serverfault.com/questions/388944/how-to-convert-a-string-to-integer-in-puppet). In short I have the following code: $foo = '123' $result = $foo % 2 Puppet give me an `Could not match %` error. If I am using multiplication with this code: $foo = '123' $result = $foo * 2 I get a `... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this
Jira (PUP-417) Add acceptance cells which test with passenger instead of webrick.
Title: Message Title Joshua Partlow commented on an issue Re: Add acceptance cells which test with passenger instead of webrick. Have made progress on this, but not done testing it with a foss passenger setup; there are still some failures related to running acceptance with Passenger (in the expectations of the tests themselves so far) There are two patches involved, both WIPs, neither a PR yet: https://github.com/jpartlow/puppet/tree/issue/master/pup-417-passenger-acceptance and https://github.com/jpartlow/beaker/tree/issue/master/qeng-188-foss-service-restarts I'm gone for two weeks and will pick this up when I return. Add Comment Puppet / PUP-417 Add acceptance cells which test with passenger instead of webrick. One way to do this is to install puppetmaster-passenger on Debian platforms. However if we want both webrick and passenger coverage on Debian, then it's not as simple as modifying the packages setup process. There is conversation about this in the 9/25 Hipchat logs around 11AM, re webrick and passenger. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title Henrik Lindberg commented on an issue Re: puppet parser validate - no output when everything's ok Also, do checkout rspec-puppet if you haven't already, it basically gives you programmatically driven catalog compilation + assertions that the results are what you expect them to be. If the main problem is authoring manifests, then a tool like Puppetlabs Geppetto that gives instant feedback (as you are typing) about syntax and stylistic problems may be the best tool. Add Comment Puppet / PUP-2341 puppet parser validate - no output when everything's ok Running `puppet parser validate init.pp` returns nothing on the command line when there are no errors. Please consider adding a message like OK or No Parse Error that indicates to the user that the file(s) passed parser validation. This comes up for discussion at almost every fundamentals class I teach, where someone asks So I see no output, is t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop
Jira (FACT-335) Revisit how facter detects GCE instances
Title: Message Title Josh Cooper commented on an issue Re: Revisit how facter detects GCE instances Merged in 83f1d52 to be released in 2.1 Add Comment Facter / FACT-335 Revisit how facter detects GCE instances With the launch of GCE v1 API, Google has revised the recommended way of determining if the virtual machine resides within GCE. Updated instructions state to use 'sudo dmidecode -s bios-vendor | grep Google' (same URL, new instructions at https://developers.google.com/compute/docs/instances#dmi). GCE v1 no longer requires google-only kernels and we ca... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-593) Facter assumes that route is in the path
Title: Message Title
Peter Huene commented on an issue
Re: Facter assumes that route is in the path
William Hopper For future tickets where you set it ready to merge, could you add a link to the ticket to the PR as well? I've added this one.
Add Comment
Facter / FACT-593
Facter assumes that route is in the path
Acceptance tests are failing on rhel7 when trying to evaluate {{dhcp_servers}} fact: {noformat} q6mzikqnvnd9urf (agent) $ env RUBYLIB=/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-puppet/lib:${RUBYLIB} PATH=/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH} facter SCRIPT CALLED Could not retrieve fact='dhcp_servers', resolution='a...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title Carthik Sharma commented on an issue Re: puppet parser validate - no output when everything's ok I am sorry my comment from redmine did not get imported. So let me paraphrase: The command: apachectl -T Returns a Syntax OK when the config files are syntactically correct. Since Puppet itself is written in ruby, the output of: ruby -c might be of interest, and it too returns a Syntax OK. Puppet is not (just) a *nix tool. Lastly, adding a -v flag would still be in keeping with Unix design philosophies. In Puppet's world, the stance taken on this issue contradicts how several command line tools behave, like puppet apply, which does not provide any means to suppress notice message, see: PUP-1126 . In any case, adding a Syntax OK message would inconvenience no one, and not having this is a bad surprise for more than a few new users, as I have observed first hand in countless trainings. Adding a flag to suppress the message would be a reasonable approach, too. Add Comment Puppet / PUP-2341 puppet parser validate - no output when everything's ok Running `puppet parser validate init.pp` returns nothing on the command line when there are no errors. Please consider adding a message like OK or No Parse Error that indicates to the user that the file(s) passed parser validation. This comes up for discussion at almost every fundamentals class I teach, where someone asks So I see no output, is t...
Jira (FACT-593) Facter assumes that route is in the path
Title: Message Title
William Hopper commented on an issue
Re: Facter assumes that route is in the path
Peter Huene Right on! I'll be sure to do that on the next one
Add Comment
Facter / FACT-593
Facter assumes that route is in the path
Acceptance tests are failing on rhel7 when trying to evaluate {{dhcp_servers}} fact: {noformat} q6mzikqnvnd9urf (agent) $ env RUBYLIB=/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-puppet/lib:${RUBYLIB} PATH=/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH} facter SCRIPT CALLED Could not retrieve fact='dhcp_servers', resolution='a...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2811) Provide method for class masquerading
Title: Message Title
Jok Thuau created an issue
Puppet / PUP-2811
Provide method for class masquerading
Issue Type:
Improvement
Assignee:
Andy Parker
Components:
DSL, Modules
Created:
19/Jun/14 5:34 PM
Priority:
Normal
Reporter:
Jok Thuau
this stems from a discussion on puppet-dev. this is an attempt at putting on the radar.
~/modules/sssd/manifests/init.pp class sssd as auth { # do something to install/setup/etc sssd }
~/modules/nslcd/manifests/init.pp class nslcd as auth { # do something to install/setup/etc nslcd }
~/modules/ssh_authz/manifests/init.pp class ssh_authz { require auth # setup something with ssh that requires groups from sssd or nslcd }
node nodeA { # include both class. because of the masquerading, nslcd is viewed as auth, and dependencies are established properly. include ssh_authz include nslcd }
node nodeB { # same for this. include sssd include ssh_authz }
node nodeC { # this fails with duplicate resources, as both class show up as auth # hopefully, the message is clear enough that it can be clear which # modules provide auth, and conflict with each other include sssd include nslcd }
With something like that (and maybe the node definition comes from an ENC, where the order is hard to enforce, and puppet shouldn't care), we don't have to have weird dependency on class definition/order and no if (defined(Class['nslcd'])) type construct to make all this works.
in the case where one would include ssh_authz but not one
Jira (PUP-2794) Specify signatures for blocks of block-accepting methods
Title: Message Title
Andy Parker commented on an issue
Re: Specify signatures for blocks of block-accepting methods
Henrik Lindberg it mostly works. The only problem is the support that the functions have for accepting a block that has a single captures rest argument (|*$x|). The signature of that doesn't match what the signature of the block to the function would be (Callable[Object, 1, 2]).
Essentially what this comes down to is: can we remove support for using captures rest on those blocks?
Add Comment
Puppet / PUP-2794
Specify signatures for blocks of block-accepting methods
Since PUP-2755, the iteration functions are implemented using the new function API, which allows specifying dispatches on parameter types, as well as the signature of the block that is accepted. However, the current implementation doesn't specify the block's signature and leaves at the default of {{Callable[Object]}}. Ideally the block signature should...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this
Jira (FACT-570) Remove windows-pr as a Windows gem dependency
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Facter / FACT-570 Remove windows-pr as a Windows gem dependency Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1811) in with regexps should set match variables
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-1811 in with regexps should set match variables Change By: Henrik Lindberg Assignee: AndyParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title Henrik Lindberg commented on an issue Re: puppet parser validate - no output when everything's ok I am willing to reconsider if there is enough demand for this, and there is a PR with an impl. It is an easier sell if it adds a --verbose flag, but I understand that the issue is when new users just run the command and they don't know about the --verbose flag. Add Comment Puppet / PUP-2341 puppet parser validate - no output when everything's ok Running `puppet parser validate init.pp` returns nothing on the command line when there are no errors. Please consider adding a message like OK or No Parse Error that indicates to the user that the file(s) passed parser validation. This comes up for discussion at almost every fundamentals class I teach, where someone asks So I see no output, is t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com.
Jira (PUP-2794) Specify signatures for blocks of block-accepting methods
Title: Message Title
Henrik Lindberg commented on an issue
Re: Specify signatures for blocks of block-accepting methods
Oh, now I get it, if the block accepted by a function is specified to be Callable[Object, 1, 2] then that would not match |*$x| since firstly, that means Callable[Object,0,default], and would thus need to be specified as | Array[Object, 1, 2| *$x| which absolutely no one would do for the utility of getting two variables into an array.
I guess it come down to what we are specifying - is it I require something that can be called given arguments of these types, or I require something that has an exact signature of I think it is more reasonable to support the first interpretation (can I call that thing with an Integer and a String?)
Add Comment
Puppet / PUP-2794
Specify signatures for blocks of block-accepting methods
Since PUP-2755, the iteration functions are implemented using the new function API, which allows specifying dispatches on parameter types, as well as the signature of the block that is accepted. However, the current implementation doesn't specify the block's signature and leaves at the default of {{Callable[Object]}}. Ideally the block signature should...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-2781 'puppet module generate' create not compatible metadata.json with forge Change By: Kenn Hussey Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-2781 'puppet module generate' create not compatible metadata.json with forge Change By: Kenn Hussey Sprint: July2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-2781 'puppet module generate' create not compatible metadata.json with forge Change By: Kenn Hussey Sprint: Week2014-6-18to2014-6-25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
