Jira (PUP-3810) Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path
Title: Message Title Joerg Jaspert created an issue Puppet / PUP-3810 Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path Issue Type: Bug Affects Versions: PUP 3.7.3, PUP 3.7.2, PUP 3.7.1 Assignee: Henrik Lindberg Components: Server Created: 2015/01/06 2:31 AM Environment: Linux (Debian), puppetmaster with passenger Priority: Blocker Reporter: Joerg Jaspert Hi, from 3.7.1 on appearently puppet does no longer allow a setting in puppet.conf, part [master] of hiera_config that looks like Use an environment specific hiera config file hiera_config = $environmentpath/$environment/etc/hiera.yaml Up to, including, 3.7.0 this worked perfectly. The directory expands to
Jira (PUP-3757) Puppet client can try to use SSL instead of TLS
Title: Message Title Josh Cooper commented on PUP-3757 Re: Puppet client can try to use SSL instead of TLS Tomas Doran Puppet 3.7 added support for persistent HTTP connections, which may explain why things work sometimes. The trouble with specifying http.ssl_version = :TLSv1 is that it forces TLSv1.0, even if ruby/openssl support later versions, e.g. ssl_version = :TLSv1_2. The preferred approach is to explicitly disable SSLv2 SSLv3, which we do in https://github.com/puppetlabs/puppet/blob/3.7.3/lib/puppet/util/monkey_patches.rb#L173-L177. Unfortunately we have to monkey patch because some code paths go through open-uri and we need to make sure they don't downgrade to insecure versions. It might be helpful to get a tcpdump on the agent and see what SSL versions, options, etc are being negotiated and go from there. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1270) 'pkg' package provider does not understand IPS package versions properly
Title: Message Title Josh Cooper commented on PUP-1270 Re: 'pkg' package provider does not understand IPS package versions properly Thanks Lauri Tirkkonen! Would you mind searching jira to see if there is already a ticket, and if not, filing one? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2362) ssh_authorized_keys temporary file Operation not permitted
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2362 ssh_authorized_keys temporary file Operation not permitted Change By: Josh Cooper Affects Version/s: PUP3.4.3 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-927) puppet apply on Windows always uses *nix style newlines from templates
Title: Message Title Josh Cooper commented on PUP-927 Re: puppet apply on Windows always uses *nix style newlines from templates It looks like the file function may have the same problem too, as it calls File.read, which will convert \r\n to \n. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1481) Incorrect PID on first start after installation on Ubuntu
Title: Message Title Josh Cooper assigned an issue to Release Engineering Puppet / PUP-1481 Incorrect PID on first start after installation on Ubuntu Change By: Josh Cooper Assignee: EricSorenson ReleaseEngineering Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1481) Incorrect PID on first start after installation on Ubuntu
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1481 Incorrect PID on first start after installation on Ubuntu Change By: Josh Cooper Component/s: TypesandProviders Component/s: RE Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3502) Puppet provider fails on first run if features are delivered during run (Windows)
Title: Message Title Damien Buckley updated an issue Puppet / PUP-3502 Puppet provider fails on first run if features are delivered during run (Windows) Change By: Damien Buckley Attachment: vcac-appliance.zip Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3502) Puppet provider fails on first run if features are delivered during run (Windows)
Title: Message Title Damien Buckley commented on PUP-3502 Re: Puppet provider fails on first run if features are delivered during run (Windows) Hi Josh, Please find a the attached zip file which contains the custom type provider and sample manifest. Thanks, Damien, Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3502) Puppet provider fails on first run if features are delivered during run (Windows)
Title: Message Title Damien Buckley assigned an issue to Josh Cooper Puppet / PUP-3502 Puppet provider fails on first run if features are delivered during run (Windows) Change By: Damien Buckley Assignee: DamienBuckley JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3810) Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path
Title: Message Title Henrik Lindberg commented on PUP-3810 Re: Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path Joshua Partlow can you comment? Esp. the part about that the error message points to a different directory than what it actually was found to be. For the rest, hiera is a singleton implementation and is not designed to change the configuration per request. The most common approach is to use a common config (across all environments) and have a level in the hierarchy that depends on the name of the environment. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3810) Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path
Title: Message Title Joerg Jaspert commented on PUP-3810 Re: Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path It may be a singleton, but the setup as I had it worked, and its a no-go to break in a minor version update. Funnily it also worked when I changed hierarchies within environments, but I may have run into some funny sideeffects from $something there (though I did some heavy changes of the hierarchies, using environments to test em before it breaks all systems). I sure can do that by running extra puppet masters for this, but thats somewhat crap when hiera seems to be the only one to demand those extra resources. Anyways, the bad point stays: It should not break like this in a minor version update. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3810) Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path
Title: Message Title R.I.Pienaar commented on PUP-3810 Re: Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path Hiera never supported per environment hiera.yaml. Here worked before most likely means broke in ways I did not discover, it was never supported. The error message and failing is definitely the better scenario rather than working kind of - of course making it environment aware would be first price. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3810) Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path
Title: Message Title Joerg Jaspert commented on PUP-3810 Re: Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path Its definitely not ok to break in such a horrible way with a minor version update. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3811) pkg provider 'latest' will refresh without updating package if newer version exists, but is not installable
Title: Message Title Lauri Tirkkonen created an issue Puppet / PUP-3811 pkg provider 'latest' will refresh without updating package if newer version exists, but is not installable Issue Type: Bug Assignee: Unassigned Created: 2015/01/06 4:42 AM Priority: Normal Reporter: Lauri Tirkkonen From PUP-1270 comments (pasted below): https://tickets.puppetlabs.com/browse/PUP-1270?focusedCommentId=120773page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-120773 — Josh, I think that's a separate bug in 'latest'. I am not seeing it on my test package, using puppet 87fad92f18966ea62544df16d251885794c5ec92 under OmniOS: kekkonen ~/repos/puppet 141 % pkg list -vfa PUP-1270-test-package FMRI IFO
Jira (PUP-3811) pkg provider 'latest' will refresh without updating package if newer version exists, but is not installable
Title: Message Title Lauri Tirkkonen updated an issue Puppet / PUP-3811 pkg provider 'latest' will refresh without updating package if newer version exists, but is not installable Change By: Lauri Tirkkonen
Jira (PUP-1270) 'pkg' package provider does not understand IPS package versions properly
Title: Message Title Lauri Tirkkonen updated an issue Puppet / PUP-1270 'pkg' package provider does not understand IPS package versions properly https://tickets.puppetlabs.com/browse/PUP-3811 – Lauri Tirkkonen | +358 50 5341376 | lotheac @ IRCnet Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1270) 'pkg' package provider does not understand IPS package versions properly
Title: Message Title Lauri Tirkkonen updated an issue Puppet / PUP-1270 'pkg' package provider does not understand IPS package versions properly https://tickets.puppetlabs.com/browse/PUP-3811 – Lauri Tirkkonen | +358 50 5341376 | lotheac @ IRCnet Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1093) PR (1201): (maint) Set Beaker AWS department to 'eso-dept' - rji
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1093 PR (1201): (maint) Set Beaker AWS department to 'eso-dept' - rji Change By: Kenneth Barber Sprint: PuppetDB2015-01-14 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1094) PR (1202): (maint) Set Beaker AWS department to 'eso-dept' - rji
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1094 PR (1202): (maint) Set Beaker AWS department to 'eso-dept' - rji Change By: Kenneth Barber Sprint: PuppetDB2015-01-14 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1092) PR (161): Remove unused parameters - ekohl
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1092 PR (161): Remove unused parameters - ekohl Change By: Kenneth Barber Sprint: PuppetDB2015-01-14 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3806) Issue with Collectors and the Future Parser
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-3806 Issue with Collectors and the Future Parser Change By: Hailee Kenney Sprint: PlatformServer2014-12-17 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Christopher Price updated an issue Puppet / PUP-3809 Separate code (content?) and configuration directories for AIO packaging Change By: Christopher Price Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1092) PR (161): Remove unused parameters - ekohl
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1092 PR (161): Remove unused parameters - ekohl Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1094) PR (1202): (maint) Set Beaker AWS department to 'eso-dept' - rji
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1094 PR (1202): (maint) Set Beaker AWS department to 'eso-dept' - rji Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1093) PR (1201): (maint) Set Beaker AWS department to 'eso-dept' - rji
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1093 PR (1201): (maint) Set Beaker AWS department to 'eso-dept' - rji Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3812) Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type
Title: Message Title Kylo Ginsberg commented on PUP-3812 Re: Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type My $.02: this change makes sense to me. I think the proposal above is for two stages to this change: server adds application/octet-stream (but still support text/plain for older agents), client switches to using application/octet-stream server removes text/plain support If so, I think the first part doesn't strictly need to be in a major version, but given how many people ignore our advice and upgrade clients before upgrading servers, a major version might save some unneeded head-banging. The second part should be in a major version, since it is breaking change. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Christopher Price updated an issue Puppet / PUP-3809 Separate code (content?) and configuration directories for AIO packaging Change By: Christopher Price Sprint: SERVER nextcandidates 2014/01/21 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1094) PR (1202): (maint) Set Beaker AWS department to 'eso-dept' - rji
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1094 PR (1202): (maint) Set Beaker AWS department to 'eso-dept' - rji Issue Type: Task Assignee: Unassigned Created: 2015/01/06 11:34 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Set Beaker AWS department to 'eso-dept' Author: Roger Ignazio m...@rogerignazio.com Company: Puppet Labs Github ID: rji Pull Request 1202 Discussion Pull Request 1202 File Diff Pull Request Description This commit sets the BEAKER_department variable to 'eso-dept', to improve AWS usage reporting. (webhooks-id: 8377168fd50ddb45c2c3040cb63f313b)
Jira (PDB-1052) Puppet 4: Terminus Environment related rspec testing failures
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber Reviewing PuppetDB / PDB-1052 Puppet 4: Terminus Environment related rspec testing failures Change By: Kenneth Barber Assignee: WyattAlt KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3806) Issue with Collectors and the Future Parser
Title: Message Title Hailee Kenney commented on PUP-3806 Re: Issue with Collectors and the Future Parser Merged into stable in 5580d0a Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1052) Puppet 4: Terminus Environment related rspec testing failures
Title: Message Title Kenneth Barber assigned an issue to Unassigned PuppetDB / PDB-1052 Puppet 4: Terminus Environment related rspec testing failures Change By: Kenneth Barber Assignee: KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1094) PR (1202): (maint) Set Beaker AWS department to 'eso-dept' - rji
Title: Message Title gepetto-bot commented on PDB-1094 Re: PR (1202): (maint) Set Beaker AWS department to 'eso-dept' - rji pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/352/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3812) Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type
Title: Message Title Josh Cooper commented on PUP-3812 Re: Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type We also use text/plain for all cert related files. SInce these are PEM format (base64-encoded), they can be transferred as text/plain, or we could switch them to using application/octet-stream as well... Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1092) PR (161): Remove unused parameters - ekohl
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1092 PR (161): Remove unused parameters - ekohl Change By: Kenneth Barber Fix Version/s: PDBmodule-4.2.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3719) Group resource non-authoritative by default
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3719 Group resource non-authoritative by default Change By: Josh Cooper Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3701) Issue with empty export resources expression in the Puppet future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3701 Issue with empty export resources _expression_ in the Puppet future parser Change By: Henrik Lindberg Sprint: PlatformServer2014-12-17 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3719) Group resource non-authoritative by default
Title: Message Title Josh Cooper commented on PUP-3719 Re: Group resource non-authoritative by default Merged in 0617e752f Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1343) Service provider in RedHat will not create K?? stop scripts
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-1343 Service provider in RedHat will not create K?? stop scripts Change By: Eric Sorenson Fix Version/s: PUP4.0.0 Fix Version/s: PUP3.7.4 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3240) Remove ignoreimport setting
Title: Message Title Henrik Lindberg commented on PUP-3240 Re: Remove ignoreimport setting For FR, attempt to use ignoreimport setting should raise an error. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-693) Retire event-query-limit
Title: Message Title Brian LaMetterey updated an issue PuppetDB / PDB-693 Retire event-query-limit Change By: Brian LaMetterey Summary: Retire events event -query-limit Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3061) Upgrade win32-eventlog to 0.6.2+
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3061 Upgrade win32-eventlog to 0.6.2+ Change By: Josh Cooper Component/s: Windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3061) Upgrade win32-eventlog to 0.6.2+
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3061 Upgrade win32-eventlog to 0.6.2+ Change By: Josh Cooper Component/s: Client Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1095) Upgrade TK version
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-1095 Upgrade TK version Issue Type: New Feature Assignee: Unassigned Created: 2015/01/06 4:39 PM Priority: Normal Reporter: Ryan Senior Once this ticket is fixed: https://tickets.puppetlabs.com/browse/SERVER-275 we should upgrade TK Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3779) Verify spec tests in dev env for Ruby 2.1.5
Title: Message Title Rob Reynolds commented on PUP-3779 Re: Verify spec tests in dev env for Ruby 2.1.5 This doesn't look too bad. I have only verified x64 so far and have two failures with spec tests, one of which may be environment related and the other is with hpux. 1) Package provider windows should be able to get a list of existing packages Failure/Error: provider.instances.each do |package| Encoding::UndefinedConversionError: U+2013 to IBM437 in conversion from UTF-16LE to UTF-8 to IBM437 # ./lib/puppet/util/windows/registry.rb:35:in `values' # ./lib/puppet/provider/package/windows/package.rb:40:in `block (5 levels) in with_key' # ./lib/puppet/util/windows/registry.rb:26:in `block in open' # ./lib/puppet/util/windows/registry.rb:25:in `open' # ./lib/puppet/provider/package/windows/package.rb:39:in `block (4 levels) in with_key'
Jira (PDB-693) Retire event-query-limit
Title: Message Title Brian LaMetterey assigned an issue to Brian LaMetterey PuppetDB / PDB-693 Retire event-query-limit Change By: Brian LaMetterey Assignee: BrianLaMetterey Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3274) Remove old parser/evaluator
Title: Message Title Josh Cooper commented on PUP-3274 Re: Remove old parser/evaluator Obsolete allow_variables_with_dashes setting removed in 1d5884a2 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3240) Remove ignoreimport setting
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3240 Remove ignoreimport setting Change By: Henrik Lindberg Sprint: PlatformServer2014-12-17 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3806) Issue with Collectors and the Future Parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3806 Issue with Collectors and the Future Parser Change By: Henrik Lindberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1481) Incorrect PID on first start after installation on Ubuntu
Title: Message Title Matthaus Owens commented on PUP-1481 Re: Incorrect PID on first start after installation on Ubuntu This is surprising unless there is already a puppet.conf in place that has been modified. The puppet.conf shipped with puppet from our repos specifies /var/run/puppet for the rundir for both master and agent. Also, the current init script doesn't pass the -m flag to start-stop-daemon, so start-stop-daemon isn't making the pidfile, puppet is (for both master and agent). Jurjen Bokma Are you seeing this with trusty's package or with our package? I'll try to reproduce this locally, but if this is a bug, I think it is a bug in puppet itself and not the packaging. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1093) PR (1201): (maint) Set Beaker AWS department to 'eso-dept' - rji
Title: Message Title gepetto-bot commented on PDB-1093 Re: PR (1201): (maint) Set Beaker AWS department to 'eso-dept' - rji Pull request (maint) Set Beaker AWS department to 'eso-dept' has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1093) PR (1201): (maint) Set Beaker AWS department to 'eso-dept' - rji
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1093 PR (1201): (maint) Set Beaker AWS department to 'eso-dept' - rji Issue Type: Task Assignee: Unassigned Created: 2015/01/06 11:33 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Set Beaker AWS department to 'eso-dept' Author: Roger Ignazio m...@rogerignazio.com Company: Puppet Labs Github ID: rji Pull Request 1201 Discussion Pull Request 1201 File Diff Pull Request Description This commit sets the BEAKER_department variable to 'eso-dept', to improve AWS usage reporting. After review and merge, please merge or cherry-pick up to 'master'.
Jira (PUP-3701) Issue with empty export resources expression in the Puppet future parser
Title: Message Title Henrik Lindberg commented on PUP-3701 Re: Issue with empty export resources _expression_ in the Puppet future parser For FR, since this was merged some time ago and subsequent FR has been made on other collection related tickets, there may not be any need for additional FR. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3567) Remove current_environment check in Puppet::Indirector::Request#environment=
Title: Message Title Henrik Lindberg commented on PUP-3567 Re: Remove current_environment check in Puppet::Indirector::Request#environment= I don't understand what that removal changes. Clearly, the current environment can only be an environment that the master supports (or it should not have been accepted as being a current environment in the first place). It may have been that we needed the check against current environment earlier when tests were not fully configuring environments, or it may have been implemented because it is faster to check if the current environment is the wanted than to look it up via the available environments (which was very slow, but probably is heavier than just checking if current is the wanted env). So, why do we need to remove this? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1093) PR (1201): (maint) Set Beaker AWS department to 'eso-dept' - rji
Title: Message Title gepetto-bot commented on PDB-1093 Re: PR (1201): (maint) Set Beaker AWS department to 'eso-dept' - rji pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/353/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2564) Specify UTF-8 as a default encoding for puppet
Title: Message Title Steve Barlow updated an issue Puppet / PUP-2564 Specify UTF-8 as a default encoding for puppet Change By: Steve Barlow Sprint: PlatformClient2015-01-07 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3796) Puppet 3.7.3 is not supported on Ruby 2.2
Title: Message Title Kylo Ginsberg commented on PUP-3796 Re: Puppet 3.7.3 is not supported on Ruby 2.2 There's a PR for ruby 2.2 support on puppet/master, so this will be fixed in 4.0. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title Kylo Ginsberg commented on PUP-3591 Re: Puppet does not plugin sync with the proper environment after agent attempts to resolve environment John Duarte this was cherry-picked to stable, see comments from 2014/11/04. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title John Duarte commented on PUP-3591 Re: Puppet does not plugin sync with the proper environment after agent attempts to resolve environment Britt Gresham please backport this commit to the stable branch so that it can get picked up by 3.7.4. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3780) Verify Ruby 2.1.5 compatibility on Windows 2003
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3780 Verify Ruby 2.1.5 compatibility on Windows 2003 Change By: Rob Reynolds Attachment: ouch.png Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3780) Verify Ruby 2.1.5 compatibility on Windows 2003
Title: Message Title Rob Reynolds commented on PUP-3780 Re: Verify Ruby 2.1.5 compatibility on Windows 2003 Doesn't seem like we are going to win here. Even in 32bit ruby it still tries to statically link up to the points in MSVCRT.dll (or whatever the name of the dll is ). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1343) Service provider in RedHat will not create K?? stop scripts
Title: Message Title Kylo Ginsberg commented on PUP-1343 Re: Service provider in RedHat will not create K?? stop scripts Scott Garman the acceptance test is failing on all the platforms we're running foss acceptance against. The test should be confined to only the platforms it should be run against - it sounds like this is rhel5/centos5 only? A heads up that the test will be a no-op in foss (for now) because we only test against platforms that provide a native ruby 1.9 (which rhel5 does not). But that's okay because once we enable AIO in the next couple weeks, we can re-enable rhel5 testing at that time. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1343) Service provider in RedHat will not create K?? stop scripts
Title: Message Title Kylo Ginsberg commented on PUP-1343 Re: Service provider in RedHat will not create K?? stop scripts And an example of how to confine is at https://github.com/puppetlabs/puppet/blob/stable/acceptance/tests/external_ca_support/apache_external_root_ca.rb#L9 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1208) md5lite, mtime not honoured for file type/provider
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1208 md5lite, mtime not honoured for file type/provider Change By: Kylo Ginsberg Scrum Team: ReleaseEngineering ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3813) Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique
Title: Message Title Rolf updated an issue Puppet / PUP-3813 Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique Change By: Rolf Summary: Autocreatedaliases Aliasispopagatingtochildresources innestedexportedresources withsamenamevarvalus(difftypes) areconflictingasnonunique Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3813) Auto created aliases in nested exported resources are conflicting as non unique
Title: Message Title
Rolf created an issue
Puppet / PUP-3813
Auto created aliases in nested exported resources are conflicting as non unique
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/01/06 5:40 PM
Priority:
Major
Reporter:
Rolf
I have an exported resource that creates other resources when its collected. Many of those resources share the same namevar value but is unique to each type. For some reason, an alias is registered at the top exported resource and then propagates to all the children, regardless of type. I have been able to replicate this issue with a fairly simple nodes.pp
import '/etc/puppet/environments/production/manifests/site.pp'
node /puppet.vagrant/ inherits default {
include puppet::master
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Christopher Price updated an issue Puppet / PUP-3809 Separate code (content?) and configuration directories for AIO packaging Change By: Christopher Price Sprint: SERVERnextcandidates2 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3810) Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path
Title: Message Title Henrik Lindberg commented on PUP-3810 Re: Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path Joerg Jaspert I understand your frustration that it breaks your setup, but it was actually a bug that it was possible to do it the way you have it set up, and while it may look like it is working there are many issues that you simply have not run into yet (there are a large number of potential issues; it may work the first time, then possibly break on subsequent requests, may break under load, may get mix of results due to caching, will most likely leak memory, etc). Understand that the message it has always been broken does not help you. But reverting the protection against using a non supported (and broken) configuration does not seem like a very good idea. We should fix the bad message though (or possibly the bug that it picked the wrong location). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1092) PR (161): Remove unused parameters - ekohl
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1092 PR (161): Remove unused parameters - ekohl Issue Type: Task Assignee: Unassigned Created: 2015/01/06 10:01 AM Labels: github module Priority: Normal Reporter: gepetto-bot Remove unused parameters Author: Ewoud Kohl van Wijngaarden Company: Antagonist Github ID: ekohl Pull Request 161 Discussion Pull Request 161 File Diff Pull Request Description (webhooks-id: 6a2ecea80c7fdf030da6aacf0ac519b5)
Jira (PDB-885) PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber
Title: Message Title gepetto-bot commented on PDB-885 Re: PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber puppetcla commented: CLA signed by all contributors. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1061) PR (1175): Allow tilde in resource name, like in puppet - saimonn
Title: Message Title gepetto-bot commented on PDB-1061 Re: PR (1175): Allow tilde in resource name, like in puppet - saimonn puppetcla commented: CLA signed by all contributors. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1082) PR (1194): (maint) Allow factset ordering on hash - wkalt
Title: Message Title gepetto-bot commented on PDB-1082 Re: PR (1194): (maint) Allow factset ordering on hash - wkalt puppetcla commented: CLA signed by all contributors. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3812) Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-3812 Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Kylo Ginsberg Components: Client, Puppet Server, Server Created: 2015/01/06 8:32 AM Priority: Normal Reporter: Jeremy Barlow The Puppet file_bucket_file API – https://docs.puppetlabs.com/guides/rest_api.html#file-bucket – requires a PUT request for a file to include a Content-Type of text/plain. Puppet agent and file_bucket_file requests through the puppet filebucket CLI face also do not include a charset along with the Content-Type. Per various industry specifications – see https://tools.ietf.org/html/rfc6657 in particular – the default charset that a receiver should assume for this case would be either US-ASCII or ISO-8859-1. Puppet agent and filebucket CLI face requests, however, currently format the request body as raw binary data. This is incompatible with the US-ASCII and ISO-8859-1 formats. In order to make the client's intentions about the request body encoding more clear, it would be better for clients to include a Content-Type of application/octet-stream. Josh Cooper suggested that we could create a new format called :binary, map that to application/octet-stream, and
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Christopher Price updated an issue Puppet / PUP-3809 Separate code (content?) and configuration directories for AIO packaging Change By: Christopher Price Sprint: SERVERnextcandidates 2 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3780) Verify Ruby 2.1.5 compatibility on Windows 2003
Title: Message Title Ethan Brown commented on PUP-3780 Re: Verify Ruby 2.1.5 compatibility on Windows 2003 Well, this is bad news. Looks like we could have saved ourselves some time as there is new discussion on GitHub for this precise issue at https://github.com/oneclick/rubyinstaller/issues/239 https://github.com/oneclick/rubyinstaller/issues/251 Based on 239, another person was able to build Ruby on XP, but had to disable networking to do so (effectively making the build useless). As Josh Cooper and I had discovered while looking at the Ruby source, it's a compile-time #ifdef rather than a runtime check used to determine if _localtime64_s and _gmtime64_s can be used or not. #if RUBY_MSVCRT_VERSION = 80 || defined(HAVE__GMTIME64_S) e = gmtime_s(rp, tp); if (e != 0) goto error; #else https://github.com/ruby/ruby/blob/fa13cb050db8091658007df77f8247ae02442e51/win32/win32.c#L7140-L7143 https://github.com/ruby/ruby/blob/fa13cb050db8091658007df77f8247ae02442e51/win32/win32.c#L7164-L7167 It does seems peculiar that the 32-bit version tries to use these 64-bit functions - but I think it's due to Ruby insisting on creating definitions for these 64-bit functions when MINGW_HAS_SECURE_API is not defined: https://github.com/ruby/ruby/blob/fa13cb050db8091658007df77f8247ae02442e51/win32/win32.c#L7122-L7125 The big question mark for me is where is HAVE_GMTIME64_S defined? Is this a MinGW define perhaps? I think the solution here is to attempt to build on 2003 x64 with an RUBY_MSVCRT_VERSION 80 and with HAVE_GMTIME64_S undefined... which may be something we have to forcefully do. Do you think that this is feasible Melissa Stone / Geoff Nichols / Rob Braden given our current Windows native toolchains for building
Jira (PUP-3810) Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3810 Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path Change By: Henrik Lindberg UX Priority: Critical Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3810) Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3810 Does not allow $environment in hiera_config variable for no good reason and falls back to non-working path Change By: Henrik Lindberg Priority: Blocker Normal Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
