Jira (PUP-1963) Generated resources never receive dependency edges
Title: Message Title Matt Palmer commented on an issue Re: Generated resources never receive dependency edges This is trivially fixed by adding the relationship edges to the relationship graph in `Puppet::Transaction::AdditionalResourceGenerator#add_resource`, in exactly the same way that `Puppet::Graph::RelationshipGraph#build_manual_dependencies` does it. I've patched my local implementation in this fashion, and it resolves the bug quite satisfactorily. Add Comment Puppet / PUP-1963 Generated resources never receive dependency edges First off I will quickly explain what it is I'm trying to do. I have installed the puppetlabs-apache-0.0.3 module that provides a new type called a2mod. My goal is to use virtual resources to collect a list of modules to enable/disable on a node. I would also however, like to ensure that all other apache modules are disabled on the system. I found the... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegrou
Jira (PDB-821) How do we simplify searching across fact-nodes, using a subquery from facts
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-821 How do we simplify searching across fact-nodes, using a subquery from facts Change By: Kenneth Barber Assignee: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-229) User provider password_max_age attribute is flawed under Solaris
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-229 User provider password_max_age attribute is flawed under Solaris Change By: Kylo Ginsberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-229) User provider password_max_age attribute is flawed under Solaris
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-229 User provider password_max_age attribute is flawed under Solaris Change By: Kylo Ginsberg Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-229) User provider password_max_age attribute is flawed under Solaris
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-229 User provider password_max_age attribute is flawed under Solaris Change By: Kylo Ginsberg Sprint: 2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-229) User provider password_max_age attribute is flawed under Solaris
Title: Message Title Rahul Gopinath assigned an issue to Rahul Gopinath Puppet / PUP-229 User provider password_max_age attribute is flawed under Solaris Change By: Rahul Gopinath Assignee: Rahul Gopinath Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-820) Consider doing something with the *> operator, its functionality overlaps with ~>
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-820 Consider doing something with the *> operator, its functionality overlaps with ~> Change By: Kenneth Barber Assignee: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-828) PR (1047): (QENG-1071) debian ec2 /etc/init.d/ec2-get-credentials... - anodelman
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-828 PR (1047): (QENG-1071) debian ec2 /etc/init.d/ec2-get-credentials... - anodelman Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-828) PR (1047): (QENG-1071) debian ec2 /etc/init.d/ec2-get-credentials... - anodelman
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-828 PR (1047): (QENG-1071) debian ec2 /etc/init.d/ec2-get-credentials... - anodelman Change By: Kenneth Barber Sprint: 20140813 to 20140827 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-809) Store top level structured fact data as JSON
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-809 Store top level structured fact data as JSON Change By: Kenneth Barber Summary: Switch to using a cache for /facts endpoint Store top level structured fact data as JSON Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-229) User provider password_max_age attribute is flawed under Solaris
Title: Message Title Rahul Gopinath commented on an issue Re: User provider password_max_age attribute is flawed under Solaris Updated with PR Add Comment Puppet / PUP-229 User provider password_max_age attribute is flawed under Solaris A user reported this, and did an excellent write up of the issue and a possible fix, so I'm just going to paste that: The password_max_age logic is flawed on Solaris. At first, it seems to work: {noformat} # tail -1 /etc/passwd foobar:x:911:911::/home/foobar:/bin/sh # tail -1 /etc/shadow foobar:GI2XGzW0DitJk:15931::182:28::: {noformat} E... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1044) FileBucket should not keep files in memory
Title: Message Title Henrik Lindberg commented on an issue Re: FileBucket should not keep files in memory So far, I have validated my work on this ticket by : info logging that agent backup computes the checksum using the file method instead of on a string a backup followed by a restore yields identical bits it passes unit and integration tests Add Comment Puppet / PUP-1044 FileBucket should not keep files in memory It should not be necessary to load entire files into memory to checksum them. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Group
Jira (PUP-3050) Fix cfacter integration to match recent cfacter changes
Title: Message Title Michael Smith commented on an issue Re: Fix cfacter integration to match recent cfacter changes Merged into master at 7fb1e6a Add Comment Puppet / PUP-3050 Fix cfacter integration to match recent cfacter changes cfacter has changed its gem so that most of the implementation now lies in the C++ source. This means we can entirely remove lib/facts.rb and change the cfacter option implementation to simply call a single method in the gem. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1044) FileBucket should not keep files in memory
Title: Message Title Henrik Lindberg commented on an issue Re: FileBucket should not keep files in memory I now have an implementation that uses a file whenever it can (it is not streaming a request to a file first, so there is still one copy in memory though). I have trouble finding a use case that I can use to measure memory consumption. Add Comment Puppet / PUP-1044 FileBucket should not keep files in memory It should not be necessary to load entire files into memory to checksum them. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3064) Prevent race condition in Windows service code from prematurely exiting win32-service Service_Main
Title: Message Title Ethan Brown updated an issue Puppet / PUP-3064 Prevent race condition in Windows service code from prematurely exiting win32-service Service_Main Change By: Ethan Brown A workaround has been put in place as part of PUP-2987 to fix issues discovered in the win32-service gem. It also has slightly restructured the Windows service daemon.This should resolve deadlocks experienced when terminating the service.However, the reason that this works is due to the fact that {{Service_Main}} now contains an ensure block that makes certain to call {{SetTheServiceStatus.call(SERVICE_STOPPED, NO_ERROR, 0, 0)}} if the thread prematurely aborts or an exception is otherwise generated.In local testing under windbg, as soon as the SCM signals the service (inside of {{Service_CtrlEx}}) that it has requested a stop, it appears that the {{Service_Main}} completely aborts, despite the fact that it is currently waiting on {{while(WaitForSingleObject(@@hStopEvent, 1000) != WAIT_OBJECT_0) do}}.It should continue to wait on {{while(WaitForSingleObject(@@hStopCompletedEvent, 1000) != WAIT_OBJECT_0) do}}, which allows for the service code to perform proper clean up, but this never happens.Instead the service stops abruptly without following the orchestration set forward by the signaled events.For our particular code, this might not be an issue -- but should the daemon code ever become more complicated, it's possible that resources may not be freed and the situation could escalate quickly.Some ideas of what to look at with this issue:* FFI calls can have a {{:blocking}} parameter set, which can control how they behave with respect to the Ruby GIL. Some of the native API calls specify this, but perhaps incorrectly? https://github.com/ffi/ffi/wiki/Callbacks* The win32-service gem uses class level variables to store state that is shared between Ruby threads, Win32 threads, and Win32 callbacks created by FFI. This feels dangerous, and should potentially be rewritten to avoid using Ruby objects (which might? translate to weird GC issues across threads that Ruby doesn't own) in lieu of passing unmanaged pointers / values where possible. The use of closures to capture class variables feels wrong.* Note that SetServiceStatus must always be called *after* any cleanup operations -> http://msdn.microsoft.com/en-us/library/windows/desktop/ms686241(v=vs.85).aspxOther helpful tips:* I prefer to install the latest x64 MSI built by Jenkins, then to modify the vendored win32-service code that should live in {{c:\program files\Puppet Labs\Puppet\sys\ruby\lib\ruby\gems\2.0.0\gems\win32-service-0.8.5\lib\win32}}* The Puppet service can be launched from the command line with {{sc start puppet --debug --trace --verbose}}* I typically wait for Puppet to fail to resolve a bogus master name before attaching to the process. Once attached {{sc stop puppet}} to observe the services shutdown behavior.* The cv2pdb application can be used to extract PDB format debug files from the Ruby that we build - see http://blog.morlad.at/blah/mingw_postmortem. Despite what this article says, it would appear that windbg searches for a {{ruby.dbg}} or {{ruby.pdb}} that lives alongside {{ruby.exe}} in the {{c:\program files\puppet labs\puppet\sys\ruby\bin}} directory* Windbg x64 must be used to attach to the ruby.exe service process. Start windbg fr
Jira (PUP-3064) Prevent race condition in Windows service code from prematurely exiting win32-service Service_Main
Title: Message Title Ethan Brown updated an issue Puppet / PUP-3064 Prevent race condition in Windows service code from prematurely exiting win32-service Service_Main Change By: Ethan Brown A workaround has been put in place as part of PUP-2987 to fix issues discovered in the win32-service gem. It also has slightly restructured the Windows service daemon.This should resolve deadlocks experienced when terminating the service.However, the reason that this works is due to the fact that {{Service_Main}} now contains an ensure block that makes certain to call {{SetTheServiceStatus.call(SERVICE_STOPPED, NO_ERROR, 0, 0)}} if the thread prematurely aborts or an exception is otherwise generated.In local testing under windbg, as soon as the SCM signals the service (inside of {{Service_CtrlEx}}) that it has requested a stop, it appears that the {{Service_Main}} completely aborts, despite the fact that it is currently waiting on {{while(WaitForSingleObject(@@hStopEvent, 1000) != WAIT_OBJECT_0) do}}.It should continue to wait on {{while(WaitForSingleObject(@@hStopCompletedEvent, 1000) != WAIT_OBJECT_0) do}}, which allows for the service code to perform proper clean up, but this never happens.Instead the service stops abruptly without following the orchestration set forward by the signaled events.For our particular code, this might not be an issue -- but should the daemon code ever become more complicated, it's possible that resources may not be freed and the situation could escalate quickly.Some ideas of what to look at with this issue:* FFI calls can have a {{:blocking}} parameter set, which can control how they behave with respect to the Ruby GIL. Some of the native API calls specify this, but perhaps incorrectly? https://github.com/ffi/ffi/wiki/Callbacks* The win32-service gem uses class level variables to store state that is shared between Ruby threads, Win32 threads, and Win32 callbacks created by FFI. This feels dangerous, and should potentially be rewritten to avoid using Ruby objects (which might? translate to weird GC issues across threads that Ruby doesn't own) in lieu of passing unmanaged pointers / values where possible. The use of closures to capture class variables feels wrong.* Note that SetServiceStatus must always be called *after* any cleanup operations -> http://msdn.microsoft.com/en-us/library/windows/desktop/ms686241(v=vs.85).aspxOther helpful tips:* I prefer to install the latest x64 MSI built by Jenkins, then to modify the vendored win32-service code that should live in {{c:\program files\Puppet Labs\Puppet\sys\ruby\lib\ruby\gems\2.0.0\gems\win32-service-0.8.5\lib\win32}}* The Puppet service can be launched from the command line with {{sc start puppet --debug --trace --verbose}}* I typically wait for Puppet to fail to resolve a bogus master name before attaching to the process. Once attached {{sc stop puppet}} to observe the services shutdown behavior.* The cv2pdb application can be used to extract PDB format debug files from the Ruby that we build - see http://blog.morlad.at/blah/mingw_postmortem. Despite what this article says, it would appear that windbg searches for a {{ruby.dbg}} or {{ruby.pdb}} that lives alongside {{ruby.exe}} in the {{c:\program files\puppet labs\puppet\sys\ruby\bin}} directory* Windbg x64 must be used to attach to the ruby.exe service process. Start windbg fr
Jira (PUP-3064) Prevent race condition in Windows service code from prematurely exiting win32-service Service_Main
Title: Message Title Ethan Brown updated an issue Puppet / PUP-3064 Prevent race condition in Windows service code from prematurely exiting win32-service Service_Main Change By: Ethan Brown Summary: Prevent race condition in Windows service code from prematurely existing exiting win32-service Service_Main Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3064) Prevent race condition in Windows service code from prematurely exiting win32-service Service_Main
Title: Message Title Ethan Brown updated an issue Puppet / PUP-3064 Prevent race condition in Windows service code from prematurely exiting win32-service Service_Main Change By: Ethan Brown A workaround has been put in place as part of PUP-2987 to fix issues discovered in the win32-service gem. It also has slightly restructured the Windows service daemon.This should resolve deadlocks experienced when terminating the service.However, the reason that this works is due to the fact that {{Service_Main}} now contains an ensure block that makes certain to call {{SetTheServiceStatus.call(SERVICE_STOPPED, NO_ERROR, 0, 0)}} if the thread prematurely aborts or an exception is otherwise generated.In local testing under windbg, as soon as the SCM signals the service (inside of {{Service_CtrlEx}}) that it has requested a stop, it appears that the {{Service_Main}} completely aborts, despite the fact that it is currently waiting on {{while(WaitForSingleObject(@@hStopEvent, 1000) != WAIT_OBJECT_0) do}}.It should continue to wait on {{while(WaitForSingleObject(@@hStopCompletedEvent, 1000) != WAIT_OBJECT_0) do}}, which allows for the service code to perform proper clean up, but this never happens.Instead the service stops abruptly without following the orchestration set forward by the signaled events.For our particular code, this might not be an issue -- but should the daemon code ever become more complicated, it's possible that resources may not be freed and the situation could escalate quickly.Some ideas of what to look at with this issue:* FFI calls can have a {{:blocking}} parameter set, which can control how they behave with respect to the Ruby GIL. Some of the native API calls specify this, but perhaps incorrectly? https://github.com/ffi/ffi/wiki/Callbacks* The win32-service gem uses class level variables to store state that is shared between Ruby threads, Win32 threads, and Win32 callbacks created by FFI. This feels dangerous, and should potentially be rewritten to avoid using Ruby objects (which might? translate to weird GC issues across threads that Ruby doesn't own) in lieu of passing unmanaged pointers / values where possible. The use of closures to capture class variables feels wrong.* Note that SetServiceStatus must always be called *after* any cleanup operations -> http://msdn.microsoft.com/en-us/library/windows/desktop/ms686241(v=vs.85).aspxOther helpful tips:* I prefer to install the latest x64 MSI built by Jenkins, then to modify the vendored win32-service code that should live in {{c:\program files\Puppet Labs\Puppet\sys\ruby\lib\ruby\gems\2.0.0\gems\win32-service-0.8.5\lib\win32}}* The Puppet service can be launched from the command line with {{sc start puppet --debug --trace --verbose}}* I typically wait for Puppet to fail to resolve a bogus master name before attaching to the process. Once attached {{sc stop puppet}} to observe the services shutdown behavior.* The cv2pdb application can be used to extract PDB format debug files from the Ruby that we build , and it appears that - see http://blog.morlad.at/blah/mingw_postmortem. Despite what this article says, it would appear that windbg searches for a {{ruby.dbg}} or {{ruby.pdb}} that lives alongside {{ruby.exe}} in the {{c:\program files\puppet labs\puppet\sys\ruby\bin}} directory* Windbg x64 must be used to attach to the ruby.exe service p
Jira (PUP-3064) Prevent race condition in Windows service code from prematurely existing win32-service Service_Main
Title: Message Title Ethan Brown updated an issue Puppet / PUP-3064 Prevent race condition in Windows service code from prematurely existing win32-service Service_Main Change By: Ethan Brown A workaround has been put in place as part of PUP-2987 to fix issues discovered in the win32-service gem. It also has slightly restructured the Windows service daemon.This should resolve deadlocks experienced when terminating the service.However, the reason that this works is due to the fact that {{Service_Main}} now contains an ensure block that makes certain to call {{SetTheServiceStatus.call(SERVICE_STOPPED, NO_ERROR, 0, 0)}} if the thread prematurely aborts or an exception is otherwise generated.In local testing under windbg, as soon as the SCM signals the service (inside of {{Service_CtrlEx}}) that it has requested a stop, it appears that the {{Service_Main}} completely aborts, despite the fact that it is currently waiting on {{while(WaitForSingleObject(@@hStopEvent, 1000) != WAIT_OBJECT_0) do}}.It should continue to wait on {{while(WaitForSingleObject(@@hStopCompletedEvent, 1000) != WAIT_OBJECT_0) do}}, which allows for the service code to perform proper clean up, but this never happens.Instead the service stops abruptly without following the orchestration set forward by the signaled events.For our particular code, this might not be an issue -- but should the daemon code ever become more complicated, it's possible that resources may not be freed and the situation could escalate quickly.Some ideas of what to look at with this issue:* FFI calls can have a {{:blocking}} parameter set, which can control how they behave with respect to the Ruby GIL. Some of the native API calls specify this, but perhaps incorrectly? https://github.com/ffi/ffi/wiki/Callbacks* The win32-service gem uses class level variables to store state that is shared between Ruby threads, Win32 threads, and Win32 callbacks created by FFI. This feels dangerous, and should potentially be rewritten to avoid using Ruby objects (which might? translate to weird GC issues across threads that Ruby doesn't own) in lieu of passing unmanaged pointers / values where possible. The use of closures to capture class variables feels wrong.* Note that SetServiceStatus must always be called *after* any cleanup operations -> http://msdn.microsoft.com/en-us/library/windows/desktop/ms686241(v=vs.85).aspxOther helpful tips:* I prefer to install the latest x64 MSI built by Jenkins, then to modify the vendored win32-service code that should live in {{c:\program files\Puppet Labs\Puppet\sys\ruby\lib\ruby\gems\2.0.0\gems\win32-service-0.8.5\lib\win32}}* The Puppet service can be launched from the command line with {{sc start puppet --debug --trace --verbose}}* I typically wait for Puppet to fail to resolve a bogus master name before attaching to the process. Once attached {{sc stop puppet}} to observe the services shutdown behavior.* The cv2pdb application can be used to extract PDB format debug files from the Ruby that we build, and it appears that - see http://blog.morlad.at/blah/mingw_postmortem. Despite what this article says, it would appear that windbg searches for a {{ruby.dbg}} or {{ruby.pdb}} that lives alongside {{ruby.exe}} in the {{c:\program files\puppet labs\puppet\sys\ruby\bin}} directory* Windbg x64 must be used to attach to the ruby.exe service pr
Jira (PUP-3064) Prevent race condition in Windows service code from prematurely existing win32-service Service_Main
Title: Message Title Ethan Brown updated an issue Puppet / PUP-3064 Prevent race condition in Windows service code from prematurely existing win32-service Service_Main Change By: Ethan Brown A workaround has been put in place as part of PUP-2987 to fix issues discovered in the win32-service gem. It also has slightly restructured the Windows service daemon.This should resolve deadlocks experienced when terminating the service.However, the reason that this works is due to the fact that {{Service_Main}} now contains an ensure block that makes certain to call {{SetTheServiceStatus.call(SERVICE_STOPPED, NO_ERROR, 0, 0)}} if the thread prematurely aborts or an exception is otherwise generated.In local testing under windbg, as soon as the SCM signals the service (inside of {{Service_CtrlEx}}) that it has requested a stop, it appears that the {{Service_Main}} completely aborts, despite the fact that it is currently waiting on {{while(WaitForSingleObject(@@hStopEvent, 1000) != WAIT_OBJECT_0) do}}.It should continue to wait on {{while(WaitForSingleObject(@@hStopCompletedEvent, 1000) != WAIT_OBJECT_0) do}}, which allows for the service code to perform proper clean up, but this never happens.Instead the service stops abruptly without following the orchestration set forward by the signaled events.For our particular code, this might not be an issue -- but should the daemon code ever become more complicated, it's possible that resources may not be freed and the situation could escalate quickly.Some ideas of what to look at with this issue:* FFI calls can have a {{:blocking}} parameter set, which can control how they behave with respect to the Ruby GIL. Some of the native API calls specify this, but perhaps incorrectly? https://github.com/ffi/ffi/wiki/Callbacks* The win32-service gem uses class level variables to store state that is shared between Ruby threads, Win32 threads, and Win32 callbacks created by FFI. This feels dangerous, and should potentially be rewritten to avoid using Ruby objects (which might? translate to weird GC issues across threads that Ruby doesn't own) in lieu of passing unmanaged pointers / values where possible. The use of closures to capture class variables feels wrong.* Note that SetServiceStatus must always be called *after* any cleanup operations -> http://msdn.microsoft.com/en-us/library/windows/desktop/ms686241(v=vs.85).aspxOther helpful tips:* I prefer to install the latest x64 MSI built by Jenkins, then to modify the vendored win32-service code that should live in {{c:\program files\Puppet Labs\Puppet\sys\ruby\lib\ruby\gems\2.0.0\gems\win32-service-0.8.5\lib\win32}}* The Puppet service can be launched from the command line with {{sc start puppet --debug --trace --verbose}}* I typically wait for Puppet to fail to resolve a bogus master name before attaching to the process. Once attached {{sc stop puppet}} to observe the services shutdown behavior.* The cv2pdb application can be used to extract PDB format debug files from the Ruby that we build, and it appears that - see http://blog.morlad.at/blah/mingw_postmortem. Despite what this article says, it would appear that windbg searches for a {{ruby.dbg}} or {{ruby.pdb}} that lives alongside {{ruby.exe}} in the {{c:\program files\puppet labs\puppet\sys\ruby\bin}} directory* Windbg x64 must be used to attach to the ruby.exe service pr
Jira (PUP-3064) Prevent race condition in Windows service code from prematurely existing win32-service Service_Main
Title: Message Title Ethan Brown created an issue Puppet / PUP-3064 Prevent race condition in Windows service code from prematurely existing win32-service Service_Main Issue Type: Bug Affects Versions: 3.x Assignee: Kylo Ginsberg Components: Client Created: 14/Aug/14 5:17 PM Fix Versions: 3.7.1 Priority: Normal Reporter: Ethan Brown A workaround has been put in place as part of PUP-2987 to fix issues discovered in the win32-service gem. It also has slightly restructured the Windows service daemon. This should resolve deadlocks experienced when terminating the service. However, the reason that this works is due to the fact that Service_Main now contains an ensure block that makes certain to call SetTheServiceStatus.call(SERVICE_STOPPED, NO_ERROR, 0, 0) if the thread prematurely aborts or an exception is otherwise generated. In local testing under windbg, as soon as the SCM signals the service (inside of Service_CtrlEx) that it has requested a stop, it appears that the Service_Main completely aborts, despite the fact t
Jira (FACT-653) Backport lost update on supported Ruby versions into Facter / master
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-653 Backport lost update on supported Ruby versions into Facter / master Change By: Kylo Ginsberg Sprint: 2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2817 Solaris Zone properties ip, dataset and inherit are not set upon zone creation Change By: Kylo Ginsberg Sprint: 2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-641) Backport lost Solaris 10 zfs_version fix into Facter / master
Title: Message Title William Hopper commented on an issue Re: Backport lost Solaris 10 zfs_version fix into Facter / master Eric Thompson Oh, my mistake! I'm glad actually, since I thought the backport had failed to address the issue . Add Comment Facter / FACT-641 Backport lost Solaris 10 zfs_version fix into Facter / master This commit was lost in the facter-2 / master merge. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-641) Backport lost Solaris 10 zfs_version fix into Facter / master
Title: Message Title Eric Thompson commented on an issue Re: Backport lost Solaris 10 zfs_version fix into Facter / master heh. William Hopper, those notes were mostly for me so i'd know what to do if i can ever find a solaris machine without zfs upgrade. but i haven't... i can't even find a solaris10 machine with cc installed on it yet. that makes it kinda hard to install ruby. but i haven't tried very hard yet Add Comment Facter / FACT-641 Backport lost Solaris 10 zfs_version fix into Facter / master This commit was lost in the facter-2 / master merge. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3063) Remove certification expiration check from puppet-4
Title: Message Title Christopher Price commented on an issue Re: Remove certification expiration check from puppet-4 Andy Parker this is the follow up ticket to PUP-3031. PR is linked. Add Comment Puppet / PUP-3063 Remove certification expiration check from puppet-4 This ticket is just a follow-on to PUP-3031, where we decided that the current approach for checking whether a client certificate is going to expire soon is a bit heavy-handed and not necessary. It was moved to a better location in 3.7 but is being removed altogether for 4.0. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3063) Remove certification expiration check from puppet-4
Title: Message Title Christopher Price assigned an issue to Christopher Price Puppet / PUP-3063 Remove certification expiration check from puppet-4 Change By: Christopher Price Assignee: Andy Parker Christopher Price Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3063) Remove certification expiration check from puppet-4
Title: Message Title Christopher Price created an issue Puppet / PUP-3063 Remove certification expiration check from puppet-4 Issue Type: Task Assignee: Andy Parker Components: Server Created: 14/Aug/14 4:35 PM Fix Versions: 4.0.0 Priority: Normal Reporter: Christopher Price This ticket is just a follow-on to PUP-3031, where we decided that the current approach for checking whether a client certificate is going to expire soon is a bit heavy-handed and not necessary. It was moved to a better location in 3.7 but is being removed altogether for 4.0. Add Comment
Jira (PUP-3031) simplify/move warn_if_near_expiration
Title: Message Title Christopher Price updated an issue Puppet / PUP-3031 simplify/move warn_if_near_expiration Change By: Christopher Price Assignee: Christopher Price Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3031) simplify/move warn_if_near_expiration
Title: Message Title Christopher Price assigned an issue to Christopher Price Puppet / PUP-3031 simplify/move warn_if_near_expiration Change By: Christopher Price Assignee: Christopher Price Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-641) Backport lost Solaris 10 zfs_version fix into Facter / master
Title: Message Title William Hopper commented on an issue Re: Backport lost Solaris 10 zfs_version fix into Facter / master Hey Eric Thompson, thanks for the review! Would you mind telling me the steps to setup the correct version of ZFS in Solaris 10 so I can work on and test a fix for the backport? Add Comment Facter / FACT-641 Backport lost Solaris 10 zfs_version fix into Facter / master This commit was lost in the facter-2 / master merge. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-641) Backport lost Solaris 10 zfs_version fix into Facter / master
Title: Message Title Eric Thompson updated an issue Facter / FACT-641 Backport lost Solaris 10 zfs_version fix into Facter / master Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-287) stringify_facts needs to be in agent, not master conf file
Title: Message Title txaj1 created an issue Hiera / HI-287 stringify_facts needs to be in agent, not master conf file Issue Type: Bug Assignee: Lauren Rother Components: DOCS Created: 14/Aug/14 3:59 PM Priority: Minor Reporter: txaj1 Hello, The documentation here : https://docs.puppetlabs.com/facter/latest/fact_overview.html states that "stringify_facts must be set to false in the [main] or [master] section on the master". If PUP-2421 is not mistaken, this is incorrect Thanks Add Comment
Jira (PUP-3050) Fix cfacter integration to match recent cfacter changes
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-3050 Fix cfacter integration to match recent cfacter changes Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3062) The default unit for `splaylimit` should not be seconds.
Title: Message Title Andy Parker commented on an issue Re: The default unit for `splaylimit` should not be seconds. There are problems with defaulting this one to minutes: all of the other durations default to seconds. We could start changing each one to its own default unit, but that seems even more confusing. A good middle ground is to not allow values that don't specify the units (the "s" is always required, even if 5 seconds is wanted). I think the way to move this forward would be to get a deprecation warning for Puppet 3.7 and change it to a failure in puppet 4. Add Comment Puppet / PUP-3062 The default unit for `splaylimit` should not be seconds. {{runinterval}} defaults to minutes, and {{splaylimit}} defaults to {{runinterval}} What's more, I can't imagine ever wanting to splay by seconds instead of minutes. I'm not opposed to the option existing, but it should not be the default unit. I've seen this confuse at least one customer, and it certainly took me time to notice this in the docs This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subs
Jira (PDB-743) Report retrieval JSON::ParserError due to random database disconnection
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-743 Report retrieval JSON::ParserError due to random database disconnection Change By: Kenneth Barber Fix Version/s: 2.2.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3062) The default unit for `splaylimit` should not be seconds.
Title: Message Title Zachary Stern created an issue Puppet / PUP-3062 The default unit for `splaylimit` should not be seconds. Issue Type: Improvement Assignee: Unassigned Created: 14/Aug/14 2:49 PM Priority: Normal Reporter: Zachary Stern runinterval defaults to minutes, and splaylimit defaults to runinterval What's more, I can't imagine ever wanting to splay by seconds instead of minutes. I'm not opposed to the option existing, but it should not be the default units. I've seen this confuse at least one customer, and it certainly took me time to notice this in the docs. Of course I should have read them more closely, but this is still confusing on its face. Add Comment This message was sent by Atlassian
Jira (PUP-3031) simplify/move warn_if_near_expiration
Title: Message Title Andy Parker commented on an issue Re: simplify/move warn_if_near_expiration Merged into master in ed9e74. For functional review: there shouldn't be any user visible change from this. The expiration warnings should still be issued by both rack and webrick masters. An easy way to get the warning is to set the certificate_expire_warning to a very high value. I used 6y (6 years) when I was testing (I only checked webrick). Add Comment Puppet / PUP-3031 simplify/move warn_if_near_expiration See related PE ticket; this is largely a placeholder just to make sure we've tried to address this before 3.7.0 release. In `http/handler.rb`'s `process` method, there is a call to a method named `warn_if_near_expiration`. The goal of this method appears to be simply to check the expiration date of the client certificate, and log a warning message if i... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsu
Jira (PUP-3062) The default unit for `splaylimit` should not be seconds.
Title: Message Title Zachary Stern commented on an issue Re: The default unit for `splaylimit` should not be seconds. The obvious caveat here would be that this change would break backwards compatibility. If this request is accepted it should be at some major release bump. Add Comment Puppet / PUP-3062 The default unit for `splaylimit` should not be seconds. {{runinterval}} defaults to minutes, and {{splaylimit}} defaults to {{runinterval}} What's more, I can't imagine ever wanting to splay by seconds instead of minutes. I'm not opposed to the option existing, but it should not be the default unit. I've seen this confuse at least one customer, and it certainly took me time to notice this in the docs This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.g
Jira (PUP-3062) The default unit for `splaylimit` should not be seconds.
Title: Message Title Zachary Stern updated an issue Puppet / PUP-3062 The default unit for `splaylimit` should not be seconds. Change By: Zachary Stern Labels: customer support Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2986) Update Windows Installer license file to reference Unknownr addition that is MIT licensed
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-2986 Update Windows Installer license file to reference Unknownr addition that is MIT licensed Change By: Ethan Brown Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3062) The default unit for `splaylimit` should not be seconds.
Title: Message Title Zachary Stern updated an issue Puppet / PUP-3062 The default unit for `splaylimit` should not be seconds. Change By: Zachary Stern {{runinterval}} defaults to minutes, and {{splaylimit}} defaults to {{runinterval}}What's more, I can't imagine ever wanting to splay by seconds instead of minutes.I'm not opposed to the option existing, but it should not be the default units unit .I've seen this confuse at least one customer, and it certainly took me time to notice this in the docs. Of course I should have read them more closely, but this is still confusing on its face. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3054) Class inheritance behaving incorrectly in the future parser
Title: Message Title Andy Parker updated an issue Puppet / PUP-3054 Class inheritance behaving incorrectly in the future parser Change By: Andy Parker Sprint: 2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3054) Class inheritance behaving incorrectly in the future parser
Title: Message Title Andy Parker updated an issue Puppet / PUP-3054 Class inheritance behaving incorrectly in the future parser Change By: Andy Parker Story Points: 2 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3056) Restore constants / deprecated call sites changed during x64 upgrade that impact ACL module
Title: Message Title Rob Reynolds commented on an issue Re: Restore constants / deprecated call sites changed during x64 upgrade that impact ACL module Merged into master at 14645e3 Add Comment Puppet / PUP-3056 Restore constants / deprecated call sites changed during x64 upgrade that impact ACL module When {{Puppet::Util::Windows::File}} and {{Puppet::Util::Windows::Security}} were refactored, mixins from older versions of the {{windows-pr]} gem were removed. At the time, we didn't check downstream modules to see if they were consuming any of the mixed in methods or constants. A scan through the ACL module has revealed that some methods were not ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3031) simplify/move warn_if_near_expiration
Title: Message Title Andy Parker updated an issue Puppet / PUP-3031 simplify/move warn_if_near_expiration Change By: Andy Parker Sprint: 2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3031) simplify/move warn_if_near_expiration
Title: Message Title Andy Parker updated an issue Puppet / PUP-3031 simplify/move warn_if_near_expiration Change By: Andy Parker Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3060) Remove Warning on Ruby 2.0 / Windows about "DL is deprecated, please use Fiddle"
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-3060 Remove Warning on Ruby 2.0 / Windows about "DL is deprecated, please use Fiddle" Change By: Ethan Brown Assignee: Kylo Ginsberg Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2987) Puppet service hangs when attempting to stop on Windows
Title: Message Title Ethan Brown commented on an issue Re: Puppet service hangs when attempting to stop on Windows Current patch merged into win32-service gem (PR # 21) addresses the hang by ensuring that even where threads abort early or exceptions are raised, that events will be signaled / SetTheServiceStatus will be called to stop the service. This still doesn't address why there is a race under some circumstances and the thread Service_Main can be prematurely aborted but it at least prevents the service from hanging while trying to STOP in a STOP_PENDING state. Add Comment Puppet / PUP-2987 Puppet service hangs when attempting to stop on Windows There is a race condition in the Puppet service code that prevents it from properly stopping. Generally speaking this can be reproduced by installing from the MSI, then attempting to upgrade / remove the MSI shortly thereafter. In the wild, we've noticed it can be either {{puppet}} / {{pe-puppet}} or {{mcollective}} / {{pe-mcollective}}, so the serv... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are sub
Jira (PUP-2889) Upgrade win32-eventlog
Title: Message Title Rob Reynolds commented on an issue Re: Upgrade win32-eventlog That pull request was yanked once we realized we were waiting on the eventlog gem to be upgraded so that the fixes for Windows 2003 would still work - that is PUP-3061 Add Comment Puppet / PUP-2889 Upgrade win32-eventlog We need to either upgrade or replace the use of win32-eventlog. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3061) Upgrade win32-eventlog to 0.6.2+ once it is released
Title: Message Title Rob Reynolds created an issue Puppet / PUP-3061 Upgrade win32-eventlog to 0.6.2+ once it is released Issue Type: Task Affects Versions: 3.7.0 Assignee: Kylo Ginsberg Components: Client Created: 14/Aug/14 2:25 PM Fix Versions: 3.7.1 Labels: windows Priority: Normal Reporter: Rob Reynolds This will incorporate https://github.com/djberg96/win32-eventlog/pull/10 fix that we need to upgrade the gems locally in puppet. Following that up we'll need to remove the patches from the puppet-win32-ruby repository.
Jira (PUP-3030) Resolve Tempfile handling issues
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3030 Resolve Tempfile handling issues Change By: Kylo Ginsberg Component/s: Server Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3032) Setting to cache `load_library` failures
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3032 Setting to cache `load_library` failures Change By: Kylo Ginsberg Component/s: Server Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3008) Already initialized constant warning when running puppet
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3008 Already initialized constant warning when running puppet Change By: Kylo Ginsberg Component/s: Client Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2907) Regression when pluginsyncing external facts on Windows
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2907 Regression when pluginsyncing external facts on Windows Change By: Kylo Ginsberg Component/s: Client Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3060) Remove Warning on Ruby 2.0 / Windows about "DL is deprecated, please use Fiddle"
Title: Message Title Ethan Brown updated an issue Puppet / PUP-3060 Remove Warning on Ruby 2.0 / Windows about "DL is deprecated, please use Fiddle" Change By: Ethan Brown Sprint: 2014-09-03 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3060) Remove Warning on Ruby 2.0 / Windows about "DL is deprecated, please use Fiddle"
Title: Message Title Ethan Brown created an issue Puppet / PUP-3060 Remove Warning on Ruby 2.0 / Windows about "DL is deprecated, please use Fiddle" Issue Type: Task Affects Versions: 3.7.0 Assignee: Kylo Ginsberg Components: Client Created: 14/Aug/14 1:58 PM Fix Versions: 3.7.0 Labels: windows Priority: Normal Reporter: Ethan Brown This is more of a nuisance message than anything else, and should be removed from our distribution so as to not confuse users. More details on DL vs Fiddle here: http://stackoverflow.com/questions/15590450/ruby-2-0-0p0-irb-error-dl-is-deprecated-please-use-fiddle
Jira (PUP-3060) Remove Warning on Ruby 2.0 / Windows about "DL is deprecated, please use Fiddle"
Title: Message Title Ethan Brown updated an issue Puppet / PUP-3060 Remove Warning on Ruby 2.0 / Windows about "DL is deprecated, please use Fiddle" Change By: Ethan Brown Sprint: 2014- 09 08 - 03 20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-657) Solaris manufacture details should use prtpicl instead of prtdiags/sneep
Title: Message Title Kristina Tripp created an issue Facter / FACT-657 Solaris manufacture details should use prtpicl instead of prtdiags/sneep Issue Type: Bug Affects Versions: 2.0.2, 2.1.0 Assignee: Eric Sorenson Created: 14/Aug/14 1:46 PM Environment: Solaris SPARC 11.2 Priority: Normal Reporter: Kristina Tripp For Bug FACT-547 Limit the output of prtdiag on Solaris the fix was to add head to the output of prtdiags but instead the correct solution is instead to initially use "prtpicl" to retrieve the manufacturing details on SPARC. On newer SPARC systems this option can be used to retrieve the details that prtdiag is being used for. Also sneep may not be installed on a system. Examples of output of prtpicl $ prtpicl -v -c chassis 0638NNN021:CH (chassis, 1d40c06) :MfgName Sun Microsystems, Inc :SerialNumber 0638NNN021 :Label 0638NNN021:CH :Description SUNW,Sun Fire T2000 Chassis :OperationalStatus enabled :_class chassis :name 0638NNN021:CH $ prtpicl -v -c chassis SYS (chassis, a640dd3) :ModelName 31703427+1+1 :MfgName Oracle Corporation :SerialNumber AK00104240 :FW-version Sun System Firmware 9.2.0.a 2014/04/08 15:17 :Label SYS :Description SPARC T5-2 :OperationalStatus enabled :_class chassis :name SYS Notice that on a T5 system this
Jira (PUP-3031) simplify/move warn_if_near_expiration
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3031 simplify/move warn_if_near_expiration Change By: Andy Parker Assignee: Andy Parker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3031) simplify/move warn_if_near_expiration
Title: Message Title Christopher Price commented on an issue Re: simplify/move warn_if_near_expiration PR submitted for 3.7. After that goes in and is merged up to 4.0, we can reassign this ticket to me and I'll file the follow-up PR. Add Comment Puppet / PUP-3031 simplify/move warn_if_near_expiration See related PE ticket; this is largely a placeholder just to make sure we've tried to address this before 3.7.0 release. In `http/handler.rb`'s `process` method, there is a call to a method named `warn_if_near_expiration`. The goal of this method appears to be simply to check the expiration date of the client certificate, and log a warning message if i... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2349) Deprecate non-string modes on file type
Title: Message Title Andy Parker assigned an issue to Kylo Ginsberg Puppet / PUP-2349 Deprecate non-string modes on file type Change By: Andy Parker Assignee: Andy Parker Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2349) Deprecate non-string modes on file type
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2349 Deprecate non-string modes on file type Change By: Andy Parker Assignee: Andy Parker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1521) Allow configuration of SSL ciphers
Title: Message Title Eric Sorenson commented on an issue Re: Allow configuration of SSL ciphers Ahh, agents in listen mode. I didn't think about that scenario. Makes total sense. Add Comment Puppet / PUP-1521 Allow configuration of SSL ciphers We run puppet in a secure environment. One of the policies in place states that no weak ciphers (key length < 128 bit) are allowed anywhere. Our puppetmasterd got flagged by a review recently as it allows such ciphers on incoming connections. I temporarily worked around it with this horrible hack in /usr/lib/ruby/1.8/webrick/ssl.rb: ctx.verify... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2855) Puppet agent segfault on OSX Mavericks when puppet master is running under passenger
Title: Message Title Chase Thompson-Baugh commented on an issue Re: Puppet agent segfault on OSX Mavericks when puppet master is running under passenger I upgraded a vanilla 10.9.4 installation to ruby-2.1.2 and now it works fine. I first installed Apple's Command Line Tools, installed Homebrew, installed RVM, installed ruby-2.1.2 using RVM, set ruby-2.1.2 as the default for the system, and reinstalled puppet with "sudo gem install puppet". I tried the Puppet Enterprise Learning VM and a vanilla 10.9.4 install using ruby-2.0.0p451 and "sudo gem install puppet" works just fine running "sudo puppet agent --server puppet --waitforcert 60 --test" Add Comment Puppet / PUP-2855 Puppet agent segfault on OSX Mavericks when puppet master is running under passenger When running under the default WEBrick server puppet master and agents function as expected. When running under passenger agents on OSX Mavericks segfault (sorry, I don't have access to other versions of OSX currently). Agents running under CentOS 6.5 continue to function normally under passenger. Dump file attached. Here is the output: bash-3.2#... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2984) MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
Title: Message Title Rob Reynolds commented on an issue Re: MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec This is now ready for review. Add Comment Puppet / PUP-2984 MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec. It also doesn't remove the older path - this is what remains after install of x86 AFTER x64: {{C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files (x86)\Puppet Labs\Puppet\bin}} and it should be {{C:\Program Files (x... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more option
Jira (PUP-2907) Regression when pluginsyncing external facts on Windows
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-2907 Regression when pluginsyncing external facts on Windows Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-656) facter generates error on Solaris kernel zone due to prtdiag
Title: Message Title Kristina Tripp created an issue Facter / FACT-656 facter generates error on Solaris kernel zone due to prtdiag Issue Type: Bug Affects Versions: 2.0.2, 2.1.0 Assignee: Eric Sorenson Created: 14/Aug/14 11:25 AM Environment: Solaris 11.2 x86 kernel zone Priority: Normal Reporter: Kristina Tripp facter when run on a Solaris 11.2 kernel zone attempts to run prtdiags. This command although present only generates an error message prtdiag prtdiag: failed to open SMBIOS: System does not export an SMBIOS table Thus when facter is run this command is outputted to the screen. Simply redirecting stderr to /dev/null when prtdiag is run corrects this issue — facter-2.0.2/lib/facter/virtual.rb.orig 2014-08-13 11:15:18.794085126 -0600 +++ facter-2.0.2/lib/facter/virtual.rb 2014-08-13 11:17:43.465379141 -0600 @@ -60,7 +60,7 @@ setcode do next "zone" if Facter::Util::Virtual.zone? output = Facter::Core::Execution.exec('prtdiag') + output = Facter::Core::Execution.exec('prtdiag 2> /dev/null') if outpu
Jira (PUP-2924) Puppet searches disk for whit classes
Title: Message Title Charlie Sharpsteen commented on an issue Re: Puppet searches disk for whit classes Yes I am. I have a decent patch that solves the problem, what is slowing me down is adding documentation around the behavior and arguments passed to Puppet::Resource#initialize. I should have that wrapped up by the end of the week. Add Comment Puppet / PUP-2924 Puppet searches disk for whit classes Our Puppet instance has been pretty slow lately so we traced a puppet agent run to see what it was doing. In the trace we see a bunch of lines like this: stat("/opt/local/lib/ruby/site_ruby/2.0.0/puppet/vendor/semantic/lib/puppet/type/completed_stage.rb", 0xFD7FFFDFE4A0) Err#2 ENOENT stat("/etc/puppet/modules/admin/lib/puppet/type/completed_stage This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-b
Jira (FACT-641) Backport lost Solaris 10 zfs_version fix into Facter / master
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Facter / FACT-641 Backport lost Solaris 10 zfs_version fix into Facter / master Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-641) Backport lost Solaris 10 zfs_version fix into Facter / master
Title: Message Title Eric Thompson commented on an issue Re: Backport lost Solaris 10 zfs_version fix into Facter / master notes for FR: facter zfs_version fails on solaris 10 versions without 'zfs upgrade' this appears to be at least before Solaris 10 10/08 (u6) Add Comment Facter / FACT-641 Backport lost Solaris 10 zfs_version fix into Facter / master This commit was lost in the facter-2 / master merge. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2924) Puppet searches disk for whit classes
Title: Message Title Kylo Ginsberg commented on an issue Re: Puppet searches disk for whit classes Charlie Sharpsteen your last comment sounds like the scope of this has increased. Are you actively working this? Or should we punt it out of 3.7? Add Comment Puppet / PUP-2924 Puppet searches disk for whit classes Our Puppet instance has been pretty slow lately so we traced a puppet agent run to see what it was doing. In the trace we see a bunch of lines like this: stat("/opt/local/lib/ruby/site_ruby/2.0.0/puppet/vendor/semantic/lib/puppet/type/completed_stage.rb", 0xFD7FFFDFE4A0) Err#2 ENOENT stat("/etc/puppet/modules/admin/lib/puppet/type/completed_stage This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-655) EC2 facts on Solaris don't use arp -an
Title: Message Title Lee Lowder created an issue Facter / FACT-655 EC2 facts on Solaris don't use arp -an Issue Type: Bug Assignee: Eric Sorenson Created: 14/Aug/14 10:53 AM Labels: support Priority: Normal Reporter: Lee Lowder In this commit, https://github.com/puppetlabs/facter/commit/0d6636261336a36d4fdaaf950218ccaa95d61487 the arp command for Solaris was changed to use arp -a instead of {{arp -an}. The reason given is: This is an invalid command on Solaris 8, but not 9 or 10. This is no long valid, as Solaris 8 is no longer supported - PE currently only supports Solaris 10 and 11. Add Comment
Jira (HI-285) Remove saucy from build_defaults.yaml
Title: Message Title William Hopper commented on an issue Re: Remove saucy from build_defaults.yaml Merged at: https://github.com/puppetlabs/hiera/commit/7aa446e784a5f71f70a978339079369788d0ea1d Add Comment Hiera / HI-285 Remove saucy from build_defaults.yaml Saucy has already gone EOL on July 17, 2014. We will be removing the saucy repo from apt.puppetlabs.com on Monday, September 15, 2014. The build_defaults.yaml file needs to be updated before then. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-645) Remove saucy from build_defaults.yaml
Title: Message Title William Hopper commented on an issue Re: Remove saucy from build_defaults.yaml Merged at: https://github.com/puppetlabs/facter/commit/f8e3365dd96e26bc23e8f53942ce76441c6792b0 Add Comment Facter / FACT-645 Remove saucy from build_defaults.yaml Saucy has already gone EOL on July 17, 2014. We will be removing the saucy repo from apt.puppetlabs.com on Monday, September 15, 2014. The build_defaults.yaml file needs to be updated before then. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3048) Remove saucy from build_defaults.yaml
Title: Message Title William Hopper commented on an issue Re: Remove saucy from build_defaults.yaml Merged at: https://github.com/puppetlabs/puppet/commit/b2c3dba204522dc243134b90e70117f8ee33b0e8 Add Comment Puppet / PUP-3048 Remove saucy from build_defaults.yaml Saucy has already gone EOL on July 17, 2014. We will be removing the saucy repo from apt.puppetlabs.com on Monday, September 15, 2014. The build_defaults.yaml file needs to be updated before then. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title Lindsey Smith PO commented on an issue Re: Provide means to request events from latest report in timeframe I don't think I know what the standard fashion is for PDB prioritization. Add Comment PuppetDB / PDB-112 Provide means to request events from latest report in timeframe h2. Summary Implement something like a {{latest-report-before}} query for the Events endpoint. This is necessary in order to enable the user experience / feature request described in [PE-1906|https://jira.puppetlabs.com/browse/PE-1906?focusedCommentId=20630&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-20630]. h2. Des... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-828) PR (1047): (QENG-1071) debian ec2 /etc/init.d/ec2-get-credentials... - anodelman
Title: Message Title gepetto-bot commented on an issue Re: PR (1047): (QENG-1071) debian ec2 /etc/init.d/ec2-get-credentials... - anodelman pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-828 PR (1047): (QENG-1071) debian ec2 /etc/init.d/ec2-get-credentials... - anodelman h2. (QENG-1071) debian ec2 /etc/init.d/ec2-get-credentials... * Author: alice nodelman* Company: Puppet Labs * Github ID: [anodelman|https://github.com/anodelman] * [Pull Request 1047 Discussion|https://github.com/puppetlabs/puppetdb/pull/1047] * [Pull Request 1047 File Diff|https://github.com/puppetlabs/puppetdb/pull/1047/fi... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups
Jira (PDB-828) PR (1047): (QENG-1071) debian ec2 /etc/init.d/ec2-get-credentials... - anodelman
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-828 PR (1047): (QENG-1071) debian ec2 /etc/init.d/ec2-get-credentials... - anodelman Issue Type: Task Assignee: Unassigned Created: 14/Aug/14 10:26 AM Labels: github Priority: Normal Reporter: gepetto-bot (QENG-1071) debian ec2 /etc/init.d/ec2-get-credentials... Author: alice nodelman Company: Puppet Labs Github ID: anodelman Pull Request 1047 Discussion Pull Request 1047 File Diff Pull Request Description ... script corrupts authorized_keys add definition for repaired debian ami
Jira (PUP-417) Add acceptance cells which test with passenger instead of webrick.
Title: Message Title Joshua Partlow commented on an issue Re: Add acceptance cells which test with passenger instead of webrick. Merged to master in e2549ac Add Comment Puppet / PUP-417 Add acceptance cells which test with passenger instead of webrick. One way to do this is to install puppetmaster-passenger on Debian platforms. However if we want both webrick and passenger coverage on Debian, then it's not as simple as modifying the packages setup process. There is conversation about this in the 9/25 Hipchat logs around 11AM, re webrick and passenger. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-827) PR (1046): DOCUMENT-97: Mention updating puppetdb module - holguinj
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-827 PR (1046): DOCUMENT-97: Mention updating puppetdb module - holguinj Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-827) PR (1046): DOCUMENT-97: Mention updating puppetdb module - holguinj
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-827 PR (1046): DOCUMENT-97: Mention updating puppetdb module - holguinj Change By: Kenneth Barber Fix Version/s: 2.2.0 Fix Version/s: 2.1.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-827) PR (1046): DOCUMENT-97: Mention updating puppetdb module - holguinj
Title: Message Title gepetto-bot commented on an issue Re: PR (1046): DOCUMENT-97: Mention updating puppetdb module - holguinj Pull request DOCUMENT-97: Mention updating puppetdb module has been closed. Add Comment PuppetDB / PDB-827 PR (1046): DOCUMENT-97: Mention updating puppetdb module - holguinj h2. DOCUMENT-97: Mention updating puppetdb module * Author: Justin Holguin* Company: Puppet Labs, Inc. * Github ID: [holguinj|https://github.com/holguinj] * [Pull Request 1046 Discussion|https://github.com/puppetlabs/puppetdb/pull/1046] * [Pull Request 1046 File Diff|https://github.com/puppetlabs/puppetdb/pull/1046/f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-827) PR (1046): DOCUMENT-97: Mention updating puppetdb module - holguinj
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-827 PR (1046): DOCUMENT-97: Mention updating puppetdb module - holguinj Change By: Kenneth Barber Sprint: 20140813 to 20140827 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title Deepak Giridharagopal commented on an issue Re: Provide means to request events from latest report in timeframe If it's no longer PE3.4 mega-urgent, then this just needs to go into the prioritization mixmaster along with everything else (HA, other bugs, etc.) in the standard fashion. Add Comment PuppetDB / PDB-112 Provide means to request events from latest report in timeframe h2. Summary Implement something like a {{latest-report-before}} query for the Events endpoint. This is necessary in order to enable the user experience / feature request described in [PE-1906|https://jira.puppetlabs.com/browse/PE-1906?focusedCommentId=20630&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-20630]. h2. Des... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs.
Jira (PDB-825) PR (1044): DOCUMENT-97: Mention updating puppetdb module - holguinj
Title: Message Title gepetto-bot commented on an issue Re: PR (1044): DOCUMENT-97: Mention updating puppetdb module - holguinj Pull request DOCUMENT-97: Mention updating puppetdb module has been closed. Add Comment PuppetDB / PDB-825 PR (1044): DOCUMENT-97: Mention updating puppetdb module - holguinj h2. DOCUMENT-97: Mention updating puppetdb module * Author: Justin Holguin* Company: Puppet Labs, Inc. * Github ID: [holguinj|https://github.com/holguinj] * [Pull Request 1044 Discussion|https://github.com/puppetlabs/puppetdb/pull/1044] * [Pull Request 1044 File Diff|https://github.com/puppetlabs/puppetdb/pull/1044/f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-825) PR (1044): DOCUMENT-97: Mention updating puppetdb module - holguinj
Title: Message Title gepetto-bot commented on an issue Re: PR (1044): DOCUMENT-97: Mention updating puppetdb module - holguinj holguinj commented: @kbarber Ok, done [PR 1046](https://github.com/puppetlabs/puppetdb/pull/1046). I'll go ahead and close this PR. Add Comment PuppetDB / PDB-825 PR (1044): DOCUMENT-97: Mention updating puppetdb module - holguinj h2. DOCUMENT-97: Mention updating puppetdb module * Author: Justin Holguin* Company: Puppet Labs, Inc. * Github ID: [holguinj|https://github.com/holguinj] * [Pull Request 1044 Discussion|https://github.com/puppetlabs/puppetdb/pull/1044] * [Pull Request 1044 File Diff|https://github.com/puppetlabs/puppetdb/pull/1044/f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bu
Jira (PDB-827) PR (1046): DOCUMENT-97: Mention updating puppetdb module - holguinj
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-827 PR (1046): DOCUMENT-97: Mention updating puppetdb module - holguinj Issue Type: Task Assignee: Unassigned Created: 14/Aug/14 9:51 AM Labels: github Priority: Normal Reporter: gepetto-bot DOCUMENT-97: Mention updating puppetdb module Author: Justin Holguin Company: Puppet Labs, Inc. Github ID: holguinj Pull Request 1046 Discussion Pull Request 1046 File Diff Pull Request Description Upgrading PuppetDB using the module is pretty easy, but we should point out that the module should be updated first. (webhooks-id: 3c794ed711c97e39fafb39b5b6310bcf)
Jira (PDB-827) PR (1046): DOCUMENT-97: Mention updating puppetdb module - holguinj
Title: Message Title gepetto-bot commented on an issue Re: PR (1046): DOCUMENT-97: Mention updating puppetdb module - holguinj pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-827 PR (1046): DOCUMENT-97: Mention updating puppetdb module - holguinj h2. DOCUMENT-97: Mention updating puppetdb module * Author: Justin Holguin* Company: Puppet Labs, Inc. * Github ID: [holguinj|https://github.com/holguinj] * [Pull Request 1046 Discussion|https://github.com/puppetlabs/puppetdb/pull/1046] * [Pull Request 1046 File Diff|https://github.com/puppetlabs/puppetdb/pull/1046/f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title Lindsey Smith PO commented on an issue Re: Provide means to request events from latest report in timeframe Ping Deepak Giridharagopal Add Comment PuppetDB / PDB-112 Provide means to request events from latest report in timeframe h2. Summary Implement something like a {{latest-report-before}} query for the Events endpoint. This is necessary in order to enable the user experience / feature request described in [PE-1906|https://jira.puppetlabs.com/browse/PE-1906?focusedCommentId=20630&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-20630]. h2. Des... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3059) add support for crlDistributionPoint
Title: Message Title rk created an issue Puppet / PUP-3059 add support for crlDistributionPoint Issue Type: Improvement Assignee: Unassigned Created: 14/Aug/14 8:12 AM Priority: Normal Reporter: rk we are re-using Puppet's PKI for additional services (notably per-node HTTPS). we would like the ability to embed crlDistributionPoint into the certificates so well-formed clients will be able to fetch the CRL. I've found csr_attributes.yaml but the CA does not sign using those attributes. ideally, the CA would be configured to add/remove specific extended attributes, minimizing the amount of configuration data that needs distributed to clients. hosting the CRL is out-of-scope: we will probably simply symlink it to /var/www and host it via apache on the Puppetmaster. Add Comment
Jira (PUP-2994) puppet parser validate shouldn't puke on exported resources
Title: Message Title Henrik Lindberg commented on an issue Re: puppet parser validate shouldn't puke on exported resources It is supposed to be a warning and do what the message says. I referred to it as an error, that was wrong. henrik Add Comment Puppet / PUP-2994 puppet parser validate shouldn't puke on exported resources {code} [root@master /etc/puppetlabs/puppet/modules/hosts]# puppet parser validate manifests/init.pp Warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 25 in file /etc/puppetlabs/puppet/modules/hosts/manifests/init.pp {code} This kinda makes {{puppet parser validate}} really non user ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppe
Jira (PDB-826) puppetdb-ssl-setup doesn't work out of the box
Title: Message Title Kenneth Barber commented on an issue Re: puppetdb-ssl-setup doesn't work out of the box PR is here: https://github.com/puppetlabs/puppetdb/pull/1045 Add Comment PuppetDB / PDB-826 puppetdb-ssl-setup doesn't work out of the box This line means that the script won't work if PuppetDB is not in your path. Like, say it's in {{/opt/puppet/sbin/}}, for example. {code} exec puppetdb "${subcommand}" "$@" {code} This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-826) puppetdb-ssl-setup doesn't work out of the box
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-826 puppetdb-ssl-setup doesn't work out of the box Change By: Kenneth Barber Affects Version/s: 1.6.3 Fix Version/s: 2.2.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-826) puppetdb-ssl-setup doesn't work out of the box
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-826 puppetdb-ssl-setup doesn't work out of the box Change By: Kenneth Barber Sprint: 20140813 to 20140827 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-826) puppetdb-ssl-setup doesn't work out of the box
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-826 puppetdb-ssl-setup doesn't work out of the box Change By: Kenneth Barber Assignee: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-824) PR (1042): (docs) Change some old URLs, remove mentions of inventory service. - nfagerlund
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-824 PR (1042): (docs) Change some old URLs, remove mentions of inventory service. - nfagerlund Change By: Kenneth Barber Fix Version/s: 2.2.0 Fix Version/s: 2.1.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-825) PR (1044): DOCUMENT-97: Mention updating puppetdb module - holguinj
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-825 PR (1044): DOCUMENT-97: Mention updating puppetdb module - holguinj Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-823) Remove saucy from build_defaults.yaml
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-823 Remove saucy from build_defaults.yaml Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-823) Remove saucy from build_defaults.yaml
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-823 Remove saucy from build_defaults.yaml Change By: Kenneth Barber Fix Version/s: 2.2.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.