Jira (PUP-3631) NIM provider uses a regex that is too restrictive when parsing RPM release tags
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3631 NIM provider uses a regex that is too restrictive when parsing RPM release tags Change By: Geoff Nichols Sprint: Agent 2017-03-22 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1334) Empty clientbucket files produce errors
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-1334 Empty clientbucket files produce errors Change By: Geoff Nichols Sprint: Agent 2017-03-22 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6762) (SPIKE) How and when do we get PO files from Transifex?
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6762 (SPIKE) How and when do we get PO files from Transifex? Change By: Geoff Nichols Sprint: AP 2016-11-16, Agent 2017-03-22 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6708) Agent does not save local copy of last_run_report.yaml if submission to report server fails
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6708 Agent does not save local copy of last_run_report.yaml if submission to report server fails Change By: Geoff Nichols Sprint: Agent 2017-03-22 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' command
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6739 If no matching local $environment folder on agent, error when running any 'puppet config' command Change By: Geoff Nichols Sprint: Agent 2017-03-22 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6675 Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Change By: Geoff Nichols Sprint: Agent 2017-03-22 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-777) Facter should not downcase fact names
Title: Message Title Geoff Nichols updated an issue Facter / FACT-777 Facter should not downcase fact names Change By: Geoff Nichols Sprint: Agent 2017-03-22 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7077) Puppet::Util::Windows::File.replace_file fails on UNC paths
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7077 Puppet::Util::Windows::File.replace_file fails on UNC paths Change By: Geoff Nichols Sprint: Agent 2017-03-22 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6764) Add PO files with translated strings to Puppet repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6764 Add PO files with translated strings to Puppet repo Change By: Geoff Nichols Sprint: Agent 2017-03-22 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6040) "puppet facts" outputs indirector object instead of simple fact list
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6040 "puppet facts" outputs indirector object instead of simple fact list Change By: Geoff Nichols Sprint: Agent 2017-04-05 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5993) Possible intermittent test failure in registry_spec.rb
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5993 Possible intermittent test failure in registry_spec.rb Change By: Geoff Nichols Sprint: Agent 2017-04-05 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1358) Add GCC 6.1.0 testing to CI, update instructions
Title: Message Title Geoff Nichols commented on FACT-1358 Re: Add GCC 6.1.0 testing to CI, update instructions We've decided to defer bumping our toolchain's GCC/Boost versions until sometime after Puppet (Agent) 5. Is this something we should consider doing independently of a GCC update? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1461) Reload facter.conf when puppet reloads its configuration
Title: Message Title Geoff Nichols commented on FACT-1461 Re: Reload facter.conf when puppet reloads its configuration Moving this out of the original FACT-1444 "Configurable Facter" Epic. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1444) Enable run-time configuration of facter
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1444 Enable run-time configuration of facter Change By: Geoff Nichols Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1462) Allow disabling subsections of structured facts
Title: Message Title Geoff Nichols commented on FACT-1462 Re: Allow disabling subsections of structured facts Moving this out of the original FACT-1444 "Configurable Facter" Epic. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1407) Facter Cacheable uses wrong external facts path
Title: Message Title Geoff Nichols commented on FACT-1407 Re: Facter Cacheable uses wrong external facts path Trey Dockendorf, no worries at all - thanks for the update. I'll move this to Closed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3551) Sanitize non-UTF-8 data in run reports
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3551 Sanitize non-UTF-8 data in run reports Change By: Geoff Nichols Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6893) Remove Ruby 1.9.3 support
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6893 Remove Ruby 1.9.3 support Change By: Geoff Nichols Team/s: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6893) Remove Ruby 1.9.3 support
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6893 Remove Ruby 1.9.3 support Change By: Geoff Nichols Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7311) runit service restart override doesn't work
Title: Message Title
Oskar Levin updated an issue
Puppet / PUP-7311
runit service restart override doesn't work
Change By:
Oskar Levin
When supplying the restart command, it still runs sv restart oskar-test-service rather than the restart command I specified.service { 'oskar-test-service': provider => 'runit', ensure => 'running', restart => '/bin/kill -HUP \$(cat /etc/service/oskar-test-service/supervise/pid)',}Using this on CentOS 7 and with systemd and it seems to work there, but not with the runit provider. Related/useful links:https://projects.puppetlabs.com/issues/2642https://projects.puppetlabs.com/issues/18021
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7308) classes do not honor refresh events when running with tags
Title: Message Title Pete Fritchman commented on PUP-7308 Re: classes do not honor refresh events when running with tags Henrik Lindberg, the class resource seems to have the proper tags in the catalog with 4.9.3. Moses Mendoza, Good call on relationship_graph.rb! It looks like the created whit resources do not have the tags of the class resource they are created from. I took a stab at the change and test here: https://github.com/fetep/puppet/commit/1fe014507c071b61e9f870b9c23f6d6b868b14bc Copying the tags over to the admissible whit with set_tags appears to do the trick - notifying Class["foo"] successfully triggers the refresh event on Exec["notify test"]! I don't understand the flow well enough to know if the tags also need to also be on the completed whit. All the tests I can run pass with this change. noformat Info: Applying configuration version '1488938101' Notice: /Stage[main]/Test/Exec[test]/returns: executed successfully Info: /Stage[main]/Test/Exec[test]: Scheduling refresh of Class[Foo] Info: Class[Foo]: Scheduling refresh of Exec[notify test] Notice: /Stage[main]/Foo/Exec[notify test]: Triggered 'refresh' from 1 events Info: Class[Foo]: Unscheduling all events on Class[Foo] Info: Stage[main]: Unscheduling all events on Stage[main] noformat Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7317) Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
Title: Message Title
SFGroups created an issue
Puppet / PUP-7317
Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
Issue Type:
Bug
Affects Versions:
PUP 4.9.2
Assignee:
Unassigned
Components:
CLI
Created:
2017/03/07 5:50 PM
Environment:
Centos 7 with Puppet v4.9.2,
Priority:
Normal
Reporter:
SFGroups
in Centos 7 with Puppet v4.9.2, trying to install java and tomcat. When i run the apply command. it giving the warning message.
pp file:
node 'webserver' {
Jira (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-3323 Checking if a report exists before inserting it is SLOW Change By: Susan McNerney Fix Version/s: PDB 4.3.x Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7261) Add/Honor charset parameter in Content-Type header
Title: Message Title Jeremy Barlow commented on PUP-7261 Re: Add/Honor charset parameter in Content-Type header Josh Cooper I'm okay with that based on your findings with the google and github requests although I do think that some HTTP clients may have problems with that given that there is the potential for ambiguity between the charset in the Content-Type header and the actual payload for JSON as you mentioned. For Puppet Server, we'd need to look into appending the charset for any Clojure-provided endpoints, which primarily include just the Puppet Server CA. For requests that we route down through the indirector in Ruby Puppet, we just take the :content-type provided back from the response and pass it on through to the webserver, per this line. Would you expect that the charset would be appended to the :content-type in core Ruby Puppet code before being passed back up to the HTTP::Handler layer, e.g., Puppet Server's Puppet::Server::Master class? /CC Adrien Thebo. I think we should consider any Puppet Server-related work for this in SERVER-1734. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-3323
Checking if a report exists before inserting it is SLOW
Change By:
Nick Walker
h1. The ProblemWorking with a customer we noticed performance degradation after updating from PE 2016.4 to 2016.5.2. Using PgBadger to analyze the PostgreSQL logs we can see that checking to see if a report already exists is taking longer than 5 seconds much more frequently than expected. Researching on my own test install I can see that the query performs a Seq Scan on reports because the where clause doesn't match an index. Adding an index on the hash column that isn't wrapped in a function causes the query plan to switch to using a Index Only Scan. {code}pe-puppetdb=# explain analyze select 1 from reports where hash = '\x7ad27615d5c7de439855b245e5eb6d7245e812f6';QUERY PLAN-- Seq Scan on reports (cost=0.00..39.31 rows=1 width=0) (actual time=0.012..0.105 rows=1 loops=1) Filter: (hash = '\x7ad27615d5c7de439855b245e5eb6d7245e812f6'::bytea) Rows Removed by Filter: 186 Planning time: 0.142 ms Execution time: 0.133 ms(5 rows)pe-puppetdb=# create unique index test on reports(hash);CREATE INDEXpe-puppetdb=# explain analyze select 1 from reports where hash = '\x7ad27615d5c7de439855b245e5eb6d7245e812f6';QUERY PLAN --- Index Only Scan using test on reports (cost=0.14..8.16 rows=1 width=0) (actual time=0.033..0.035 rows=1 loops=1) Index Cond: (hash = '\x7ad27615d5c7de439855b245e5eb6d7245e812f6'::bytea) Heap Fetches: 1 Planning time: 0.346 ms Execution time: 0.062 ms(5 rows){code}h1. Customer Impact / How it manifestedWe saw that PuppetDB could only manage to work 5 commands / sec despite trying to bump command processing threads to 10 on a 8 core PuppetDB node. CPU usage on the PostgreSQL node showed steady 40% use on 2016.4 and immediately increased to 60% after the upgrade to 2016.5. Not perfect science here but that's a 50% degradation in CPU use. h1. Possible SolutionsAdding the index should make the query faster, {{CREATE UNIQUE INDEX idx_reports_hash on reports(hash)}}Otherwise we can simply stop checking if the report already exists before inserting it. h1. Additional ThoughtsI think we should research the current index on the hash column and determine if queries are being designed to hit it or if queries are being constructed like the one above. We hopefully shouldn't need two indexes on the same column but we should make it easy to construct queries without special knowledge of how to make the where clause.
Jira (PUP-7240) A custom LookupAdapter provided to a Puppet::Pops::Lookup::Invocation is ignored if a parent_invocation exists.
Title: Message Title Joshua Partlow commented on PUP-7240 Re: A custom LookupAdapter provided to a Puppet::Pops::Lookup::Invocation is ignored if a parent_invocation exists. We have this patch in PE and are testing it in this pipeline with MEEP (https://jenkins-master-prod-1.delivery.puppetlabs.net/view/pe-integration/view/pe-modules-next/) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7261) Add/Honor charset parameter in Content-Type header
Title: Message Title Josh Cooper commented on PUP-7261 Re: Add/Honor charset parameter in Content-Type header Strictly speaking the charset is redundant because json parsers are supposed to detect the encoding, UTF-8, UTF-16 (BE or LE) , UTF-32 (BE or LE), based on the presences of null bytes in the first 4 octets, see https://www.ietf.org/rfc/rfc4627.txt, section 3 Encoding. But in practice, both google and github include the following charset: curl -i https://api.github.com/users/joshcooper HTTP/1.1 403 Forbidden Server: GitHub.com Date: Wed, 08 Mar 2017 00:22:23 GMT Content-Type: application/json; charset=utf-8 curl -i https://www.googleapis.com/customsearch/v1 HTTP/1.1 400 Bad Request Vary: X-Origin
Jira (PDB-3324) Remove redundant acceptance tests
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3324 Remove redundant acceptance tests Change By: Russell Mull Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3324) Remove redundant acceptance tests
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3324 Remove redundant acceptance tests Change By: Russell Mull Story Points: 1 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3326) Clean up temp dir handling in integration tests
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3326 Clean up temp dir handling in integration tests Issue Type: Bug Assignee: Unassigned Created: 2017/03/07 4:21 PM Priority: Normal Reporter: Russell Mull Current handling of temporary state is haphazard at best. There should be a different top-level temp dir used for each test case, which contains puppetdb + puppetserver configuration, agent config dirs, and whatever other temporary state is required. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3325) Audit acceptance / integration tests for coverage gaps
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3325 Audit acceptance / integration tests for coverage gaps Issue Type: New Feature Assignee: Unassigned Created: 2017/03/07 4:19 PM Priority: Normal Reporter: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-3324) Remove redundant acceptance tests
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3324 Remove redundant acceptance tests Issue Type: New Feature Assignee: Unassigned Created: 2017/03/07 4:19 PM Priority: Normal Reporter: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-3310) [module PR] Fix duplicate resource errors for puppet service due to parse order
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3310 [module PR] Fix duplicate resource errors for puppet service due to parse order Change By: Russell Mull Summary: [module PR ] Fix duplicate resource errors for puppet service due to parse order Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3310) [module] Fix duplicate resource errors for puppet service due to parse order
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-3310 [module] Fix duplicate resource errors for puppet service due to parse order Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3310) [module] Fix duplicate resource errors for puppet service due to parse order
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3310 [module] Fix duplicate resource errors for puppet service due to parse order Change By: Russell Mull Summary: [module] Fix duplicate resource errors for puppet service due to parse order Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3308) Error 500 on 'puppet agent -t' (SSL Problem)
Title: Message Title Russell Mull commented on PDB-3308 Re: Error 500 on 'puppet agent -t' (SSL Problem) Hi Wolfgang Grossinger, In order to connect to PuppetDB over HTTPS, the hostname in your sever_url needs to be the same as the Common Name on your PuppetDB's SSL certificate (or be listed in the cert as an alternate name). I think that should help your problem. > It might be that I can find the problem by myself but for me it seems that at least the documentation is not complete (as far as I could see, I did everything as notet in the docs). That's not great; if this fixes your problem (and I think it should) we'll take a look at the docs to see if there's anything we can clarify. Just for completeness, can you tell us which docs you were following? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title Adam Bottchen updated an issue PuppetDB / PDB-3323 Checking if a report exists before inserting it is SLOW Change By: Adam Bottchen Release Notes: Known Issue Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3308) Error 500 on 'puppet agent -t' (SSL Problem)
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-3308 Error 500 on 'puppet agent -t' (SSL Problem) Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-868) Deprecate Unusable Certificate Faces
Title: Message Title
James Ralston commented on PUP-868
Re: Deprecate Unusable Certificate Faces
Andrew Parker, we use the certificate_revocation_list face to distribute our CA master's crl to our [non-CA] Puppet master pool, by having the non-CA masters regularly poll the CA master for the latest crl:
$ puppet certificate_revocation_list find ca --terminus rest
I do not see a way to do this using puppet cert. The only way I see to do it is to call the Puppet HTTP API directly. E.g.:
$ CA_SERVER=$(puppet config print --section master ca_server)
$ LOCAL_CA_CERT=$(puppet config print --section master localcacert)
$ curl --cacert ${LOCAL_CA_CERT} https://${CA_SERVER}:8140/puppet-ca/v1/certificate_revocation_list/ca\?environment\=ignored
Am I missing how to perform the same action using puppet cert?
Or are you deprecating a face that provides needed functionality (for sites running Puppet Open Source with multiple Puppet servers) without providing a functional replacement?
Add Comment
Jira (FACT-1583) Facter fails to build on fedora 24 (libfacter tests fail)
Title: Message Title Josh Cooper updated an issue Facter / FACT-1583 Facter fails to build on fedora 24 (libfacter tests fail) Change By: Josh Cooper Release Notes Summary: This change provides more debugging info if/when the test next fails. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6979) Puppet Module List fails in code page 65001 on ja-JP windows
Title: Message Title Erick Banks commented on PUP-6979 Re: Puppet Module List fails in code page 65001 on ja-JP windows Attached the full output for a "puppet module list --debug" while in code page 65001 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7289) PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7289 PUP 4.9.3 interpolation in hiera.yaml datadir stopped working Change By: Eric Thompson Labels: flanders-ss regression Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7316) Dissimilar results from puppet facts vs. facter -p
Title: Message Title Thomas Speigner created an issue Puppet / PUP-7316 Dissimilar results from puppet facts vs. facter -p Issue Type: Bug Assignee: Unassigned Created: 2017/03/07 3:29 PM Priority: Normal Reporter: Thomas Speigner In the facter --help it states that facter -p has been deprecated and that users should instead use puppet facts. The problem that I have found is that the functionality varies between the two implementations. Results: #facter -p uptime 11 days puppet facts uptime dumps the entire JSON output WITHOUT displaying the fact specifically (like facter -p does) The expected behavior is that the functionality that was replaced should act the same was the original functionality. Expected results are that each output is the same or at least similar. Add Comment
Jira (PUP-6979) Puppet Module List fails in code page 65001 on ja-JP windows
Title: Message Title Erick Banks updated an issue Puppet / PUP-6979 Puppet Module List fails in code page 65001 on ja-JP windows Change By: Erick Banks Attachment: puppet module list japanese Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7272) Puppet not using latest facts
Title: Message Title Moses Mendoza commented on PUP-7272 Re: Puppet not using latest facts thanks Jacky Leung. Given this info I think you are encountering the same as PUP-7198 - thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-560) hiera() and lookup() performing merge by default
Title: Message Title Thomas Hallgren commented on HI-560 Re: hiera() and lookup() performing merge by default Eric Thompson is correct. We had an issue that made both the hiera and the lookup function merge arrays when a merge_behavior was defined in hiera.yaml. That was incorrect. The merge_behavior in hiera.yaml should only be used by the hiera_hash function and nowhere else. This was fixed in PUP-7286 which will be released in 4.9.4. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7314) Implied module namespace for PCore objects
Title: Message Title Henrik Lindberg commented on PUP-7314 Re: Implied module namespace for PCore objects That would require a new keyword which is a bigger thing and would need to wait until major release. I am also somewhat reluctant over what nesting of namespaces would mean as it kind of suggests containment rather than lexical scoping. If the intent is to make all the names available I can imagine something like: import MyModule::TypeSet or some variation thereof - i.e. make all the names in that namespace be names in this file. That as an alternative to mounting them on a prefix - e.g. import MyPrefix = MyModule::TypeSet Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1583) Facter fails to build on fedora 24 (libfacter tests fail)
Title: Message Title Josh Cooper updated an issue Facter / FACT-1583 Facter fails to build on fedora 24 (libfacter tests fail) Change By: Josh Cooper Fix Version/s: FACT 3.6.2 Fix Version/s: FACT 3.4.3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1583) Facter fails to build on fedora 24 (libfacter tests fail)
Title: Message Title Josh Cooper updated an issue Facter / FACT-1583 Facter fails to build on fedora 24 (libfacter tests fail) Change By: Josh Cooper Fix Version/s: FACT 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-560) hiera() and lookup() performing merge by default
Title: Message Title Scott Nolin commented on HI-560 Re: hiera() and lookup() performing merge by default In my understanding, yes hiera_array merging them is expected, not hiera (or default lookup). I looked for a similar PUP ticket, didn't quite find it. It's not that it's always doing a merge. It's always doing a merge on non-scalar data types. On scalar data types it's as expected. Scott Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6885) Remove warning about server_list and server conflicting
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6885 Remove warning about server_list and server conflicting Change By: Geoff Nichols Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7070) Remove stacktrace property of http error response object
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7070 Remove stacktrace property of http error response object Change By: Geoff Nichols Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1583) Facter fails to build on fedora 24 (libfacter tests fail)
Title: Message Title Josh Cooper updated an issue Facter / FACT-1583 Facter fails to build on fedora 24 (libfacter tests fail) Change By: Josh Cooper Summary: puppet-agent#stable Facter fails to build on fedora 24 (libfacter tests fail) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1583) Facter fails to build on fedora 24 (libfacter tests fail)
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Facter / FACT-1583 Facter fails to build on fedora 24 (libfacter tests fail) Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1583) puppet-agent#stable fails to build on fedora 24 (libfacter tests fail)
Title: Message Title Josh Cooper commented on FACT-1583 Re: puppet-agent#stable fails to build on fedora 24 (libfacter tests fail) Moving to facter project Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1583) puppet-agent#stable fails to build on fedora 24 (libfacter tests fail)
Title: Message Title Josh Cooper moved an issue Facter / FACT-1583 puppet-agent#stable fails to build on fedora 24 (libfacter tests fail) Change By: Josh Cooper Key: PA FACT - 985 1583 Project: Puppet Agent Facter Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-560) hiera() and lookup() performing merge by default
Title: Message Title
Eric Thompson commented on HI-560
Re: hiera() and lookup() performing merge by default
interestingly, hiera_array merges them:
[root@tj0x2q33kxhsdx6 ~]# puppet apply -e 'notice(hiera_array("array"))' --environment merge_strategies_p1nlft2w
Warning: The function 'hiera_array' is deprecated in favor of using 'lookup'. See https://docs.puppet.com/puppet/4.9.4/reference/deprecated_language.html
(file & line not available)
Warning: /etc/puppetlabs/puppet/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
(in /etc/puppetlabs/puppet/hiera.yaml)
Notice: Scope(Class[main]): [foo, bar]
Notice: Compiled catalog for tj0x2q33kxhsdx6.delivery.puppetlabs.net in environment merge_strategies_p1nlft2w in 0.11 seconds
Notice: Applied catalog in 0.02 seconds
Jira (HI-560) hiera() and lookup() performing merge by default
Title: Message Title
Eric Thompson commented on HI-560
Re: hiera() and lookup() performing merge by default
Thomas Hallgren i believe this is fixed in the most recent (unreleased build):
[root@tj0x2q33kxhsdx6 ~]# puppet apply -e 'notice(hiera("array"))' --environment merge_strategies_p1nlft2w
Warning: The function 'hiera' is deprecated in favor of using 'lookup'. See https://docs.puppet.com/puppet/4.9.4/reference/deprecated_language.html
(file & line not available)
Warning: /etc/puppetlabs/puppet/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
(in /etc/puppetlabs/puppet/hiera.yaml)
Notice: Scope(Class[main]): [foo]
Notice: Compiled catalog for tj0x2q33kxhsdx6.delivery.puppetlabs.net in environment merge_strategies_p1nlft2w in 0.10 seconds
Notice: Applied catalog in 0.10 seconds
[root@tj0x2q33kxhsdx6 ~]# puppet apply -e 'notice(lookup("array"))' --environment merge_strategies_p1nlft2w
Jira (PUP-7308) classes do not honor refresh events when running with tags
Title: Message Title
Moses Mendoza updated an issue
Puppet / PUP-7308
classes do not honor refresh events when running with tags
Change By:
Moses Mendoza
It appears that classes are not inheriting tags properly when included, but their resources are. This breaks notifying a class when running with --tags, and results in the relevant resources not getting the notify.tagsbug.pp:{noformat}class foo { exec { 'notify test':command => '/bin/true',refreshonly => true, }}class test { include foo exec { 'test':command => '/bin/true',#notify => Class['foo'],notify => Exec['notify test'], }}include test{noformat}Running: puppet apply --test --tags test tagsbug.ppWith Exec['test'] notifying Exec['notify test']:{noformat}Info: Applying configuration version '1488579119'Notice: /Stage[main]/Test/Exec[test]/returns: executed successfullyInfo: /Stage[main]/Test/Exec[test]: Scheduling refresh of Exec[notify test]Notice: /Stage[main]/Foo/Exec[notify test]: Triggered 'refresh' from 1 eventsInfo: Class[Foo]: Unscheduling all events on Class[Foo]Info: Stage[main]: Unscheduling all events on Stage[main]{noformat}With Exec['test'] notifying Class['foo']:{noformat}Info: Applying configuration version '1488579147'Notice: /Stage[main]/Test/Exec[test]/returns: executed successfullyInfo: /Stage[main]/Test/Exec[test]: Scheduling refresh of Class[Foo]Info: Class[Foo]: Unscheduling all events on Class[Foo]Info: Stage[main]: Unscheduling all events on Stage[main]{noformat}Exec['notify test'] does not get notified/run. Looking at the --debug output:{noformat}Debug: Class[Foo]: Not tagged with testDebug: Class[Foo]: Resource is being skipped, unscheduling all events{noformat}Is this expected behavior? I even tried replacing 'include foo' with:{noformat} class { 'foo': tag => 'test', }{noformat}but the behavior of sending a notify to Class['foo'] is the same (itdoes not trigger Exec['notify test']). *Notes** Initial guess was that this was due to use of `include` instead of `contain` but it was determined that `contain`ed classes also fail to properly refresh events* Internally, classes (containers) are replaced in the graph with whit "resources" (see https://github.com/puppetlabs/puppet/blob/ebd96213cab43bb2a8071b7ac0206c3ed0be8e58/lib/puppet/graph/relationship_graph.rb#L230-L273)* it's possible tags are not correctly being propagated or evaluated to these resources
Add Comment
Jira (HI-560) hiera() and lookup() performing merge by default
Title: Message Title Kenn Hussey commented on HI-560 Re: hiera() and lookup() performing merge by default Henrik Lindberg Thomas Hallgren is this expected? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7308) classes do not honor refresh events when running with tags
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7308 classes do not honor refresh events when running with tags Change By: Moses Mendoza Summary: issue classes do not honor refresh events when running with tags and notifying a class Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-3323
Checking if a report exists before inserting it is SLOW
Change By:
Nick Walker
h1. The ProblemWorking with a customer we noticed performance degradation after updating from PE 2016.4 to 2016.5.2. Using PgBadger to analyze the PostgreSQL logs we can see that checking to see if a report already exists is taking longer than 5 seconds much more frequently than expected. Researching on my own test install I can see that the query performs a Seq Scan on reports because the where clause doesn't match an index. Adding an index on the hash column that isn't wrapped in a function causes the query plan to switch to using a Index Only Scan. {code}pe-puppetdb=# explain analyze select 1 from reports where hash = '\x7ad27615d5c7de439855b245e5eb6d7245e812f6';QUERY PLAN-- Seq Scan on reports (cost=0.00..39.31 rows=1 width=0) (actual time=0.012..0.105 rows=1 loops=1) Filter: (hash = '\x7ad27615d5c7de439855b245e5eb6d7245e812f6'::bytea) Rows Removed by Filter: 186 Planning time: 0.142 ms Execution time: 0.133 ms(5 rows)pe-puppetdb=# create unique index test on reports(hash);CREATE INDEXpe-puppetdb=# explain analyze select 1 from reports where hash = '\x7ad27615d5c7de439855b245e5eb6d7245e812f6';QUERY PLAN --- Index Only Scan using test on reports (cost=0.14..8.16 rows=1 width=0) (actual time=0.033..0.035 rows=1 loops=1) Index Cond: (hash = '\x7ad27615d5c7de439855b245e5eb6d7245e812f6'::bytea) Heap Fetches: 1 Planning time: 0.346 ms Execution time: 0.062 ms(5 rows){code}h1. How it manifestedWe saw that PuppetDB could only manage to work 5 commands / sec despite trying to bump command processing threads to 10 on a 8 core PuppetDB node. CPU usage on the PostgreSQL node showed steady 40% use on 2016.4 and immediately increased to 60% after the upgrade to 2016.5. Not perfect science here but that's a 50% degradation in CPU use. h1. Possible SolutionsAdding the index should make the query faster, {{CREATE UNIQUE INDEX idx_reports_hash on reports(hash)}}Otherwise we can simply stop checking if the report already exists before inserting it. h1. Additional ThoughtsI think we should research the current index on the hash column and determine if queries are being designed to hit it or if queries are being constructed like the one above. We hopefully shouldn't need two indexes on the same column but we should make it easy to construct queries without special knowledge of how to make the where clause.
Jira (PUP-7308) issue with tags and notifying a class
Title: Message Title Moses Mendoza commented on PUP-7308 Re: issue with tags and notifying a class I'm going to update the title of the ticket to focus in on the issue we have, ie that classes aren't receiving refresh events when running with tags Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-560) hiera() and lookup() performing merge by default
Title: Message Title
Eric Thompson updated an issue
Hiera / HI-560
hiera() and lookup() performing merge by default
Change By:
Eric Thompson
We migrated from puppet 3.8 to 4.9I found that hiera() calls no longer default to the first value found for arrays and hashes. It instead now always does a merge. I tried using the new lookup() command, but it behaves the same.Our hiera.yaml is setup with :merge_behavior: deeperWhich I read is now redundant. But that shouldn't affect the default behavior of lookup/hieraI tested by making simple hieradata entry in common.yaml - {{ hieradata_test: foo }} Then in our node specific file set "bar"With this datatype it behaves as expected, reports the first entry - for us, 'bar', the node data.Then turned it into an array {code} hieradata_test - 'foo' {code} In that case hiera('hieradata_test') returned {code} Notice: /Stage[main]/Profiles::Hieradebug/Notify[hiera data test: [foo, bar]]/message: defined 'message' as 'hiera data test: [foo, bar]' {code} I worked around this by changing all of our now 'surprising' calls like this to use lookup() and explicitly setting 'lookup_options' for each key type in common.yaml to 'merge: first'.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-7308) issue with tags and notifying a class
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7308 issue with tags and notifying a class Change By: Moses Mendoza Sprint: Agent Triage Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7308) issue with tags and notifying a class
Title: Message Title Moses Mendoza commented on PUP-7308 Re: issue with tags and notifying a class thanks for pointing that out Pete Fritchman. I repro'd your case and I think I agree this is a bug. Per https://docs.puppet.com/puppet/4.9/lang_relationships.html, If a class or defined resource gets a refresh event, every resource it contains will also get a refresh event. By the letter of that doc, doing notify => Class['foo'] should indeed ensure that the exec is triggered, and it's not. I did some work around tag propagation recently in PUP-6741 , and I think this issue may be floating around somewhere in https://github.com/puppetlabs/puppet/blob/master/lib/puppet/transaction/event_manager.rb, but not sure. Will need to do a bit more investigation to confirm. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7308) issue with tags and notifying a class
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7308 issue with tags and notifying a class Change By: Moses Mendoza Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-560) hiera() and lookup() performing merge by default
Title: Message Title Scott Nolin created an issue Hiera / HI-560 hiera() and lookup() performing merge by default Issue Type: Bug Affects Versions: HI 3.3.0 Assignee: Unassigned Created: 2017/03/07 1:55 PM Environment: Centos 7, puppet-agent-1.9.2-1, puppetserver-2.7.2-1, puppetlabs-release-pc1-1.1.0-5 Priority: Normal Reporter: Scott Nolin We migrated from puppet 3.8 to 4.9 I found that hiera() calls no longer default to the first value found for arrays and hashes. It instead now always does a merge. I tried using the new lookup() command, but it behaves the same. Our hiera.yaml is setup with :merge_behavior: deeper Which I read is now redundant. But that shouldn't affect the default behavior of lookup/hiera I tested by making simple hieradata entry in common.yaml - hieradata_test: foo Then in our node specific file set "bar" With this datatype it behaves as expected, reports the first entry - for us, 'bar', the node data. Then turned it into an array hieradata_test
Jira (PUP-7289) PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Title: Message Title
Thomas Hallgren commented on PUP-7289
Re: PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Alex P, it looks like you are trying to do hiera_hash using lookup instead of a hiera_include. The hiera_include function expects arrays and will simply do a shallow and unique merge of what it finds. The corresponding command using lookup would be:
include(lookup('classes', { 'merge' => 'unique' }))
There is no expectation that hiera_include and the lookup that you are using should give the same result.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7292) Allow to set password warning days for user type
Title: Message Title John Duarte updated an issue Puppet / PUP-7292 Allow to set password warning days for user type Change By: John Duarte Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7292) Allow to set password warning days for user type
Title: Message Title John Duarte updated an issue Puppet / PUP-7292 Allow to set password warning days for user type Change By: John Duarte Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7295) Puppet is too permissive about skipping SSL verification
Title: Message Title John Duarte updated an issue Puppet / PUP-7295 Puppet is too permissive about skipping SSL verification Change By: John Duarte Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7295) Puppet is too permissive about skipping SSL verification
Title: Message Title John Duarte updated an issue Puppet / PUP-7295 Puppet is too permissive about skipping SSL verification Change By: John Duarte Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7302) Puppet HTTP Node API: make fact_merge optional
Title: Message Title John Duarte updated an issue Puppet / PUP-7302 Puppet HTTP Node API: make fact_merge optional Change By: John Duarte Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7302) Puppet HTTP Node API: make fact_merge optional
Title: Message Title John Duarte updated an issue Puppet / PUP-7302 Puppet HTTP Node API: make fact_merge optional Change By: John Duarte Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7298) SUGGESTION: Add return code to error message on file resources
Title: Message Title John Duarte updated an issue Puppet / PUP-7298 SUGGESTION: Add return code to error message on file resources Change By: John Duarte Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7298) SUGGESTION: Add return code to error message on file resources
Title: Message Title John Duarte updated an issue Puppet / PUP-7298 SUGGESTION: Add return code to error message on file resources Change By: John Duarte Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7307) Tidy should support 'purge' or update file resource
Title: Message Title John Duarte updated an issue Puppet / PUP-7307 Tidy should support 'purge' or update file resource Change By: John Duarte Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7307) Tidy should support 'purge' or update file resource
Title: Message Title John Duarte updated an issue Puppet / PUP-7307 Tidy should support 'purge' or update file resource Change By: John Duarte Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7308) issue with tags and notifying a class
Title: Message Title John Duarte updated an issue Puppet / PUP-7308 issue with tags and notifying a class Change By: John Duarte Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7308) issue with tags and notifying a class
Title: Message Title John Duarte updated an issue Puppet / PUP-7308 issue with tags and notifying a class Change By: John Duarte Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7311) runit service restart override doesn't work
Title: Message Title John Duarte updated an issue Puppet / PUP-7311 runit service restart override doesn't work Change By: John Duarte Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7311) runit service restart override doesn't work
Title: Message Title John Duarte updated an issue Puppet / PUP-7311 runit service restart override doesn't work Change By: John Duarte Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7312) Confine systemd provider to /lib/systemd/system
Title: Message Title John Duarte updated an issue Puppet / PUP-7312 Confine systemd provider to /lib/systemd/system Change By: John Duarte Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7314) Implied module namespace for PCore objects
Title: Message Title John Duarte updated an issue Puppet / PUP-7314 Implied module namespace for PCore objects Change By: John Duarte Sprint: PDE Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7314) Implied module namespace for PCore objects
Title: Message Title John Duarte updated an issue Puppet / PUP-7314 Implied module namespace for PCore objects Change By: John Duarte Team: Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7271) performance regression in puppet 4.9
Title: Message Title Paul Kranenburg commented on PUP-7271 Re: performance regression in puppet 4.9 PUP-7309 looks like it may make a difference; I'll re-test with 4.9.4 as soon as possible. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1935) puppetd ignores local ca.pem when connecting to master for the first time
Title: Message Title David Lutterkort assigned an issue to Adrien Thebo Puppet / PUP-1935 puppetd ignores local ca.pem when connecting to master for the first time Change By: David Lutterkort Assignee: Adrien Thebo Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7312) Confine systemd provider to /lib/systemd/system
Title: Message Title John Duarte updated an issue Puppet / PUP-7312 Confine systemd provider to /lib/systemd/system Change By: John Duarte Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7314) Implied module namespace for PCore objects
Title: Message Title
Thomas Hallgren commented on PUP-7314
Re: Implied module namespace for PCore objects
That solution still requires that you prefix everything with the name used for the import, i.e. no gain at all compared to the init_typeset in a module.
Another idea would be to have an explicit mechanism that shortens all names (not just names of types). Example:
namespace MyModule {
// names in here are first resolved locally as , then globally as MyModule::, and lastly as ::
}
It should be possible to nest such namespaces (similar to Ruby modules).
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop
Jira (PUP-7289) PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Title: Message Title Alex P commented on PUP-7289 Re: PUP 4.9.3 interpolation in hiera.yaml datadir stopped working Just an additional note, I'm not saying that lookup function doesn't merge at all.. It merged other hashes, i.e. apt in example above. But for some reason failed to merge a hash with an array in it. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7285) Set metric-id setting in http report processor
Title: Message Title Ruth Linehan updated an issue Puppet / PUP-7285 Set metric-id setting in http report processor Change By: Ruth Linehan Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7289) PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Title: Message Title Alex P commented on PUP-7289 Re: PUP 4.9.3 interpolation in hiera.yaml datadir stopped working It took me quite a bit to troubleshoot (with distraction to other things) but finally was able to locate it. And do confirm, there is still a problem with hash/array merging by puppet lookup! There are two environments configured: Corporate , as per above, i.e. srv01 has multiple sources and destinations in Syslog-ng (each log flow is described as combination of subsets of sources and destinations via syslog_ng::log), managed by Puppet; Enterprise , prod01 server that has local syslog_ng sources and at least one network destination pointed to srv01; As soon as we upgraded to nightly build (puppet-agent 1.9.2.33.gb3e54a4-1jessie), it fixed all Puppet functionality except of syslog_ng on srv01. Got following in trace: --- /etc/syslog-ng/conf.d/90logging.conf2016-10-04 20:17:22.416351058 -0600 +++ /tmp/puppet-file20170306-19595-1g7591e 2017-03-06 08:59:12.942340864 -0700 @@ -1,33 +1,3 @@ # This file is generated by Puppet # DO NOT EDIT!!!
Jira (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title Adam Bottchen commented on PDB-3323 Re: Checking if a report exists before inserting it is SLOW Should this be added as a known issue for 2016.5.2? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3323 Checking if a report exists before inserting it is SLOW Change By: Russell Mull Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3323 Checking if a report exists before inserting it is SLOW Change By: Russell Mull Sprint: SE 2017-03-08 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7315) acceptance: add test for hiera interpolated options
Title: Message Title John Duarte updated an issue Puppet / PUP-7315 acceptance: add test for hiera interpolated options Change By: John Duarte QA Risk Assessment: Needs Assessment Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7308) issue with tags and notifying a class
Title: Message Title Henrik Lindberg commented on PUP-7308 Re: issue with tags and notifying a class This seems to be related to application (agent side) and not compilation. Still it is worth looking at the catalogs produced for 3.8 and your 4.x version to see if there is a difference in the catalog. If not, the issue is all on the agent side. I removed the "won't fix" and returned the ticket to "needs information". Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title Russell Mull commented on PDB-3323 Re: Checking if a report exists before inserting it is SLOW I can easily repro this on puppetdb 4.3.1; looks like it's limited to the insert check, fortunately. We should probably change the query to use the index we already have, to avoid a costly reindex migration. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7308) issue with tags and notifying a class
Title: Message Title Pete Fritchman commented on PUP-7308 Re: issue with tags and notifying a class But it doesn't work, even with class containment. The test in my last comment demonstrates that. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
