Jira (PUP-6698) create_resources does not honor '@@resource' as exported resource
Title: Message Title Angel L. Mateo commented on PUP-6698 Re: create_resources does not honor '@@resource' as exported resource In my case: I had a custom type that write information to a file (among other things). I created exported resources of that type with create_resources. Changing this to a lambda, didn't fix the problem, I think that because the used path for the file didn't exist on the node exporting the resource. But I can't be 100% sure because I changed the implementation of this type. Instead of manually create the file in my provider I changed the type to use a puppet file resource internally. And I don't have any problem with this reimplementation. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3096) log time elapsed for command processing
Title: Message Title Charlie Sharpsteen commented on PDB-3096 Re: log time elapsed for command processing Currently we log a message at info level after each command is processed that includes the certname and the command type. It would be awesome if this message also included the elapsed processing time and command size. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1551) WSA not initalized before loading custom facts
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Facter / FACT-1551 WSA not initalized before loading custom facts Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1551) WSA not initalized before loading custom facts
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1551 WSA not initalized before loading custom facts Change By: Maggie Dreyer Sprint: AP 2017-01-11 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1551) WSA not initalized before loading custom facts
Title: Message Title Susan McNerney commented on FACT-1551 Re: WSA not initalized before loading custom facts Approved for inclusion in Agent 1.7.2/PE 2016.4.3 for the Davis LTS by the Davis leads. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1551) WSA not initalized before loading custom facts
Title: Message Title Eric Thompson updated an issue Facter / FACT-1551 WSA not initalized before loading custom facts Change By: Eric Thompson QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1551) WSA not initalized before loading custom facts
Title: Message Title Eric Thompson updated an issue Facter / FACT-1551 WSA not initalized before loading custom facts Change By: Eric Thompson QA Risk Assessment Reason: covered by unit tests QA Contact: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6763) Make CI job to update POT files
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-6763 Make CI job to update POT files Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6763) Make CI job to update POT files
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-6763 Make CI job to update POT files Change By: Maggie Dreyer Sprint: AP 2017- 02 01 - 08 11 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7021) Handle incompatible encodings in Puppet::Parameter#format
Title: Message Title
Moses Mendoza updated an issue
Puppet / PUP-7021
Handle incompatible encodings in Puppet::Parameter#format
Change By:
Moses Mendoza
[ Puppet::Parameter#format |https://github.com/puppetlabs/puppet/blob/83909490a047b15f7fd4ca4f72490112740a7aec/lib/puppet/parameter.rb#L541-L543] currently does not check if the strings it is interpolating are of incompatible encodings.This method is used, among other places, in the resource harness when [ setting the message for failed change events |https://github . com/puppetlabs/puppet/blob/83909490a047b15f7fd4ca4f72490112740a7aec/lib/puppet/transaction/resource_harness.rb#L147-L149]. If the strings contain incompatible encodings (i.e., they cannot be concatenated) the format method will fail, the event will not contain a message, and then it will fail to be logged.This also results in error messages that look like this:{code}Error: /Stage[main]/Main/Node[ubuntu16.localdomain]/User[foo]: Could not evaluate: Puppet::Util::Log requires a message{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7021) Handle incompatible encodings in Puppet::Parameter#format
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7021 Handle incompatible encodings in Puppet::Parameter#format Issue Type: Bug Assignee: Unassigned Created: 2016/12/15 3:13 PM Fix Versions: PUP 4.9.0 Labels: maintenance Priority: Normal Reporter: Moses Mendoza Puppet::Parameter#format currently does not check if the strings it is interpolating are of incompatible encodings. This method is used, among other places, in the resource harness when setting the message for change events. If the strings contain incompatible encodings (i.e., they cannot be concatenated) the format method will fail, the event will not contain a message, and then it will fail to be logged. This also results in error messages that look like this: Error: /Stage[main]/Main/Node[ubuntu16.localdomain]/User[foo]: Could not evaluate: Puppet::Util::Log requires a message
Jira (PUP-7021) Handle incompatible encodings in Puppet::Parameter#format
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7021 Handle incompatible encodings in Puppet::Parameter#format Change By: Moses Mendoza Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7020) Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7020 Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist Change By: Henrik Lindberg Fix Version/s: PUP 4.9.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7020) Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7020 Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7020) Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist
Title: Message Title Henrik Lindberg commented on PUP-7020 Re: Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist merged to master at: 3265450 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7020) Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-7020 Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist Change By: Henrik Lindberg Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6698) create_resources does not honor '@@resource' as exported resource
Title: Message Title Henrik Lindberg commented on PUP-6698 Re: create_resources does not honor '@@resource' as exported resource Angel L. Mateo Any news from you? As I read your comments it seems that just using puppet syntax instead of create_resources solved your problem. Have you figured out what the problem is/was? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6698) create_resources does not honor '@@resource' as exported resource
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6698
create_resources does not honor '@@resource' as exported resource
Change By:
Henrik Lindberg
I have an in house nagios module (that will eventually be on the forge) that has a file export defined in it. Every time that export is hit the exporting client side throws an error because it's trying to write the file locally when it shouldn't be. This only happens when Puppet Agent 1.6.1 is installed on the puppet server (I back reved the server to 2.4.0 and installed latest 1.6.1 agent and ran into it as well so it's likely in the agent, but as it requires exported resources working I can't give a test with just the agent)Example error:{code}Error: Puppet::Util::FileType::FileTypeFlat could not write /etc/nagios/conf.d/host_ldap.home.bardicgrove.org_ldap.home.bardicgrove.org.cfg: No such file or directory @ rb_sysopen - /etc/nagios/conf.d/host_ldap.home.bardicgrove.org_ldap.home.bardicgrove.org.cfgError: /Stage[main]/Nagios::Client/Nagios::Resource[ldap.home.bardicgrove.org]/Nagios::Resource::Host[ldap.home.bardicgrove.org]/Nagios_host[ldap.home.bardicgrove.org]: Could not evaluate: Puppet::Util::FileType::FileTypeFlat could not write /etc/nagios/conf.d/host_ldap.home.bardicgrove.org_ldap.home.bardicgrove.org.cfg: No such file or directory @ rb_sysopen - /etc/nagios/conf.d/host_ldap.home.bardicgrove.org_ldap.home.bardicgrove.org.cfg{code}The code that is getting called is listed in [0] which gets called by [1] on all systems.[0] https://github.com/tykeal/puppet-nagios/blob/master/manifests/resource.pp#L87-L91[1] https://github.com/tykeal/puppetserver-mod-profile/blob/master/manifests/nagios/client.ppFull lab / environment configuration can be found by a combination of the following 4 repositories:https://github.com/tykeal/puppetserver-mainhttps://github.com/tykeal/puppetserver-hierahttps://github.com/tykeal/puppetserver-mod-profilehttps://github.com/tykeal/puppetserver-mod-role UPDATEThe problem here came from use of {{create_resources}} with resource type preceded by {{@@}} to indicate that the resource is exported.There may also be a problem with virtual resources.
Add Comment
Jira (PUP-6698) create_resources does not honor '@@resource' as exported resource
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6698 create_resources does not honor '@@resource' as exported resource Change By: Henrik Lindberg Summary: Puppet server 2.5.0 create_resources does not properly handle honor '@@resource' as exported file resources resource Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Henrik Lindberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources Thanks Andrew Grimberg for coming back with that information. I will update the title to better reflect the actual problem. (BTW: There may be a problem with virtual resources as well). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Andrew Grimberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources Just following up. I finally managed to get some time to rewrite all the create_resources calls in the module. It looks like the problem is specific to create_resources for exported resources. Since create_resources is supposed to get a quoted resource name to create, any '@@something' ends up having this failure. Other create_resources work just fine. Switching to a lambda notation does appear to completely resolve the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7015) [SPIKE] Add Japanese locale to AppVeyor host for spec runs
Title: Message Title Glenn Sarti assigned an issue to Unassigned Puppet / PUP-7015 [SPIKE] Add Japanese locale to AppVeyor host for spec runs Change By: Glenn Sarti Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7020) Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist
Title: Message Title Thomas Hallgren commented on PUP-7020 Re: Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist We do have unit tests that mixes a Hiera v3 global config with a Hiera v5 environment. They execute OK. @erict, if you still have the machine up, it would be very helpful if you could run the above command again with --trace so that a stack-trace is provided. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7020) Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist
Title: Message Title Eric Thompson commented on PUP-7020 Re: Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist [root@a4xvm5abchlei0i environments]# puppet lookup --environment v4_hieradata_with_v5_configs_r7fi52mw environment_key --explain Warning: /etc/puppetlabs/puppet/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5 (in /etc/puppetlabs/puppet/hiera.yaml) Error: Could not run: undefined method `invocation' for false:FalseClass [root@a4xvm5abchlei0i environments]# mv /etc/puppetlabs/puppet/hiera.yaml ~ [root@a4xvm5abchlei0i environments]# puppet lookup --environment v4_hieradata_with_v5_configs_r7fi52mw environment_key --explain Searching for "lookup_options" Global Data Provider (hiera configuration version 5) No such key: "lookup_options"
Jira (PUP-7020) Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist
Title: Message Title Eric Thompson commented on PUP-7020 Re: Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist fyi: Henrik Lindberg default PA hiera.yaml (v3) causes ruby error when using v5 environment hiera.yaml Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7020) Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist
Title: Message Title Eric Thompson assigned an issue to Thomas Hallgren Puppet / PUP-7020 Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist Change By: Eric Thompson Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7020) Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7020 Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist Change By: Eric Thompson Issue Type: Bug CI Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7020) Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7020 Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist Change By: Eric Thompson QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7020) Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist
Title: Message Title Michael Smith created an issue Puppet / PUP-7020 Acceptance tests fail if both hiera v3 and hiera v5 yaml config exist Issue Type: Bug Assignee: Unassigned Created: 2016/12/15 12:05 PM Priority: Normal Reporter: Michael Smith https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppet_intn-van-sys_master/42 failed on tests. That failure seems to have been traced to having two hiera configs on the system. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6966) Tidy and File cannot remove fifo or socket files
Title: Message Title Thomas Kishel commented on PUP-6966 Re: Tidy and File cannot remove fifo or socket files Submitted a new pull request, because rspec. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7019) Investigate why ENV behaves differently under Japanese Windows and Ruby 2.3.x
Title: Message Title
Glenn Sarti commented on PUP-7019
Re: Investigate why ENV behaves differently under Japanese Windows and Ruby 2.3.x
Possibly something to do with filesystem encoding vs locale encoding
Japanese Windows - CP932
31] pry(#)> Encoding.find("internal")
=> nil
[32] pry(#)> Encoding.find("external")
=> #
[33] pry(#)> Encoding.find("filesystem")
=> #
[34] pry(#)> Encoding.find("locale")
=> #
38] pry(#)> ENV.key?(codepage_key)
Jira (PUP-7019) Investigate why ENV behaves differently under Japanese Windows and Ruby 2.3.x
Title: Message Title
Glenn Sarti commented on PUP-7019
Re: Investigate why ENV behaves differently under Japanese Windows and Ruby 2.3.x
Interesting notes;
Ruby 2.4
rb_w32_get_environ https://github.com/ruby/ruby/blob/9db0b2d7eeae0986e79444a8721dc49ec3234aff/win32/win32.c#L6003-L6036
rb_w32_getenv(const char *name) calls w32_getenv(CP_ACP) <--- WHAT THE?
rb_w32_ugetenv https://github.com/ruby/ruby/blob/9db0b2d7eeae0986e79444a8721dc49ec3234aff/win32/win32.c#L5143-L5146
rb_w32_getenv https://github.com/ruby/ruby/blob/9db0b2d7eeae0986e79444a8721dc49ec3234aff/win32/win32.c#L5150-L5153
w32_getenv_unknown() flips encoding (unicode vs cp_acp) based on rb_locale_encindex() == rb_ascii8bit_encindex() https://github.com/ruby/ruby/blob/5ec23b5222811bcbce0b3049d53f89311f6e43b5/hash.c#L3057-L3068
https://github.com/ruby/ruby/blob/5ec23b5222811bcbce0b3049d53f89311f6e43b5/hash.c#L3134-L3142
Ruby 2.3
w32_getenv flips encoding based on rb_locale_encindex being the same as rb_ascii8bit_encindex https://github.com/ruby/ruby/blob/ruby_2_3/hash.c#L2853-L2862
rb_ascii8bit_encindex = ENCINDEX_ASCII https://github.com/ruby/ruby/blob/ruby_2_3/encoding.c#L1313-L1316
rb_locale_encindex https://github.com/ruby/ruby/blob/ruby_2_3/encoding.c#L1351-L1366 defaults to ENCINDEX_ASCII
env_has_key(VALUE env, VALUE key) { const char *s; s = env_name(key); if (getenv(s)) return Qtrue; return Qfalse; }
https://github.com/ruby/ruby/blob/ruby_2_3/hash.c#L3831-L3839
env_name just creates a pointer from a string
getenv is defined as w32_getenv on windows https://github.com/ruby/ruby/blob/ruby_2_3/hash.c#L2863
rb_locale_encindex https://github.com/ruby/ruby/blob/ruby_2_3/encoding.c#L1351-L1366
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7019) Investigate why ENV behaves differently under Japanese Windows and Ruby 2.3.x
Title: Message Title Glenn Sarti created an issue Puppet / PUP-7019 Investigate why ENV behaves differently under Japanese Windows and Ruby 2.3.x Issue Type: Task Assignee: Unassigned Created: 2016/12/15 11:39 AM Priority: Normal Reporter: Glenn Sarti spec/unit/util_spec.rb has a few tests to describe the behaviour of ENV under different Ruby versions. Recently on testing under a Japanese version of Windows, using Ruby 2.3.0 it was failing. This ticket is to investigate why. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6260) SPIKE - PUP-6188 determine how we can test 6188
Title: Message Title Geoff Nichols commented on PUP-6260 Re: SPIKE - PUP-6188 determine how we can test 6188 Ethan Brown and Erick Banks - is this still needed? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5958) Docs: Update installer screenshots when branding work is finished
Title: Message Title Geoff Nichols assigned an issue to Jorie Tappa Puppet / PUP-5958 Docs: Update installer screenshots when branding work is finished Change By: Geoff Nichols Assignee: Jorie Tappa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5958) Docs: Update installer screenshots when branding work is finished
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5958 Docs: Update installer screenshots when branding work is finished Change By: Geoff Nichols Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' command
Title: Message Title Jeremy Adams updated an issue Puppet / PUP-6739 If no matching local $environment folder on agent, error when running any 'puppet config' command Change By: Jeremy Adams Summary: If no matching local $environment folder on agent, error when running any 'puppet config' command Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config'
Title: Message Title Jeremy Adams updated an issue Puppet / PUP-6739 If no matching local $environment folder on agent, error when running any 'puppet config' Change By: Jeremy Adams Summary: If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title Jeremy Adams commented on PUP-6739 Re: If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command Eric Sorenson I'm not opposed to 'puppet module list' having that behavior, it was just something additional that I found that is related to this (uses the same underlying code). My main issue is that on an agent, I want to configure settings such as server, certname, environment during bootstrap, and the environment I specify is referring to an environment on the master, the settings in puppet.conf should not depend on the state of the agent's filesystem. A case of excessive error checking. I agree with 'puppet module' complaining about non-existent environments. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6975) When using puppet apply to create a file with a non-existent group, the exit code should be non-zero.
Title: Message Title Geoff Nichols commented on PUP-6975 Re: When using puppet apply to create a file with a non-existent group, the exit code should be non-zero. Sean Griffin, does this behave as expected if run with --detailed-exitcodes? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1551) WSA not initalized before loading custom facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1551 WSA not initalized before loading custom facts Change By: Geoff Nichols Fix Version/s: FACT 3.5.1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1551) WSA not initalized before loading custom facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1551 WSA not initalized before loading custom facts Change By: Geoff Nichols Fix Version/s: FACT 3.4.2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1551) WSA not initalized before loading custom facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1551 WSA not initalized before loading custom facts Change By: Geoff Nichols Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title Eric Sorenson commented on PUP-6739 Re: If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command Jeremy Adams if you are doing this from a script, can you also make the directory as part of your scripting? i'm not sure it's the config read/write subsystem's responsibility to manage stuff on the filesystem. Because it makes total sense to me that if you set the environment to a non existent directory and then try to run 'puppet module list' from that environment, you get an error. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1551) WSA not initalized before loading custom facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1551 WSA not initalized before loading custom facts Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6739 If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command Change By: Geoff Nichols Sprint: AP Triage Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6519) Allow The Initial Facter Run in an Agent Run To Log its Output To a File on Disk
Title: Message Title Charlie Sharpsteen commented on PUP-6519 Re: Allow The Initial Facter Run in an Agent Run To Log its Output To a File on Disk Something close to this has actually been possible for a while by setting the facts cache terminus to "yaml" in /etc/puppetlabs/puppet/routes.yaml agent: facts: cache: yaml That will cause the agent to update $clientyamldir/facts/$certname.yaml each time Facts are loaded. The problem is that MCollective expects facts to be in a slightly different format, it just wants the fact values and not the surrounding metadata. That's why the cron job contains: facts_y = facts.values.to_yaml So, this would probably also require an update to MCollective so that it can load Puppet fact sets directly, instead of demanding its own separate format. Add Comment
Jira (PDB-3209) Collect PuppetDB stats/metrics from puppetserver perf test runs
Title: Message Title Ryan Senior commented on PDB-3209 Re: Collect PuppetDB stats/metrics from puppetserver perf test runs Putting this in blocked as we can't really test it until TK-427 is merged, released, incorporated in PuppetDB etc Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3209) Collect PuppetDB stats/metrics from puppetserver perf test runs
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3209 Collect PuppetDB stats/metrics from puppetserver perf test runs Change By: Ryan Senior Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3209) Collect PuppetDB stats/metrics from puppetserver perf test runs
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3209 Collect PuppetDB stats/metrics from puppetserver perf test runs Change By: Ryan Senior Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6538) deprecate hiera_xxx functions (in favour of lookup)
Title: Message Title Henrik Lindberg commented on PUP-6538 Re: deprecate hiera_xxx functions (in favour of lookup) merged to master at: 0de73bd Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6908) selmodule syncversion => false behavior incorrect
Title: Message Title Thomas Mueller commented on PUP-6908 Re: selmodule syncversion => false behavior incorrect Jordan Conway RedHat re-introduces the version number as a bugfix update in RHEL 7.3: https://bugzilla.redhat.com/show_bug.cgi?id=1395733 https://bugzilla.redhat.com/show_bug.cgi?id=1392573 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5649) "syncversion" maybe obsolete for selmodule type in Fedora >= 23
Title: Message Title
Jordan Conway commented on PUP-5649
Re: "syncversion" maybe obsolete for selmodule type in Fedora >= 23
I got hit with this on CentOS 7.3, here's the hacky workaround I put in my base profile that quiets things in the meantime. Similar could be used for Fedora >=23 but I don't have any Fedora machines.
if $::operatingsystemrelease >= '7.3' {
Selmodule <|tag == 'selinux::module::redhat'|> { syncversion => undef }
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (PDB-2758) Remove Ubuntu 15.10 Wily (i386, amd64) from puppetdb pipelines
Title: Message Title Ryan Senior commented on PDB-2758 Re: Remove Ubuntu 15.10 Wily (i386, amd64) from puppetdb pipelines I was looking at the PuppetDB pipelines today and thought we could probably get rid of the Ubuntu 15.10 tests, which led me to this ticket. What info are we waiting on for this Geoff Nichols? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6908) selmodule syncversion => false behavior incorrect
Title: Message Title
Jordan Conway commented on PUP-6908
Re: selmodule syncversion => false behavior incorrect
Confirming, here's the hacky workaround I put in my base profile that quiets things in the meantime. Similar could be used for Fedora >=23 but I don't have any Fedora machines.
if $::operatingsystemrelease >= '7.3' {
Selmodule <|tag == 'selinux::module::redhat'|> { syncversion => undef }
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (FACT-1551) WSA not initalized before loading custom facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1551 WSA not initalized before loading custom facts Change By: Geoff Nichols Acceptance Criteria: On Windows, a custom fact using using net/http to query a network service does not fail with "getaddrinfo: Either the application has not called WSAStartup, or WSAStartup failed." Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1728) OS X Lion group membership not updated
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-1728 OS X Lion group membership not updated Change By: Geoff Nichols Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1728) OS X Lion group membership not updated
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-1728 OS X Lion group membership not updated Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6927) Recursively copying a directory to Windows 7 nodes fails on files with tilde in the filename
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6927 Recursively copying a directory to Windows 7 nodes fails on files with tilde in the filename Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6927) Recursively copying a directory to Windows 7 nodes fails on files with tilde in the filename
Title: Message Title Geoff Nichols commented on PUP-6927 Re: Recursively copying a directory to Windows 7 nodes fails on files with tilde in the filename Hi Colin Conway - I'll go ahead and close this for now. If this still seems to be an issue after your test, please feel free to re-open and we'll be happy to take another look. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6538) deprecate hiera_xxx functions (in favour of lookup)
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-6538 deprecate hiera_xxx functions (in favour of lookup) Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6981) Reroute hiera_xxx functions to the new lookup logic
Title: Message Title Henrik Lindberg commented on PUP-6981 Re: Reroute hiera_xxx functions to the new lookup logic merged to master at: 84c870b Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7010) Allow usage of .te files in selmodule
Title: Message Title Thomas Mueller commented on PUP-7010 Re: Allow usage of .te files in selmodule Eric Seyden thanks for the pointer to this module. Don't know how i missed to find this. I don't know anybody who don't uses the make way when developing selinux modules. but yes it is possible to compile it without make - but i don't know what (and if) additonal packages are required when using the manual compile approach. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7010) Allow usage of .te files in selmodule
Title: Message Title Eric Seynaeve commented on PUP-7010 Re: Allow usage of .te files in selmodule I admit we're new to SELinux but checking e.g. http://selinuxproject.org/page/Building_a_Basic_Policy, I don't see a dependency on make for compiling .pp files. Only checkmodule and semodule_package are required which are installed by default. This is also confirmed in https://stuckinadoloop.wordpress.com/2011/06/15/puppet-managed-deployment-of-selinux-modules/. There is already a forge module out there which seems pretty good: jfryman/selinux. Unfortunately the maintainers doesn't have time for it anymore and has transfered the code to voxpupuli: https://github.com/voxpupuli/puppet-selinux/issues/106 and puppet/selinux. Strangely enough it uses the make command ?? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
