Jira (PDB-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilati
Title: Message Title Ryan Senior commented on PDB-949 Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilation. Joshua Partlow Kenneth Barber I was just talking with a user on IRC (simon_c) who ran into this issue. Specifically the Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted' on node error. From what I understand a user should only see this if they have PuppetDB as their facts cache. Is that right? When I have seen this in the past it was because a routes.yml file wasn't setup properly, causing the master to fail back to PuppetDB for the cache. Can we get a list of troubleshooting steps together to diagnose why a puppet master would be falling back to PuppetDB for it's cache? It seems like this problem might be more frequent at users are upgrading PuppetDB. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1916) puppet cert clean cannot remove signing requests
Title: Message Title Michael Moll commented on PUP-1916 Re: puppet cert clean cannot remove signing requests Same on 3.7.x. Is there any progress on this? Or was the change done on purpose? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3651) enabling storeconfigs in main sets resource terminus to store_configs
Title: Message Title Erik Daln created an issue Puppet / PUP-3651 enabling storeconfigs in main sets resource terminus to store_configs Issue Type: Bug Affects Versions: PUP 3.7.3, PUP 3.7.1 Assignee: Unassigned Created: 2014/11/10 3:33 AM Priority: Normal Reporter: Erik Daln If storeconfigs is enabled in the main of user sections (which it needs to be for puppet apply with storeconfigs to work) then the terminus for the resource application is changed from ral to store_configs. Not sure what the best way to solve this is. A workaround is to add this to your routes.yaml: resources: resources: terminus: ral
Jira (FACT-697) If NetworkManager is installed but not used facter throws a warning.
Title: Message Title Trevor Vaughan commented on FACT-697 Re: If NetworkManager is installed but not used facter throws a warning. Added a PR for this issue. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1020) clj-http-client logging into pe-puppetserver-daemon.log
Title: Message Title Christopher Price moved an issue PuppetDB / PDB-1020 clj-http-client logging into pe-puppetserver-daemon.log Change By: Christopher Price Workflow: Platform Engineering Workflow Key: SERVER PDB - 107 1020 Project: PuppetServer PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1020) clj-http-client logging into pe-puppetserver-daemon.log
Title: Message Title Christopher Price updated an issue PuppetDB / PDB-1020 clj-http-client logging into pe-puppetserver-daemon.log Change By: Christopher Price Assignee: ChristopherPrice Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1020) clj-http-client logging into pe-puppetserver-daemon.log
Title: Message Title Christopher Price commented on PDB-1020 Re: clj-http-client logging into pe-puppetserver-daemon.log Wyatt Alt done, thanks. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1020) PuppetDB terminus contains `puts` statement that causes duplicate error messages in daemon.log file
Title: Message Title Christopher Price updated an issue PuppetDB / PDB-1020 PuppetDB terminus contains `puts` statement that causes duplicate error messages in daemon.log file Change By: Christopher Price Summary: clj-http-clientloggingintope-puppetserver- PuppetDBterminuscontains`puts`statementthatcausesduplicateerrormessagesin daemon.log file Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3642) Remove environment name from URL path
Title: Message Title Christopher Price commented on PUP-3642 Re: Remove environment name from URL path Yes; since almost all agent URLs are assembled via very general network code, there's no super-easy way to make an informed decision about which endpoints would have the environment included in the URL/body and which wouldn't. So, for this round of changes, my proposed path forward would still include it for all endpoints. These endpoints would all land under a '/v3' URL namespace. Whenever we start working on a v4 API, that's when I'd hope that we could start tackling individual endpoints one at a time and making more specific decisions about their inputs/outputs. Andy Parker or Josh Cooper do you have any interest in reviewing the code I linked above a bit before I begin work on this? If Kylo and Henrik are both on board with option 1 then I'm comfortable going ahead and starting to work towards that. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3615) Remove automatic string to number conversion
Title: Message Title Henrik Lindberg commented on PUP-3615 Re: Remove automatic string to number conversion Language specification updated to reflect the decision in this ticket. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3642) Remove environment name from URL path
Title: Message Title Andy Parker commented on PUP-3642 Re: Remove environment name from URL path I took a look. It looks like you are just moving the environment from the path to a parameter, and then handling it the same everywhere else. That seems completely reasonable to me. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3642) Remove environment name from URL path
Title: Message Title Christopher Price commented on PUP-3642 Re: Remove environment name from URL path OK, thanks. I'll go ahead and get started on polishing this up and getting a PR together. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilati
Title: Message Title Joshua Partlow commented on PDB-949 Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilation. Ryan Senior The easiest way to reproduce would be to have puppetdb set as the facts cache, or to not have a facts cache set at all, or to make a request to the master that does not include the facts (say a manual curl of a catalog endpoint after facts for the node have been stored in puppetdb). However, it can be seen if a different facts terminus (say the yaml cache) is unable to read the facts (facts have been deleted, or an io error occurs) just when the master is requesting the catalog and the catalog indirector makes it's node request which makes a facts request You can't normally reproduce this just by manually deleting the facts cache, because the catalog compiler terminus stores the given facts from the request before making it's node request, and that act of storing the facts usually initializes the facts cache as well. (If you are thinking there may be some excessive storing and querying of facts in all of this, you are mostly likely correct). But, we did see this occur occasionally during test runs because of a bug in Puppet Server ( SERVER-38 ) that would sometimes prevent a read of the facts cache if a catalog request was coming in while the puppet server was still initializing some of it's jruby instances. If they are using puppet server, I would expect it's that scenario – a puppet server restart, and catalog request being fielded before all of the request handlers have finished initializing. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3621) Environments::Cached#get! bypasses the environment cache.
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3621 Environments::Cached#get! bypasses the environment cache. Change By: Joshua Partlow Assignee: JoshuaPartlow Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3621) Environments::Cached#get! bypasses the environment cache.
Title: Message Title Joshua Partlow commented on PUP-3621 Re: Environments::Cached#get! bypasses the environment cache. Merged to stable as e3cd823 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3652) Service Provider for Suse tries enable false to true even if its alreay ON
Title: Message Title Adrian Raemy created an issue Puppet / PUP-3652 Service Provider for Suse tries enable false to true even if its alreay ON Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Kylo Ginsberg Components: Client Created: 2014/11/10 10:39 AM Environment: Suse Sles 11 sp2 and sp3 Labels: chkconfig enable init suse runlevel service Priority: Normal Reporter: Adrian Raemy After upgrading from puppet 3.5.1 to 3.7.1 and also with puppet 3.7.3 the service provider redhat.rb for Suse is broken. At every Puppet run puppet tries to enable from false to true the Services even if they are already ON and running. I could reproduce this, when you set only runlevel 3 and 5 ON only, then the next run does not try to re-enable the
Jira (PUP-3652) Service Provider for Suse tries enable false to true even if its alreay ON
Title: Message Title Adrian Raemy updated an issue Puppet / PUP-3652 Service Provider for Suse tries enable false to true even if its alreay ON Change By: Adrian Raemy Afterupgradingfrompuppet3.5.1to3.7.1andalsowithpuppet3.7.3theserviceproviderredhat.rbforSuseisbroken.AteveryPuppetrunpuppettriestoenablefromfalsetotruetheServiceseveniftheyarealreadyONandrunning.Icouldreproducethis,whenyousetonlyrunlevel3and5ON only ,thenthenextrundoesnottrytore-enabletheservice.Butifyouhaveforaservicerunlevel2or4set,thenittriesateverypuppetruntoenableit.Notice:/Stage[main]/Puppet::Client/Service[puppet]/enable:enablechanged'false'to'true'Settingtheprovider/service/redhat.rb(enabled?)partbackasitwasinpuppet3.5.1theneverythingisworkingasitshould.Sopleasefixthisormaybesetupasuse.rbifthisiscausingproblemintheredhat.rb. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-754) Facter::Core::Execution::Posix.which(bin) method will return a directory
Title: Message Title Ben Schofield created an issue Facter / FACT-754 Facter::Core::Execution::Posix.which(bin) method will return a directory Issue Type: Bug Affects Versions: FACT 2.3.0 Assignee: Eric Sorenson Components: Community Created: 2014/11/10 10:47 AM Priority: Normal Reporter: Ben Schofield If a directory is found on the PATH before the actual executable being searched for then Facter::Core::Execution::Posix.which(bin) will return the directory which is not a valid executable. An example is if /etc is prefixed to the PATH on RHEL/Centos. /etc/blkid is returned instead of /sbin/blkid when evaluating the partitions fact. Add Comment
Jira (PUP-3615) Remove automatic string to number conversion
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-3615 Remove automatic string to number conversion Change By: Hailee Kenney Assignee: HaileeKenney Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3511) Refactor Application.run() logic in core Ruby Puppet for external reuse
Title: Message Title Kevin Corcoran assigned an issue to Kevin Corcoran Puppet / PUP-3511 Refactor Application.run() logic in core Ruby Puppet for external reuse Change By: Kevin Corcoran Assignee: KevinCorcoran Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilati
Title: Message Title Simon Crute commented on PDB-949 Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilation. I'm simon_c on IRC. I'm seeing this with a puppet master running puppet 3.7.3 under apache/passenger connected to puppetdb 2.2 with puppetdb-terminus 2.2. Interestingly, I haven't upgraded puppetdb-terminus on my other puppet master, and that is working correctly. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3271) Remove filebucket support for pson
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-3271 Remove filebucket support for pson Change By: Michael Smith Assignee: MichaelSmith Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3521) puppet incorrectly swallows some errors
Title: Message Title Preben Ingvaldsen assigned an issue to Preben Ingvaldsen Puppet / PUP-3521 puppet incorrectly swallows some errors Change By: Preben Ingvaldsen Assignee: PrebenIngvaldsen Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilati
Title: Message Title Joshua Partlow commented on PDB-949 Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilation. Another aspect of this I forgot to mention is that the Puppet[:trusted_node_data] setting needs to be true. I haven't seen this problem with an apache passenger instance yet, but then, trusted_node_data still defaults to false in foss. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilati
Title: Message Title Simon Crute commented on PDB-949 Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilation. I'm using trusted_node_data = true in puppet.conf $trusted[certname] in my site.pp Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3300) Rework Puppet::Util::Checksums to not extend itself
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-3300 Rework Puppet::Util::Checksums to not extend itself Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3653) Unable to create/force empty Windows groups
Title: Message Title
Chris Stephens created an issue
Puppet / PUP-3653
Unable to create/force empty Windows groups
Issue Type:
Bug
Affects Versions:
PUP 3.7.3
Assignee:
Aaron Armstrong
Components:
PE
Created:
2014/11/10 12:41 PM
Environment:
Windows 2008 R2, Windows 2012, Windows 2012 R2
Labels:
puppet-agent windows
Priority:
Normal
Reporter:
Chris Stephens
In Windows, many groups are built-in and cannot be removed, therefore 'ensure = absent' is useless. Another approach would be to define the group as present with no members. For example:
group { 'Guests': ensure = 'present', members = [], }
Unfortunately, this will not remove any members
Jira (PUP-1467) DIE :undef, DIE!
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1467 DIE :undef, DIE! Change By: Henrik Lindberg Story Points: 3 1 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1467) DIE :undef, DIE!
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1467 DIE :undef, DIE! Change By: Henrik Lindberg Story Points: 1 3 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3634) Security bug: User resource exposes hashed password when changing password or adding user
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3634 Security bug: User resource exposes hashed password when changing password or adding user Change By: Charlie Sharpsteen Affects Version/s: PUP3.7.3 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3634) Security bug: User resource exposes hashed password when changing password or adding user
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3634 Security bug: User resource exposes hashed password when changing password or adding user Change By: Charlie Sharpsteen Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3634) Security bug: User resource exposes hashed password when changing password or adding user
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3634 Security bug: User resource exposes hashed password when changing password or adding user Change By: Charlie Sharpsteen Labels: security type_user Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3637) Change store report processor to write report in JSON
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3637 Change store report processor to write report in JSON Change By: Charlie Sharpsteen Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-405) Remove ActiveRecord stored configs
Title: Message Title Steve Barlow updated an issue Puppet / PUP-405 Remove ActiveRecord stored configs Change By: Steve Barlow Sprint: SERVERnextcandidates3 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3634) Security bug: User resource exposes hashed password when changing password or adding user
Title: Message Title Charlie Sharpsteen commented on PUP-3634 Re: Security bug: User resource exposes hashed password when changing password or adding user Re-produced on current master branch: [root@poss-head-master ~]# puppet resource user test ensure=present password=foobar --debug Debug: Runtime environment: puppet_version=3.7.3, ruby_version=1.9.3, run_mode=user, default_encoding=UTF-8 Debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dsimport does not exist Debug: Failed to load library 'ldap' for feature 'ldap' Debug: Puppet::Type::User::ProviderLdap: feature ldap is missing Debug: Puppet::Type::User::ProviderPw: file pw does not exist Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist Debug: Loaded state in 0.00 seconds
Jira (PUP-3653) Unable to create/force empty Windows groups
Title: Message Title Josh Cooper commented on PUP-3653 Re: Unable to create/force empty Windows groups It should be possible to define the members of a group to be an empty list. Given the manifest above, puppet attempts to remove all existing members from the group as can be seen from the output below: Notice: /Stage[main]/Main/Group[Guests]/members: members changed 'WIN-QP47VOHA2P4\Guest' to '' However, the change doesn't seem to take effect for some reason, so puppet will try to reapply it every time it runs. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-405) Remove ActiveRecord stored configs
Title: Message Title Steve Barlow updated an issue Puppet / PUP-405 Remove ActiveRecord stored configs Change By: Steve Barlow Sprint: SERVERnextcandidates3 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3653) Unable to create/force empty Windows groups
Title: Message Title Aaron Armstrong updated an issue Puppet / PUP-3653 Unable to create/force empty Windows groups Change By: Aaron Armstrong Assignee: AaronArmstrong Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3554) Validate all of the forge modules using future parser
Title: Message Title Eric Sorenson commented on PUP-3554 Re: Validate all of the forge modules using future parser This seems like a huge amount of effort for a quickly-diminishing return on investment, more of a research/code archaeology project than something that would produce a bunch of actionable work. If we could scope it to top N that'd be better, but the top modules by any useful metric are also the most likely to work with the new stuff. Andy said he filed this on Deepak Giridharagopal's request – comment if you've got a different opinion, D, otherwise I'm closing as Won't Fix. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3288) Remove support for case-insensitive SSL file names
Title: Message Title Kylo Ginsberg commented on PUP-3288 Re: Remove support for case-insensitive SSL file names puppet-server will take this over, so closing this as won't fix. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3627) Remove ignore certdnsnames setting
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-3627 Remove ignore certdnsnames setting Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3271) Remove filebucket support for pson
Title: Message Title Michael Smith commented on PUP-3271 Re: Remove filebucket support for pson https://github.com/puppetlabs/puppet/blob/master/lib/puppet/network/format_support.rb#L91 defines an identical method. Do we have a ticket to remove it? https://github.com/puppetlabs/puppet/blob/master/lib/puppet/external/pson/pure/generator.rb#L199 also defines a to_pson method, but with different behavior. I can verify that the method no longer exists if I also comment out both of those to_pson definitions. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3271) Remove filebucket support for pson
Title: Message Title Michael Smith commented on PUP-3271 Re: Remove filebucket support for pson No externally accessible behavior to verify. I used irb puppet 'require'; Puppet::FileBucket::File.new(foo).to_pson to verify it. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3271) Remove filebucket support for pson
Title: Message Title Michael Smith assigned an issue to Kylo Ginsberg Puppet / PUP-3271 Remove filebucket support for pson Change By: Michael Smith Assignee: MichaelSmith KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3275) Remove from_pson
Title: Message Title Michael Smith commented on PUP-3275 Re: Remove from_pson No uses of from_pson exist, no external access to the method. FR looks good. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3271) Remove filebucket support for pson
Title: Message Title Kylo Ginsberg commented on PUP-3271 Re: Remove filebucket support for pson This was just about filebucket specifically. PUP-3540 will remove pson everywhere. (This ticket was created first, and IMHO this could have been closed once we create that one, but ... jira is too much fun!) Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3271) Remove filebucket support for pson
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet / PUP-3271 Remove filebucket support for pson Change By: Michael Smith Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3554) Validate all of the forge modules using future parser
Title: Message Title Deepak Giridharagopal commented on PUP-3554 Re: Validate all of the forge modules using future parser I'd be fine with scoping it to top N, but regardless I'd like to actually see the scope for this before we close it. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3627) Remove ignore certdnsnames setting
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-3627 Remove ignore certdnsnames setting Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3293) Removed unused pson and rubygems features
Title: Message Title Kylo Ginsberg commented on PUP-3293 Re: Removed unused pson and rubygems features This doesn't need FR, just orphaned code. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3463) Remove tagmail
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3463 Remove tagmail Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3472) make acceptance/tests/environment/directory.rb more atomic
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3472 make acceptance/tests/environment/directory.rb more atomic Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3511) Refactor Application.run() logic in core Ruby Puppet for external reuse
Title: Message Title
Kevin Corcoran updated an issue
Puppet / PUP-3511
Refactor Application.run() logic in core Ruby Puppet for external reuse
Change By:
Kevin Corcoran
FortheworkinPE-4355,someofthelogicfromthePuppet Inhttps : :Application //github . run()methodincoreRubyPuppet's... com / lib puppetlabs /puppet -server / application.rb pull/39,somecode wascopied intothe outof{{ Puppet:: JVM::Master Application . initialize()methodinJVM run}}into Puppet 'ssrc/ruby/jvm-puppet-lib/puppet/jvm/master Server . rb. Thisallowed JVM Puppet master Server topropagatethroughmodulepathsettingsfordirectoryenvironmentuselikethe coreRuby MRI Puppetmasterdoes.Itwouldbebetterforthislogictoberelocatedfromitscurrentlocationinthe coreRubyPuppet puppet codeintoahelpermethodthatcanbereusedbyboth theRubyPuppet puppet and JVM Puppet master Server .Ideallybysharingthiscode,anyfuturemaintenancewouldkeepthetwomastersinsync. ThisticketwilllikelyneedtobeseparatedintoaPUPticketforthecoreRubyPuppetworkvs.aPEticketfortheJVMPuppetwork.
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
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-3274) Remove old parser/evaluator
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3274 Remove old parser/evaluator Change By: Henrik Lindberg Sprint: PlatformServer2014-12-10 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1640) Provide agnostic mechanism for Hiera Based Data in Modules
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1640 Provide agnostic mechanism for Hiera Based Data in Modules Change By: Henrik Lindberg Sprint: PlatformServer2014-12-10 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3274) Remove old parser/evaluator
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-3274 Remove old parser/evaluator Change By: Henrik Lindberg Assignee: AndyParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2366) Replace hosts using Ruby 1.8.7 for Puppet 4.0 Acceptance
Title: Message Title Roger Ignazio assigned an issue to Roger Ignazio Puppet / PUP-2366 Replace hosts using Ruby 1.8.7 for Puppet 4.0 Acceptance Change By: Roger Ignazio Assignee: RogerIgnazio Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2366) Replace hosts using Ruby 1.8.7 for Puppet 4.0 Acceptance
Title: Message Title Roger Ignazio commented on PUP-2366 Re: Replace hosts using Ruby 1.8.7 for Puppet 4.0 Acceptance Removed rhel6, rhel5, centos5, lucid, precise, precise_and_lucid, and squeeze platforms from Puppet Package Acceptance, master branch. Also removed RHEL 6 from Puppet Acceptance Future Parser, master branch. PR opened (see links above) against Puppet master to bump the masters for Windows testing from EL 6 to EL 7. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-577) Efforts not currently approved for a release
Title: Message Title Kylo Ginsberg commented on PUP-577 Re: Efforts not currently approved for a release Jira scrub. The last PE 3.x release has shipped! So this epic can be retired. If the tickets become of interest again they will find new epic homes. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3036) Replace keywords `and` and `or` where they don't change semantics, using rubocop:Style/AndOr
Title: Message Title Kylo Ginsberg commented on PUP-3036 Re: Replace keywords `and` and `or` where they don't change semantics, using rubocop:Style/AndOr Jira scrub. Shutting down the original Static Analysis epic and marking this ticket Ready for Engineering. Redoing this should take into account the newer rubocop which has some improved logic around this/related cops. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3635) Add a scanf function for string to numeric conversion (and more)
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-3635 Add a scanf function for string to numeric conversion (and more) Change By: Hailee Kenney Assignee: HaileeKenney Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3641) Changes to Puppet URL structure
Title: Message Title Christopher Price updated an issue Puppet / PUP-3641 Changes to Puppet URL structure Change By: Christopher Price Sprint: SERVER nextcandidates3 2014-11-19 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3642) Remove environment name from URL path
Title: Message Title Christopher Price assigned an issue to Christopher Price Puppet / PUP-3642 Remove environment name from URL path Change By: Christopher Price Assignee: ChristopherPrice Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3642) Remove environment name from URL path
Title: Message Title Christopher Price updated an issue Puppet / PUP-3642 Remove environment name from URL path Change By: Christopher Price Sprint: SERVER nextcandidates3 2014-11-19 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3642) Remove environment name from URL path
Title: Message Title Christopher Price commented on PUP-3642 Re: Remove environment name from URL path I have an initial PR up for review. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3654) Deprecate Puppet::newtype
Title: Message Title William Hopper created an issue Puppet / PUP-3654 Deprecate Puppet::newtype Issue Type: Improvement Affects Versions: PUP 3.7.3 Assignee: William Hopper Created: 2014/11/10 4:09 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: William Hopper The newtype class method of the Puppet module includes a comment from 2011 stating that the method should be deprecated, but was under heavy use at the time: 150 # Create a new type. Just proxy to the Type class. The mirroring query 151 # code was deprecated in 2008, but this is still in heavy use. I suppose
Jira (PUP-3654) Deprecate Puppet.newtype
Title: Message Title William Hopper updated an issue Puppet / PUP-3654 Deprecate Puppet.newtype Change By: William Hopper Summary: DeprecatePuppet :: . newtype Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3036) Replace keywords `and` and `or` where they don't change semantics, using rubocop:Style/AndOr
Title: Message Title Henrik Lindberg commented on PUP-3036 Re: Replace keywords `and` and `or` where they don't change semantics, using rubocop:Style/AndOr This should wait until after the code removal phase. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3635) Add a scanf function for string to numeric conversion (and more)
Title: Message Title Hailee Kenney commented on PUP-3635 Re: Add a scanf function for string to numeric conversion (and more) Merged into stable in 1d8f7e3e6 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1011) Create execute query as a PuppetDBServer service function
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-1011 Create execute query as a PuppetDBServer service function Change By: Ryan Senior Assignee: RyanSenior Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3481) Regex problem with an SELinux context type with a dash
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3481 Regex problem with an SELinux context type with a dash Change By: Josh Cooper Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3446) CertificateError when running tests with OpenSSL = 1.0.1i
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3446 CertificateError when running tests with OpenSSL = 1.0.1i Change By: Josh Cooper Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3446) CertificateError when running tests with OpenSSL = 1.0.1i
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3446 CertificateError when running tests with OpenSSL = 1.0.1i Change By: Josh Cooper Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3481) Regex problem with an SELinux context type with a dash
Title: Message Title Josh Cooper commented on PUP-3481 Re: Regex problem with an SELinux context type with a dash Jude N We had some comments on the PR, I'm assigning this ticket back to you to resolve. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3481) Regex problem with an SELinux context type with a dash
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3481 Regex problem with an SELinux context type with a dash Change By: Josh Cooper Assignee: JudeN Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
