Jira (PUP-2507) puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec
Title: Message Title Klavs Klavsen created an issue Puppet / PUP-2507 puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec Issue Type: Bug Affects Versions: 3.5.1 Assignee: Unassigned Created: 07/May/14 1:31 AM Priority: Normal Reporter: Klavs Klavsen I just updated all my hosts to puppet 3.5.1 (from 3.4.2) after having tested on a few. Unfortunately puppet run now fails on 50% of my hosts, with this failure: puppet agent -t /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3:in `require': no such file to load – json (LoadError) from /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/files.rb:1:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/files.rb:1 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/templatewrapper.rb:1:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/templatewrapper.rb:1 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/scope.rb:6:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/scope.rb:6 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/methods.rb:2:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/methods.rb:2 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/method_call.rb:2:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/method_call.rb:2 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast.rb:115:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast.rb:115 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/parser.rb:11:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/parser.rb:11 from /usr/lib/ruby/site_ruby/1.8/puppet/parser.rb:4:in `require' from
Jira (PDB-597) Add Trusty (Ubuntu 14.04) Packaging Support for 2.x (master)
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-597 Add Trusty (Ubuntu 14.04) Packaging Support for 2.x (master) Change By: Kenneth Barber Sprint: 20140507to20140521 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-658) Refactor remaining query endpoints to new query language code
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-658 Refactor remaining query endpoints to new query language code Change By: Kenneth Barber Sprint: 20140507to20140521 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-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update Change By: Kenneth Barber Fix Version/s: 2.0.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 (PDB-653) Certain metrics aren't getting updated
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-653 Certain metrics aren't getting updated Change By: Kenneth Barber Sprint: 20140507to20140521 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-659) PuppetDB 2.0 Can't run on Ubuntu 12.04 LTS without manually installing JDK 1.7 from PPA
Title: Message Title Kenneth Barber commented on an issue Re: PuppetDB 2.0 Can't run on Ubuntu 12.04 LTS without manually installing JDK 1.7 from PPA Gabriel Lesprance I can't replicate this issue, when I install PuppetDB on a clean 12.04 machine, it installs openjdk-7 quite sucessfullly: https://gist.github.com/kbarber/688a85afa901b19edd5c This is the repository setup on the Ubuntu box I used to test: https://gist.github.com/kbarber/3ba18d6870b5b17fe82e Add Comment PuppetDB / PDB-659 PuppetDB 2.0 Can't run on Ubuntu 12.04 LTS without manually installing JDK 1.7 from PPA It seems that the latest PuppetDB package (v2.0) that we get when we use the apt sources installed via http://apt.puppetlabs.com/puppetlabs-release-precise.deb is not compatible with JDK 1.7 ; the problem is that Oracle Java 7 is not formally supported by Ubuntu. Hence, the package updates and installs without warning but PuppetDB doesn't run... 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 (PUP-2508) Failed compilation does not populate environment, transaction_uuid in report
Title: Message Title Kenneth Barber created an issue Puppet / PUP-2508 Failed compilation does not populate environment, transaction_uuid in report Issue Type: Bug Affects Versions: 3.6.0 RC Assignee: Unassigned Created: 07/May/14 7:02 AM Priority: Normal Reporter: Kenneth Barber Seems that the transaction_uuid and environment is not populated in a report submission from the agent when the catalog fails to compile. Looking at various other patches around this it looks like at least the environment was intended to appear here but the existing code doesn't achieve this. transaction_uuid on the other hand I believe was just never added to the correct places for this to ever work. This has surfaced because of PDB-16, we're trying to pass on the status of a failed run in a report but currently we make 'environment' mandatory. Obviously one temporary solution for PDB is to make this optional. My current fix is something like this: https://gist.github.com/kbarber/515440b085a627ff573a. Let me see if I can put this into a patch. Add Comment
Jira (PDB-16) Store status for reports
Title: Message Title Kenneth Barber commented on an issue Re: Store status for reports PUP-2508 blocks us with the existing patch here: https://github.com/puppetlabs/puppetdb/pull/960. This is because a failed compilation does not send the correct environment (and transaction_uuid) to the report receiver on the master. Since we require environment to be mandatory, PDB will reject the command submission. While we can fix this bug, we're still beholden to Puppet 3.5.1 so we may find we have to make environment optional. I'm looking into how hard the fix is for Puppet, this is my rough work-around: https://gist.github.com/kbarber/515440b085a627ff573a Add Comment PuppetDB / PDB-16 Store status for reports We recently learned that when a puppet run fails due to catalog compilation error or catalog timeout, the agent will submit a report with a status of `failed`, but without any events. Because the current implementation of report storage in PuppetDB relies entirely on events to indicate success/failure, there is no way to look at the PuppetDB data and ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-523) Add 'private' as a keyword to make classes (and defines?) private to a module
Title: Message Title Henrik Lindberg commented on an issue Re: Add 'private' as a keyword to make classes (and defines?) private to a module I don't understand the motivation to put this off until later. While the functionality comes during 4x, the keyword should be reserved in 3.7 future, and issue a deprecation warning in 3.7 current. We would otherwise have a breaking change to introduce this. This issue (PUP-523) is about adding it as a reserved keyword only. Suggested implementation is to introduce it in the lexer and grammar where it will appear, and to validate it - (decide on one of): a warning that it has no effect yet an error no-op silently ignored The recognize and validate provides the best possibility to provide feedback. Add Comment Puppet / PUP-523 Add 'private' as a keyword to make classes (and defines?) private to a module Add the keyword 'private' to classes (and defines?) to make them restricted for use from within the same module.
Jira (PDB-467) Merge versioning tests for http testing into non-versioned files
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-467 Merge versioning tests for http testing into non-versioned files Change By: Kenneth Barber Sprint: 20140507to20140521 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-653) Certain metrics aren't getting updated
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-653 Certain metrics aren't getting updated Added some screenshots to confirm my assumptions - indeed the DLO size on disk and discarded messages are not updated until the first fault seen since startup. The first screenshot shows these as ? before failure, second screenshot shows the results immediately after failure. Change By: Kenneth Barber Attachment: ScreenShot2014-05-07at15.36.15.png Attachment: ScreenShot2014-05-06at17.54.39.png 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-137) Document use of PuppetDB with SELinux
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-137 Document use of PuppetDB with SELinux Change By: Kenneth Barber Affects Version/s: 1.5.0 Labels: docs redmine Issue Type: Bug Task 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-660) Support streaming for all end-points
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-660 Support streaming for all end-points Issue Type: Improvement Assignee: Unassigned Created: 07/May/14 7:51 AM Priority: Normal Reporter: Kenneth Barber We've managed to get streaming working for most end-points but we still have some to go, this ticket tracks the work to provide streaming for all end-points where possible/feasible. The motivation is partially for performance, but also will provide us with more code consistency in our http/*.clj end-points. /reports query field could also become optional, making it consistent with our other end-points also. This may or may not make sense on all end-points, we'll have to determine how far we should go. Add Comment This message was
Jira (PDB-601) For /reports query operator should be optional
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-601 For /reports query operator should be optional Change By: Kenneth Barber Sprint: 20140507to20140521 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-657) Refactor query logic to separate SQL generation from query object types
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-657 Refactor query logic to separate SQL generation from query object types Change By: Kenneth Barber Sprint: 20140507to20140521 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-660) Support streaming for all end-points
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-660 Support streaming for all end-points Change By: Kenneth Barber Sprint: 20140507to20140521 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-167) Query for deactivated nodes
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-167 Query for deactivated nodes Change By: Kenneth Barber Sprint: 20140507to20140521 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-1028) Test future evaluator impl of Node Expresson
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1028 Test future evaluator impl of Node Expresson 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-628) PuppetDB 2.0.0 Release (May 7th, 2014)
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-628 PuppetDB 2.0.0 Release (May 7th, 2014) Change By: Kenn Hussey Sprint: 20140423to20140507 ,20140507to20140521 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-651) PR (962): Allow configurable url prefix - cprice404
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-651 PR (962): Allow configurable url prefix - cprice404 Change By: Kenn Hussey Sprint: 20140423to20140507 ,20140507to20140521 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-16) Store status for reports
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-16 Store status for reports Change By: Kenn Hussey Sprint: 20140423to20140507 ,20140507to20140521 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-659) PuppetDB 2.0 Can't run on Ubuntu 12.04 LTS without manually installing JDK 1.7 from PPA
Title: Message Title Gabriel Lesprance commented on an issue Re: PuppetDB 2.0 Can't run on Ubuntu 12.04 LTS without manually installing JDK 1.7 from PPA My bad It seems that openjdk-7-jre is indeed installed : $ dpkg -s openjdk-7-jre-headless | grep Status Status: install ok installed moreover it seems properly detected as a java-alternative: $ sudo update-java-alternatives -l java-1.6.0-openjdk-amd64 1061 /usr/lib/jvm/java-1.6.0-openjdk-amd64 java-1.7.0-openjdk-amd64 1051 /usr/lib/jvm/java-1.7.0-openjdk-amd64 Perhaps something is causing PuppetDB not to use the proper JDK as I am still getting the same error as I pasted in the ticket. Add Comment PuppetDB / PDB-659 PuppetDB 2.0 Can't run on Ubuntu 12.04 LTS without manually installing JDK 1.7 from PPA It seems that the latest PuppetDB package (v2.0) that we get when we use the apt sources installed via http://apt.puppetlabs.com/puppetlabs-release-precise.deb is not compatible with JDK 1.7 ; the problem is that Oracle Java 7 is not formally supported by Ubuntu. Hence, the package updates and installs without warning but PuppetDB doesn't run...
Jira (PDB-658) Refactor remaining query endpoints to new query language code
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-658 Refactor remaining query endpoints to new query language code Change By: Kenn Hussey Story Points: 5 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-551) Make a statement about new API versioning for 2.0.0
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-551 Make a statement about new API versioning for 2.0.0 Change By: Kenn Hussey Sprint: 20140423to20140507 ,20140507to20140521 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-659) PuppetDB 2.0 Can't run on Ubuntu 12.04 LTS without manually installing JDK 1.7 from PPA
Title: Message Title Gabriel Lesprance commented on an issue Re: PuppetDB 2.0 Can't run on Ubuntu 12.04 LTS without manually installing JDK 1.7 from PPA I was able to fix the problem by modifying /etc/default/puppetdb so that JAVA_BIN=/usr/lib/jvm/java-7-openjdk-amd64/bin/java Any idea why /etc/default/puppetdb hasn't been updated properly when updating the PuppetDB package ? Add Comment PuppetDB / PDB-659 PuppetDB 2.0 Can't run on Ubuntu 12.04 LTS without manually installing JDK 1.7 from PPA It seems that the latest PuppetDB package (v2.0) that we get when we use the apt sources installed via http://apt.puppetlabs.com/puppetlabs-release-precise.deb is not compatible with JDK 1.7 ; the problem is that Oracle Java 7 is not formally supported by Ubuntu. Hence, the package updates and installs without warning but PuppetDB doesn't run... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2509) puppet resource service on Solaris needs -H flag
Title: Message Title
Drew Fisher created an issue
Puppet / PUP-2509
puppet resource service on Solaris needs -H flag
Issue Type:
Bug
Affects Versions:
3.4.1
Assignee:
Andy Parker
Components:
Modules
Created:
07/May/14 8:49 AM
Environment:
Solaris 11.2
Priority:
Normal
Reporter:
Drew Fisher
On Solaris 11.2, the following behavior happens when 'puppet resource service' runs:
root@solaris:~# puppet resource service service { 'FMRI': ensure = 'stopped', enable = 'false', }
service { 'PRESERVE': ensure = 'stopped', }
...
Those entries are due to the header output of /usr/bin/svcs:
$ /usr/bin/svcs | head -5 STATE STIME FMRI legacy_run 8:33:43 lrc:/etc/rc2_d/S47pppd legacy_run 8:33:44 lrc:/etc/rc2_d/S81dodatadm_udaplt legacy_run 8:33:44 lrc:/etc/rc2_d/S89PRESERVE disabled 8:33:05 svc:/platform/i86pc/acpihpd:default
A possible fix is to update puppet/provider/service/smf.rb like so:
Jira (PUP-2510) Overrides and definitions don't mix
Title: Message Title
Thomas Bellman created an issue
Puppet / PUP-2510
Overrides and definitions don't mix
Issue Type:
Bug
Affects Versions:
3.4.2
Assignee:
Unassigned
Created:
07/May/14 9:30 AM
Environment:
CentOS 6, Fedora 19
Priority:
Normal
Reporter:
Thomas Bellman
The following manifest writes a zero (0) to /tmp/bug.txt, instead of the expected one (1).
However, if foo::enable is included directly from Node[default] instead of via the trigger_bug definition, as indicated by the outcommented line, it works as expected and 1 is written to bug.txt. Likewise, if the file declaration is inlined into foo::disable and foo::enable, as I have done with /tmp/nobug.txt, it also works as expected.
This has been tested with Puppet 3.4.2 on Fedora 19, and Puppet 2.7.23 on CentOS 6.
define myfile($value) { file { $name: ensure = file, content = $ {value}
\n; } }
class foo::disable { myfile { /tmp/bug.txt: value = 0; }
file { /tmp/nobug.txt: ensure = file, content = 0\n; }
}
class foo::enable inherits foo::disable { Myfile[/tmp/bug.txt] { value = 1 }
Jira (PUP-2511) Add parser function digest: uses digest_algorithm to hash, not strictly md5
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2511 Add parser function digest: uses digest_algorithm to hash, not strictly md5 Issue Type: New Feature Assignee: Unassigned Created: 07/May/14 10:26 AM Labels: redmine Priority: Normal Reporter: Rob Reynolds Puppet has an md5 parser function, which returns the MD5 digest of its argument. On hosts configured for compliance with U.S. Federal Information Processing Standard (FIPS) 140-2, attempts to use the MD5 algorithm cause errors, because MD5 is no longer FIPS Approved. This patch adds a parser function called digest, which returns the digest of its argument using the algorithm named by the digest_algorithm setting in puppet.conf. Therefore, where md5 may fail on some hosts, the digest function should always return a value; but the value may vary if the digest_algorithm setting is changed. Add Comment
Jira (PUP-1840) Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts
Title: Message Title Rob Reynolds commented on an issue Re: Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts Moved the last part of this functionality to a new ticket PUP-2511 to track separately. Add Comment Puppet / PUP-1840 Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts I'm using Puppet in part to ensure [Federal Information Processing Standard 140-2](http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf) (FIPS 140-2) compliance on my network. Part of this compliance for the system underlying Puppet is to make sure that only [FIPS Approved](http://csrc.nist.gov/publications/fips/fips140-2/fips1402annexa.pdf) algo... 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-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title Peter Huene updated an issue Puppet / PUP-2031 unless_uid on user is completely broken wrt ranges Change By: Peter Huene Priority: Critical 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-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Peter Huene commented on an issue
Re: unless_uid on user is completely broken wrt ranges
I'm not sure if we should be asking users to install a gem to get a previously documented and, albeit it incorrectly, implemented feature to work in a point release. For 4.x, we should obviously support ranges from the parser, but in 3.x I think the least impact on users is to fix the implementation to support what was originally intended (i.e. '[x..y]') as a special syntax for the parameter.
Also, I disagree this bug is critical. A bug inherently means something is broken, so we'd have to treat all bugs as critical with that definition. A bug is critical if it is a security vulnerability or crash. This bug is neither and has an usable workaround that is forwards-compatible, even if it isn't the best in terms of performance.
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Peter Huene commented on an issue
Re: unless_uid on user is completely broken wrt ranges
Also, looking at the original PR that implemented this parameter, it seems that Jeff McCune's feedback on the PR was never addressed, so it should never have been merged in the first place. But since it went out in a release, we might as well fix it in 3.x and remove/deprecate/rework it in 4.x.
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
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-2303) ArgumentErrors in file_server config parser are swallowed by raising the error wrong
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2303 ArgumentErrors in file_server config parser are swallowed by raising the error wrong Change By: Adrien Thebo Sprint: Week2014-5-7to2014-5-14 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-2303) ArgumentErrors in file_server config parser are swallowed by raising the error wrong
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2303 ArgumentErrors in file_server config parser are swallowed by raising the error wrong Change By: Adrien Thebo Assignee: AdrienThebo 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-2303) ArgumentErrors in file_server config parser are swallowed by raising the error wrong
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2303 ArgumentErrors in file_server config parser are swallowed by raising the error wrong Change By: Adrien Thebo 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-2339) ci-bootstrap-from-artifacts.sh should fall-back to public Rubygems
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2339 ci-bootstrap-from-artifacts.sh should fall-back to public Rubygems Change By: Adrien Thebo 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-2339) ci-bootstrap-from-artifacts.sh should fall-back to public Rubygems
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2339 ci-bootstrap-from-artifacts.sh should fall-back to public Rubygems Change By: Adrien Thebo Sprint: Week2014-5-7to2014-5-14 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-460) ci-bootstrap-from-artifacts.sh should fall-back to public Rubygems
Title: Message Title Adrien Thebo updated an issue Facter / FACT-460 ci-bootstrap-from-artifacts.sh should fall-back to public Rubygems Change By: Adrien Thebo Sprint: Week2014-5-7to2014-5-14 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-460) ci-bootstrap-from-artifacts.sh should fall-back to public Rubygems
Title: Message Title Adrien Thebo updated an issue Facter / FACT-460 ci-bootstrap-from-artifacts.sh should fall-back to public Rubygems Change By: Adrien Thebo 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 (FACT-233) Fact to add DHCP Server Details
Title: Message Title Kylo Ginsberg commented on an issue Re: Fact to add DHCP Server Details Pull request to fix up acceptance coming. Add Comment Facter / FACT-233 Fact to add DHCP Server Details Add per interface fact that shows the DHCP server IP for that interface if the interface IP is DHCP assigned. e.g. 'dhcp_server_eth0' Also add a 'dhcp_server' fact if the interface the machine uses to reach the default gateway is dhcp enabled. PR created: https://github.com/puppetlabs/facter/pull/559 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-2369) Add extra info to property's return
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2369 Add extra info to property's return Change By: Adrien Thebo 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-2369) Add extra info to property's return
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2369 Add extra info to property's return Change By: Adrien Thebo Sprint: Week2014-5-7to2014-5-14 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-2369) Add extra info to property's return
Title: Message Title Adrien Thebo commented on an issue Re: Add extra info to property's return Merged in f89f1a5. Add Comment Puppet / PUP-2369 Add extra info to property's return When working with boolean types in providers it happens too often that the values being passed around aren't what we think they are leading the developer down a twisty road of despair while trying to figure out why his methods aren't working. 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-2369) Add extra info to property's return
Title: Message Title Joshua Partlow commented on an issue Re: Add extra info to property's return Merged to master in f89f1a5 Add Comment Puppet / PUP-2369 Add extra info to property's return When working with boolean types in providers it happens too often that the values being passed around aren't what we think they are leading the developer down a twisty road of despair while trying to figure out why his methods aren't working. 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-1736) Add encoding information to debug output
Title: Message Title
Andy Parker commented on an issue
Re: Add encoding information to debug output
Merged into master in 0c51f1
Add Comment
Puppet / PUP-1736
Add encoding information to debug output
Lots of Puppet encoding issues are sensitive to the locale settings that the Ruby process happens to be using. Investigating encoding issues frequently involves patching Puppet so that encoding info is printed out. This info should be added to the standard {{--debug}} output --- preferably somewhere prominent. Printing out the value of {{Encoding.defau...
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-1736) Add encoding information to debug output
Title: Message Title Andy Parker updated an issue Puppet / PUP-1736 Add encoding information to debug output Change By: Andy Parker Sprint: Week2014-5-7to2014-5-14 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-2253) Enable manifest ordering by default
Title: Message Title Andy Parker updated an issue Puppet / PUP-2253 Enable manifest ordering by default Change By: Andy Parker Sprint: Week2014-5-7to2014-5-14 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-2253) Enable manifest ordering by default
Title: Message Title Andy Parker updated an issue Puppet / PUP-2253 Enable manifest ordering by default Change By: Andy Parker 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-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.
Title: Message Title Andy Parker updated an issue Puppet / PUP-2426 Puppet's v2 environment listing does not display config_version and environment_timeout as well. Change By: Andy Parker Sprint: Week2014-5-7to2014-5-14 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-2214) Many puppet commands fail when using a configured or requested directory environment that doesn't exist.
Title: Message Title Andy Parker updated an issue Puppet / PUP-2214 Many puppet commands fail when using a configured or requested directory environment that doesn't exist. Change By: Andy Parker Sprint: Week2014-5-7to2014-5-14 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-2252) Legacy settings take precedence over directory settings in a puppet config print.
Title: Message Title Andy Parker updated an issue Puppet / PUP-2252 Legacy settings take precedence over directory settings in a puppet config print. Change By: Andy Parker Sprint: Week2014-5-7to2014-5-14 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-2214) Many puppet commands fail when using a configured or requested directory environment that doesn't exist.
Title: Message Title Andy Parker updated an issue Puppet / PUP-2214 Many puppet commands fail when using a configured or requested directory environment that doesn't exist. Change By: Andy Parker Story Points: 5 2 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-2214) Many puppet commands fail when using a configured or requested directory environment that doesn't exist.
Title: Message Title Andy Parker updated an issue Puppet / PUP-2214 Many puppet commands fail when using a configured or requested directory environment that doesn't exist. Change By: Andy Parker Story Points: 2 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-1736) Add encoding information to debug output
Title: Message Title Andy Parker updated an issue Puppet / PUP-1736 Add encoding information to debug output Change By: Andy Parker 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-2512) Validation for `enable` in service{} is lacking.
Title: Message Title
Ashley Penney created an issue
Puppet / PUP-2512
Validation for `enable` in service{} is lacking.
Issue Type:
Bug
Assignee:
Unassigned
Created:
07/May/14 11:54 AM
Priority:
Normal
Reporter:
Ashley Penney
[root@ccoifar9r5c1giy postgresql]# puppet resource service postgresql enable=running Error: The systemd provider can not handle attribute enable Error: /Service[postgresql]/enable: change from true to running failed: The systemd provider can not handle attribute enable
I discovered this while breaking Postgresql. It happily passes a value of running into the providers which then explode.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2512) Validation for `enable` in service{} is lacking.
Title: Message Title
Ashley Penney assigned an issue to Ashley Penney
Puppet / PUP-2512
Validation for `enable` in service{} is lacking.
Change By:
Ashley Penney
Assignee:
AshleyPenney
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-2512) Validation for `enable` in service{} is lacking.
Title: Message Title
Ashley Penney updated an issue
Puppet / PUP-2512
Validation for `enable` in service{} is lacking.
Change By:
Ashley Penney
Assignee:
AshleyPenney AdrienThebo
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-2512) Validation for `enable` in service{} is lacking.
Title: Message Title
Ashley Penney commented on an issue
Re: Validation for `enable` in service{} is lacking.
I figured I'd assign it to you so it doesn't get lost
Add Comment
Puppet / PUP-2512
Validation for `enable` in service{} is lacking.
[root@ccoifar9r5c1giy postgresql]# puppet resource service postgresql enable=running Error: The systemd provider can not handle attribute enable Error: /Service[postgresql]/enable: change from true to running failed: The systemd provider can not handle attribute enable I discovered this while breaking Postgresql. It happily passes a value of running...
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-2513) puppet module install fails when url includes basic auth
Title: Message Title Michael Moghadas created an issue Puppet / PUP-2513 puppet module install fails when url includes basic auth Issue Type: Bug Affects Versions: 3.5.1, 3.2.4 Assignee: Michael Moghadas Components: Modules Created: 07/May/14 12:00 PM Environment: Tested on OSX + CentOS Labels: github puppet pupet-module Priority: Normal Reporter: Michael Moghadas When --module_repository is set to url that includes basic auth info like below... 'https://forgeuser:forgepassw...@forgeserver.example.com/' puppet module install will fail with following error: Error: userinfo not supported. [RFC3986] Error: Try 'puppet help module install' for usage I've submitted following pull request for the fix:
Jira (PUP-2508) Failed compilation does not populate environment, transaction_uuid in report
Title: Message Title Andy Parker assigned an issue to Kenneth Barber Puppet / PUP-2508 Failed compilation does not populate environment, transaction_uuid in report Change By: Andy Parker Assignee: KennethBarber 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-2508) Failed compilation does not populate environment, transaction_uuid in report
Title: Message Title Andy Parker commented on an issue Re: Failed compilation does not populate environment, transaction_uuid in report Kenneth Barber is this a regression or is this something missing from the fixes that you submitted earlier for puppetdb functionality in puppet? Add Comment Puppet / PUP-2508 Failed compilation does not populate environment, transaction_uuid in report Seems that the transaction_uuid and environment is not populated in a report submission from the agent when the catalog fails to compile. Looking at various other patches around this it looks like at least the environment was intended to appear here but the existing code doesn't achieve this. transaction_uuid on the other hand I believe was just never ... 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
Jira (PUP-2484) `puppet module build` should provide deprecated functionality with warning until Puppet v4
Title: Message Title Andy Parker updated an issue Puppet / PUP-2484 `puppet module build` should provide deprecated functionality with warning until Puppet v4 Change By: Andy Parker 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-2484) `puppet module build` should provide deprecated functionality with warning until Puppet v4
Title: Message Title Andy Parker updated an issue Puppet / PUP-2484 `puppet module build` should provide deprecated functionality with warning until Puppet v4 Change By: Andy Parker Sprint: Week2014-5-7to2014-5-14 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-2357) Validation missing for meaningless sequences
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2357 Validation missing for meaningless sequences Change By: Henrik Lindberg Sprint: Week2014-5-7to2014-5-14 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-1027) Add warning for use of bare words that clash with new keywords
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1027 Add warning for use of bare words that clash with new keywords Change By: Henrik Lindberg Sprint: Week2014-5-7to2014-5-14 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-2345) Upgrading from 3.4 to 3.5 causes Puppet to fail with Could not evaluate: uninitialized constant Puppet::FileSystem::File
Title: Message Title Stefan Lasiewski commented on an issue Re: Upgrading from 3.4 to 3.5 causes Puppet to fail with Could not evaluate: uninitialized constant Puppet::FileSystem::File Thanks for the tip. It looks like Ruby gems did install the 'puppet' and 'puppet-lint' gems. I uninstalled both of those using `gem uninstall puppet` and now the error goes away. ``` gem list LOCAL GEMS *** ansi (1.4.3) awesome_print (1.2.0, 1.0.2) clamp (0.6.3, 0.6.2) daemon_controller (1.2.0, 1.1.5) facter (1.7.5) fastercsv (1.5.5, 1.5.4) fastthread (1.0.7) foreman_api (0.1.11) gettext (2.1.0) hammer_cli (0.0.18) hashie (2.0.5) hiera (1.3.2) highline (1.6.21, 1.6.20) json (1.5.5) json_pure (1.8.1) kafo (0.5.2, 0.4.0, 0.3.17) kafo_parsers (0.0.2, 0.0.1) little-plugger (1.1.3) locale (2.0.5) logging (1.8.2, 1.8.1) mime-types (1.16) multi_json (1.9.2, 1.8.2) oauth (0.4.7) passenger (4.0.40, 4.0.5) powerbar (1.0.11) puppet (3.4.3) puppet-lint (0.3.2) rack (1.5.2, 1.1.0) rack-protection (1.5.2) rack-test (0.6.2, 0.5.4) rake (10.1.1, 0.8.7) rdoc (4.1.1, 3.12) rest-client (1.6.7, 1.6.1) rgen (0.6.6) rkerberos (0.1.2) rubyipmi (0.7.0) sinatra (1.4.4, 1.0) table_print (1.5.1, 1.1.5) tilt (1.4.1) # Add Comment Puppet / PUP-2345 Upgrading from 3.4 to 3.5 causes Puppet to fail with Could not evaluate: uninitialized constant
Jira (PUP-1603) puppet apply failure if puppet is upgraded
Title: Message Title Rob Reynolds commented on an issue Re: puppet apply failure if puppet is upgraded Thanks, was just adding this question based on a similar ticket. Add Comment Puppet / PUP-1603 puppet apply failure if puppet is upgraded I am testing an update from puppet 3.2.4 to 3.4.2 and I am receiving a failure that I have found in a few different places on the internet but that has no bug and no reproducer (for reference, I believe these are related links: https://groups.google.com/forum/#!topic/puppet-users/318TmfkO9Js and https://github.com/purpleidea/puppet-puppet/commit/8b7dae5ca... 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-2106) Update http://links.puppetlabs.com/env-settings-deprecations to point to appropriate 3.6 docs.
Title: Message Title Nicholas Fagerlund commented on an issue Re: Update http://links.puppetlabs.com/env-settings-deprecations to point to appropriate 3.6 docs. This link should instead point to http://docs.puppetlabs.com/puppet/latest/reference/environments_classic.html, which has details about the deprecation right up top. Joshua Partlow, it looks like you're the owner of the google link; could you change the target please? Add Comment Puppet / PUP-2106 Update http://links.puppetlabs.com/env-settings-deprecations to point to appropriate 3.6 docs. This link is referenced in all of the environment setting deprecations added in PUP-1433. Currently we're pointing to the general 3.5 directory environment docs. This should be changed to something in the 3.6 docs, which is more specific to deprecation of implicit environment settings. 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
Jira (PUP-2106) Update http://links.puppetlabs.com/env-settings-deprecations to point to appropriate 3.6 docs.
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2106 Update http://links.puppetlabs.com/env-settings-deprecations to point to appropriate 3.6 docs. Change By: Nicholas Fagerlund Assignee: NicholasFagerlund JoshuaPartlow 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-2253) Enable manifest ordering by default
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-2253 Enable manifest ordering by default 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.
