Jira (PUP-292) Mount type `atboot` property validation is too restrictive in 3.3.0rcX
Title: Message Title Raoul Bhatia commented on PUP-292 Re: Mount type `atboot` property validation is too restrictive in 3.3.0rcX is atboot even doing something? For me, it seems it does not ... 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-3628) mount's atboot property not used
Title: Message Title
Raoul Bhatia created an issue
Puppet / PUP-3628
mount's atboot property not used
Issue Type:
Bug
Affects Versions:
PUP 3.6.1
Assignee:
Unassigned
Created:
2014/11/06 1:58 AM
Priority:
Normal
Reporter:
Raoul Bhatia
It seems that the atboot property of the mount type is not honored correctly, at least on my Linux machine.
Sample .pp:
mount { 'mountNFS': name = '/mnt', ensure = present, atboot = no, device = 127.0.0.1:/data/nfs/export, options = 'retrans=5,timeo=14,intr,tcp,_netdev', pass = 0, dump = 0, remounts = true, fstype = 'nfs', tag = 'nfsmount', }
Expected result in /etc/fstab: 127.0.0.1:/data/nfs/export /mnt nfs retrans=5,timeo=14,intr,tcp,_netdev,noauto 0 0
Actual result: 127.0.0.1:/data/nfs/export /mnt nfs retrans=5,timeo=14,intr,tcp,_netdev 0 0
Am I doing something wrong or is there any specific reason why this is not working?
Thanks, Raoul
Jira (PUP-3628) mount's atboot property not used
Title: Message Title
Raoul Bhatia updated an issue
Puppet / PUP-3628
mount's atboot property not used
Change By:
Raoul Bhatia
Itseemsthattheatbootpropertyofthemounttypeisnothonoredcorrectly,atleastonmyLinuxmachine.Sample nfsmount .pp: {{ mount{'mountNFS':name='/mnt',ensure=present,atboot=no,device=127.0.0.1:/data/nfs/export,options='retrans=5,timeo=14,intr,tcp,_netdev',pass=0,dump=0,remounts=true,fstype='nfs',tag='nfsmount',} }} Expectedresultin/etc/fstab: {{ 127.0.0.1:/data/nfs/export /mnt nfs retrans=5,timeo=14,intr,tcp,_netdev,noauto 0 0 }} Actualresult: {{ 127.0.0.1:/data/nfs/export /mnt nfs retrans=5,timeo=14,intr,tcp,_netdev 0 0 }} AmIdoingsomethingwrongoristhereanyspecificreasonwhythisisnotworking?Thanks,Raoul
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-3628) mount's atboot property not used
Title: Message Title
Raoul Bhatia updated an issue
Puppet / PUP-3628
mount's atboot property not used
Change By:
Raoul Bhatia
Itseemsthattheatbootpropertyofthemounttypeisnothonoredcorrectly,atleastonmyLinuxmachine.Samplenfsmount.pp:{ { quote} mount{'mountNFS':name='/mnt',ensure=present,atboot=no,device=127.0.0.1:/data/nfs/export,options='retrans=5,timeo=14,intr,tcp,_netdev',pass=0,dump=0,remounts=true,fstype='nfs',tag='nfsmount',} {quote } } Expectedresultin/etc/fstab:{ { quote} 127.0.0.1:/data/nfs/export /mnt nfs retrans=5,timeo=14,intr,tcp,_netdev,noauto 0 0 {quote } } Actualresult:{ { quote} 127.0.0.1:/data/nfs/export /mnt nfs retrans=5,timeo=14,intr,tcp,_netdev 0 0 {quote } } AmIdoingsomethingwrongoristhereanyspecificreasonwhythisisnotworking?Thanks,Raoul
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-3628) mount's atboot property not used
Title: Message Title
Raoul Bhatia updated an issue
Puppet / PUP-3628
mount's atboot property not used
Change By:
Raoul Bhatia
Itseemsthattheatbootpropertyofthemounttypeisnothonoredcorrectly,atleastonmyLinuxmachine.Samplenfsmount.pp:{ quote noformat }mount{'mountNFS':name='/mnt',ensure=present,atboot=no,device=127.0.0.1:/data/nfs/export,options='retrans=5,timeo=14,intr,tcp,_netdev',pass=0,dump=0,remounts=true,fstype='nfs',tag='nfsmount',}{ quote noformat }Expectedresultin/etc/fstab:{quote}127.0.0.1:/data/nfs/export /mnt nfs retrans=5,timeo=14,intr,tcp,_netdev,noauto 0 0{quote}Actualresult:{quote}127.0.0.1:/data/nfs/export /mnt nfs retrans=5,timeo=14,intr,tcp,_netdev 0 0{quote}AmIdoingsomethingwrongoristhereanyspecificreasonwhythisisnotworking?Thanks,Raoul
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-3628) mount's atboot property not used
Title: Message Title
Raoul Bhatia updated an issue
Puppet / PUP-3628
mount's atboot property not used
Change By:
Raoul Bhatia
Itseemsthattheatbootpropertyofthemounttypeisnothonoredcorrectly,atleastonmyLinuxmachine.Samplenfsmount.pp:{noformat}mount{'mountNFS':name='/mnt',ensure=present,atboot=no,device=127.0.0.1:/data/nfs/export,options='retrans=5,timeo=14,intr,tcp,_netdev',pass=0,dump=0,remounts=true,fstype='nfs',tag='nfsmount',}{noformat}Expectedresultin/etc/fstab:{noformat}127.0.0.1:/data/nfs/export /mnt nfs retrans=5,timeo=14,intr,tcp,_netdev, b noauto /b 0 0{noformat}Actualresult:{noformat}127.0.0.1:/data/nfs/export /mnt nfs retrans=5,timeo=14,intr,tcp,_netdev 0 0{noformat}AmIdoingsomethingwrongoristhereanyspecificreasonwhythisisnotworking?Thanks,Raoul
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-3628) mount's atboot property not used
Title: Message Title
Raoul Bhatia updated an issue
Puppet / PUP-3628
mount's atboot property not used
Change By:
Raoul Bhatia
Itseemsthattheatbootpropertyofthemounttypeisnothonoredcorrectly,atleastonmyLinuxmachine.Samplenfsmount.pp:{noformat}mount{'mountNFS':name='/mnt',ensure=present,atboot=no,device=127.0.0.1:/data/nfs/export,options='retrans=5,timeo=14,intr,tcp,_netdev',pass=0,dump=0,remounts=true,fstype='nfs',tag='nfsmount',}{noformat}Expectedresultin/etc/fstab:{ quote noformat }127.0.0.1:/data/nfs/export /mnt nfs retrans=5,timeo=14,intr,tcp,_netdev,noauto 0 0{ quote noformat }Actualresult:{ quote noformat }127.0.0.1:/data/nfs/export /mnt nfs retrans=5,timeo=14,intr,tcp,_netdev 0 0{ quote noformat }AmIdoingsomethingwrongoristhereanyspecificreasonwhythisisnotworking?Thanks,Raoul
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-3628) mount's atboot property not used
Title: Message Title
Raoul Bhatia updated an issue
Puppet / PUP-3628
mount's atboot property not used
Change By:
Raoul Bhatia
Itseemsthattheatbootpropertyofthemounttypeisnothonoredcorrectly,atleastonmyLinuxmachine.Samplenfsmount.pp:{noformat}mount{'mountNFS':name='/mnt',ensure=present,atboot=no,device=127.0.0.1:/data/nfs/export,options='retrans=5,timeo=14,intr,tcp,_netdev',pass=0,dump=0,remounts=true,fstype='nfs',tag='nfsmount',}{noformat}Expectedresultin/etc/fstab ,including*noauto* :{noformat}127.0.0.1:/data/nfs/export /mnt nfs retrans=5,timeo=14,intr,tcp,_netdev, b noauto /b 0 0{noformat}Actualresult ,without*noauto* :{noformat}127.0.0.1:/data/nfs/export /mnt nfs retrans=5,timeo=14,intr,tcp,_netdev 0 0{noformat}AmIdoingsomethingwrongoristhereanyspecificreasonwhythisisnotworking?Thanks,Raoul
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-2782) Yumrepo target attribute does not work
Title: Message Title Tim Meusel updated an issue Puppet / PUP-2782 Yumrepo target attribute does not work Change By: Tim Meusel 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-2782) Yumrepo target attribute does not work
Title: Message Title Tim Meusel commented on PUP-2782 Re: Yumrepo target attribute does not work we had a little discussion in the IRC about this issue. Somebody (maybe Hunter?) mentioned to remove the yumrepo type from the puppet core and put it into an own module as this would be easier as fixing the code. Any thoughts on 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-3550) Issue with manually issuing manually submitting certificate request over API
Title: Message Title Viktor Petersson commented on PUP-3550 Re: Issue with manually issuing manually submitting certificate request over API Grr, so it turns out that it was literally one character that messed it all up. It should be: curl -s -k -X PUT -H Content-Type: text/plain --data-binary @test10.foobar.local.csr https://puppet.foobar.local:8140/production/certificate_request/$1 Instead of: curl -s -k -X PUT -H Content-Type: text/plain --data-binary test10.foobar.local.csr https://puppet.foobar.local:8140/production/certificate_request/$1 Thanks a lot for your work on this. It just turns out that I was an idiot. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PDB-950) PuppetDB returns 500 error as HTML when query contains invalid regex
Title: Message Title Kenneth Barber commented on PDB-950 Re: PuppetDB returns 500 error as HTML when query contains invalid regex Looks like we have a PR actually, not sure if thats what you meant Lindsey Smith PO? https://github.com/puppetlabs/puppetdb/pull/1142 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-1017) Node tests broken due to bug in assertion code
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-1017 Node tests broken due to bug in assertion code Issue Type: Bug Assignee: Unassigned Created: 2014/11/06 4:53 AM Priority: Normal Reporter: Ryan Senior While looking into another issue, I found two issues related to our node-query tests, specifically here: https://github.com/puppetlabs/puppetdb/blob/master/test/puppetlabs/puppetdb/http/nodes_test.clj#L65. There are tests in that namespace that actually generate incorrect SQL, I see a stacktrace in standard error, but the error isn't returned and PuppetDB is actually responding with a 200 and an empty body. The empty body causes the doseq above to be skipped, and since the response is 200, the test runs successfully, even though there was a failure and no results were returned. We should also look into our bad handling of this failed query. Ideally it should be returning a 4xx error, but certainly shouldn't return a 200. Add Comment
Jira (PDB-1017) Node tests broken due to bug in assertion code
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1017 Node tests broken due to bug in assertion code Change By: Ryan Senior Sprint: PuppetDB2014-12-03 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-3612) Ubuntu 14.04 vagrant box
Title: Message Title John Cooper commented on PUP-3612 Re: Ubuntu 14.04 vagrant box Might want to update all the beaker docs as well. On 5 November 2014 17:26, Scott Schneider (JIRA) – John Cooper - Web Systems Administrator/Developer IT Services, Information Directorate University of York http://www.york.ac.uk/docs/disclaimer/email.htm 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 Erik Daln commented on PUP-3274 Re: Remove old parser/evaluator As an example of existing third party functions using lambdas: https://github.com/dalen/puppet-defn I'll fix them to use the new syntax of course, but might be worth mentioning in release notes anyway. 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-3629) Add a timeout metaparameter
Title: Message Title Ryan DeShone created an issue Puppet / PUP-3629 Add a timeout metaparameter Issue Type: New Feature Assignee: Unassigned Created: 2014/11/06 6:21 AM Priority: Normal Reporter: Ryan DeShone I recently encountered an issue where a rogue yum process had failed to finish and was holding open the rpm db lock. This was causing puppet to hang on the server, as the package resources could not obtain the lock and yum just loops forever trying to obtain it until manually interrupted (poor design on their part, but still, it is what it is). This got me to thinking, it would be helpful if we could set a timeout on individual resources, in case we have a resource that sometimes hangs for whatever reason. If the resource is unable to complete in the allotted time, puppet should give up on it and report an error for that resource. Add Comment
Jira (PUP-3550) Issue with manually issuing manually submitting certificate request over API
Title: Message Title Viktor Petersson commented on PUP-3550 Re: Issue with manually issuing manually submitting certificate request over API Haha, great. So I did actually run into a semi-related issue. Once I've managed to submit the CSR etc, I still cannot run a regular Puppet run. I do see the cert submitted and approved on the server, but the agent tells me to clean the certificate on the server and client. I'm thinking that this might have something to do with the CA (or something similar). Do I need to copy in any certificates from the server to the box generating the certificates for this to work? 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-1486) The resources type should be more generic
Title: Message Title Henrik Lindberg commented on PUP-1486 Re: The resources type should be more generic A thread was started on puppet-dev to discuss ideas for this. 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-1018) PR (151): (maint) Correct path for hsqldb storage - kbarber
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1018 PR (151): (maint) Correct path for hsqldb storage - kbarber Issue Type: Task Assignee: Unassigned Created: 2014/11/06 8:09 AM Labels: github module Priority: Normal Reporter: gepetto-bot (maint) Correct path for hsqldb storage Author: Ken Barber k...@bob.sh Company: Puppet Labs Inc. Github ID: kbarber Pull Request 151 Discussion Pull Request 151 File Diff Pull Request Description For some reasons we switched this to use /usr/share/puppetdb/db, which has a softlink to /var/lib/puppetdb/db. This is not aligned with the PuppetDB core nor is it following FHS. Signed-off-by: Ken Barber
Jira (PUP-3612) Ubuntu 14.04 vagrant box
Title: Message Title Charlie Sharpsteen commented on PUP-3612 Re: Ubuntu 14.04 vagrant box John Cooper: Good idea, I've filed puppetlabs/beaker#528 for 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 (PDB-1018) PR (151): (maint) Correct path for hsqldb storage - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1018 PR (151): (maint) Correct path for hsqldb storage - kbarber Change By: Kenneth Barber Sprint: PuppetDB2014-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 (PDB-1018) PR (151): (maint) Correct path for hsqldb storage - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1018 PR (151): (maint) Correct path for hsqldb storage - kbarber Change By: Kenneth Barber Affects Version/s: module-4.0.0 Assignee: KennethBarber Story Points: 0 Fix Version/s: module-4.1.0 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-3547) File Server Mounts Should Support Directory Environments
Title: Message Title Joshua M. Keyes commented on PUP-3547 Re: File Server Mounts Should Support Directory Environments I guess I'll need to roll up my sleeves and learn some Clojure. 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 William Hopper commented on PUP-3627 Re: Remove ignore certdnsnames setting Merged at bb84599ff 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-3613) Add a parameter to the exec resource to support running commands in software collections without always using scl enable
Title: Message Title Charlie Sharpsteen commented on PUP-3613 Re: Add a parameter to the exec resource to support running commands in software collections without always using scl enable This would require a non-trivial amount of build out in code, tests, debugging info, etc. to support a RHEL-specific option for a very universal and heavily-used type. There would be ongoing costs in terms of bugs and manintenance. I'm not convinced there is a good trade-off in favor of this feature given that this use case is supported by pre-pending three words, scl enable foo, to a command. Four a large numbers of commands, the overhead of setting and updating this could be reduced by using variables. As a user and debugger of puppet code, I'd rather see this context explicitly inline with the command rather than having to hunt through manuals and resource defaults in order to figure out what is getting run. Any use cases that would justify the cost and complexity of implementing this? 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-1012) Fix up tests for rspec against master
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1012 Fix up tests for rspec against master Change By: Wyatt Alt Assignee: WyattAlt 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-3604) Puppet fails to install correct package when 'ensure = $version' is set
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3604 Puppet fails to install correct package when 'ensure = $version' is set Change By: Adrien Thebo Story Points: 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-3388) Issue Creating Multiple Mirrors in Zpool Resource
Title: Message Title Josh Cooper commented on PUP-3388 Re: Issue Creating Multiple Mirrors in Zpool Resource It looks like puppet is executing: zpool create data mirror disk1 disk2 disk3 disk4 Instead of: zpool create data mirror disk1 disk2 mirror disk3 disk4 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
Jira (PUP-3624) Running with --test should run with at least info level
Title: Message Title Josh Cooper commented on PUP-3624 Re: Running with --test should run with at least info level From Erik Daln, make sure this works for both agent and apply 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-3388) Issue Creating Multiple Mirrors in Zpool Resource
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3388 Issue Creating Multiple Mirrors in Zpool Resource Change By: Josh Cooper Assignee: KyloGinsberg AdamPapotto 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-3547) File Server Mounts Should Support Directory Environments
Title: Message Title Josh Cooper commented on PUP-3547 Re: File Server Mounts Should Support Directory Environments Joshua M. Keyes, Felix Frank so about the PR and ticket... it sounds like we should close the PR, and either close this ticket, or move it to the SERVER project, with discussion on `puppet-dev`. Sound 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-3560) Add support for properly signed trusted facts
Title: Message Title Justin May assigned an issue to Justin May Puppet / PUP-3560 Add support for properly signed trusted facts Change By: Justin May Assignee: JustinMay 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-3568) module skeleton should use puppet-lint v1
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3568 module skeleton should use puppet-lint v1 Change By: Josh Cooper Assignee: garretthoneycutt 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-3569) module skeleton should not require rubygems
Title: Message Title Josh Cooper assigned an issue to garrett honeycutt Puppet / PUP-3569 module skeleton should not require rubygems Change By: Josh Cooper Assignee: garretthoneycutt 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-1805) Drop Ruby 1.8.7 support
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1805 Drop Ruby 1.8.7 support Change By: Kylo Ginsberg Epic Name: Deprecate Remove Ruby1.8.7 Support 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-3604) Puppet fails to install correct package when 'ensure = $version' is set
Title: Message Title Adrien Thebo commented on PUP-3604 Re: Puppet fails to install correct package when 'ensure = $version' is set Merged in a63f843. 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-950) PuppetDB returns 500 error as HTML when query contains invalid regex
Title: Message Title Lindsey Smith PO commented on PDB-950 Re: PuppetDB returns 500 error as HTML when query contains invalid regex Thanks for the update Kenneth Barber. What trigger the comment was more learning that the PDB wasn't planning to do 2.x release in the near future, which would mean we wouldn't be able to get this into a PE 3.7.x unless went some route like cherrypicking a fix, etc. 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-950) PuppetDB returns 500 error as HTML when query contains invalid regex
Title: Message Title Lindsey Smith PO commented on PDB-950 Re: PuppetDB returns 500 error as HTML when query contains invalid regex In any case, it's good that there's already a PR. Who would need to be involved with getting this into PE? 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-950) PuppetDB returns 500 error as HTML when query contains invalid regex
Title: Message Title Kenneth Barber commented on PDB-950 Re: PuppetDB returns 500 error as HTML when query contains invalid regex Lindsey Smith PO we haven't expressed to anyone that we won't ship a 2.2.x, FYI. I'm not sure where you heard that . We are totally open to doing that. I would imagine this is a bug fix of a kind, so a 2.2.3 (and thus a 3.7.1) is not out of the question if its needed. FYI we plan every second Wednesday, this is when we discuss priorities, this is your best bet for getting any votes into what we work on, as opposed to commenting on particular tickets - ie. this doesn't feed into our operational priority list generally. Alternatively you can proxy these through Steve Barlow who is our project manager. Point being, we get priorities from everywhere, and we have 3 product managers involved in our day to day which is crazy ... and yet no decent funnel beyond ourselves . 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-950) PuppetDB returns 500 error as HTML when query contains invalid regex
Title: Message Title Steve Barlow commented on PDB-950 Re: PuppetDB returns 500 error as HTML when query contains invalid regex Kenneth Barber Lindsey Smith Any confusion here is my fault. I was talking to Lindsey about Releases, and what I was trying to say that as of the moment there were no specific plans for a 2.2.x, and assuming nothing came in the change that like bugs or fix requests I did not think there would be one. I did not mean to imply that if business reasons came up that caused us to reevaluate that we would not do it. Sorry for adding to confusion and I hope this makes sense now. If not, poke me again. 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-3630) Odd behavior with noop
Title: Message Title Jay Wallace created an issue Puppet / PUP-3630 Odd behavior with noop Issue Type: Bug Assignee: Unassigned Created: 2014/11/06 12:48 PM Labels: support Priority: Normal Reporter: Jay Wallace This behavior is really quirky. It seems if a defined type is restructured to include the noop parameter, you get the expected behavior described initially in the ticket (ie a noop overwrite). Without restructuring the defined type, noop = false will not take precedence over what is set in let's say site.pp. This could be due to an issue with the way noop is being inherited by the resources with the defined type. I am using inherited pretty loosely here, as this isn't actually the way this works. Further investigation needed, please feel free to either escalate or open a bug with my last update. Add Comment
Jira (PUP-3630) Odd behavior with noop
Title: Message Title Lee Lowder updated an issue Puppet / PUP-3630 Odd behavior with noop Change By: Lee Lowder Thisbehaviorisreallyquirky.Itseemsifadefinedtypeisrestructuredtoincludethenoopparameter,yougettheexpectedbehaviordescribedinitiallyintheticket(ieanoopoverwrite).Withoutrestructuringthedefinedtype,noop=falsewillnottakeprecedenceoverwhatissetinlet'ssaysite.pp.Thiscouldbeduetoanissuewiththewaynoopisbeinginheritedbytheresourceswiththedefinedtype.Iamusinginheritedprettylooselyhere,asthisisn'tactuallythewaythisworks. Furtherinvestigationneeded,pleasefeelfreetoeitherescalateoropenabugwithmylastupdate. 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-3388) Issue Creating Multiple Mirrors in Zpool Resource
Title: Message Title Adam Papotto commented on PUP-3388 Re: Issue Creating Multiple Mirrors in Zpool Resource https://github.com/puppetlabs/puppet/pull/3282 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 William Hopper assigned an issue to William Hopper Puppet / PUP-3293 Removed unused pson and rubygems features Change By: William Hopper Assignee: WilliamHopper 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 William Hopper updated an issue Puppet / PUP-3293 Removed unused pson and rubygems features Change By: William Hopper Sprint: PlatformClient2014-11-12 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-3147) New gid fact is causing problems in one of my defined types
Title: Message Title Nick Lewis commented on PUP-3147 Re: New gid fact is causing problems in one of my defined types Reopening as this still seems like incorrect behavior, despite having a workaround. 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-3631) NIM provider uses a regex that is too restrictive when parsing RPM release tags
Title: Message Title Kaitlin Carter created an issue Puppet / PUP-3631 NIM provider uses a regex that is too restrictive when parsing RPM release tags Issue Type: Improvement Assignee: Unassigned Created: 2014/11/06 2:53 PM Labels: support Priority: Normal Reporter: Kaitlin Carter The NIM provider uses a regex that is too restrictive when parsing RPM release tags, it only allows numbers. For example if a package has a security release that includes letters it will fail to recognize it as a valid package name. The package wget-1.9.1-2ssl gives the error: Unable to parse output from nimclient showres: package string does not match expected rpm package string format Add Comment
Jira (PUP-3312) Remove deprecated code from the Puppet module
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-3312 Remove deprecated code from the Puppet module Change By: William Hopper Assignee: WilliamHopper 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-3312) Remove deprecated code from the Puppet module
Title: Message Title William Hopper updated an issue Puppet / PUP-3312 Remove deprecated code from the Puppet module Change By: William Hopper Sprint: PlatformClient2014-11-12 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-1974) Mechanism for securing sensitive catalog data
Title: Message Title Chris Barker updated an issue Puppet / PUP-1974 Mechanism for securing sensitive catalog data Change By: Chris Barker Labels: tse 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-3632) Update paths and defaults for the unified FS layout
Title: Message Title Matthaus Owens created an issue Puppet / PUP-3632 Update paths and defaults for the unified FS layout Issue Type: Task Assignee: Unassigned Created: 2014/11/06 3:13 PM Priority: Normal Reporter: Matthaus Owens The coming update to the FS layout for our projects requires several changes to default pathing and config files to ensure that the correct directories are used. Off the top of my head this includes defaults.rb and puppet.conf but it may extend into other files as well. The new layout is described here: https://confluence.puppetlabs.com/display/DEL/Unified+Puppet+Agent+Layout Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (FACT-753) Update FS layout for Facter
Title: Message Title Matthaus Owens created an issue Facter / FACT-753 Update FS layout for Facter Issue Type: Task Assignee: Eric Sorenson Created: 2014/11/06 3:14 PM Priority: Normal Reporter: Matthaus Owens The coming update to the FS layout for our projects requires several changes to default pathing and config files to ensure that the correct directories are used. Off the top of my head this includes external facts for facter. The new layout is described here: https://confluence.puppetlabs.com/display/DEL/Unified+Puppet+Agent+Layout Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-298) Update FS layout for hiera
Title: Message Title Matthaus Owens created an issue Hiera / HI-298 Update FS layout for hiera Issue Type: Task Assignee: Unassigned Created: 2014/11/06 3:16 PM Priority: Normal Reporter: Matthaus Owens The coming update to the FS layout for our projects requires several changes to default pathing and config files to ensure that the correct directories are used. Off the top of my head this includes default datadir for hiera data. The new layout is described here: https://confluence.puppetlabs.com/display/DEL/Unified+Puppet+Agent+Layout Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PUP-3632) Update paths and defaults for the unified FS layout
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: Matthaus Owens ThecomingupdatetotheFSlayoutforourprojectsrequiresseveralchangestodefaultpathingandconfigfilestoensurethatthecorrectdirectoriesareused.Offthetopofmyheadthisincludesdefaults.rbandpuppet.confbutitmayextendintootherfilesaswell. Defaultloggingisprobablyalsoaffected. Thenewlayoutisdescribedhere:https://confluence.puppetlabs.com/display/DEL/Unified+Puppet+Agent+Layout 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-1019) unending retry when postgres is inaccessible on PDB startup
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1019 unending retry when postgres is inaccessible on PDB startup Issue Type: Bug Affects Versions: 2.2.2 Assignee: Unassigned Created: 2014/11/06 3:51 PM Priority: Normal Reporter: Wyatt Alt If I change my subname to subname = //localhost:5431/puppetdb and start PuppetDB, BoneCP will start throwing these messages: 2014-11-06 15:39:03,159 ERROR [BoneCP-pool-watch-thread] [c.j.b.h.AbstractConnectionHook] Failed to acquire connection Sleeping for 7000ms and trying again. Attempts left: 5. Exception: java.net.ConnectException: Connection refused
Jira (PUP-3633) passenger runs as user apache instead of puppet
Title: Message Title Eric Thompson created an issue Puppet / PUP-3633 passenger runs as user apache instead of puppet Issue Type: Bug Assignee: Unassigned Created: 2014/11/06 3:57 PM Priority: Normal Reporter: Eric Thompson Investigate if this is an issue. for instance: directory environments are typically owned by puppet. when passenger tries to modify them as the apache user, strange things can happen see: acceptance/tests/environment/directory_environment_production_created_master.rb Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PUP-3633) passenger runs as user apache instead of puppet
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3633 passenger runs as user apache instead of puppet Change By: Eric Thompson Priority: Normal Minor 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-3633) passenger runs as user apache instead of puppet
Title: Message Title Eric Thompson commented on PUP-3633 Re: passenger runs as user apache instead of puppet hmmm. this may have been a false alarm. might be worth looking into anyway. 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 Abe Singer created an issue Puppet / PUP-3634 Security bug: User resource exposes hashed password when changing password or adding user Issue Type: Bug Affects Versions: PUP 2.7.23 Assignee: Unassigned Created: 2014/11/06 5:22 PM Environment: Debian Wheezy Labels: security Priority: Normal Reporter: Abe Singer The User resource, when creating a user or changing the user's password, apparently passes the password hash to useradd on the command line, using the -p argument. That is a well known security vulnerability and is even noted in the manpage for useradd. The hash is visible to any user via ps, while the command is running. A big no-no on any multi-user system. Documentation provided below. The proper way to set the password is to pipe it via stdin, or use some secure means of modifying /etc/shadow. I discovered this by accident because I had a typo in the manifest. As a result, I got this error
Jira (PUP-2733) Puppet squats on the PuppetX::Puppetlabs and PuppetX::Puppet namespaces
Title: Message Title Henrik Lindberg commented on PUP-2733 Re: Puppet squats on the PuppetX::Puppetlabs and PuppetX::Puppet namespaces Marked as blocked by PUP-2965 since it squatted on the name Puppet::Plugins 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-2906) Reimplement Collection without 3x AST
Title: Message Title Henrik Lindberg assigned an issue to Hailee Kenney Puppet / PUP-2906 Reimplement Collection without 3x AST Change By: Henrik Lindberg 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-3635) Add a scanf function for string to numeric conversion (and more)
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-3635 Add a scanf function for string to numeric conversion (and more) Issue Type: New Feature Assignee: Andy Parker Components: DSL Created: 2014/11/06 5:44 PM Fix Versions: PUP 3.7.4 Priority: Normal Reporter: Henrik Lindberg Ruby has support for scanf on String and we are already using sprintf to convert to string with formatting support. Therefore, adding support for the scanf function is a natural choice (also see PUP-3615). We need this function as there is no other function/mechanism that converts strings to numbers. It will also make it easier to handle conversion of strings that contains additional text e.g. 32.3 sec, or multiple values without having to recreate the regular expressions that match numbers (which is quit complex).
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Luke Kanies commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' Eric Sorenson Does this show up anywhere in our plans? Seems like there's a lot of interest. For those who are watching, do you have a clear idea of how you want this to work? 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-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title
Spencer Krum commented on PUP-1054
Re: Services should support 'reload' in addition to 'restart'
This can be pretty easily worked around by:
file { /etc/config: ensure = present }
~ service { 'myservice': ensure = running, restart = '/usr/bin/apachectl reload', #or something like that }
This should probably be better documented/publicized though. I used to think that this ticket was a huge problem. I've kind of gotten over that. Its seductive to say that we should add a reload parameter to the service type. I think it will lead us into having more and more parameters to the service type (reload, graceful_reload, close_all_connections_and_turn_off, give_me_a_pony, and so on). I also think we will quickly end up with two services who define the word 'reload' and/or 'graceful reload' differently.
So what do I think should be done? I think the workaround of overloading the restart parameter should be exercised. Are there places it doesn't work? Where are those places? If we change Puppet we should make sure we don't leave those cases out in the cold.
To go a bit further, this makes me wonder if notify/subscribe should be extended. I'm not sure exactly what that would look like. But right now notify/subscribe is 'You should restart.' I think what I'm suggesting is a richer language for resources to interact. A file resource could notify the service resource with 'refresh' or with 'restart.' I'm usually pretty weary of adding complexity, but I can imagine types and providers writing handlers for arbitrary events, and that could enable some super cool behaviors in puppet.
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
Jira (PUP-1244) Yum provider using version-release to validate installation.
Title: Message Title Kylo Ginsberg commented on PUP-1244 Re: Yum provider using version-release to validate installation. Yeah there was a ton of review of this along the way. Resolving. 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-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Patrick Hemmer commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' There's a significant problem with your solution. Lets say you upgrade apache. How are you going to restart 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-3636) Converting from config environments should be less confusing
Title: Message Title Luke Kanies created an issue Puppet / PUP-3636 Converting from config environments should be less confusing Issue Type: Bug Assignee: Eric Sorenson Created: 2014/11/06 8:20 PM Priority: Normal Reporter: Luke Kanies Trying to follow the path of deprecation warnings from a puppet.conf that specifies modulepath and manifest to one that uses directory environments is quite confusing. The link given by the warning: http://links.puppetlabs.com/env-settings-deprecations points to the old configuration instead of a page about how to convert. Yes, that page has deprecation warnings, but this doesn't make sense. The link should point to the new configuration, with some migration information. Then, when you follow the link to the new page, it doesn't talk about the actual parameters you have to convert. The page is here: https://docs.puppetlabs.com/puppet/latest/reference/environments.html And there's no mention at all of 'manifest' or 'modulepath' on this page. These deprecation warnings need a clear path of migration - not a link to more detail on the deprecation, but a link to detail on how to make the warning go away. If I'm using 'manifest' and 'modulepath' to override these values right now (which I am, in my home directory, when running Puppet as myself on my laptop), how do I convert to directory environments? Note that I'm not actually using environments at all, I just want a custom value for these variables. How do I make these warnings go away? Where is that clearly documented?
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title
Colin Alston commented on PUP-1054
Re: Services should support 'reload' in addition to 'restart'
Some things like Postgres need restart under different conditions. Eg a nicer thing to do might be
service {'postgresql': ensure = running}
file {'/etc/postgresql/postgresql.conf': notify = Service['postgresql'] }
file {'/etc/postgresql/pg_hba.conf': reload = Service['postgresql'] }
You need control over /when/ you reload, not replacing the entire restart command.
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.
