Jira (PUP-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Michael Smith commented on PUP-6675 Re: Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Trying to apply firewall rules with puppetlabs-firewall via mco puppet runonce appears to screw up when SELinux is involved, because iptables-save can't write to the temp file. MODULES-3125 may be related. 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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Rob Nelson commented on PUP-6675 Re: Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Michael, I think that's the right way to go. File based IPC is always risky, and esp with SELinux involved. Do you have a repro for this in situ, in addition to when calling ruby -e? 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-3182) puppet catalog download fails
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-3182 puppet catalog download fails Change By: John Duarte Assignee: qa John Duarte 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-3182) puppet catalog download fails
Title: Message Title John Duarte updated an issue Puppet / PUP-3182 puppet catalog download fails Change By: John Duarte Fix Version/s: PUP 4.8.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-3182) puppet catalog download fails
Title: Message Title
John Duarte updated an issue
Puppet / PUP-3182
puppet catalog download fails
Change By:
John Duarte
Release Notes Summary:
This fixes a long standing issue in faces that implement the {{save}} command. This corrects the underlying call to the Indirection#save method with arguments in the correct positions. Previously, calls to faces utilizing the save facility would throw and error. One example of this was {{puppet catalog download}}.
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-3182) puppet catalog download fails
Title: Message Title John Duarte updated an issue Puppet / PUP-3182 puppet catalog download fails Change By: John Duarte Release Notes: Bug Fix 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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Michael Smith updated an issue Puppet / PUP-6675 Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Change By: Michael Smith Labels: selinux 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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Michael Smith updated an issue Puppet / PUP-6675 Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Change By: Michael Smith Team: Agent & Platform Support 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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Michael Smith commented on PUP-6675 Re: Puppet::Util::Execution.execute 'hostname' returns nothing as daemon In general, using tmp files for output isn't the right thing to do here, we should be using pipes. Apparently that's been done before, but I think Facter 3 might do it right so it seems fixable. 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-6678) Acceptance: Add test for puppet catalog download
Title: Message Title John Duarte created an issue Puppet / PUP-6678 Acceptance: Add test for puppet catalog download Issue Type: Task Assignee: Unassigned Created: 2016/09/02 5:06 PM Priority: Normal Reporter: John Duarte Add acceptance test to ensure that puppet catalog download works properly on all supported platforms Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-3182) puppet catalog download fails
Title: Message Title John Duarte commented on PUP-3182 Re: puppet catalog download fails Manually validated on RedHat 7 and Windows 2012r2 using a pre-release version of puppet-agent at SHA e15c8b5 containing puppet at SHA 78e897b. Redhat [root@ygznluu0hpmmxmq ~]# cat /opt/puppetlabs/puppet/VERSION 1.6.1.141.ge15c8b5 [root@ygznluu0hpmmxmq ~]# puppet catalog download --server=ygznluu0hpmmxmq.delivery.puppetlabs.net Notice: Saved catalog for ygznluu0hpmmxmq.delivery.puppetlabs.net to /opt/puppetlabs/puppet/cache/client_yaml/catalog/ygznluu0hpmmxmq.delivery.puppetlabs.net.yaml [root@ygznluu0hpmmxmq ~]# head /opt/puppetlabs/puppet/cache/client_yaml/catalog/ygznluu0hpmmxmq.delivery.puppetlabs.net.yaml --- !ruby/object:Puppet::Resource::Catalog name: ygznluu0hpmmxmq.delivery.puppetlabs.net catalog_uuid: f4a7a8d4-76d0-4018-ad06-1ba266b883be
Jira (PUP-6338) Allow arrow syntax following call to include, contain or require
Title: Message Title John Duarte updated an issue Puppet / PUP-6338 Allow arrow syntax following call to include, contain or require Change By: John Duarte QA Risk Assessment Reason: Covered by unit tests 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-6338) Allow arrow syntax following call to include, contain or require
Title: Message Title John Duarte updated an issue Puppet / PUP-6338 Allow arrow syntax following call to include, contain or require Change By: John Duarte QA Risk Assessment: Medium Low 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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Michael Smith commented on PUP-6675 Re: Puppet::Util::Execution.execute 'hostname' returns nothing as daemon It turns out this is a wider problem with SELinux blocking read/write to /tmp/* files used by Puppet for redirection. 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-6677) alias parameter in nagios_host type clashes with metaparameter alias
Title: Message Title Matt Schuchard updated an issue Puppet / PUP-6677 alias parameter in nagios_host type clashes with metaparameter alias Change By: Matt Schuchard Environment: Any Labels: agent nagios types Priority: Minor Normal 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-6677) alias parameter in nagios_host type clashes with metaparameter alias
Title: Message Title Igor Garcia created an issue Puppet / PUP-6677 alias parameter in nagios_host type clashes with metaparameter alias Issue Type: Bug Affects Versions: PUP 3.8.8 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/09/02 4:08 PM Priority: Minor Reporter: Igor Garcia It appears to be the same issue as the one reported in https://projects.puppetlabs.com/issues/3507. Nagios hosts have an alias parameter, and they can be repeated multiple times. When creating several nagios_host resources though, one gets the error "can not create alias x object already exists". It seems as though that refers to the metaparameter alias. Add Comment
Jira (PDOC-89) Exit 1 when an error occurs
Title: Message Title Henrik Lindberg commented on PDOC-89 Re: Exit 1 when an error occurs Thanks for the report. We are aware of a number of problems with the current version of Puppet Strings and we are in the process of fixing up a lot of those issues. Not sure if this is one of the known issues - we will look into this. 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-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Henrik Lindberg commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions Merde, I misread 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-6676) Broken repo link
Title: Message Title Gowtham Ramu created an issue Puppet / PUP-6676 Broken repo link Issue Type: Bug Affects Versions: PUP 4.6.1 Assignee: Unassigned Created: 2016/09/02 3:24 PM Fix Versions: None Priority: Major Reporter: Gowtham Ramu PM V2015.3.1 Agent 4.6.1 After adding class "pe_repo::platform::el_6_x86_64" puppet agent -t on PM fails Notice: /Stage[main]/Pe_repo::Platform::El_6_x86_64/Pe_repo::El[el-6-x86_64]/Pe_repo::Repo[el-6-x86_64 2015.3.1]/Pe_staging::Deploy[puppet-agent-el-6-x86_64.tar.gz]/Pe_staging::File[puppet-agent-el-6-x86_64.tar.gz]/Exec[/opt/puppetlabs/server/data/staging/pe_repo-puppet-agent-1.6.1/puppet-agent-el-6-x86_64.tar.gz]/returns: % Total% Received % Xferd Average Speed TimeTime Time Current
Jira (PUP-6279) Cannot call type() function using postfix notation e.g 1.type()
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-6279 Cannot call type() function using postfix notation e.g 1.type() Change By: Sean Griffin Assignee: Sean Griffin 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-6221) Add SemVer and SemVerRange types to the Puppet Type System
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-6221 Add SemVer and SemVerRange types to the Puppet Type System Change By: Sean Griffin Assignee: Sean Griffin 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-6361) Validate and error if a class or define is given a name starting with ::
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-6361 Validate and error if a class or define is given a name starting with :: Change By: Sean Griffin Assignee: Sean Griffin 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-5860) Static catalog acceptance: Catalog application stability against out-of-band updates, Story PUP-5526
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-5860 Static catalog acceptance: Catalog application stability against out-of-band updates, Story PUP-5526 Change By: Sean Griffin Assignee: Sean Griffin 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-5864) Static catalog acceptance: Server should only allow access to /environments/*/modules/*/files/*, Story PUP-5534
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-5864 Static catalog acceptance: Server should only allow access to /environments/*/modules/*/files/*, Story PUP-5534 Change By: Sean Griffin Assignee: Sean Griffin 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-5740) lookup does not honor environment.conf setting 'environment_data_provider = "function"'
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-5740 lookup does not honor environment.conf setting 'environment_data_provider = "function"' Change By: Sean Griffin Assignee: Sean Griffin 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-6053) type mismatch error involving struct member should quote member name
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-6053 type mismatch error involving struct member should quote member name Change By: Sean Griffin Assignee: Sean Griffin 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-5802) Yum provider incorrectly computes epoch for RPM package versions
Title: Message Title Sean Griffin assigned an issue to Eric Sorenson Puppet / PUP-5802 Yum provider incorrectly computes epoch for RPM package versions Change By: Sean Griffin Assignee: Sean Griffin Eric Sorenson 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-5699) Inline symlink metadata
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-5699 Inline symlink metadata Change By: Sean Griffin Assignee: Sean Griffin 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-5705) As a puppet admin, I want to enable static catalogs on a per-env basis so I can test the behavior without affecting production nodes
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-5705 As a puppet admin, I want to enable static catalogs on a per-env basis so I can test the behavior without affecting production nodes Change By: Sean Griffin Assignee: Sean Griffin 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-4904) puppet describe -s ssh_authorized_key output is really bad
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-4904 puppet describe -s ssh_authorized_key output is really bad Change By: Sean Griffin Assignee: Sean Griffin 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-1416) Facter solaris_zones fact does not include non-running zones
Title: Message Title Sean Griffin assigned an issue to Unassigned Facter / FACT-1416 Facter solaris_zones fact does not include non-running zones Change By: Sean Griffin Assignee: Sean Griffin 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-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Thomas Hallgren commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions Chris Price, please note though, that the problem still remains in 1.7.26. It's fixed in 9.0.0.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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Michael Smith commented on PUP-6675 Re: Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Puppet execute may actually want to enable STDOUT.sync = true. Ref: http://stackoverflow.com/questions/8859768/thin-doesnt-output-when-fork-exec-ed-from-ruby 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-6513) Increase the amount of debug logging when using the lookup function
Title: Message Title John Duarte commented on PUP-6513 Re: Increase the amount of debug logging when using the lookup function Validated on Debian 8 amd64 using pre-release version of puppet-agent at SHA e15c8b5 containing puppet at SHA 78e897b. For a non-existent key of foo, the output that would be seen on the command line for puppet lookup --explain is reflected in the Debug output of puppet when puppet's log_level is set to debug ~# cat /opt/puppetlabs/puppet/VERSION 1.6.1.141.ge15c8b5 ~# puppet lookup --explain foo Merge strategy first Data Binding "hiera" No such key: "foo" Data Provider "EnvironmentDataProvider" No such key: "foo"
Jira (PUP-6513) Increase the amount of debug logging when using the lookup function
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-6513 Increase the amount of debug logging when using the lookup function Change By: John Duarte Assignee: qa John Duarte 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-3025) Make stockpile release for cmd-proc-refactor -> master
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3025 Make stockpile release for cmd-proc-refactor -> master Change By: Rob Browning Assignee: Rob Browning 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-5871) Add Timestamp and Timespan to Puppet type system
Title: Message Title
John Duarte commented on PUP-5871
Re: Add Timestamp and Timespan to Puppet type system
These functions are tested quite robustly via the spec tests. A sanity check was performed on Windows 2012r2 to ensure that there were no fundamental surprises on that platform.
Using puppet-agent at SHA e15c8b5 containing puppet at SHA 78e897b the sanity check passed on Windows 2012r2.
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\cygwin64\home\Administrator>type test.pp
type test.pp
$t0 =Timestamp.new.strftime("%N"); notice("Timestamp formatted in %N: $t0")
$t1 =Timestamp.new.strftime("%F"); notice("Timestamp formatted in %F: $t1")
$t2 =Timestamp.new.strftime("%c"); notice("Timestamp formatted in %c: $t2")
Jira (PDB-3029) Add tests for dlo initialization when there are existing messages and test discard-stream more thoroughly
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3029 Add tests for dlo initialization when there are existing messages and test discard-stream more thoroughly Change By: Rob Browning Assignee: Rob Browning 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 (PDOC-89) Exit 1 when an error occurs
Title: Message Title Matthew Haughton created an issue Puppet Strings / PDOC-89 Exit 1 when an error occurs Issue Type: Bug Assignee: Unassigned Created: 2016/09/02 10:38 AM Priority: Normal Reporter: Matthew Haughton When there's an error raised during processing, I expect the exit code is not 0. Sample output from rake strings:generate (same happens with puppet strings): snafu109@foswiki:~/puppet-nginx$ bundle exec rake strings:generate [error]: Exception occurred while generating 'nginx/resource/vhost.html' [error]: ParseErrorWithIssue: Syntax error at end of file [error]: Stack trace:
Jira (PDOC-51) Pin yard to a very specific version
Title: Message Title Matthew Haughton commented on PDOC-51 Re: Pin yard to a very specific version Very close to done - when https://github.com/puppetlabs/puppetlabs-strings/pull/96 is merged this could be closed. 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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title
Michael Smith created an issue
Puppet / PUP-6675
Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/09/02 10:22 AM
Priority:
Normal
Reporter:
Michael Smith
When Puppet::Util::Execution.execute 'hostname' is invoked by Puppet running as a daemon, no output is written. This seems to be exclusive to hostname, and may be restricted to certain Linux versions. I've tried it on RedHat 7 (64-bit).
This can happen in a provider when using commands :hostname => 'hostname', and then invoking hostname. The root appears to be how /usr/bin/hostname handles file handles.
This is getting into some core Ruby weirdness:
ruby -e "Kernel.fork { \$stdout.reopen('/tmp/foo', 'w+'); Kernel.exec 'hostname' }"
prints hostname to /tmp/foo when run from the command-line. When run as a systemd script:
Jira (PUP-5871) Add Timestamp and Timespan to Puppet type system
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5871 Add Timestamp and Timespan to Puppet type system Change By: John Duarte Assignee: qa John Duarte 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-6612) Scope effort for i18n string externalization
Title: Message Title Andrew Henroid commented on PUP-6612 Re: Scope effort for i18n string externalization I've created a tool to perform basic analysis. Currently, the heuristics to determine if strings are user-visible are very simplistic, resulting in many false positives, and possibly some false negatives. The GitHub repo is here: https://github.com/ahenroid/rxstrings Below is a snippet from a run against Puppet (rxstrings -s puppet/lib) ... rxstrings: 25 instances, 22 files: -d rxstrings: 26 instances, 15 files: name... rxstrings: 26 instances, 4 files: Node rxstrings: 27 instances, 11 files: a rxstrings: 27 instances, 15 files: type rxstrings: 27 instances, 17 files: String rxstrings: 30 instances, 12 files: value rxstrings: 30 instances, 1 files: query_uuid rxstrings: 30 instances, 1 files: No currently active task. ITask is NULL. rxstrings: 33 instances, 1 files: amenity rxstrings: 34 instances, 1 files: amenity... rxstrings: 35 instances, 5 files: baz rxstrings: 39 instances, 23 files: w rxstrings: 57 instances, 29 files: name rxstrings: 72 instances, 3 files: service rxstrings: 77 instances, 5 files: bar rxstrings: 78 instances, 1 files: region... rxstrings: 78 instances, 6 files: foo rxstrings: 83 instances, 2 files: property... rxstrings: 189 instances, 1 files: egrammar.ra rxstrings: 14001 strings (14001 unmarked), 8939 unique strings (2859 multi-part), 954 files Obviously, many of these strings are not user-visible. It is likely that some filtering or prioritization could be done based on simple heuristics, e.g. strings that contain spaces are likely to be phrases and user-visible. However, non-trivial effort will be required to either develop good heuristics and/or manually categorize the list of strings produced by this tool. 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
Jira (FACT-1482) mountpoints fact does not show mounts on tmpfs
Title: Message Title John Duarte assigned an issue to qa Facter / FACT-1482 mountpoints fact does not show mounts on tmpfs Change By: John Duarte Status: Ready for CI Test Assignee: qa 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-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Chris Price commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions Awesome, thanks for testing that, Thomas Hallgren. We have already updated to 1.7.26 in our master branch, and are in the process of doing long-running memory testing against it. As soon as that completes we'll be shipping OSS releases containing that version, so hopefully that'll take care of it. I'll make sure this comes up in triage so we can discuss test coverage. 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-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title John Duarte updated an issue Puppet / PUP-6275 Compiler PROFILE output should be logged at INFO level Change By: John Duarte QA Risk Assessment: Low 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-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title John Duarte updated an issue Puppet / PUP-6275 Compiler PROFILE output should be logged at INFO level Change By: John Duarte QA Status: Reviewed 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-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6275 Compiler PROFILE output should be logged at INFO level Change By: John Duarte Status: Ready for CI Test Assignee: qa 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-5871) Add Timestamp and Timespan to Puppet type system
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-5871 Add Timestamp and Timespan to Puppet type system Change By: John Duarte Status: Ready for CI Test Assignee: qa 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-6669) Puppet should return better errors for Enum mismatches
Title: Message Title Henrik Lindberg commented on PUP-6669 Re: Puppet should return better errors for Enum mismatches merged to master at: c52773e 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-4643) Add continue/next/break for iteration control
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4643 Add continue/next/break for iteration control Change By: Henrik Lindberg Sprint: Language Triage 2016-09-07 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-4643) Add continue/next/break for iteration control
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4643
Add continue/next/break for iteration control
Change By:
Henrik Lindberg
Acceptance Criteria:
That:* break() breaks the innermost iteration* next(v) or next() returns v or undef respectively from a lambda, or function* return(v) or return() returns v or undef respectively from a function* that next and return have the same behavior in a function body* that a return from a lambda makes the function it is used in return* that errors are raised if the next/return/break "signal" reaches a scope where it is not allowed
Release Notes Summary:
The functions {{break()}}, {{next()}} and {{return()}} have been added to make it possible to do an "early exit" from a block of code. In summary {{break()}} will break the innermost iteration, {{next()}} will return from a lambda/block/class or resource body and {{return()}} will return from a function or class or resource body. See the respective function for more details.
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-4643) Add continue/next/break for iteration control
Title: Message Title Henrik Lindberg commented on PUP-4643 Re: Add continue/next/break for iteration control Will work as suggested by R.I.Pienaar, only using return() or next() as break() is reserved to break an ongoing iteration. Even if a class or define body may be in an iteration it is too spooky to break that look and skip that particular class or resource from being created (that would just be strange). 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-4643) Add continue/next/break for iteration control
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4643 Add continue/next/break for iteration control Change By: Henrik Lindberg Fix Version/s: PUP 4.8.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-6674) Acceptance: amend pcore loader tests to cover complex catalog
Title: Message Title John Duarte created an issue Puppet / PUP-6674 Acceptance: amend pcore loader tests to cover complex catalog Issue Type: Task Assignee: Unassigned Created: 2016/09/02 8:28 AM Priority: Normal Reporter: John Duarte The existing pcore loader acceptance tests do not provide enough coverage as exhibited by PUP-6653. They need to be amended or expanded to ensure that the loading precedence does not regress. See PUP-6653 for details Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6653) Ruby types still loaded even when a PCore type is found
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6653 Ruby types still loaded even when a PCore type is found Ah, thanks Henrik Lindberg. The quick filter was flagging this issue because the "release notes" field wasn't set (even though you had provided a summary). All good now. Change By: Kenn Hussey Release Notes: Bug Fix 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-6662) Sensitive values are not passed to 3.x user defined types and classes
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6662 Sensitive values are not passed to 3.x user defined types and classes Change By: Kenn Hussey Flagged: Impediment 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-6653) Ruby types still loaded even when a PCore type is found
Title: Message Title Henrik Lindberg commented on PUP-6653 Re: Ruby types still loaded even when a PCore type is found Kenn Hussey There is already a release note in this ticket. Not good enough? 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-6650) hiera_include doesn't work when using environment catalogs and environment caching
Title: Message Title John Duarte updated an issue Puppet / PUP-6650 hiera_include doesn't work when using environment catalogs and environment caching Change By: John Duarte QA Risk Assessment: High 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-6650) hiera_include doesn't work when using environment catalogs and environment caching
Title: Message Title John Duarte updated an issue Puppet / PUP-6650 hiera_include doesn't work when using environment catalogs and environment caching Change By: John Duarte QA Status: Reviewed 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-6673) Acceptance: Add test for hiera_include with cached environment
Title: Message Title John Duarte created an issue Puppet / PUP-6673 Acceptance: Add test for hiera_include with cached environment Issue Type: Task Assignee: Unassigned Created: 2016/09/02 8:16 AM Priority: Normal Reporter: John Duarte Add acceptance test to validate that the override of hiera_include in the environment compiler works also when an environment is cached, and when the environment has been in use for regular compilations before an environment compilation. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6662) Sensitive values are not passed to 3.x user defined types and classes
Title: Message Title John Duarte updated an issue Puppet / PUP-6662 Sensitive values are not passed to 3.x user defined types and classes Change By: John Duarte QA Highest Test Level: Acceptance 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-6662) Sensitive values are not passed to 3.x user defined types and classes
Title: Message Title John Duarte updated an issue Puppet / PUP-6662 Sensitive values are not passed to 3.x user defined types and classes Change By: John Duarte QA Risk Assessment Reason: Broken defined functionality with no workaround available 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-6662) Sensitive values are not passed to 3.x user defined types and classes
Title: Message Title John Duarte updated an issue Puppet / PUP-6662 Sensitive values are not passed to 3.x user defined types and classes Change By: John Duarte QA Status: Reviewed 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-6662) Sensitive values are not passed to 3.x user defined types and classes
Title: Message Title John Duarte updated an issue Puppet / PUP-6662 Sensitive values are not passed to 3.x user defined types and classes Change By: John Duarte QA Risk Assessment: High 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-6672) Acceptance: Add test for Sensitive data in defined types and classes
Title: Message Title John Duarte created an issue Puppet / PUP-6672 Acceptance: Add test for Sensitive data in defined types and classes Issue Type: Task Assignee: Unassigned Created: 2016/09/02 7:33 AM Priority: Normal Reporter: John Duarte Ensure that Sensitive data types can be used as values in parameters to resources and classes. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6662) Sensitive values are not passed to 3.x user defined types and classes
Title: Message Title Kenn Hussey commented on PUP-6662 Re: Sensitive values are not passed to 3.x user defined types and classes John Duarte can this be resolved now that the release has shipped? 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-6650) hiera_include doesn't work when using environment catalogs and environment caching
Title: Message Title Kenn Hussey commented on PUP-6650 Re: hiera_include doesn't work when using environment catalogs and environment caching John Duarte can this be resolved now that the release has shipped? 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-6653) Ruby types still loaded even when a PCore type is found
Title: Message Title Kenn Hussey commented on PUP-6653 Re: Ruby types still loaded even when a PCore type is found Thanks, John Duarte, is this ready for review then? Henrik Lindberg could you please add release notes for this 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-6671) Unable to start puppetserver after upgrade
Title: Message Title Ameya Agashe commented on PUP-6671 Re: Unable to start puppetserver after upgrade Hi Team, Any update ? Kind Regards, Ameya Agashe 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-6671) Unable to start puppetserver after upgrade
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6671 Unable to start puppetserver after upgrade Change By: Henrik Lindberg Scrum Team: Puppet Server 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-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6241 puppet agent ostensibly succeeds when environment directory has wrong permissions Change By: Henrik Lindberg Scrum Team: Language Puppet Server 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-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Henrik Lindberg commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions Phew, that is good news. Chris Price signing this over to Server as it seems to be a matter of getting an updated JRuby to users. Not sure what to do with the acceptance test associated with this PR - it is clearly testing expected behavior so it is probably of value to add it. 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-6669) Puppet should return better errors for Enum mismatches
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6669 Puppet should return better errors for Enum mismatches Change By: Thomas Hallgren Fix Version/s: PUP 4.8.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-1082) pip provider should handle multiple pips/pythons
Title: Message Title
drew j commented on PUP-1082
Re: pip provider should handle multiple pips/pythons
Hello,
This issue has been outstanding for almost three years and I wondered whether any movement has been made to resolve it?
As it currently stands, the pip provider for the Package resource can manage packages for the system installed version of pip. It's not possible to manage packages for virtualenvs, etc.
It would be nice if there was a method to pass in the path to the pip binary to use for operations related to this provider.
For example,
package { $pkg_name:
ensure => present,
provider => 'pip',
pip_path => '/opt/myvirtualenv/venv/bin/pip',
}
To me, this seems like a useful enhancement of this package and will reduce the need for people to use Execs to get this to work correctly.
Thanks, Drew
Add Comment
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title
Thomas Hallgren commented on PUP-6241
Re: puppet agent ostensibly succeeds when environment directory has wrong permissions
Did some testing using JRuby and Pathname. Seems JRuby has addressed this already.
With 1.7.26
jruby-1.7.26 :001 > x = Pathname('/home/thhal/tmp/foo/bar.txt')
=>
jruby-1.7.26 :002 > x.read
Errno::ENOENT: No such file or directory - /home/thhal/tmp/foo/bar.txt
Same thing with 9.0.5.0
jruby-9.0.5.0 :001 > x = Pathname('/home/thhal/tmp/foo/bar.txt')
=>
jruby-9.0.5.0 :002 > x.read
Errno::EACCES: Permission denied - /home/thhal/tmp/foo/bar.txt
