Jira (PUP-847) Manage security descriptor owner & group
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-847 Manage security descriptor owner & group Change By: Rob Reynolds Assignee: Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-470) Investigate and implement setStatementsCacheSize for repetitive SQL performance
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-470 Investigate and implement setStatementsCacheSize for repetitive SQL performance Change By: Kenneth Barber Summary: Investigate and implement setStatementsCacheSize for repeat repetitive SQL performance Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-470) Investigate and implement setStatementsCacheSize for repeat SQL performance
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-470 Investigate and implement setStatementsCacheSize for repeat SQL performance Change By: Kenneth Barber Summary: Investigate and implement setStatementsCacheSize for repeat SQL performance Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1678) Environment Endpoint should show configuration and not all modules
Title: Message Title
Andrew Parker commented on an issue
Re: Environment Endpoint should show configuration and not all modules
Updated api/docs, changed the schema, modified what it returns. At the same time I took a pass at fixing up the way it identifies the search paths for the environments. It is now using file URIs and a data URI for the special case of internally defined environments (those are ones that are created internally only the fly). The internal environments normally don't show up anywhere that a user would see them, but having a clear URI is useful in debugging.
Add Comment
Puppet / PUP-1678
Environment Endpoint should show configuration and not all modules
Right now the environments endpoint is showing all of the modules for an environment. After talking with the group that is going to be using this information, they actually need to know something else. They need to know the settings of the environment, specifically the {{modulepath}} and {{manifest}} values. We need to remove the list of modules and re...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google
Jira (PDB-470) Investigate setStatementsCacheSize for performance
Title: Message Title
Kenneth Barber updated an issue
PuppetDB / PDB-470
Investigate setStatementsCacheSize for performance
Change By:
Kenneth Barber
It seems the setting setStatementsCacheSize for BoneCPConfig will enable prepared statements cache.This seems to have a great effect on our insert time, especially at high load.So far I've tested this 3 times and found that the number of seconds spent doing inserts is almost halved.The proposal is to implement this setting as a user configurable item and set it to a reasonable default perhaps. We should confirm the numbers I've seen here first, and also do some more research on the feature to understand its side-effects. We might also want to consider just doing our own prepared statement handling and the value of that versus this approach, although this might be a good phase 1 regardless.The patch I was working with is here:{code}--- a/src/com/puppetlabs/jdbc.clj+++ b/src/com/puppetlabs/jdbc.clj@@ -300,6 +300,7 @@ (defn make-connection-pool (.setStatisticsEnabled stats) (.setIdleMaxAgeInMinutes (pl-time/to-minutes conn-max-age)) (.setIdleConnectionTestPeriodInMinutes (pl-time/to-minutes conn-keep-alive+ (.setStatementsCacheSize 1000) ;; paste the URL back together from parts. (.setJdbcUrl (str "jdbc:" subprotocol ":" subname)){code}My test code for submitting a random catalog is here:{code}#!/usr/bin/env rubyrequire 'rubygems'require 'net/http'require 'uri'require 'json'require 'pp'def replace_catalog(catalog) uri = URI.parse("http://localhost:8080/v3/commands") http = Net::HTTP.new(uri.host, uri.port) request = Net::HTTP::Post.new(uri.request_uri) request.set_form_data({ "payload" => {"command" => "replace catalog","version" => 3,"payload" => catalog.to_json, }.to_json} ) response = http.request(request) puts response.bodyenddef random_string (0...50).map { ('a'..'z').to_a[rand(26)] }.joinenddef random_resource {"type" => "Class","title" => random_string,"exported" => false,"file" => "asdf","line" => 3,"tags" => ["asdf"],"parameters" => {} }endpayload1 = { "metadata" => { "api_version" => 1 }, "data" => {"name" => "host-0","version" => "3","transaction-uuid" => "foo","edges" => [ {"source" => { "type" => "Class", "title" => "foo",},"target" => { "type" => "File", "title" => "foo",},"relationship" => "contains", },],"resources" => [ {"type" => "Class","title" => "foo","exported" => false,"file" => "asdf","line" => 3,"tags" => ["asdf"],"parameters" => {}, }, {"type" => "File","title" => "foo","exported" => false,"file" => "asdf","line" => 3,"tags" => ["asdf"],"parameters" => {}, },] }}1.times do payload1["data"]["resources"].push random_resourceend#pp payload1replace_catalog(payload1){code}
Jira (PDB-470) Investigate setStatementsCacheSize for performance
Title: Message Title
Kenneth Barber commented on an issue
Re: Investigate setStatementsCacheSize for performance
Find attached a couple of screenshots for before/after patch results. Like I said, I've tried this 3 times and found similar results each time, so I'm sure its not by accident.
This appears to be a simple facility that provides hashes lookups of previously prepared statements so they can be re-used. Without this, prepared statements are being prepared then destroyed after a single use. By using prepared statements we avoid a hard-parse in postgresql and with multiple use Postgresql can avoid plan calculation after a while once it considers a plan stable. So big performance benefits it would seem.
The alternative is to look at doing our own prepared statements.
Add Comment
PuppetDB / PDB-470
Investigate setStatementsCacheSize for performance
It seems the setting setStatementsCacheSize for BoneCPConfig will enable prepared statements cache. This seems to have a great effect on our insert time, especially at high load. So far I've tested this 3 times and found that the number of seconds spent doing inserts is almost halved. The patch I was working with is here: {code} --- a/src/com...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-470) Investigate setStatementsCacheSize for performance
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-470 Investigate setStatementsCacheSize for performance Change By: Kenneth Barber Attachment: Screen Shot 2014-02-21 at 02.44.58.png Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-470) Investigate setStatementsCacheSize for performance
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-470 Investigate setStatementsCacheSize for performance Change By: Kenneth Barber Attachment: Screen Shot 2014-02-21 at 02.45.07.png Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-470) Investigate setStatementsCacheSize for performance
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-470 Investigate setStatementsCacheSize for performance Issue Type: Improvement Assignee: Unassigned Created: 20/Feb/14 6:53 PM Fix Versions: 2.0.x Labels: trivial Priority: Normal Reporter: Kenneth Barber It seems the setting setStatementsCacheSize for BoneCPConfig will enable prepared statements cache. This seems to have a great effect on our insert time, especially at high load. So far I've tested this 3 times and found that the number of seconds spent doing inserts is almost halved. The patch I was working with is here: --- a/src/com/puppetlabs/jdbc.clj +++ b/src/com/puppetlabs/jdbc.clj @@ -300,6 +300,7 @@ (defn make-connection-pool (.setStatisticsEnabled stats) (.setIdleMaxAgeInMinutes (pl-time/to-minutes conn-max-age)) (.setIdleConnectionTestPeriodInMinutes (pl-time/to-minutes conn-keep-alive + (.setStatementsCacheSize 1000) ;; paste the URL back together from parts. (.setJdbcUrl (str "jdbc:" subprotocol ":" subname))
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Ronald Valente commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Anyone seeing a regression in 3.4.3 regarding this issue? "(err): Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation" Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1592) Puppet excessively stats the filesystem when looking for defined types
Title: Message Title Henrik Lindberg commented on an issue Re: Puppet excessively stats the filesystem when looking for defined types merged 1219a4a Add Comment Puppet / PUP-1592 Puppet excessively stats the filesystem when looking for defined types [~masterzen] and I realized that when puppet tries to resolve a defined type, it always tries to first find the defined type within all the plugin directories as it tries to first load it as a resource type and then as a defined type. We should be able to avoid a lot of stats on the filesystem by simply changing the lookup order. [~masterzen] has so... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1707) Faces help sometimes blows up when descriptions are absent
Title: Message Title
Joshua Cooper commented on an issue
Re: Faces help sometimes blows up when descriptions are absent
Merged to master in d50cdbb to be released in 3.5.0
Add Comment
Puppet / PUP-1707
Faces help sometimes blows up when descriptions are absent
Right now, {{puppet man config}} will explode, because there's no description for the --section option. This isn't the intended behavior; it should devolve gracefully to the summary if the description is missing. We're naïvely doing gsub on a value that might be nil.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1707) Faces help sometimes blows up when descriptions are absent
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1707 Faces help sometimes blows up when descriptions are absent Change By: Joshua Cooper Assignee: Joshua Cooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1592) Puppet excessively stats the filesystem when looking for defined types
Title: Message Title Henrik Lindberg commented on an issue Re: Puppet excessively stats the filesystem when looking for defined types Checked with PS if anyone has seen ruby based resource types in the wild with '::' in their names and no one has seen this, or even tried it. An attempt to add and use such types fails. Add Comment Puppet / PUP-1592 Puppet excessively stats the filesystem when looking for defined types [~masterzen] and I realized that when puppet tries to resolve a defined type, it always tries to first find the defined type within all the plugin directories as it tries to first load it as a resource type and then as a defined type. We should be able to avoid a lot of stats on the filesystem by simply changing the lookup order. [~masterzen] has so... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.
Jira (PUP-922) Fedora 19: 'puppet resource service' doesn't show puppet
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Fedora 19: 'puppet resource service' doesn't show puppet
I couldn't reproduce this on Fedora 19: https://gist.github.com/kylog/9126648 has some exploration.
Add Comment
Puppet / PUP-922
Fedora 19: 'puppet resource service' doesn't show puppet
Fedora 19: {{puppet resource service}} doesn't show puppet but {{puppet resource service puppet ensure=running}} will start it.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1584) Puppet module tool should work with new directory environments
Title: Message Title Joshua Partlow assigned an issue to Unassigned Puppet / PUP-1584 Puppet module tool should work with new directory environments Change By: Joshua Partlow Assignee: Joshua Partlow Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1678) Environment Endpoint should show configuration and not all modules
Title: Message Title
Andrew Parker commented on an issue
Re: Environment Endpoint should show configuration and not all modules
Checked with Patrick Carlisle, Eric Sorenson, and others on a decision that needed to be made. There is an option of showing the modulepath as just the subset of configured directories that actually exist, or of showing everything that was configured. We all agreed that including the fully configured modulepath was the right approach.
Add Comment
Puppet / PUP-1678
Environment Endpoint should show configuration and not all modules
Right now the environments endpoint is showing all of the modules for an environment. After talking with the group that is going to be using this information, they actually need to know something else. They need to know the settings of the environment, specifically the {{modulepath}} and {{manifest}} values. We need to remove the list of modules and re...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bug
Jira (PUP-1452) sshkey changed on every run when using a custom function, except there is no change
Title: Message Title Trevor Vaughan commented on an issue Re: sshkey changed on every run when using a custom function, except there is no change My guess is that you have trailing whitespace coming from that function. Try chomping it before you return it and see if that solves the problem. Add Comment Puppet / PUP-1452 sshkey changed on every run when using a custom function, except there is no change Everything is working, as long as I'm not using my custom function to collect all ipaddresses (IPv4 and IPv6) in an array. The manifest used to collect the keys: [[https://github.com/saz/puppet-ssh/blob/master/manifests/hostkeys.pp]] The manifest used to realize the keys: [[https://github.com/saz/puppet-ssh/blob/master/manifests/knownhosts.pp]] *Pu... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this gro
Jira (PUP-1678) Environment Endpoint should show configuration and not all modules
Title: Message Title Andrew Parker assigned an issue to Andrew Parker Puppet / PUP-1678 Environment Endpoint should show configuration and not all modules Change By: Andrew Parker Assignee: Joshua Partlow Andrew Parker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1742) Specifying mode in puppet.conf creates incorrect file permissions
Title: Message Title Andrew Parker assigned an issue to Andrew Parker Puppet / PUP-1742 Specifying mode in puppet.conf creates incorrect file permissions Change By: Andrew Parker Assignee: Andrew Parker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1742) Specifying mode in puppet.conf creates incorrect file permissions
Title: Message Title Andrew Parker commented on an issue Re: Specifying mode in puppet.conf creates incorrect file permissions I've put together a patch that seems to fix the problem. It is still missing tests. Add Comment Puppet / PUP-1742 Specifying mode in puppet.conf creates incorrect file permissions I've tested as far back as 3.1.0, but I suspect that we've had this wrong since 2.6. [~josh] tracked the problem down to a commit (b268fb3d4c) for redmine issue #7144. Unfortunately the change caused it to interpret a mode string as a decimal. This means that a mode of "0644" results in an actually applied mode of "0204". *To reproduce* Create a pup... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1742) Specifying mode in puppet.conf creates incorrect file permissions
Title: Message Title
Andrew Parker created an issue
Puppet / PUP-1742
Specifying mode in puppet.conf creates incorrect file permissions
Issue Type:
Bug
Affects Versions:
3.3.0
Assignee:
Unassigned
Created:
20/Feb/14 3:44 PM
Priority:
Major
Reporter:
Andrew Parker
I've tested as far back as 3.1.0, but I suspect that we've had this wrong since 2.6. Joshua Cooper tracked the problem down to a commit (b268fb3d4c) for redmine issue #7144. Unfortunately the change caused it to interpret a mode string as a decimal. This means that a mode of "0644" results in an actually applied mode of "0204".
To reproduce
Create a puppet.conf that contains:
signeddir = $cadir/signed { mode = 0644 }
Delete the ssldir:
rm -rf `puppet config print ssldir --section master`
Run the master
puppet master --no-daemonize --debug
The master will error
Jira (PUP-1456) Type "exec" is executed, although "require"d type failed
Title: Message Title Trevor Vaughan commented on an issue Re: Type "exec" is executed, although "require"d type failed I had a similar issue where puppet agent would not honor both 'unless' and 'onlyif' in the same exec. Puppet apply handled it properly making for an exciting time tracking down the issue. This is in 2.7.24. I'm not sure if it still happens in 3.X but it seems like it might be relevant. Add Comment Puppet / PUP-1456 Type "exec" is executed, although "require"d type failed An "exec"-type is executed although a "require"d type (an "exec", too) has failed. The strange thing is, that when doing an agent run ,the output of "puppet agent --test" says "Skipping because of failed dependency". The output is correct (as expected), but nevertheless the "exec"-type gets executed. As I have problems in my productive code, that woul... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group
Jira (PUP-1073) Common package name in two different providers
Title: Message Title Trevor Vaughan updated an issue Puppet / PUP-1073 Common package name in two different providers Change By: Trevor Vaughan Affects Version/s: 2.7.25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1073) Common package name in two different providers
Title: Message Title
Trevor Vaughan commented on an issue
Re: Common package name in two different providers
This seems to be something that has been asked for for around 6 or so years.
Any chance of getting some traction on this? Gem conflicts with local package names are absolutely deadly.
Add Comment
Puppet / PUP-1073
Common package name in two different providers
I have a common package name, that's in two different package managers (one with yum the other with gem) package { "remove-mysql": name => "mysql", provider => "yum", ensure => absent, } - package { "gem-mysql...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet
Jira (PDB-221) puppetdb-export/import doesn't contain node facts
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-221 puppetdb-export/import doesn't contain node facts Change By: Ryan Senior Assignee: Ryan Senior Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-216) Merge into pe branch
Title: Message Title Melissa Stone updated an issue Hiera / HI-216 Merge into pe branch Change By: Melissa Stone This release is getting merged into the pe-hiera 3.3.x branch , after the current pe-hiera 3.2.x branch gets merged up into pe-hiera 3.3.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-216) Merge into pe branch
Title: Message Title Melissa Stone updated an issue Hiera / HI-216 Merge into pe branch Change By: Melissa Stone This release is getting merged into the pe-hiera 3.3.x branch Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-217) Update the downloads page
Title: Message Title gepetto-bot created an issue Hiera / HI-217 Update the downloads page Issue Type: Sub-task Assignee: Melissa Stone Created: 20/Feb/14 1:10 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-218) Send out announcements
Title: Message Title gepetto-bot created an issue Hiera / HI-218 Send out announcements Issue Type: Sub-task Assignee: Melissa Stone Created: 20/Feb/14 1:10 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1636) Add a rhel7 host to acceptance
Title: Message Title Kylo Ginsberg commented on an issue Re: Add a rhel7 host to acceptance No more coding changes AFAIK, but this can't be enabled in Jenkins until Hiera 1.3.2 is released, so blocking on that ticket. Add Comment Puppet / PUP-1636 Add a rhel7 host to acceptance This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-219) Close all resolved tickets in Jira
Title: Message Title gepetto-bot created an issue Hiera / HI-219 Close all resolved tickets in Jira Issue Type: Sub-task Assignee: Melissa Stone Created: 20/Feb/14 1:10 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-203) Hiera 1.3.2 Release
Title: Message Title Kylo Ginsberg updated an issue Hiera / HI-203 Hiera 1.3.2 Release Change By: Kylo Ginsberg Sprint: Week 2014-2-19 to 2014-2-26 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-215) Merge tag into the right branch, push out updated branch(es) and tag
Title: Message Title gepetto-bot created an issue Hiera / HI-215 Merge tag into the right branch, push out updated branch(es) and tag Issue Type: Sub-task Assignee: Melissa Stone Created: 20/Feb/14 1:10 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-216) Merge into pe branch
Title: Message Title gepetto-bot created an issue Hiera / HI-216 Merge into pe branch Issue Type: Sub-task Assignee: Melissa Stone Created: 20/Feb/14 1:10 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-214) Packages pushed
Title: Message Title gepetto-bot created an issue Hiera / HI-214 Packages pushed Issue Type: Sub-task Assignee: Melissa Stone Created: 20/Feb/14 1:10 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-213) Docs pushed
Title: Message Title gepetto-bot created an issue Hiera / HI-213 Docs pushed Issue Type: Sub-task Assignee: Justin Holguin Created: 20/Feb/14 1:10 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-212) Go/no-go meeting
Title: Message Title gepetto-bot created an issue Hiera / HI-212 Go/no-go meeting Issue Type: Sub-task Assignee: Melissa Stone Created: 20/Feb/14 1:09 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-210) Tag the release and create packages
Title: Message Title gepetto-bot created an issue Hiera / HI-210 Tag the release and create packages Issue Type: Sub-task Assignee: Melissa Stone Created: 20/Feb/14 1:09 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-203) Hiera 1.3.2 Release
Title: Message Title Kylo Ginsberg updated an issue Hiera / HI-203 Hiera 1.3.2 Release Change By: Kylo Ginsberg Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-211) Smoke test packages
Title: Message Title gepetto-bot created an issue Hiera / HI-211 Smoke test packages Issue Type: Sub-task Assignee: Andrew Parker Created: 20/Feb/14 1:09 PM Priority: Normal Reporter: gepetto-bot Procedure may vary by project and point in the release cycle. Ask around. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop
Jira (HI-204) Is checklist current
Title: Message Title gepetto-bot created an issue Hiera / HI-204 Is checklist current Issue Type: Sub-task Assignee: Andrew Parker Created: 20/Feb/14 1:09 PM Priority: Normal Reporter: gepetto-bot Do sub-tickets here match steps in https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process? And do those steps need updating for any recent tooling changes? Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you a
Jira (HI-206) Is there a bug targeted at the release for every commit?
Title: Message Title gepetto-bot created an issue Hiera / HI-206 Is there a bug targeted at the release for every commit? Issue Type: Sub-task Assignee: Andrew Parker Created: 20/Feb/14 1:09 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-209) Prepare long form release notes
Title: Message Title gepetto-bot created an issue Hiera / HI-209 Prepare long form release notes Issue Type: Sub-task Assignee: Melissa Stone Created: 20/Feb/14 1:09 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-208) Is a new version created for the next version in the series?
Title: Message Title gepetto-bot created an issue Hiera / HI-208 Is a new version created for the next version in the series? Issue Type: Sub-task Assignee: Andrew Parker Created: 20/Feb/14 1:09 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-205) Ensure tests are passing
Title: Message Title gepetto-bot created an issue Hiera / HI-205 Ensure tests are passing Issue Type: Sub-task Assignee: Andrew Parker Created: 20/Feb/14 1:09 PM Priority: Normal Reporter: gepetto-bot All tests (spec, acceptance) should be passing on all platforms. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop rec
Jira (HI-207) Is there a commit for every bug targeted at the release?
Title: Message Title gepetto-bot created an issue Hiera / HI-207 Is there a commit for every bug targeted at the release? Issue Type: Sub-task Assignee: Andrew Parker Created: 20/Feb/14 1:09 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-203) Hiera 1.3.2 Release
Title: Message Title gepetto-bot created an issue Hiera / HI-203 Hiera 1.3.2 Release Issue Type: Task Assignee: Andrew Parker Created: 20/Feb/14 1:09 PM Priority: Normal Reporter: gepetto-bot See https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiv
Jira (PUP-1656) Merge into pe branch
Title: Message Title Joshua Cooper assigned an issue to Melissa Stone Puppet / PUP-1656 Merge into pe branch Change By: Joshua Cooper Assignee: Joshua Cooper Melissa Stone Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1707) Faces help sometimes blows up when descriptions are absent
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Puppet / PUP-1707 Faces help sometimes blows up when descriptions are absent Change By: Joshua Cooper Assignee: Joshua Cooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1656) Merge into pe branch
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Puppet / PUP-1656 Merge into pe branch Change By: Joshua Cooper Assignee: Joshua Cooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-848) Manage security descriptor protected field
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-848 Manage security descriptor protected field Change By: Rob Reynolds Assignee: Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1677) Placeholder for pe-puppet acceptance test changes Brannan has made which we need to pull into stable and pe-puppet
Title: Message Title Joshua Partlow assigned an issue to Unassigned Puppet / PUP-1677 Placeholder for pe-puppet acceptance test changes Brannan has made which we need to pull into stable and pe-puppet Change By: Joshua Partlow Assignee: Joshua Partlow Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1677) Placeholder for pe-puppet acceptance test changes Brannan has made which we need to pull into stable and pe-puppet
Title: Message Title Joshua Partlow commented on an issue Re: Placeholder for pe-puppet acceptance test changes Brannan has made which we need to pull into stable and pe-puppet Merged to stable in e6e6468, to master in 8cda16b Add Comment Puppet / PUP-1677 Placeholder for pe-puppet acceptance test changes Brannan has made which we need to pull into stable and pe-puppet This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1677) Placeholder for pe-puppet acceptance test changes Brannan has made which we need to pull into stable and pe-puppet
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-1677 Placeholder for pe-puppet acceptance test changes Brannan has made which we need to pull into stable and pe-puppet Change By: Joshua Partlow Assignee: Joshua Partlow Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1204) Puppet Master (3.2.2/CentOs) -> Puppet Agent (3.2.2/W2008)
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1204 Puppet Master (3.2.2/CentOs) -> Puppet Agent (3.2.2/W2008) Change By: Joshua Cooper Labels: redmine ssl Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1273) Error message ssl_connect returned=1 errno=0 state=sslv3 read server certificate b: certificate verify failed
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1273 Error message ssl_connect returned=1 errno=0 state=sslv3 read server certificate b: certificate verify failed Change By: Joshua Cooper Labels: redmine ssl Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1411) Windows agents experience intermittent SSL_connect failures in acceptance testing
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1411 Windows agents experience intermittent SSL_connect failures in acceptance testing Change By: Joshua Cooper Labels: ssl windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1273) Error message ssl_connect returned=1 errno=0 state=sslv3 read server certificate b: certificate verify failed
Title: Message Title
Joshua Cooper commented on an issue
Re: Error message ssl_connect returned=1 errno=0 state=sslv3 read server certificate b: certificate verify failed
The {read server certificate b: certificate verify failed}
message is telling us this is different than
PUP-1411
, and is almost certainly due to clocks not being in sync between the agent and master. If anyone runs into this issue, please include output with `--debug --trace` from both the agent and master. Also include details about the puppet, ruby and openssl versions.
Also in the time since the bug was originally filed in redmine, we've modified the certificate signing code to set the `not_before` date to be slightly in the past when signing certificates and crls.
Add Comment
Puppet / PUP-1273
Error message ssl_connect returned=1 errno=0 state=sslv3 read server certificate b: certificate verify failed
The following error message comes up commonly, based on search results. Information about the error: http://projects.puppetlabs.com/projects/puppet Unfortunately, I have not experienced this error directly. If you are experiencing this error, please append detailed logging information using the --verbose, --debug, and --evaltrace options.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1677) Placeholder for pe-puppet acceptance test changes Brannan has made which we need to pull into stable and pe-puppet
Title: Message Title Branan Purvine-Riley assigned an issue to Branan Purvine-Riley Puppet / PUP-1677 Placeholder for pe-puppet acceptance test changes Brannan has made which we need to pull into stable and pe-puppet Change By: Branan Purvine-Riley Assignee: Branan Purvine-Riley Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1433) Deprecate manifest setting and update packaging
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-1433 Deprecate manifest setting and update packaging Change By: Joshua Partlow Fix Version/s: 3.5.0 Fix Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1204) Puppet Master (3.2.2/CentOs) -> Puppet Agent (3.2.2/W2008)
Title: Message Title Joshua Cooper commented on an issue Re: Puppet Master (3.2.2/CentOs) -> Puppet Agent (3.2.2/W2008) If you are using the same version of ruby, e.g. 1.9, for both client and master, and are using webrick on the master, then this issue is like the same as PUP-1411 . The issue was the agent makes a TCP connection, and then initializes openssl. However, the master will only hold the connection open for 6.2 seconds, and could timeout the connection the client initiated the SSL handshake. If you see errors like "Client disconnected before connection could be established" in the master's webrick log, then that's the issue. We have worked around the issue in the puppetmaster webrick server by extending the timeout to 10s, and modified the agent to ensure that openssl is initialized before starting the TCP handshake. That fix went into 3.4.3, so I recommend giving that a try. If you are using ruby 1.9 on the agent, but ruby 1.8 on the master, then the issue there can be due to the openssl on the client sending TLS SNI extensions that the master's openssl library doesn't understand. I don't have good troubleshooting for that unfortunately. Add Comment Puppet / PUP-1204 Puppet Master (3.2.2/CentOs) -> Puppet Agent (3.2.2/W2008) Hello, I am experiencing this issue. Could not retrieve domain: undefined method `gsub' for nil:NilClass Could not retrieve domain: undefined method `gsub' for nil:NilClass Could not retrieve domain: undefined method `gsub' for nil:NilClass Error: Failed to apply catalog: SSL_connect SYSCALL returned=5 errno=0 state=SSL v2/v3 read server hello A...
Jira (PUP-1592) Puppet excessively stats the filesystem when looking for defined types
Title: Message Title Andrew Parker assigned an issue to Henrik Lindberg Puppet / PUP-1592 Puppet excessively stats the filesystem when looking for defined types Change By: Andrew Parker Assignee: Brice Figureau Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1678) Environment Endpoint should show configuration and not all modules
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-1678 Environment Endpoint should show configuration and not all modules Change By: Joshua Partlow Assignee: Andrew Parker Joshua Partlow Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Alejandro Figueroa commented on an issue Re: Invalid parameter provider for custom types/providers I can confirm Net Kgk's diagnosis. The module was different on my servers (puppetlabs/vcsrepo) but the results were the same. Add Comment Puppet / PUP-1515 Invalid parameter provider for custom types/providers In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-897) package type should accept virtual package for rpm
Title: Message Title
Peter Huene commented on an issue
Re: package type should accept virtual package for rpm
For functional review, you can use a the "vim" virtual package to see if it will install without errors.
package { 'vim':
ensure => installed
}
Without the fix, yum will install "vim" (vim-enhanced is the package that should be installed) and then rpm will fail to query it, causing an error.
With the fix, yum will install "vim" and then rpm will find the vim virtual package, so it should install successfully.
Add Comment
Puppet / PUP-897
package type should accept virtual package for rpm
Rpm ( like many similar package systems ) define a system of virtual package, with the tag Provides. For example, on Mandriva, we have : $ rpm -q --provides perl-Term-Size-Any-0.1.0-2mdv2010.1 perl(Term::Size::Any) = 0.1.0 perl-Term-Size-Any = 0.1.0-2mdv2010.1 So I can use "urpmi perl(Term::Size::Any)" to install the rpm. On puppet,...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1741) yumrepo can create a non-idempotent repository file
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-1741
yumrepo can create a non-idempotent repository file
Change By:
Christopher Wood
If I use this the attached yumrepo declaration :yumrepo { 'centos-media': baseurl => "file:///media/CentOS/\nfile:///media/cdrom/\nfile:///media/cdrecorder/", #baseurl => "file:///media/CentOS/\nfile:///media/cdrom/\nfile:///media/cdrecorder/", enabled => "0", gpgcheck => "1", gpgkey => 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6', mirrorlist => absent, descr => 'CentOS-$releasever - Media', priority => absent,}Then then things are fine (notice the leading spaces before the next two file urls):[root@cwt1 ~]# puppet apply --verbose /tmp/yr.pp Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rbInfo: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/pe_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/root_home.rbInfo: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rbInfo: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rbInfo: Loading facts in /var/lib/puppet/lib/facter/iptables_persistent_version.rbNotice: Compiled catalog for cwt1.carrierzone.com in environment production in 0.08 secondsInfo: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rbInfo: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/pe_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/root_home.rbInfo: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rbInfo: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rbInfo: Loading facts in /var/lib/puppet/lib/facter/iptables_persistent_version.rbInfo: Applying configuration version '1392918241'Info: create new repo centos-media in file /etc/yum.repos.d/centos-media.repoNotice: /Stage[main]/Main/Yumrepo[centos-media]/descr: descr changed '' to 'CentOS-$releasever - Media'Notice: /Stage[main]/Main/Yumrepo[centos-media]/baseurl: baseurl changed '' to 'file:///media/CentOS/file:///media/cdrom/file:///media/cdrecorder/'Notice: /Stage[main]/Main/Yumrepo[centos-media]/enabled: enabled changed '' to '0'Notice: /Stage[main]/Main/Yumrepo[centos-media]/gpgcheck: gpgcheck changed '' to '1'Notice: /Stage[main]/Main/Yumrepo[centos-media]/gpgkey: gpgkey changed '' to 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6'Info: changing mode of /etc/yum.repos.d/centos-media.repo from 600 to 644Notice: Finished catalog run in 0.16 seconds[root@cwt1 ~]# puppet apply --verbose /tmp/yr.pp Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rbInfo: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/pe_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/root_home.rbInfo: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rbInfo: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rbInfo: Loading facts in /var/lib/puppet/lib/facter/iptables_persistent_version.rbNotice: Compiled catalog for cwt1.carrierzone.com in environment pro
Jira (PUP-1676) Puppet config print respects legacy but not directory environments
Title: Message Title
Joshua Partlow commented on an issue
Re: Puppet config print respects legacy but not directory environments
Merged to master in bed03b9. We ended up with a different approach for the present; we're constructing a block of settings if unable to find a legacy environment and current environment matches a directory environment.
Add Comment
Puppet / PUP-1676
Puppet config print respects legacy but not directory environments
Puppet config print and --configprint respect only legacy environments if specified. For example: {code} jpartlow@percival:~/work/puppet$ cat ~/.puppet/puppet.conf [legacy] modulepath=/home/jpartlow/work/tmp/envs/legacy jpartlow@percival:~/work/puppet$ tree ~/.puppet/environments/ /home/jpartlow/.puppet/environments/ └── direnv └── mod...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at h
Jira (PUP-1741) yumrepo can create a non-idempotent repository file
Title: Message Title Christopher Wood updated an issue Puppet / PUP-1741 yumrepo can create a non-idempotent repository file Since the formatting is bad in the description, I am attaching the yumrepo resource in question. Change By: Christopher Wood Attachment: yr.pp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1072) support HTTP(S) URL as the file 'source'
Title: Message Title
Khoury Brazil commented on an issue
Re: support HTTP(S) URL as the file 'source'
Agreed, this would make working with windows hosts (particularly ones that aren't on a domain) a lot simpler.
Add Comment
Puppet / PUP-1072
support HTTP(S) URL as the file 'source'
Lots and lots of folks want to be able to do this: file { "/tmp/example.txt": source => 'http://example.com/example.txt' } This would be good to support; obviously the metadata for the HTTP URI is much less available than via puppet file serving, but this would make a lot of people very, very happy.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1741) yumrepo can create a non-idempotent repository file
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-1741
yumrepo can create a non-idempotent repository file
Change By:
Christopher Wood
If I use this yumrepo declaration:yumrepo { 'centos-media': baseurl => "file:///media/CentOS/\nfile:///media/cdrom/\nfile:///media/cdrecorder/", #baseurl => "file:///media/CentOS/\nfile:///media/cdrom/\nfile:///media/cdrecorder/", enabled => "0", gpgcheck => "1", gpgkey => 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6', mirrorlist => absent, descr => 'CentOS-$releasever - Media', priority => absent, }Then things are fine (notice the leading spaces before the next two file urls):[root@cwt1 ~]# puppet apply --verbose /tmp/yr.pp Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rbInfo: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/pe_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/root_home.rbInfo: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rbInfo: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rbInfo: Loading facts in /var/lib/puppet/lib/facter/iptables_persistent_version.rbNotice: Compiled catalog for cwt1.carrierzone.com in environment production in 0.08 secondsInfo: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rbInfo: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/pe_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/root_home.rbInfo: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rbInfo: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rbInfo: Loading facts in /var/lib/puppet/lib/facter/iptables_persistent_version.rbInfo: Applying configuration version '1392918241'Info: create new repo centos-media in file /etc/yum.repos.d/centos-media.repoNotice: /Stage[main]/Main/Yumrepo[centos-media]/descr: descr changed '' to 'CentOS-$releasever - Media'Notice: /Stage[main]/Main/Yumrepo[centos-media]/baseurl: baseurl changed '' to 'file:///media/CentOS/file:///media/cdrom/file:///media/cdrecorder/'Notice: /Stage[main]/Main/Yumrepo[centos-media]/enabled: enabled changed '' to '0'Notice: /Stage[main]/Main/Yumrepo[centos-media]/gpgcheck: gpgcheck changed '' to '1'Notice: /Stage[main]/Main/Yumrepo[centos-media]/gpgkey: gpgkey changed '' to 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6'Info: changing mode of /etc/yum.repos.d/centos-media.repo from 600 to 644Notice: Finished catalog run in 0.16 seconds[root@cwt1 ~]# puppet apply --verbose /tmp/yr.pp Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rbInfo: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/pe_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/root_home.rbInfo: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rbInfo: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rbInfo: Loading facts in /var/lib/puppet/lib/facter/iptables_persistent_version.rbNotice: Compiled catalog for cwt1.carrierzone.com in environment productio
Jira (PUP-1741) yumrepo can create a non-idempotent repository file
Title: Message Title
Christopher Wood created an issue
Puppet / PUP-1741
yumrepo can create a non-idempotent repository file
Issue Type:
Bug
Affects Versions:
3.4.2
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
20/Feb/14 9:56 AM
Environment:
[root@cwt1 ~]# cat /etc/redhat-release CentOS release 6.2 (Final) [root@cwt1 ~]# uname -a Linux cwt1 2.6.32-220.el6.x86_64 #1 SMP Tue Dec 6 19:48:22 GMT 2011 x86_64 x86_64 x86_64 GNU/Linux [root@cwt1 ~]# puppet --version 3.4.2
Priority:
Minor
Reporter:
Christopher Wood
If I use this yumrepo declaration:
yumrepo { 'centos-media': baseurl => "file:///media/CentOS/\nfile:///media/cdrom/\nfile:///media/cdrecorder/", #baseurl => "file:///media/CentOS/\n file:///media/cdrom/\n file:///media/cdrecorder/", enabled => "0", gpgcheck => "1", gpgkey => 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6', mirrorlist => absent, descr => 'CentOS-$releasever - Media', priority => absent, }
Then things are fine (notice the leading spaces before the next two file urls):
[root@cwt1 ~
Jira (PUP-1740) Augeas provider doesn't handle escapes properly
Title: Message Title
Theo Cabrerizo Diem created an issue
Puppet / PUP-1740
Augeas provider doesn't handle escapes properly
Issue Type:
Bug
Affects Versions:
3.4.2
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
20/Feb/14 7:34 AM
Environment:
Debian/Linux wheezy (stable), using puppet packages from apt.puppetlabs.com
Labels:
augeas
Priority:
Critical
Reporter:
Theo Cabrerizo Diem
Augeas provider cannot properly pass escapes to libaugeas as some lenses need it. For example:
# cat test.pp
node 'puppet' {
augeas { "/tmp/mytest.txt":
lens=> 'Shellvars.lns',
incl=> '/tmp/mytest.txt',
changes => [ "set VAR1[last() + 1] '\$VAR1 value4'",
Jira (FACT-344) facter packages depend on dmidecode but it is unavailable on arm architecture
Title: Message Title Christophe Bliard created an issue Facter / FACT-344 facter packages depend on dmidecode but it is unavailable on arm architecture Issue Type: Bug Affects Versions: 1.7.5, 1.7.4 Assignee: Eric Sorenson Created: 20/Feb/14 7:03 AM Environment: Debian Wheezy 7.0 on Raspberry PI. uname -a -> Linux goldberry 3.6.11+ #408 PREEMPT Wed Apr 10 20:33:39 BST 2013 armv6l GNU/Linux Priority: Normal Reporter: Christophe Bliard facter debian packages from http://apt.puppetlabs.com/ cannot be installed on ARM architecture due to dependency on the dmidecode package. The dmidecode debian package is not available on the ARM architecture. In fact it is stated in the dmidecode home page that dmidecode is only available on i386, x86-64 and ia64 architectures. dmidecode dependency has been introduced with facter 1.6.4. Package: facter Version: 1.6.4-1puppetlabs1 Architecture: all Maintainer: Puppet Labs Installed-Size: 416 Depends: ruby1.8, libopenssl-ruby1.8, dmidecode Section: ruby facter packages from Debian repositories solve this by moving this to a Recom
Jira (PUP-1570) Puppet Agent hanging on applying configuration
Title: Message Title Glenn Schmidt commented on an issue Re: Puppet Agent hanging on applying configuration I think i'm experiencing the same problem. It's happened more than once. Currently I have 2 hosts that have been stuck at 'applying configuration' for the past 17 days. These are running Ubuntu 12.04.4, kernel 3.8.0-35-generic x86_64. $ ps -eF | grep puppet root 1252 1 0 26289 43940 3 Jan31 ?00:00:08 /usr/bin/ruby /usr/bin/puppet agent root 13511 1252 0 39871 77352 4 Feb03 ?00:00:01 puppet agent: applying configurat $ strace -p 13511 Process 13511 attached - interrupt to quit select(5, [4], NULL, NULL, NULL ^C Process 13511 detached $ ls -l /proc/13511/fd/ total 0 lr-x-- 1 root root 64 Feb 20 20:49 0 -> /dev/null l-wx-- 1 root root 64 Feb 20 20:49 1 -> /dev/null l-wx-- 1 root root 64 Feb 20 20:49 2 -> /dev/null lrwx-- 1 root root 64 Feb 20 20:49 3 -> socket:[11712] lrwx-- 1 root root 64 Feb 20 20:49 4 -> socket:[145611] $ lsof | grep 145611 puppet13511 root4u IPv4 145611 0t0TCP this.puppet.agent:48099->my.puppet.master:8140 (ESTABLISHED) Puppet 3.4.2, Facter 1.7.5 Add Comment Puppet / PUP-1570 Puppet Agent hanging on applying configuration
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Net Kgk commented on an issue Re: Invalid parameter provider for custom types/providers I've got this issue, with next settings: ... [master] ... environment = production ... manifest = $confdir/environments/$environment/manifests/site.pp modulepath = $confdir/environments/$environment/modules ... Then, when I've updated different environment (let's say test) with new module (puppet-labs/mysql), I've got this exception on master while running puppet agent with --environment='test' on different host, because puppet-labs/mysql was absent in production environment. Add Comment Puppet / PUP-1515 Invalid parameter provider for custom types/providers In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
