Jira (PUP-2576) Implement behavioral change in the crontab provider to allow more drastic purging
Title: Message Title Josh Cooper commented on an issue Re: Implement behavioral change in the crontab provider to allow more drastic purging Felix Frank the deprecation warning should be removed in the puppet-4 branch now Add Comment Puppet / PUP-2576 Implement behavioral change in the crontab provider to allow more drastic purging See PUP-1381 for details on the bug being fixed. This new ticket was created to track the fix itself vs. adding a warning about the change. 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-2576) Implement behavioral change in the crontab provider to allow more drastic purging
Title: Message Title Josh Cooper commented on an issue Re: Implement behavioral change in the crontab provider to allow more drastic purging I'm not sure if removing the deprecation warning means reverting commit https://github.com/puppetlabs/puppet/commit/dfe0887ecd6b37157c7dbcc48486d138a8153851 or just removing the deprecation_warning? Add Comment Puppet / PUP-2576 Implement behavioral change in the crontab provider to allow more drastic purging See PUP-1381 for details on the bug being fixed. This new ticket was created to track the fix itself vs. adding a warning about the change. 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-514) Add optional type to parameters
Title: Message Title
Josh Cooper commented on an issue
Re: Add optional type to parameters
Henrik Lindberg can you provide more details about how to verify this ticket?
Add Comment
Puppet / PUP-514
Add optional type to parameters
It is of great value to be able to optionally type the parameters of defines and classes (as well as types). This is quite easy to implement as there now is a type system. The default type is Optional[Variant[Object,Type]] i.e. anything To optionally type a parameter simply enter the type before the parameter: {code} define foo(String $x, Integ...
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-2576) Implement behavioral change in the crontab provider to allow more drastic purging
Title: Message Title Felix Frank commented on an issue Re: Implement behavioral change in the crontab provider to allow more drastic purging Well, there is a desire to support this style of deprecation in Type code. However, it introduces cost to the manifest compilation for all users, where only few will benefit from it, and for many versions, none will, when no types actually emit any deprecation warnings. That is actually the norm. I'm torn, leaning towards removing the code. Add Comment Puppet / PUP-2576 Implement behavioral change in the crontab provider to allow more drastic purging See PUP-1381 for details on the bug being fixed. This new ticket was created to track the fix itself vs. adding a warning about the change. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-2789) Windows : group creation not working and cause agent to fail
Title: Message Title Clement XaT created an issue Puppet / PUP-2789 Windows : group creation not working and cause agent to fail Issue Type: Bug Affects Versions: 3.6.2, 3.6.1 Assignee: Unassigned Attachments: puppet.bug.170614.tar.gz Created: 17/Jun/14 2:36 AM Environment: Xubuntu 14.04 for puppetmaster, Win7Entreprise64b for client Labels: windows Priority: Blocker Reporter: Clement XaT Managing windows group doesn't working on my configuration. I don't know why. I tried to purge everything and start from fresh : first attemps worked (just the + group creation) then i worked a little about my manifests/modules with minimal code then error is back. Client side log : http://pastebin.com/XQ5yAYSF# Server side log :
Jira (PUP-2789) Windows : group creation not working and cause agent to fail
Title: Message Title Clement XaT updated an issue Puppet / PUP-2789 Windows : group creation not working and cause agent to fail Change By: Clement XaT Managingwindowsgroupdoesn'tworkingonmyconfiguration.Idon'tknowwhy.Itriedtopurgeeverythingandstartfromfresh:firstattempsworked(justthe+groupcreation)theniworkedalittleaboutmymanifests/moduleswithminimalcodethenerrorisback. [gist]https://gist.github.com/XaaT/8ba53baf51cedc85e71c Clientsidelog:http://pastebin.com/XQ5yAYSF#Serversidelog:http://pastebin.com/j4KcJUtC# 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-2789) Windows : group creation not working and cause agent to fail
Title: Message Title Clement XaT updated an issue Puppet / PUP-2789 Windows : group creation not working and cause agent to fail Change By: Clement XaT Managingwindowsgroupdoesn'tworkingonmyconfiguration.Idon'tknowwhy.Itriedtopurgeeverythingandstartfromfresh:firstattempsworked(justthe+groupcreation)theniworkedalittleaboutmymanifests/moduleswithminimalcodethenerrorisback. Ithinkthegroupcreationgoingbadbecauseof..idon'tknowandsendingwrongthingtopuppetagent(theCouldnotevaluate:Puppet::Util::Logrequiresamessage)whichsendniltosomewhatwhichendedbymetricnamenilisnotastring.. [gist]https://gist.github.com/XaaT/8ba53baf51cedc85e71cClientsidelog:http://pastebin.com/XQ5yAYSF#Serversidelog:http://pastebin.com/j4KcJUtC# 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-571) Error messages with IPv6-enabled interfaces.
Title: Message Title
redmine.exporter created an issue
Facter / FACT-571
Error messages with IPv6-enabled interfaces.
Issue Type:
Bug
Assignee:
Eric Sorenson
Created:
17/Jun/14 4:35 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
pre cabbage ~ # facter --puppet no such file to load – ldap ifconfig: status: SIOCGLIFFLAGS: bge0:1: no such interface ifconfig: status: SIOCGLIFFLAGS: bge0:1: no such interface ifconfig: status: SIOCGLIFFLAGS: bge0:1: no such interface ifconfig: status: SIOCGLIFFLAGS: bge0:1: no such interface ifconfig: status: SIOCGLIFFLAGS: bge0:1: no such interface /pre
A workaround would be to skip the IPv6 interface names:
precode class=diff index 9fb7034..748bb1d 100644 — a/lib/facter/util/ip.rb +++ b/lib/facter/util/ip.rb @@ -59,7 +59,7 @@ module Facter::Util::IP when 'Linux', 'OpenBSD', 'NetBSD', 'FreeBSD', 'Darwin' output = %x {/sbin/ifconfig -a}
when 'SunOS'
output = %x {/usr/sbin/ifconfig -a}
+ output = %x {/usr/sbin/ifconfig -a4}
end output end /code/pre
Jira (FACT-571) Error messages with IPv6-enabled interfaces.
Title: Message Title Andreas Schuster commented on an issue Re: Error messages with IPv6-enabled interfaces. Issue still exists on facter 1.7.5 and newer on Solaris 11.1: mysystem# facter ifconfig: status: SIOCGLIFFLAGS: ipmp0:1: no such interface ifconfig: status: SIOCGLIFFLAGS: ipmp0:1: no such interface ifconfig: status: SIOCGLIFFLAGS: ipmp0:1: no such interface ifconfig: status: SIOCGLIFFLAGS: ipmp0:1: no such interface ifconfig: status: SIOCGLIFFLAGS: ipmp0:1: no such interface ifconfig: status: SIOCGLIFFLAGS: ipmp0:1: no such interface ... interfaces = vnet0,vnet1,vnet2,lo0,ipmp0,ipmp1,ipmp0_1 ipaddress = 5.79.50.233 ipaddress6 = :: ipaddress_ipmp0 = 5.79.50.33 ipaddress_ipmp1 = 5.77.50.33 ipaddress_lo0 = 127.0.0.1 ipaddress_vnet0 = 0.0.0.0 ipaddress_vnet1 = 0.0.0.0 ipaddress_vnet2 = 5.79.50.233 ... netmask = 255.255.254.0 netmask_ipmp0 = 255.255.254.0 netmask_ipmp1 = 255.255.254.0 netmask_lo0 = 255.0.0.0 netmask_vnet0 = 255.0.0.0 netmask_vnet1 = 255.0.0.0 netmask_vnet2 = 255.255.254.0 network_ipmp0 = 5.79.50.0 network_ipmp1 = 5.77.50.0 network_lo0 = 127.0.0.0 network_virtual = ldom network_vnet0 = 0.0.0.0 network_vnet1 = 0.0.0.0 network_vnet2 = 5.79.50.0 ... Output of ifconfig -a: vnet0: flags=11000843UP,BROADCAST,RUNNING,MULTICAST,IPv4,PHYSRUNNING mtu 1500 index 4 inet 0.0.0.0 netmask ff00 broadcast 0.255.255.255 groupname ipmp0 ether 0:14:4f:fa:95:cd vnet1: flags=11000843UP,BROADCAST,RUNNING,MULTICAST,IPv4,PHYSRUNNING mtu 1500 index 6 inet 0.0.0.0 netmask ff00 broadcast 0.255.255.255 groupname ipmp1 ether 0:14:4f:f8:18:f3 vnet2: flags=11000843UP,BROADCAST,RUNNING,MULTICAST,IPv4,PHYSRUNNING mtu 1500 index 1 inet 5.79.50.233 netmask fe00 broadcast 5.79.51.255 ether 0:14:4f:f8:a7:2f lo0: flags=2001000849UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL mtu 8232 index 2 inet 127.0.0.1 netmask ff00 ipmp0: flags=108001000843UP,BROADCAST,RUNNING,MULTICAST,IPv4,IPMP,PHYSRUNNING mtu 1500 index 3 inet 5.79.50.33 netmask fe00 broadcast 5.79.51.255 groupname ipmp0 ipmp1: flags=108001000843UP,BROADCAST,RUNNING,MULTICAST,IPv4,IPMP,PHYSRUNNING mtu 1500 index 5 inet 5.77.50.33 netmask fe00 broadcast 5.77.51.255 groupname ipmp1 lo0: flags=2002000849UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL mtu 8252 index 2 inet6 ::1/128 ipmp0: flags=128002004841UP,RUNNING,MULTICAST,DHCP,IPv6,IPMP,PHYSRUNNING mtu 1500 index 3 inet6 fe80::21ee:52aa:adc9:5c49/10 groupname ipmp0 ipmp0:1: flags=128002000841UP,RUNNING,MULTICAST,IPv6,IPMP,PHYSRUNNING mtu 1500 index 3 inet6 fd00:4711:815:1234:abcd::33/64 ipmp1: flags=128002000840RUNNING,MULTICAST,IPv6,IPMP,PHYSRUNNING mtu 1500 index 5 inet6 ::/10 groupname ipmp1 vnet0: flags=120002000841UP,RUNNING,MULTICAST,IPv6,PHYSRUNNING mtu 1500 index 4 inet6 ::/0 groupname ipmp0 ether 0:14:4f:fa:95:cd vnet1: flags=120002000841UP,RUNNING,MULTICAST,IPv6,PHYSRUNNING mtu 1500 index 6 inet6 ::/0 groupname ipmp1 ether 0:14:4f:f8:18:f3 vnet2: flags=120002000840RUNNING,MULTICAST,IPv6,PHYSRUNNING mtu 1500 index 1 inet6 ::/10 ether 0:14:4f:f8:a7:2f
Jira (PUP-2789) Windows : group creation not working and cause agent to fail
Title: Message Title Clement XaT updated an issue Puppet / PUP-2789 Windows : group creation not working and cause agent to fail Change By: Clement XaT Managingwindowsgroupdoesn'tworkingonmyconfiguration.Idon'tknowwhy.Itriedtopurgeeverythingandstartfromfresh:firstattempsworked(justthe+groupcreation)theniworkedalittleaboutmymanifests/moduleswithminimalcodethenerrorisback.Ithinkthegroupcreationgoingbadbecauseof..idon'tknowandsendingwrongthingtopuppetagent(theCouldnotevaluate:Puppet::Util::Logrequiresamessage)whichsendniltosomewhatwhichendedbymetricnamenilisnotastring..[gist]https://gist.github.com/XaaT/8ba53baf51cedc85e71cClientsidelog:http://pastebin.com/XQ5yAYSF#Serversidelog:http://pastebin.com/j4KcJUtC# Server:x64xubuntu14.04uptodatewith3.6.2puppetmaster,alllastversionsofpuppet/facter/etcfoundontheaptrepoClient:x64win7entreprisewithlastversionsofpuppet3.6.2andfacteretcI'montheircatXaT,pleaseHLmeifyouwantmoreinformations. 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-2789) critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc)
Title: Message Title Clement XaT updated an issue Puppet / PUP-2789 critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc) Change By: Clement XaT Summary: Windows criticalbug,windowsagent : cantdosomebasicstuff( groupcreation notworkingandcauseagenttofail ,packageinstallation,etc) 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-2579) ssh_authorized_key does not handle options with escaped double quotes
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2579 ssh_authorized_key does not handle options with escaped double quotes Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-514) Add optional type to parameters
Title: Message Title
Henrik Lindberg commented on an issue
Re: Add optional type to parameters
Lambdas
with(1, false, hello) | Integer $x, Boolean $y, String $z | { notice [$x, $y, $z] } # notice array of args
with(1, false, hello) | Data *$stuff | { notice $stuff } # notice array of args
with(1, 1, 1) | Boolean $x, Boolean $y, Boolean $z | { notice [$x, $y, $z] } # error
Similar for class, define and EPP (no splat support though).
define foo(Integer $x, Boolean $y, String $z) {
notice [$x, $y, $z]
}
foo { 'this-is-my-foo': $x = 1, $y = false, $z = hello }
# etc etc
Add Comment
Puppet / PUP-514
Add optional type to parameters
It is of great value to be able to optionally type the parameters of defines and classes (as well as types). This is quite easy to implement as there now is a type system. The default type is Optional[Variant[Object,Type]] i.e. anything To optionally type a parameter simply enter the type before the parameter: {code} define foo(String $x, Integ...
This message was sent by Atlassian JIRA
Jira (PUP-1060) enablerepo and disablerepo for yum type
Title: Message Title
Malte Krupa commented on an issue
Re: enablerepo and disablerepo for yum type
Hi,
currently I'm running 3.6.2 on master/agents and try to use this feature on CentOS 6.5 but no matter what I do, the agent ignores my install_options option.
I tried the following lines (also with ensure = installed and ' instead of ):
package {foo: ensure = latest, install_options = [{ --enablerepo = bar }] }
package {foo: ensure = latest, install_options = { --enablerepo = bar } }
package {foo: ensure = latest, install_options = [{ enablerepo = bar }] }
package {foo: ensure = latest, install_options = { enablerepo = bar } }
package {foo: ensure = latest, install_options = [{ --enablerepo=bar }] }
package {foo: ensure = latest, install_options = { --enablerepo=bar } }
package {foo: ensure = latest, install_options = [{ enablerepo=bar }] }
package {foo: ensure = latest, install_options = { enablerepo=bar } }
Did I miss something? Correct me if I'm wrong, but as far as I can see this should be available in 3.6.2 (8aaa17e6 is tagged with 3.6.2).
Thanks in advance for your effort.
Regards, Malte Krupa
Add Comment
Puppet / PUP-1060
enablerepo and disablerepo for yum type
it would be nice to be able to enable a disabled repo for the installation on one package. for example installing facter from EPEL. something like; {noformat} package { facter: ensure = installed, enablerepo = [ epel, epel-testing ]; } {noformat}
Jira (PUP-2271) yumrepo attributes cannot be set to '_none_'
Title: Message Title
Tim Sheppard commented on an issue
Re: yumrepo attributes cannot be set to '_none_'
Hi,
This is a big issue for us at the moment as we use the proxy = none to access repos that are behind our corporate firewall. The rest of the yum config sets global proxy variables in /etc/yum.conf so we cannot use {{proxy = absent }} as this uses the corporate proxy and cannot find our local repos.
Currently we have to hold all yum/rpm based hosts on 3.4.3 which is the last version that would allows us to do this.
Add Comment
Puppet / PUP-2271
yumrepo attributes cannot be set to '_none_'
The {{yumrepo}} attribute cannot be set to the value _none_ even though this is a supported value for the yum {{proxy}} parameter. We should fix this. {code} $ puppet apply -e yumrepo {'base': proxy = '_none_'} Notice: Compiled catalog for localhost.localdomain in environment production in 0.03 seconds Error: Parameter proxy failed on Yumrepo[b...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google
Jira (PUP-2789) critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc)
Title: Message Title Clement XaT updated an issue Puppet / PUP-2789 critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc) Change By: Clement XaT Managingwindowsgroupdoesn'tworkingonmyconfiguration.Idon'tknowwhy.Itriedtopurgeeverythingandstartfromfresh:firstattempsworked(justthe+groupcreation)theniworkedalittleaboutmymanifests/moduleswithminimalcodethenerrorisback.Ithinkthegroupcreationgoingbadbecauseof..idon'tknowandsendingwrongthingtopuppetagent(theCouldnotevaluate:Puppet::Util::Logrequiresamessage)whichsendniltosomewhatwhichendedbymetricnamenilisnotastring..[gist]https://gist.github.com/XaaT/8ba53baf51cedc85e71cClientsidelog:http://pastebin.com/XQ5yAYSF#Serversidelog:http://pastebin.com/j4KcJUtC#Server:x64xubuntu14.04uptodatewith3.6.2puppetmaster,alllastversionsofpuppet/facter/etcfoundontheaptrepoClient:x64win7entreprisewithlastversionsofpuppet3.6.2andfacteretcI'montheircatXaT,pleaseHLmeifyouwantmoreinformations. edit:buggingtoowithpackageinstallation.Ireproducebugwith3.6.2linuxpuppetmaster(xubuntu14.04)and3.6.0/3.6.1/3.6.2windowsagentwiththisconffiles:http://azora.fr:8080/archives/puppet.bug.170614-1.tar.gz(MINIMALCODE!Oneline.) 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-2789) critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc)
Title: Message Title Clement XaT updated an issue Puppet / PUP-2789 critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc) Change By: Clement XaT Managingwindowsgroupdoesn'tworkingonmyconfiguration.Idon'tknowwhy.Itriedtopurgeeverythingandstartfromfresh:firstattempsworked(justthe+groupcreation)theniworkedalittleaboutmymanifests/moduleswithminimalcodethenerrorisback.Ithinkthegroupcreationgoingbadbecauseof..idon'tknowandsendingwrongthingtopuppetagent(theCouldnotevaluate:Puppet::Util::Logrequiresamessage)whichsendniltosomewhatwhichendedbymetricnamenilisnotastring..[gist]https://gist.github.com/XaaT/8ba53baf51cedc85e71cClientsidelog:http://pastebin.com/XQ5yAYSF#Serversidelog:http://pastebin.com/j4KcJUtC#Server:x64 EN xubuntu14.04uptodatewith3.6.2puppetmaster,alllastversionsofpuppet/facter/etcfoundontheaptrepoClient:x64 FR win7entreprisewithlastversionsofpuppet3.6.2andfacteretcI'montheircatXaT,pleaseHLmeifyouwantmoreinformations.edit:buggingtoowithpackageinstallation.Ireproducebugwith3.6.2linuxpuppetmaster(xubuntu14.04)and3.6.0/3.6.1/3.6.2windowsagentwiththisconffiles:http://azora.fr:8080/archives/puppet.bug.170614-1.tar.gz(MINIMALCODE!Oneline.) edit:addingFRrelativetowin7e 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
Jira (PUP-2755) Move iterative functions to 4x function API
Title: Message Title Henrik Lindberg commented on an issue Re: Move iterative functions to 4x function API Doc-stubs added (for all 4x functions). Comments from merge review fixed. Also removed special handling of the iterative functions since the new API does not transform arguments (the 3x_runtime had special check for the iterative functions - that is now removed). Add Comment Puppet / PUP-2755 Move iterative functions to 4x function API The iterative functions (each, map, filter, reduce, slice) should be moved to the 4x function API. (Currently there is a cheat implemented in the evaluator when these are called to avoid having the arguments transformed to the 3x function API). 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-567) Support Bundler workflow on x64
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Facter / FACT-567 Support Bundler workflow on x64 Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2755) Move iterative functions to 4x function API
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2755 Move iterative functions to 4x function API Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2790) if initctl --version doesn't list a matching string, upstart service provider fails badly.
Title: Message Title Sven Mueller created an issue Puppet / PUP-2790 if initctl --version doesn't list a matching string, upstart service provider fails badly. Issue Type: Bug Affects Versions: 3.4.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 17/Jun/14 9:26 AM Environment: Ubuntu 14.04 Priority: Normal Reporter: Sven Mueller We are running puppet during the installation process, using Debian installers late_command option. At this point, calling status avahi-daemon returns: - cut here - Warning: Fake initctl called, doing nothing. - cut here - (As does any other call to initctl, such as initctl list) Unfortunately, I was unable to determine if this was on STDOUT or (partially) on STDERR, because it was replaced in the meantime by the standard initctl from upstart. However, that output causes this: 17 Jun 2014 14:32:00 puppet.py:1289 DEBUG PUPPET: Debug: Executing '/sbin/status avahi-daemon' 17 Jun 2014 14:32:00 puppet.py:1289 DEBUG PUPPET: Error:
Jira (PUP-2790) if initctl --version doesn't list a matching string, upstart service provider fails badly.
Title: Message Title Sven Mueller updated an issue Puppet / PUP-2790 if initctl --version doesn't list a matching string, upstart service provider fails badly. Change By: Sven Mueller Affects Version/s: 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2790) if initctl --version doesn't list a matching string, upstart service provider fails badly.
Title: Message Title Sven Mueller updated an issue Puppet / PUP-2790 if initctl --version doesn't list a matching string, upstart service provider fails badly. Crude patch that fixes the issue I observed. However, it is probably not the best approach, since it simply assumes that if the provider is selected (has to happen manually in this case) and /sbin/initctl --version does not contain the right marker initctl (upstart, than the version of upstart is assumed to be post 2011-03-15 (and post the 0.9.0 release). Change By: Sven Mueller Attachment: puppet.patch Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.
Title: Message Title Kurt Wall commented on an issue Re: Puppet's v2 environment listing does not display config_version and environment_timeout as well. Joshua Partlow I figured it out. I did ruby ./install.rb --full, re-edited auth.conf, restarted the puppetmaster, and it worked. Verified at SHA=05dfc157fd8e36f5cd87868d6ad56c18cfc9a0b3. Add Comment Puppet / PUP-2426 Puppet's v2 environment listing does not display config_version and environment_timeout as well. We added config_version and environment_timeout settings to directory environment environment.conf. Puppet's v2 environments listing needs to show these environment parameters as well. (lib/puppet/network/http/api/v2/environments.rb) Will also need to update the API docs for v2.0/environments This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-2791) Incorrect EPP syntax in epp() function documentation
Title: Message Title Andy Parker created an issue Puppet / PUP-2791 Incorrect EPP syntax in epp() function documentation Issue Type: Bug Assignee: Andy Parker Components: DOCS, DSL Created: 17/Jun/14 10:13 AM Fix Versions: 3.7.0 Priority: Major Reporter: Andy Parker The current docs for epp() show the parameter declaration syntax as % ( parameters ) %. The real syntax uses pipes (|) instead of parentheses ((). Add Comment
Jira (PUP-2788) Puppet package source check fails with DFS share
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2788 Puppet package source check fails with DFS share Change By: Rob Reynolds Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.
Title: Message Title Kurt Wall updated an issue Puppet / PUP-2426 Puppet's v2 environment listing does not display config_version and environment_timeout as well. Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2788) Puppet package source check fails with DFS share
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2788 Puppet package source check fails with DFS share Change By: Rob Reynolds 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-2788) Puppet package source check fails with DFS share
Title: Message Title
Rob Reynolds commented on an issue
Re: Puppet package source check fails with DFS share
Kurt Gardiner can you try backslashes in your source instead? I think this leans to a documentation issue.
package { 'NetFx452':
ensure = installed,
source = '\\dfs_share\software\dotNetFx452_Full_x86_x64.exe',
install_options = ['/q'],
}
Add Comment
Puppet / PUP-2788
Puppet package source check fails with DFS share
{noformat} package { 'NetFx452': ensure = installed, source = '//dfs_share/software/dotNetFx452_Full_x86_x64.exe', install_options = ['/q'], } {noformat} fails with error {noformat} Error: The source does not exist: '//dfs_share/software/dotNetFx452_Full_x86_x64.exe' {noformat} Digging through th...
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
Jira (PUP-2791) Incorrect EPP syntax in epp() function documentation
Title: Message Title
Andy Parker updated an issue
Puppet / PUP-2791
Incorrect EPP syntax in epp() function documentation
Change By:
Andy Parker
Thecurrentdocsfor{{epp()}}showtheparameterdeclarationsyntaxas{{% \ -(parameters) \ -%}}.Therealsyntaxusespipes({{|}})insteadofparentheses({{(}}).
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-1568) Error reporting within augeas provider fails
Title: Message Title
Adrien Thebo commented on an issue
Re: Error reporting within augeas provider fails
Looking at the second error indicates that the lens you're trying to use is malformed, and the augeas bindings don't try to take account for that. It looks like the original ticket was dealing with a different problem so I think you should open a new ticket reporting that the augeas provider doesn't emit errors that occurred while trying to parse a lens.
Add Comment
Puppet / PUP-1568
Error reporting within augeas provider fails
If the augeas provider fails to store a change to a file it's error reporting is broken due to the refactoring that happened in https://github.com/puppetlabs/puppet/commit/000b8fef6a33e5c9f56c0801523de15a0e5bc30b {noformat} # cat foo.pp augeas{'enable_shorewall': context = '/files/etc/sysconfig/shorewall', changes = 'set startup 1', lens ...
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
Jira (PUP-2789) critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2789 critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc) Change By: Josh Cooper Assignee: ClementXaT 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-2789) critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2789 critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc) Change By: Josh Cooper Component/s: TypesandProviders 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-2789) critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc)
Title: Message Title Josh Cooper commented on an issue Re: critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc) Clement XaT I'm having difficulty understanding what issue you are reporting. Please provide more information than cant do some basic stuff. From your error logs, it looks like you are trying to apply a set of different modules. Can you narrow this down to a specific module? We will need a sample manifest that demonstrates the issue. If you can reproduce the problem in a simple scenario, please run `puppet agent -td --trace` and attach the backtrace to this ticket. I'm assigning this to you for more information. Add Comment Puppet / PUP-2789 critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc) Managing windows group doesn't working on my configuration. I don't know why. I tried to purge everything and start from fresh : first attemps worked (just the + group creation) then i worked a little about my manifests/modules with minimal code then error is back. I think the group creation going bad because of.. i don't know and sending wrong thi... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2789) critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2789 critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc) Change By: Josh Cooper Priority: Blocker Normal 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-2793) Failed to apply catalog: incompatible character encodings: UTF-8 and ASCII-8BIT
Title: Message Title Christopher Timm created an issue Puppet / PUP-2793 Failed to apply catalog: incompatible character encodings: UTF-8 and ASCII-8BIT Issue Type: Bug Affects Versions: 3.3.3 Assignee: Kylo Ginsberg Components: Catalog Application Created: 17/Jun/14 11:03 AM Environment: Puppet 3.3.3 (Puppet Enterprise 3.1.1) OS: SLES 11.3 Priority: Normal Reporter: Christopher Timm Hello guys, I ran into a nasty issue that i can't really get a hold of. So we use puppet to setup java and wildfly and afterwards deploy (actually just ensure= present) an ear-file in the deployment directory of wildfly. The ear-File is downloaded from artifactory using a slightly modified version of this module: https://forge.puppetlabs.com/jcraigbrown/artifactory The problem is, that running via command line works fine, but when running via the pe-puppet service or a cronjob it will look just fine until the very end, where it fails with the error: Failed to apply catalog: incompatible
Jira (PUP-1046) puppet module generate should produce a skeleton spec test
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-1046 puppet module generate should produce a skeleton spec test Change By: Kenn Hussey Sprint: Week2014-7-2to2014-7-9 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-1046) puppet module generate should produce a skeleton spec test
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-1046 puppet module generate should produce a skeleton spec test Change By: Kenn Hussey Sprint: Week2014- 7 6 - 2 18 to2014- 7 6 - 9 25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2791) Incorrect EPP syntax in epp() function documentation
Title: Message Title Andy Parker updated an issue Puppet / PUP-2791 Incorrect EPP syntax in epp() function documentation Change By: Andy Parker Sprint: Week2014-6-11to2014-6-18 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-2794) Specify signatures for blocks of block-accepting methods
Title: Message Title Andy Parker created an issue Puppet / PUP-2794 Specify signatures for blocks of block-accepting methods Issue Type: Improvement Assignee: Andy Parker Components: DSL Created: 17/Jun/14 11:38 AM Fix Versions: 3.7.0 Priority: Normal Reporter: Andy Parker Since PUP-2755, the iteration functions are implemented using the new function API, which allows specifying dispatches on parameter types, as well as the signature of the block that is accepted. However, the current implementation doesn't specify the block's signature and leaves at the default of Callable[Object]. Ideally the block signature should be specified so that we can more completely control and specify the signature. Specifying a more specific signature would also unify all of the signature mismatch error reporting in the same system. In most cases the accepted signature is mostly Callable[Object, 1, 2]. The problem is the mostly. We also test that you can call the iteration functions with a block that has a signature of |*$x|. This signature is often treated as the same has having passed two arguments (Callable[Object, Object, 2, 2]), but that isn't how the type system interprets it (Callable[Object]). This mismatch means that in order to apply type signatures for these blocks either the Callable type will need to be modified somehow (I'm not sure how), or support needs to be dropped for using capture
Jira (PUP-2794) Specify signatures for blocks of block-accepting methods
Title: Message Title
Andy Parker commented on an issue
Re: Specify signatures for blocks of block-accepting methods
I made the change as an experiment. Most of the failures that I got from the spec tests were simply that the error message changed. There were one or two that show the problem that this ticket is about deciding on.
Failure in spec/unit/functions/reduce_spec.rb:41
8) the reduce method should be callable as reduce on an array with captures rest in lambda
Failure/Error: catalog = compile_to_catalog(-MANIFEST)
Puppet::Error:
Evaluation Error: Error while evaluating a Method call, function 'reduce' called with mis-matched arguments
expected one of:
reduce(Object enumerable, Callable[Object, Object] block) - arg count {2}
reduce(Object enumerable, Object memo, Callable[Object, Object] block) - arg count {3}
actual:
reduce(Tuple[Integer, Integer, Integer], Callable[Object]) - arg count {2} at line 2:16 on node foonode
Add Comment
Puppet / PUP-2794
Specify signatures for blocks of block-accepting methods
Since PUP-2755, the iteration functions are implemented using the new function API, which allows specifying dispatches on parameter types, as well as the signature of the block that is accepted. However, the current implementation doesn't specify the block's signature and leaves at the default of {{Callable[Object]}}. Ideally the block signature should...
Jira (PUP-2423) Filebucket server should warn, not fail, if checksum type is not supported
Title: Message Title
Adrien Thebo commented on an issue
Re: Filebucket server should warn, not fail, if checksum type is not supported
I've split out the file_metadata issue into PUP-2795.
Add Comment
Puppet / PUP-2423
Filebucket server should warn, not fail, if checksum type is not supported
PUP-1840 allows users to specify the digest algorithm to use for file bucketing and the file checksum parameter. However, if you reconfigure the master to use SHA256: {noformat} [main] digest_algorithm=sha256 {noformat} Then it will reject file bucket requests from agents that haven't switched over: {noformat} # puppet agent -td ... Error: ...
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-2795) `digest_algorithm` mismatch between Puppet master and agent breaks file idempotency
Title: Message Title
Adrien Thebo created an issue
Puppet / PUP-2795
`digest_algorithm` mismatch between Puppet master and agent breaks file idempotency
Issue Type:
Bug
Affects Versions:
3.6.0
Assignee:
Unassigned
Created:
17/Jun/14 11:58 AM
Fix Versions:
3.7.0
Priority:
Normal
Reporter:
Adrien Thebo
When a Puppet master and agent have mismatched digest algorithms, the master may return file metadata that that doesn't match the agent digest algorithm. This means that file contents behave like they're constantly out of sync:
Notice: /Stage[main]/Main/Node[default]/File[/tmp/unbucketed-file]/content: content changed '{md5}9cf25922ced56ba90c987e4c31c51927' to '{sha256}cf77e2dfbdb2a001f9daac15548d611b14f51f2f69793be6fd203d105d1b3e1b'
When the master can respect the digest algorithm specified by the agent, it should try to use the digest algorithm specified in the metadata request. If the agent tries to use a digest algorithm that the master does not allow, the metadata request should fail.
Jira (PUP-2755) Move iterative functions to 4x function API
Title: Message Title Andy Parker commented on an issue Re: Move iterative functions to 4x function API Merged into master in cc13e1. Add Comment Puppet / PUP-2755 Move iterative functions to 4x function API The iterative functions (each, map, filter, reduce, slice) should be moved to the 4x function API. (Currently there is a cheat implemented in the evaluator when these are called to avoid having the arguments transformed to the 3x function API). This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1057) Remove 'collect' and 'select' iterative function stubs
Title: Message Title Andy Parker commented on an issue Re: Remove 'collect' and 'select' iterative function stubs Merged into master in cc13e1. Add Comment Puppet / PUP-1057 Remove 'collect' and 'select' iterative function stubs The functions 'select' and 'collect' are currently stubs that raise an error (to help those using the future parser from 3.5 migrate their code). In 4.0.0 those stubs should be removed. 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-2791) Incorrect EPP syntax in epp() function documentation
Title: Message Title
Andy Parker commented on an issue
Re: Incorrect EPP syntax in epp() function documentation
This was found and fixed while reviewing PUP-2755.
Merged into master in cc13e1.
Add Comment
Puppet / PUP-2791
Incorrect EPP syntax in epp() function documentation
The current docs for {{epp()}} show the parameter declaration syntax as {{%\-( parameters )\-%}}. The real syntax uses pipes ({{|}}) instead of parentheses ({{(}}).
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-567) Support Bundler workflow on x64
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Facter / FACT-567 Support Bundler workflow on x64 Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2795) `digest_algorithm` mismatch between Puppet master and agent breaks file idempotency
Title: Message Title
Josh Cooper commented on an issue
Re: `digest_algorithm` mismatch between Puppet master and agent breaks file idempotency
dup of PUP-2427?
Add Comment
Puppet / PUP-2795
`digest_algorithm` mismatch between Puppet master and agent breaks file idempotency
When a Puppet master and agent have mismatched digest algorithms, the master may return file metadata that that doesn't match the agent digest algorithm. This means that file contents behave like they're constantly out of sync: {noformat} Notice: /Stage[main]/Main/Node[default]/File[/tmp/unbucketed-file]/content: content changed '{md5}9cf25922ced56ba...
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-567) Support Bundler workflow on x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Support Bundler workflow on x64
Steps to generate the gem:
bundle install --path .bundle/gems
bundle exec rake package:implode #this may not be needed
bundle exec rake package:bootstrap
bundle exec rake package:gem
Add Comment
Facter / FACT-567
Support Bundler workflow on x64
Facter expresses Windows gem dependencies, but it only applies to ruby x86. When running on x64, the gem dependencies do not apply, so you can't use bundler to install gems, and run specs. Currently, facter's Gemfile uses the bundler `mingw` platform identifier, effectively: {noformat} platform :mingw do gem 'ffi' ... end {noformat} {{Bu...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-2796) Puppet always modifies nagios check commands
Title: Message Title
Brian Rak created an issue
Puppet / PUP-2796
Puppet always modifies nagios check commands
Issue Type:
Bug
Affects Versions:
3.6.0
Assignee:
Unassigned
Created:
17/Jun/14 12:26 PM
Priority:
Normal
Reporter:
Brian Rak
I have a number of exported nagios service entries that end up getting recreated on every Puppet run. I see this in the logs:
Notice: /Stage[main]/Icinga::Install/Nagios_service[check_http_auswindowsmirror.example.com_windowsmirror.example.com]/check_command: check_command changed 'check_http!10.0.0.1!windowsmirror.example.com!80!-4' to 'check_http!10.0.0.1!windowsmirror.example.com!80!-4 '
The relevant part of the nagios config:
define service { ## --PUPPET_NAME-- (called '_naginator_name' in the manifest) check_http_auswindowsmirror.vultr.com_windowsmirror.example.com check_command check_http!10.0.0.1!windowsmirror.example.com!80!-4 host_name auswindowsmirror.example.com service_description HTTP on windowsmirror.example.com:80 use generic-service }
In the manifest, it's defined like this:
@@nagios_service { check_http_${::clientcert}_$ {name}: check_command = check_http!${monitorip}!${name}
!$ {port}!-4 ${monitorargs}, host_name = $::clientcert, use = 'generic-service', service_description = HTTP on ${name}:${port}
, }
Running puppet in debug mode doesn't produce any further output about why it thinks those two check commands are different.
Jira (PUP-839) FFI Puppet::Util::Windows::Security module
Title: Message Title
Ethan Brown commented on an issue
Re: FFI Puppet::Util::Windows::Security module
Ready for review Josh Cooper.
I have a few notes in there for additional comment.
Phew.. this one was a longer one...
Add Comment
Puppet / PUP-839
FFI Puppet::Util::Windows::Security module
Use FFI to define and invoke Windows APIs. Always call the wide-version, where applicable, e.g. CreateFileW. Also don't do things like: {code} def supports_acl?(path) flags = 0.chr * 4 {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1417) puppet parser not order independent
Title: Message Title Trevor Vaughan commented on an issue Re: puppet parser not order independent Is this something that could be targeted for the future parser? It would be a shame to have all this work done and then have these types of things hanging around. Add Comment Puppet / PUP-1417 puppet parser not order independent The puppet parser has number of issues regarding order-of evaluation: * It does not always ensure that included classes are evaluated before qualified variables referring to them are evaluated. ([[LanguageTutorial#qualified-variables]]) * It may evaluate classes before the scope in which they are defined is evaluated. * the defined() function is unf... 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-675) init.d script silently fails if PIDfile is missing
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-675 init.d script silently fails if PIDfile is missing Change By: Kenneth Barber Assignee: KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-2700
Puppet 3.6.1 File recurse improperly handles spaces in filenames
Notes for functional review:
The issue exposed here is that file resources with a source URI that contains reserved characters are double encoded. The issue only shows up under Puppet 3.6.0 – 3.6.2 and only causes a failure when the Puppet Master is running under Passenger.
Attached to this ticket is a test module, test_url_encode, that contains a bunch of files named with reserved characters. Adding the following to a node definition will trigger a recursive copy of the files to /tmp/test_url_encode:
class{test_url_encode:}
Under Puppet 3.6.0 – 3.6.2, the agent should fail to copy the files listed in my comment from June 11th. After updating to a version of Puppet containing commit 591198c, char_63_question_mark?.txt should be the only file that fails to transfer.
Change By:
Charlie Sharpsteen
Attachment:
test-test_url_encode-0.1.0.tar.gz
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2579) ssh_authorized_key does not handle options with escaped double quotes
Title: Message Title
Kurt Wall commented on an issue
Re: ssh_authorized_key does not handle options with escaped double quotes
Josh Cooper When I try to apply the manifest in the description, I get a syntax error. It looks like this is blocked on PUP-2727.
# git log -1
commit 318d5f7da5728cee7a063548eae58ac0d1775bc9
Merge: cc13e18 6d47ff6
Author: Peter Huene peterhu...@gmail.com
Date: Tue Jun 17 13:12:37 2014 -0700
Merge pull request #2666 from ffrank/maint/eliminate-type-doc-todos
(maint) Resolve some documentation TODOs in Puppet::Type
# bundle exec puppet apply --parser future ../x.pp
Error: Could not parse for environment production: Syntax error at 'type' at /root/x.pp:6:5 on node centos6-5-base.localdomain
Error: Could not parse for environment production: Syntax error at 'type' at /root/x.pp:6:5 on node centos6-5-base.localdomain
# bundle exec puppet apply --parser current ../x.pp
Warning: Future reserved word: type. Either choose a different name or quote the string, if possible. In /root/x.pp:6. See http://links.puppetlabs.com/reserved-words-4
(at /root/puppet/lib/puppet/parser/lexer.rb:615:in `warn_if_reserved')
Notice: Compiled catalog for centos6-5-base.localdomain in environment production in 0.07 seconds
Notice: Finished catalog run in 0.03 seconds
Add Comment
Puppet / PUP-2579
ssh_authorized_key does not handle options with escaped double quotes
With the following declaration: {code} ssh_authorized_key { 'title': user = 'root', ensure = 'present', name = 'mykey', options = [ 'command=/usr/local/bin/mybin \$SSH_ORIGINAL_COMMAND\' ], type = 'ssh-rsa', key = 'xxx', } {code} It creates the following entry: {code}command=/usr/local/bin/myb...
Jira (PUP-2796) Puppet always modifies nagios check commands
Title: Message Title
Brian Rak updated an issue
Puppet / PUP-2796
Puppet always modifies nagios check commands
Change By:
Brian Rak
IhaveanumberofexportednagiosserviceentriesthatendupgettingrecreatedoneveryPuppetrun.Iseethisinthelogs:Notice:/Stage[main]/Icinga::Install/Nagios_service[check_http_auswindowsmirror.example.com_windowsmirror.example.com]/check_command:check_commandchanged'check_http!10.0.0.1!windowsmirror.example.com!80!-4'to'check_http!10.0.0.1!windowsmirror.example.com!80!-4'Therelevantpartofthenagiosconfig:defineservice{##--PUPPET_NAME--(called'_naginator_name'inthemanifest)check_http_auswindowsmirror. vultr example .com_windowsmirror.example.comcheck_commandcheck_http!10.0.0.1!windowsmirror.example.com!80!-4host_nameauswindowsmirror.example.comservice_descriptionHTTPonwindowsmirror.example.com:80usegeneric-service}Inthemanifest,it'sdefinedlikethis:@@nagios_service{check_http_${::clientcert}_${name}:check_command=check_http!${monitorip}!${name}!${port}!-4${monitorargs},host_name=$::clientcert,use='generic-service',service_description=HTTPon${name}:${port},}Runningpuppetindebugmodedoesn'tproduceanyfurtheroutputaboutwhyitthinksthosetwocheckcommandsaredifferent.
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-2579) ssh_authorized_key does not handle options with escaped double quotes
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-2579 ssh_authorized_key does not handle options with escaped double quotes Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-392) Validate win32 gems on x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-392 Validate win32 gems on x64 Change By: Josh Cooper Sprint: Week2014-6- 18 25 to2014- 6 7 - 25 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-390) Modify build process to generate x86 and x64 versions of ruby
Title: Message Title Josh Cooper updated an issue Puppet / PUP-390 Modify build process to generate x86 and x64 versions of ruby Change By: Josh Cooper Sprint: Week2014- 6 7 - 25 2 to2014-7- 2 9 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-2727) Reserved keywords conflict with resource type parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2727 Reserved keywords conflict with resource type parameters Change By: Henrik Lindberg Sprint: Week2014-6-11to2014-6-18 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-569) Run Facter acceptance against ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Facter / FACT-569 Run Facter acceptance against ruby 2.0 x64 Change By: Josh Cooper Sprint: Week2014- 6 7 - 25 2 to2014-7- 2 9 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-2388) Run Puppet acceptance against ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2388 Run Puppet acceptance against ruby 2.0 x64 Change By: Josh Cooper Sprint: Week2014- 6 7 - 25 2 to2014-7- 2 9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2738) Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer
Title: Message Title Rob Reynolds commented on an issue Re: Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer I really restricted the memory on both a 32-bit box and a x64 box to try to get memory pressure issues to arise. So far it's just really slowed down the test time, but no memory failures yet. Will update once they are done Add Comment Puppet / PUP-2738 Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer As of the merge for PUP-2657, we've noticed some intermittent test failures (in both CI and locally) in semi-random locations. The merge commit is as follows: https://github.com/puppetlabs/puppet/commit/d38153bd712167e2777bdd4c63d37e2e8d1cdb39 The commit itself has been reviewed and it doesn't seem to have issues itself, but it's likely it's trigge... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-1362) Rubyize yumhelper.py to remove dependency on python
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1362 Rubyize yumhelper.py to remove dependency on python Change By: Kylo Ginsberg Fix Version/s: 3.7.0 Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2573) Puppet::Agent::Locker#lock doesn't return whether it acquired the lock or not
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2573 Puppet::Agent::Locker#lock doesn't return whether it acquired the lock or not Change By: Kylo Ginsberg Fix Version/s: 3.7.0 Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2349) Deprecate non-string modes on file type
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2349 Deprecate non-string modes on file type Change By: Kylo Ginsberg Component/s: TypesandProviders Component/s: DSL 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-572) add $::isPuppetMaster fact that supports cluster of Puppet Masters
Title: Message Title
Rodney Beede created an issue
Facter / FACT-572
add $::isPuppetMaster fact that supports cluster of Puppet Masters
Issue Type:
Improvement
Assignee:
Eric Sorenson
Created:
17/Jun/14 2:28 PM
Priority:
Minor
Reporter:
Rodney Beede
A fact should be available called $::isPuppetMaster that has a value of true when the catalog is being applied to a node that is a Puppet Master. false otherwise.
This should include all Puppet Masters that may exist in a cluster and not just a single Puppet Master.
Today I can detect a single Puppet Master with the following:
if $servername == $::fqdn { # do some specific action on the Puppet Master }
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2573) Puppet::Agent::Locker#lock doesn't return whether it acquired the lock or not
Title: Message Title
Adrien Thebo commented on an issue
Re: Puppet::Agent::Locker#lock doesn't return whether it acquired the lock or not
We don't plan on working on this in the immediate future so we're untargeting this from 3.7.0. If there's a pull request filed we can retarget this at 3.7.0 or 4.0.0 depending on when the PR is filed.
Add Comment
Puppet / PUP-2573
Puppet::Agent::Locker#lock doesn't return whether it acquired the lock or not
The [Puppet::Agent::Locker#lock|https://github.com/puppetlabs/puppet/blob/3.5.1/lib/puppet/agent/locker.rb] method documentation says {quote}Return true/false depending on whether we get the lock.{quote} But that's not actually what happens. Instead it returns whatever the yielded block returns. As a result, there's no way to know if the lock was successf...
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
Jira (PUP-2573) Puppet::Agent::Locker#lock doesn't return whether it acquired the lock or not
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2573 Puppet::Agent::Locker#lock doesn't return whether it acquired the lock or not Change By: Kylo Ginsberg Fix Version/s: 4.0.0 Fix Version/s: future 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-2579) ssh_authorized_key does not handle options with escaped double quotes
Title: Message Title
Josh Cooper commented on an issue
Re: ssh_authorized_key does not handle options with escaped double quotes
The future parser bug was present before this change. I don't think PUP-2727 should block this issue.
Add Comment
Puppet / PUP-2579
ssh_authorized_key does not handle options with escaped double quotes
With the following declaration: {code} ssh_authorized_key { 'title': user = 'root', ensure = 'present', name = 'mykey', options = [ 'command=/usr/local/bin/mybin \$SSH_ORIGINAL_COMMAND\' ], type = 'ssh-rsa', key = 'xxx', } {code} It creates the following entry: {code}command=/usr/local/bin/myb...
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-2797) Populate el7 dependencies directory with missing packages
Title: Message Title Marc Villacorta created an issue Puppet / PUP-2797 Populate el7 dependencies directory with missing packages Issue Type: Task Assignee: Unassigned Created: 17/Jun/14 2:33 PM Priority: Normal Reporter: Marc Villacorta Looks like there are some missing packages in: http://yum.puppetlabs.com/el/7/dependencies/x86_64/ For instance, to enable deeper merge behavior in 'hiera', I need the 'rubygem-deep-merge' package. Based on the 'el6' listing here: http://yum.puppetlabs.com/el/6/dependencies/x86_64/ ... I assume some packages slipped off. Add Comment
Jira (PUP-1638) Puppet 3.4.2 broken in OpenBSD
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Puppet 3.4.2 broken in OpenBSD
Re-produced with Puppet 3.4.2 and 3.6.2, both installed from gems. The OpenBSD Puppet package, version 3.4.2 installed via pkg_add, does not exhibit this behavior. I suspect there is a patch being carried in the source for the BSD port that resolves this issue.
However, figuring out how to pull the source of an OpenBSD port and examine the patches has proven to be a difficult, opaque process and I've given up trying. If anyone knows how to pull the source for the port or isolate the the patch, a pointer or pull request would be much appreciated!
Add Comment
Puppet / PUP-1638
Puppet 3.4.2 broken in OpenBSD
When running puppet agent -t --debug --trace I get the following error: {quote} Debug: Failed to load library 'selinux' for feature 'selinux' Debug: Using settings: adding file resource 'confdir': 'File[/etc/puppet]{:path=/etc/puppet, :ensure=:directory, :loglevel=:debug, :links=:follow, :backup=false}' Debug: Failed to load library 'shadow' f...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You
Jira (PUP-2797) Populate el7 dependencies directory with missing packages
Title: Message Title
Marc Villacorta updated an issue
Puppet / PUP-2797
Populate el7 dependencies directory with missing packages
Change By:
Marc Villacorta
Looksliketherearesomemissingpackagesin:{code:none}http://yum.puppetlabs.com/el/7/dependencies/x86_64/{code}Forinstance,toenabledeepermergebehaviorin_'hiera'_,Ineedthe_'rubygem-deep-merge'_package. Basedonthe equivalent _'el6'_ listing directory here : ... {code:none}http://yum.puppetlabs.com/el/6/dependencies/x86_64/{code}...Iassumesomepackagesslippedoff.
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-2576) Implement behavioral change in the crontab provider to allow more drastic purging
Title: Message Title
Kurt Wall commented on an issue
Re: Implement behavioral change in the crontab provider to allow more drastic purging
Unable to verify this in master at SHA=318d5f7da5728cee7a063548eae58ac0d1775bc9. Non-root crontabs are not purged:
resources { cron: purge = true, }
cron { 'jennyfoo':
command = 'date',
ensure = present,
user = jenny,
}
# crontab -l -u jenny
# HEADER: This file was autogenerated at Tue Jun 17 14:33:33 -0700 2014 by puppet.
# HEADER: While it can still be managed manually, it is definitely not recommended.
# HEADER: Note particularly that the comments starting with 'Puppet Name' should
# HEADER: not be deleted, as doing so could cause duplicate cron jobs.
# Puppet Name: jennyfoo
* * * * * date
# be puppet apply --verbose x.pp
Warning: Change notice: purging cron entries will be more aggressive in future versions, take care when updating your agents. See http://links.puppetlabs.com/puppet-aggressive-cron-purge
(at /root/puppet/lib/puppet/type/resources.rb:140:in `deprecate_params')
Notice: Compiled catalog for centos6-5-base.localdomain in environment production in 0.08 seconds
Info: Applying configuration version '1403041056'
Notice: Finished catalog run in 0.07 seconds
# puppet resource cron jennyfoo
cron { 'jennyfoo':
ensure = 'absent',
}
# crontab -l -u jenny
# HEADER: This file was autogenerated at Tue Jun 17 14:33:33 -0700 2014 by puppet.
# HEADER: While it can still be managed manually, it is definitely not recommended.
# HEADER: Note particularly that the comments starting with 'Puppet Name' should
# HEADER: not be deleted, as doing so could cause duplicate cron jobs.
# Puppet Name: jennyfoo
* * * * * date
Puppet clearly knows about the jennyfoo crontab, because it changes the attribute values successfully:
# be puppet apply -e cron { 'jennyfoo': command = 'whoami', ensure = present, user = jenny,}
Notice: Compiled catalog for centos6-5-base.localdomain in environment production in 0.07 seconds
Notice: /Stage[main]/Main/Cron[jennyfoo]/command: command changed 'date' to 'whoami'
Notice: Finished catalog run in 0.07 seconds
And I'm pretty sure I have current bits:
# git branch -v
* master 318d5f7 Merge pull request #2666 from ffrank/maint/eliminate-type-doc-todos
# git remote -v
origin git://github.delivery.puppetlabs.net/puppetlabs-puppet (fetch)
origin git://github.delivery.puppetlabs.net/puppetlabs-puppet (push)
Add Comment
Jira (PUP-2727) Reserved keywords conflict with resource type parameters
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2727 Reserved keywords conflict with resource type parameters Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-458) Implement changes for AIX Memory facts (already commited)
Title: Message Title Adrien Thebo updated an issue Facter / FACT-458 Implement changes for AIX Memory facts (already commited) Change By: Adrien Thebo Labels: backport redmine 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-458) Implement changes for AIX Memory facts (already commited)
Title: Message Title Adrien Thebo updated an issue Facter / FACT-458 Implement changes for AIX Memory facts (already commited) Change By: Adrien Thebo 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 (FACT-458) Implement changes for AIX Memory facts (already commited)
Title: Message Title Adrien Thebo updated an issue Facter / FACT-458 Implement changes for AIX Memory facts (already commited) Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1019) Deprecate ZAML
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1019 Deprecate ZAML Story points of 3 is a bit of a guess. It appears that zaml is only used for writing, not for reading. Change By: Kylo Ginsberg Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2727) Reserved keywords conflict with resource type parameters
Title: Message Title Andy Parker commented on an issue Re: Reserved keywords conflict with resource type parameters Merged into master in commit c24626 Add Comment Puppet / PUP-2727 Reserved keywords conflict with resource type parameters The words function, type, and attr are now reserved and produce warnings in the current parser and errors in the future parser. However, type conflicts with the type parameter on the ssh_authorized_key resource type. This means that under the future parser you can't fully use that type, or any others that happen to have a type, function, or ... 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-2579) ssh_authorized_key does not handle options with escaped double quotes
Title: Message Title
Kurt Wall commented on an issue
Re: ssh_authorized_key does not handle options with escaped double quotes
The failure to handle escaped double quotes is resolved. PUP-2727 is related, but not a blocker. Will put a note in that bug to test this case, too, when this comes up for FR. Accordingly, marking this Resolved.
Add Comment
Puppet / PUP-2579
ssh_authorized_key does not handle options with escaped double quotes
With the following declaration: {code} ssh_authorized_key { 'title': user = 'root', ensure = 'present', name = 'mykey', options = [ 'command=/usr/local/bin/mybin \$SSH_ORIGINAL_COMMAND\' ], type = 'ssh-rsa', key = 'xxx', } {code} It creates the following entry: {code}command=/usr/local/bin/myb...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more
Jira (PUP-2798) Stop issuing deprecation warnings for reserved words
Title: Message Title Andy Parker created an issue Puppet / PUP-2798 Stop issuing deprecation warnings for reserved words Issue Type: Improvement Assignee: Andy Parker Components: DSL Created: 17/Jun/14 3:33 PM Fix Versions: 3.7.0 Priority: Normal Reporter: Andy Parker PUP-1027 introduced warnings for new keywords that we want to reserve for functionality that will appear during the Puppet 4.x series. Unfortunately this ended up stopping some types (notably ssh_authorized_key) from working since keywords are generally allowed as parameter names. In PUP-2727 the future parser stopped issuing errors when the reserved words were used as parameters, but didn't change when the warnings are issued. The problem of properly issuing warnings in the current parser is more complicated than we can tackle without changes to the grammar. Added to this is the overwhelming number of deprecation warnings that users are starting to receive. We need to remove the warnings introduced by PUP-1027 . There is still a reasonable upgrade story for users since the new behavior is available under the future parser, which will either
Jira (PUP-2532) parameter lookup produces screwy result for default values
Title: Message Title Andy Parker updated an issue Puppet / PUP-2532 parameter lookup produces screwy result for default values Change By: Andy Parker Sprint: Week2014-6-25to2014-7-2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1299) Deprecate and eliminate magic parameter array handling
Title: Message Title Andy Parker updated an issue Puppet / PUP-1299 Deprecate and eliminate magic parameter array handling Change By: Andy Parker Sprint: Week2014-6-25to2014-7-2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2703) tag should be a statement function in future parser
Title: Message Title Andy Parker updated an issue Puppet / PUP-2703 tag should be a statement function in future parser Change By: Andy Parker Sprint: Week2014-6-18to2014-6-25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2727) Reserved keywords conflict with resource type parameters
Title: Message Title Kurt Wall commented on an issue Re: Reserved keywords conflict with resource type parameters When verifying this ticket, please (re)verify PUP-2579 . It verified for that ticket, but fails on the type attribute in 2579. Add Comment Puppet / PUP-2727 Reserved keywords conflict with resource type parameters The words function, type, and attr are now reserved and produce warnings in the current parser and errors in the future parser. However, type conflicts with the type parameter on the ssh_authorized_key resource type. This means that under the future parser you can't fully use that type, or any others that happen to have a type, function, or ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this
Jira (PUP-494) Make future parser/evaluator have acceptable performance
Title: Message Title Andy Parker updated an issue Puppet / PUP-494 Make future parser/evaluator have acceptable performance Change By: Andy Parker Sprint: Week2014-6-18to2014-6-25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-511) Specify Resource Expression Evaluation
Title: Message Title Andy Parker updated an issue Puppet / PUP-511 Specify Resource _expression_ Evaluation Change By: Andy Parker Sprint: Week2014-7-2to2014-7-9 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-2663) Allow string to numeric conversion to start with + or -
Title: Message Title Andy Parker updated an issue Puppet / PUP-2663 Allow string to numeric conversion to start with + or - Change By: Andy Parker Sprint: Week2014-6-18to2014-6-25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1852) deprecate the 'search' function
Title: Message Title Andy Parker updated an issue Puppet / PUP-1852 deprecate the 'search' function Change By: Andy Parker Sprint: Week2014-6-18to2014-6-25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1782) Deprecation warning when attempt to match a number with a regexp in 3.x
Title: Message Title Andy Parker updated an issue Puppet / PUP-1782 Deprecation warning when attempt to match a number with a regexp in 3.x Change By: Andy Parker Sprint: Week2014-6-25to2014-7-2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2682) Trailing commas should be allowed in node definitions
Title: Message Title Andy Parker updated an issue Puppet / PUP-2682 Trailing commas should be allowed in node definitions Change By: Andy Parker Sprint: Week2014-6-18to2014-6-25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2654) label provider for class/define should capitalize all segments
Title: Message Title Andy Parker updated an issue Puppet / PUP-2654 label provider for class/define should capitalize all segments Change By: Andy Parker Sprint: Week2014-7-2to2014-7-9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1811) in with regexps should set match variables
Title: Message Title Andy Parker updated an issue Puppet / PUP-1811 in with regexps should set match variables Change By: Andy Parker Sprint: Week2014-7-2to2014-7-9 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-675) init.d script silently fails if PIDfile is missing
Title: Message Title Kenneth Barber assigned an issue to Unassigned PuppetDB / PDB-675 init.d script silently fails if PIDfile is missing Change By: Kenneth Barber Assignee: KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2788) Puppet package source check fails with DFS share
Title: Message Title
Kurt Gardiner commented on an issue
Re: Puppet package source check fails with DFS share
Rob Reynolds We started with backslashes, same deal:
PS C:\Windows\system32 puppet resource package 'krut' ensure=installed source='\\dfs_share\software\jdk6\jdk-6u45-windows-x64.exe'
Error: The source does not exist: '\\dfs_share\software\jdk6\jdk-6u45-windows-x64.exe'
Error: /Package[krut]/ensure: change from absent to present failed: The source does not exist: '\\dfs_share\software\jdk6\jdk-6u45-windows-x64.exe'
package { 'krut':
ensure = 'absent',
}
PS C:\Windows\system32 puppet resource package 'krut' ensure=installed source='dfs_share\\software\\jdk6\\jdk-6u45-windows-x64.exe'
Error: The source does not exist: 'dfs_share\\software\\jdk6\\jdk-6u45-windows-x64.exe'
Error: /Package[krut]/ensure: change from absent to present failed: The source does not exist: 'dfs_share\\software\\jdk6\\jdk-6u45-windows-x64.exe'
package { 'krut':
ensure = 'absent',
Add Comment
Puppet / PUP-2788
Puppet package source check fails with DFS share
{noformat} package { 'NetFx452': ensure = installed, source = '//dfs_share/software/dotNetFx452_Full_x86_x64.exe', install_options = ['/q'], } {noformat} fails with error {noformat} Error: The source does not exist: '//dfs_share/software/dotNetFx452_Full_x86_x64.exe' {noformat} Digging through th...
Jira (PUP-2579) ssh_authorized_key does not handle options with escaped double quotes
Title: Message Title
Kurt Wall commented on an issue
Re: ssh_authorized_key does not handle options with escaped double quotes
And, with PUP-2727 in master, the type error is gone, too:
[root@centos6-5-base puppet]# cat ../x.pp
ssh_authorized_key { 'title':
user= 'root',
ensure = 'present',
name= 'mykey',
options = [ 'command=/usr/local/bin/mybin \$SSH_ORIGINAL_COMMAND\' ],
type= 'ssh-rsa',
key = 'xxx',
}
# be puppet apply --verbose --parser future ../x.pp
Notice: Compiled catalog for centos6-5-base.localdomain in environment production in 0.33 seconds
Info: Applying configuration version '1403045352'
Notice: Finished catalog run in 0.04 seconds
Add Comment
Puppet / PUP-2579
ssh_authorized_key does not handle options with escaped double quotes
With the following declaration: {code} ssh_authorized_key { 'title': user = 'root', ensure = 'present', name = 'mykey', options = [ 'command=/usr/local/bin/mybin \$SSH_ORIGINAL_COMMAND\' ], type = 'ssh-rsa', key = 'xxx', } {code} It creates the following entry: {code}command=/usr/local/bin/myb...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2700 Puppet 3.6.1 File recurse improperly handles spaces in filenames Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-573) Facter is generating an error message on stderr darwin
Title: Message Title Josh Cooper created an issue Facter / FACT-573 Facter is generating an error message on stderr darwin Issue Type: Bug Assignee: Eric Sorenson Created: 17/Jun/14 3:54 PM Priority: Normal Reporter: Josh Cooper $ bundle exec facter 2014-06-17 15:49:36.069 system_profiler[73699:707] Found bsdName (0x3003) for AppleUSBEthernet ... operatingsystem = Darwin operatingsystemrelease = 12.5.0 ... Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-573) Facter is generating an error message on stderr darwin
Title: Message Title Josh Cooper updated an issue Facter / FACT-573 Facter is generating an error message on stderr darwin Change By: Josh Cooper Assignee: EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
