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 Don't think so. The way I envision it (and currently experimenting with) is a loader that is initialized with a set of imports. Each import is a TypedName (which means that we, in the future, also can allow import to denote a name authority). The loader is parented by the loader that would otherwise be in effect for the given file. When resolving, the loader will prefix any name passed to it with each name from its import list and pass it to its parent loader. That processing ends as soon as the parent loader finds something. It ends by passing the original name verbatim to the parent loader. 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
Thomas Hallgren commented on PUP-7289
Re: PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
I missed the part around alias. Here is an exeperpt from the documentation on the alias interpolation function.
When you use the alias function, its interpolation token must be the only text in that string. For example, the following would be an error:
aliased: "%{alias('original')} - 'three'"
This means that the alias in the provide example is incorrect. Classic Hiera had a bug that would let it slip through, basically transforming it into a
%{hiera('xxx')}
but that bug has since been fixed.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7325) Interpolations in a key name in hiera work no longer
Title: Message Title Francois Lafont created an issue Puppet / PUP-7325 Interpolations in a key name in hiera work no longer Issue Type: Bug Affects Versions: PUP 4.9.3 Assignee: Unassigned Created: 2017/03/08 9:13 PM Priority: Normal Reporter: Francois Lafont Hi, With puppet-agent 1.8.3 (so hiera 3.2.2), I had this in hiera: A yaml file --- mymodule::param1:
Jira (PUP-7289) PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Title: Message Title
Eric Thompson commented on PUP-7289
Re: PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Alex P i don't understand what you are accomplishing with the call to alias() in the context above. maybe this is a simplified datafile?
alias simply makes a new hiera key equal to another key's data. but in the context above you aren't setting it to a new key name. so
sudo::configs:
"%{dev_username}":
'content' : "%{dev_username} ALL=(ALL:ALL) APACHECTL, NGINX, !SU, !SHELLS, REBOOT, APACHECONF, POSTGRESQL, COMPOSER
'ensure' : 'present'
should do the same thing, and indeed remove the errors related to alias() interpolation you were seeing above.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
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 Release Notes Summary: PostgreSQL CPU usage increaseAfter upgrading a split install to 2016.5.1 or 2016.5.2, PostgreSQL CPU usage increases by 50 percent. To workaround this issue, we've created the pdb_3323_workaround module.1. On the Puppet master, download the [module](https://forge.puppet.com/puppetlabs/pdb_3323_workaround).2. Classify the node hosting pe-postgresql with the `pdb_3323_workaround` class.3. On the node hosting pe-postgresql, run Puppet.After you install this module, it's safe to forget about. The index will be removed when you upgrade in the future. 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 Release Notes Summary: PostgreSQL CPU usage increaseAfter upgrading a split install to 2016.5.1 or 2016.5.2, PostgreSQL CPU usage increases by 50 percent. To workaround this issue, we've created the puppetlabs- pdb_3323_workaround module.1. On the Puppet master, download the [module](https://forge.puppet.com/puppetlabs/pdb_3323_workaround).2. Classify the node hosting pe-postgresql with the `pdb_3323_workaround` class.3. On the node hosting pe-postgresql, run Puppet.After you install this module, it's safe to forget about. The index will be removed when you upgrade in the future. 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 Release Notes Summary: PostgreSQL CPU usage increaseAfter upgrading a split install to 2016.5.1 or 2016.5.2, PostgreSQL CPU usage increases by 50 percent. To workaround this issue, we've created the puppetlabs-pdb_3323_workaround module.1. On the Puppet master, download the [module](https://forge.puppet.com/puppetlabs/pdb_3323_workaround).2. Classify the node hosting pe-postgresql with the `pdb_3323_workaround` class.3. On the Puppet master and the node hosting pe-postgresql, run Puppet.After you install this module, it's safe to ignore forget about . The class index will be removed when you upgrade in the future. 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 Isaac Eldridge updated an issue PuppetDB / PDB-3323 Checking if a report exists before inserting it is SLOW Change By: Isaac Eldridge Release Notes Summary: PostgreSQL CPU usage increase After upgrading a split install to 2016.5.1 or 2016.5.2, PostgreSQL related CPU usage increases by around 50 % percent . To workaround this issue, use we've created the puppetlabs- pdb_3323_workaround module to create and manage an index that provides a short-term fix: . 1. On the Puppet master, download the [module]( https://forge.puppet.com/puppetlabs/pdb_3323_workaround ).2. Classify the node hosting pe-postgresql with the `pdb_3323_workaround` class.3. On the Puppet master and the node hosting pe-postgresql, run Puppet.After you install this module, it's safe to ignore. The class will be removed when you upgrade in the future. 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. Suggested workaroundhttps:// github forge . puppet. com/puppetlabs/ puppetlabs- pdb_3323_workaroundh1. 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 (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 Release Notes Summary: After upgrading to 2016.5.1 or 2016.5.2, PostgreSQL related CPU usage increases by around 50%. To workaround this issue, add use the pdb_3323_workaround module to create and manage an index to the reports table that provides a short-term fix : su - pe-postgres -s https: / bin / bash -c "/opt/puppetlabs/server/bin/psql -d pe-puppetdb -c \"CREATE UNIQUE INDEX CONCURRENTLY _idx_reports_hash on reports(hash)\""This index can be removed prior to upgrading to versions newer than 2016 forge . 5 puppet . 2. The command to do so is:su - pe-postgres -s com / bin/bash -c "/opt/ puppetlabs/ server/bin/psql -d pe-puppetdb -c \"DROP INDEX CONCURRENTLY _idx_reports_hash\"" pdb_3323_workaround 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-3322) PuppetDB fails to update catalogs when sensitive parameters are added
Title: Message Title Karen Van der Veer assigned an issue to Ryan Senior PuppetDB / PDB-3322 PuppetDB fails to update catalogs when sensitive parameters are added Change By: Karen Van der Veer Assignee: Ryan Senior 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. Suggested workaroundhttps://github.com/puppetlabs/puppetlabs-pdb_3323_workaroundh1. 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 (PDB-3322) PuppetDB fails to update catalogs when sensitive parameters are added
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3322 PuppetDB fails to update catalogs when sensitive parameters are added Change By: Karen Van der Veer Team: Systems 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-6979) Puppet Module List fails in code page 65001 on ja-JP windows
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6979 Puppet Module List fails in code page 65001 on ja-JP windows Change By: Ethan Brown Sprint: Agent 2017-03-22 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 Ethan Brown commented on PUP-6979 Re: Puppet Module List fails in code page 65001 on ja-JP windows Ah yes, thanks Erick Banks... sorry I missed that in the environment info you had already entered. I wasn't initially sure if you were using vmpooler or a custom box. 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 win-2012r2-ja-x86_64 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 Ethan Brown commented on PUP-6979 Re: Puppet Module List fails in code page 65001 on ja-JP windows Erick Banks what you attached is a Ruby segfault. I didn't look too closely, but it's probably the same thing as PUP-5717 . What was the host OS? 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-5068) Windows - Allow logging to a different event log
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5068 Windows - Allow logging to a different event log Change By: Ethan Brown Sprint: Agent 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-5068) Windows - Allow logging to a different event log
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5068 Windows - Allow logging to a different event log Change By: Ethan Brown Fix Version/s: PUP 4.y 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 (FACT-1583) Facter fails to build on fedora 24 (libfacter tests fail)
Title: Message Title Josh Cooper assigned an issue to Michael Smith Facter / FACT-1583 Facter fails to build on fedora 24 (libfacter tests fail) Change By: Josh Cooper Assignee: Josh Cooper Michael Smith 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 commented on FACT-1583 Re: Facter fails to build on fedora 24 (libfacter tests fail) Michael Smith is working on permanent fix to use a mock server, thereby avoiding external dependencies. 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-3351) PuppetDB should allow collection only from originating nodes environments as a feature flag
Title: Message Title
Zachary Smith updated an issue
PuppetDB / PDB-3351
PuppetDB should allow collection only from originating nodes environments as a feature flag
Change By:
Zachary Smith
Currently as there is no ACLs in puppetdb , when a test node in say development environment exports a resource e.g. an `Ssh_authorized_key`, nodes in say the production environment collect that. This violates the environmental boundries that normally exist for separation of changes defined by the git branch/puppet environment separation. I would expect the default behaviour to limit collection of resource based on environments, however since that is not currently the case, we could enable that as a feature flag. It seem this environment information is in fact collected and available when collecting resources. Here is an example query: {code}curl -G -H "Accept: application/json" 'http://localhost:8080/pdb/query/v4/resources' --data-urlencode 'query=["and",["=","exported", true],["=","environment","production"]]'{code}{code}{"certname": "pe-201621-master.puppetdebug.vlan","environment": "production","exported": true,"file": "/opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/profile/amq/broker.pp","line": 172, ...{code}# Proposed SolutionWhile I believe ACLs are likely a good long term fix, I believe we could simply allow users to append this environment clause in during compilation. It appears we currently construct a query in the resource terminus here https://github.com/puppetlabs/puppetdb/blob/master/puppet/lib/puppet/indirector/resource/puppetdb.rb#L18-L22I believe if we simply just add the nodes environment (e.g. `node.environment` to the request hash ) likely as a key called `: environment ` https://github.com/puppetlabs/puppetdb/blob/master/puppet/lib/puppet/indirector/resource/puppetdb.rb#L13 we could then use that in the construction of the query.The terminus currently includes the `Puppet::Util::Puppetdb` class and that has the `Puppet::Util::Puppetdb.config` method that can be used to lookup configuration params from puppetdb.conf. This simply means we could enable this feature as a flag in that configuration default it to off.
Add Comment
Jira (PDB-3351) PuppetDB should allow collection only from originating nodes environments as a feature flag
Title: Message Title
Zachary Smith updated an issue
PuppetDB / PDB-3351
PuppetDB should allow collection only from originating nodes environments as a feature flag
Change By:
Zachary Smith
Currently as there is no ACLs in puppetdb , when a test node in say development environment exports a resource e.g. an `Ssh_authorized_key`, nodes in say the production environment collect that. This violates the environmental boundries that normally exist for separation of changes defined by the git branch/puppet environment separation. I would expect the default behaviour to limit collection of resource based on environments, however since that is not currently the case, we could enable that as a feature flag. It seem this environment information is in fact collected and available when collecting resources. Here is an example query: {code}curl -G -H "Accept: application/json" 'http://localhost:8080/pdb/query/v4/resources' --data-urlencode 'query=["and",["=","exported", true],["=","environment","production"]]'{code}{code}{"certname": "pe-201621-master.puppetdebug.vlan","environment": "production","exported": true,"file": "/opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/profile/amq/broker.pp","line": 172, ...{code}# # Proposed SolutionWhile I believe ACLs are likely a good long term fix, I believe we could simply allow users to append this environment clause in during compilation. It appears we currently construct a query in the resource terminus here https://github.com/puppetlabs/puppetdb/blob/master/puppet/lib/puppet/indirector/resource/puppetdb.rb#L18-L22I believe if we simply just add the nodes environment (e.g. `node.environment` to the request hash ) likely as a key called environmenthttps://github.com/puppetlabs/puppetdb/blob/master/puppet/lib/puppet/indirector/resource/puppetdb.rb#L13 we could then use that in the construction of the query.The terminus currently includes the `Puppet::Util::Puppetdb` class and that has the `Puppet::Util::Puppetdb.config` method that can be used to lookup configuration params from puppetdb.conf. This simply means we could enable this feature as a flag in that configuration default it to off.
Add Comment
Jira (PDB-3351) PuppetDB should allow collection only from originating nodes environments as a feature flag
Title: Message Title Zachary Smith updated an issue PuppetDB / PDB-3351 PuppetDB should allow collection only from originating nodes environments as a feature flag Change By: Zachary Smith Summary: PuppetDB should allow collection only from originating nodes environments as a feature flag 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-3351) PuppetDB should allow collection from originating nodes environments as a feature flag
Title: Message Title Zachary Smith created an issue PuppetDB / PDB-3351 PuppetDB should allow collection from originating nodes environments as a feature flag Issue Type: New Feature Affects Versions: PDB 4.3.2 Assignee: Unassigned Components: PuppetDB Created: 2017/03/08 2:55 PM Priority: Normal Reporter: Zachary Smith Currently as there is no ACLs in puppetdb , when a test node in say development environment exports a resource e.g. an `Ssh_authorized_key`, nodes in say the production environment collect that. This violates the environmental boundries that normally exist for separation of changes defined by the git branch/puppet environment separation. I would expect the default behaviour to limit collection of resource based on environments, however since that is not currently the case, we could enable that as a feature flag. It seem this environment information is in fact collected and available when collecting resources. Here is an example query:
Jira (PUP-7322) Cannot obtain a source that uses http with basic web auth
Title: Message Title Shaun Martin commented on PUP-7322 Re: Cannot obtain a source that uses http with basic web auth Moses Mendoza you tagged the wrong person in your response, confused the hell out of me. 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-7324) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Nick Lewis created an issue Puppet / PUP-7324 Filtering resources by tag interferes with corrective vs. intentional change determination Issue Type: Bug Assignee: Unassigned Created: 2017/03/08 2:41 PM Priority: Normal Reporter: Nick Lewis Reproduction steps: • Add a new resource to site.pp • Run puppet agent -t on the node • Observe that the change is properly marked as intentional • Modify the resource on disk • Run puppet agent -t on the node • Observe that the change is properly marked as corrective • Modify the resource on disk • Run puppet agent -t --tags faketag on the node (this can be done before or after the previous step) • Observe that no change is made • Run puppet agent -t on the node • Observe that the change is wrongly marked as intentional The agent uses a transaction persistence file to store the previous desired state (or actual state? unclear) which it can compare to the current state on the next run. That file seems to only include resources that are actually managed on a given run, so any resource that is skipped due to tags is omitted. That causes the agent to think that every change is intentional the next time around. I expect this is also broken for resources which are skipped due to failed dependencies, though I haven't tested that. Add Comment
Jira (PUP-7044) Add Japanese Windows to Puppet spec testing matrices
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7044 Add Japanese Windows to Puppet spec testing matrices Change By: Josh Cooper Fix Version/s: PUP 4.10.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-7044) Add Japanese Windows to Puppet spec testing matrices
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7044 Add Japanese Windows to Puppet spec testing matrices Change By: Josh Cooper 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-7044) Add Japanese Windows to Puppet spec testing matrices
Title: Message Title Ethan Brown commented on PUP-7044 Re: Add Japanese Windows to Puppet spec testing matrices Confirmed Puppet is running against Japanese Windows at https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent%20components/view/puppet/job/platform_puppet_unit-ruby-win_master/272/ 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-3291) KahaDB: Some journal files are missing - lost of connection to puppet master
Title: Message Title David Chou [FE] commented on PDB-3291 Re: KahaDB: Some journal files are missing - lost of connection to puppet master thank you! 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-7044) Add Japanese Windows to Puppet spec testing matrices
Title: Message Title Ethan Brown updated an issue Puppet / PUP-7044 Add Japanese Windows to Puppet spec testing matrices Change By: Ethan Brown Sprint: Agent Ready for Engineering 2017-03-22 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-4039) package resource doesn't find new packages in yum repo
Title: Message Title
Matthew Cover commented on PUP-4039
Re: package resource doesn't find new packages in yum repo
I also tested this in vagrant, with the same set up as above.
This time using puppet.
#!/bin/bash
run() {
echo "==> Running: $@"
"$@" 2>&1 | awk '{ print "\t", $0; fflush(); }'
}
metadata_age() {
echo "`date '+%s'`-`stat -c '%Y' /var/cache/yum/x86_64/7/test/cachecookie`" | bc -l
}
Jira (PUP-4039) package resource doesn't find new packages in yum repo
Title: Message Title Matthew Cover commented on PUP-4039 Re: package resource doesn't find new packages in yum repo Submitted a PR https://github.com/puppetlabs/puppet/pull/5699. 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-7044) Add Japanese Windows to Puppet spec testing matrices
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-7044
Add Japanese Windows to Puppet spec testing matrices
Change By:
Ethan Brown
There are currently no static spec boxes that Puppet can run against in CI.next with Japanese Windows.Once Japanese spec boxes are available, I would recommend that they be added to multiple pipelines (note that these are current job locations and subject to change once CI.next is fully productionized):* puppet (master) component pipeline step 2.b - component specs on Windows - https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppet_unit-ruby-win_master/* puppet (stable) component pipeline step 2.b - component specs on Windows - https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppet_unit-ruby-win_stable/ Note that separate tickets should be filed for {{facter}}, {{hiera}}, and {{pxp-agent}} testing pipelines.
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-1584) Add Japanese Windows to Facter spec testing matrices
Title: Message Title Ethan Brown commented on FACT-1584 Re: Add Japanese Windows to Facter spec testing matrices Moved to a later epic since this isn't considered a "Phase 1 blocker" issue. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7044) Add Japanese Windows to Puppet spec testing matrices
Title: Message Title Michael Smith commented on PUP-7044 Re: Add Japanese Windows to Puppet spec testing matrices It seems sufficient. I don't think the Facter unit tests would exercise much of the localization anyway. 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-7044) Add Japanese Windows to Puppet spec testing matrices
Title: Message Title Ethan Brown commented on PUP-7044 Re: Add Japanese Windows to Puppet spec testing matrices For now, I think we'll just have to rely on the fact that Facter is exercised directly by its own acceptance suite and indirectly by the acceptance tests from Puppet... You know the Facter spec suite better than I Michael Smith - does this seem sufficient for now? 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-7322) Cannot obtain a source that uses http with basic web auth
Title: Message Title
Shaun Martin commented on PUP-7322
Re: Cannot obtain a source that uses http with basic web auth
Sure here is a simple example tested and fails as well.
class phr_uploads (
$config_env = 'dev',
$web_xml_source = "http://serv-foreman:PW@$serverip:81/$config_env/$hostname/uploads",
$customer = 'ead',
)
{
file { "/root/web.xml":
ensure => file,
replace => true,
source => "$web_xml_source/$customer.xml",
Jira (PUP-7044) Add Japanese Windows to Puppet spec testing matrices
Title: Message Title Michael Smith commented on PUP-7044 Re: Add Japanese Windows to Puppet spec testing matrices Oh right, all the test fixtures need to be copied, and we currently compile in absolute paths for finding those fixtures. Relative paths are trickier, but could be 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 (PUP-7044) Add Japanese Windows to Puppet spec testing matrices
Title: Message Title Ethan Brown commented on PUP-7044 Re: Add Japanese Windows to Puppet spec testing matrices Michael Smith "portable" was Kylos term, and he seemed to imply that it wasn't the norm for C++ projects to be able to relocate their binaries and still run tests. Part of the discussion was that the tests were very tightly coupled to the paths on disk where the binary was built, and that moving the tree around could cause problems. I always thought that you should be able to bundle the compiled test runner, and ship it around with the compiled binaries to any platform you wished to test on... as long as a little care was made to embed test fixtures in the test library, etc, etc. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3291) KahaDB: Some journal files are missing - lost of connection to puppet master
Title: Message Title Wyatt Alt commented on PDB-3291 Re: KahaDB: Some journal files are missing - lost of connection to puppet master David Chou [FE] yep, have a look here: https://docs.puppet.com/pe/latest/config_java_args.html#puppetdb 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 In one way that is nice (namespace) - kind of like '' in java, OTOH, the '' in java can create problems (and the reason why IDEs expand the '*' to the classes you actually used and then saves that. Not sure what I like best. With reference to typeset you need to know that the set exist as opposed to its individual types. Makes refactoring harder (create a set out of types). Am I missing something else we should consider? 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-7044) Add Japanese Windows to Puppet spec testing matrices
Title: Message Title Michael Smith commented on PUP-7044 Re: Add Japanese Windows to Puppet spec testing matrices I don't think it was ever ticketed. I'm not sure what you mean by "portable", other than zip everything from the build up and copy it around. 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 Affects Version/s: PDB 4.3.1 Affects Version/s: PDB 4.3.0 Affects Version/s: PDB 4.2.5 Affects Version/s: PDB 4.2.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 (FACT-1584) Add Japanese Windows to Facter spec testing matrices
Title: Message Title Ethan Brown moved an issue Facter / FACT-1584 Add Japanese Windows to Facter spec testing matrices Change By: Ethan Brown Key: PUP FACT - 7323 1584 Project: Puppet 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 (PUP-7323) Add Japanese Windows to Facter spec testing matrices
Title: Message Title Ethan Brown created an issue Puppet / PUP-7323 Add Japanese Windows to Facter spec testing matrices Issue Type: Task Assignee: Unassigned Created: 2017/03/08 1:33 PM Labels: i18n utf-8 Priority: Normal Reporter: Ethan Brown There are currently no static spec boxes that Facter can run against in CI.next with Japanese Windows. The following pipeline should be updated to include testing against Japanese Windows. Unfortunately due to the design of the pipelines, packaging and testing are a single step. So to do this in the current pipeline structure would require adding another 45+ minute job to build Facter on Japanese Windows, which kicks off the tests: Project facter (master) Component Pipeline Step 3 – Integration Packaging - https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent%20components/view/facter/job/platform_facter_pkg-van-ship_master/ This is pretty undesirable and suggests that the pipeline should be refactored to first build, then test, in independent steps. A ticket should be filed to block this ticket on such an effort.
Jira (PUP-1334) Empty clientbucket files produce errors
Title: Message Title Moses Mendoza assigned an issue to Moses Mendoza Puppet / PUP-1334 Empty clientbucket files produce errors Change By: Moses Mendoza Assignee: Moses Mendoza 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-7322) Cannot obtain a source that uses http with basic web auth
Title: Message Title Moses Mendoza commented on PUP-7322 Re: Cannot obtain a source that uses http with basic web auth hi Shaun Martin. Thanks for filing. Would you mind adding a simple manifest reproducing the bug for you? 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 Thomas Hallgren commented on PUP-7289 Re: PUP 4.9.3 interpolation in hiera.yaml datadir stopped working Alex P, the knockout_prefix is a deep merge behavior. It cannot be applied to the unique merge or the Hiera 3 array merge. It wasn't possible before and it's not possible now. And no, unique merges arrays uniquely. It does not merge hashes. Unless you are now using PUP-4 .9.4 (or the latest on stable) you still suffer from PUP-7286 , and I'll have to ask you to wait for that bug to be fixed before pointing out more problems with hiera_include. It is currently affected (but shouldn't be) by deep behavior. There are some subtle differences in how the hiera family of functions work and how the new lookup function work with respect to merge options. I added a ticket DOC-3122 requesting this to be more explicit in the documentation. 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-7044) Add Japanese Windows to Puppet spec testing matrices
Title: Message Title Ethan Brown commented on PUP-7044 Re: Add Japanese Windows to Puppet spec testing matrices A long time ago, I tried to make the case that we should not be mixing compilation with testing for native projects (don't recall if it was specifically for pxp-agent or facter). There was some pushback because that would require additional effort to make the tests "portable" - though I don't think it was that much work, and I thought it was ticketed. I can't seem to find the ticket, but supporting different languages correctly is a pretty compelling reason to do this, since rebuilding on Windows is currently so expensive, and the binaries won't change. 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-6339) Hiera Data in Module give bad results when environment_timeout is unlimited
Title: Message Title Thomas Hallgren commented on PUP-6339 Re: Hiera Data in Module give bad results when environment_timeout is unlimited Adam Winberg, can you run with log-level debug? That might be very verbose (and a bit slower) but it might also reveal more about when this happens. 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 Yes, and no. All types in a typeset can be auto-loaded without knowledge of if they live in a typeset or not. The typeset is hence, just a packaging detail for types that are available to the auto-loader. With that in mind, perhaps typesets should be taken out of the equation altogether. I.e. you import a namespace, not a typeset. 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-3346) Packages pushed (PDB 4.3.2)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3346 Packages pushed (PDB 4.3.2) Issue Type: Sub-task Assignee: Melissa Stone Created: 2017/03/08 12:59 PM Priority: Normal Reporter: Russell Mull (Initial planned release date: 2017-03-08) Push packages run `rake pl:jenkins:uber_ship` You will need the keys to the castle (aka the passphrase) for this to work. Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms. Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay. If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file. If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Haus for more details. This file also needs to be manually signed.
Jira (PDB-3335) PuppetDB 4.3.2 2017-03-08 Release
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3335 PuppetDB 4.3.2 2017-03-08 Release Change By: Russell Mull Sprint: SE 2017-03-22 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-3335) PuppetDB 4.3.2 2017-03-08 Release
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3335 PuppetDB 4.3.2 2017-03-08 Release Change By: Russell Mull Story Points: 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 (PUP-7322) Cannot obtain a source that uses http with basic web auth
Title: Message Title Shaun Martin created an issue Puppet / PUP-7322 Cannot obtain a source that uses http with basic web auth Issue Type: Bug Affects Versions: PUP 4.8.2 Assignee: Unassigned Components: Puppet Server Created: 2017/03/08 1:02 PM Priority: Major Reporter: Shaun Martin When I try and access a source from a simple apache server using basic authentication with .htaccess and .htpassword puppet does not retrieve the source. Below is output of me running the puppet agent -t with the error. I then show I use that exact same URL to try and retrieve the file and it works while puppet failed. [root@smartin-test opt]# puppet agent -t
Jira (PDB-3342) Tag the release and create packages (PDB 4.3.2)
Title: Message Title
Russell Mull created an issue
PuppetDB / PDB-3342
Tag the release and create packages (PDB 4.3.2)
Issue Type:
Sub-task
Assignee:
Melissa Stone
Created:
2017/03/08 12:59 PM
Priority:
Normal
Reporter:
Russell Mull
(Initial planned release date: 2017-03-08)
Tag and create packages
Developer provides the SHA - Russell Mull - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
checkout the sha
Make sure you are about to tag the correct thing
Create the tag e.g.) git tag -s -u {GPG key}
-m "1.7.3" 1.7.3
You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
DO NOT push the tag to the repo, keep it local only
`git describe` will show you the tag. Make sure you're building what you think you're building.
Jira (PDB-3349) Update dujour to notify users to use 4.3.2 (PDB 4.3.2)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3349 Update dujour to notify users to use 4.3.2 (PDB 4.3.2) Issue Type: Sub-task Assignee: Russell Mull Created: 2017/03/08 12:59 PM Priority: Normal Reporter: Russell Mull (Initial planned release date: 2017-03-08) Update dujour to notify users to use 4.3.2. Dependencies: Packages pushed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3340) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.3.2)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3340 Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.3.2) Issue Type: Sub-task Assignee: Russell Mull Created: 2017/03/08 12:59 PM Priority: Normal Reporter: Russell Mull (Initial planned release date: 2017-03-08) This happens on Jira - we need to clean up the current release and prepare for the next release. Mark the version that's going out as "Released" in the Project Admin -> Versions panel. Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future) Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket): 'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone 'project = XX AND
Jira (PDB-3337) Reconcile git commits and JIRA tickets (PDB 4.3.2)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3337 Reconcile git commits and JIRA tickets (PDB 4.3.2) Issue Type: Sub-task Assignee: Russell Mull Created: 2017/03/08 12:59 PM Priority: Normal Reporter: Russell Mull (Initial planned release date: 2017-03-08) Use the ticketmatch script to ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. cd ~/work git clone https://github.com/puppetlabs/ticketmatch cd ~/work/puppet # or whatever the repo is you're releasing from ruby ../ticketmatch/ticketmatch.rb Enter Git From Rev: 4.1.0 Enter Git To Rev: |master| stable Enter JIRA project: |PUP| Enter JIRA fix version: PUP 4.2.0 The output may contain the following headers: COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF ...) Lists git commits that don't have a corresponding ticket, at least not for the specified fix version. If the commit has a ticket, but the ticket is not targeted correctly, then the ticket's fixVersion should be updated. This can frequently happen if a ticket is initially targeted for a future release (master), but is pulled into
Jira (PDB-3347) Docs pushed (PDB 4.3.2)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3347 Docs pushed (PDB 4.3.2) Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2017/03/08 12:59 PM Priority: Normal Reporter: Russell Mull (Initial planned release date: 2017-03-08) Push the documentation updates to docs.puppetlabs.com. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3336) Is the code ready for release? (PDB 4.3.2)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3336 Is the code ready for release? (PDB 4.3.2) Issue Type: Sub-task Assignee: Russell Mull Created: 2017/03/08 12:59 PM Priority: Normal Reporter: Russell Mull (Initial planned release date: 2017-03-08) If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable & master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%224.3.2%22
Jira (PDB-3338) Update version number in source (PDB 4.3.2)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3338 Update version number in source (PDB 4.3.2) Issue Type: Sub-task Assignee: Russell Mull Created: 2017/03/08 12:59 PM Priority: Normal Reporter: Russell Mull (Initial planned release date: 2017-03-08) Bump VERSION in lib/PDB/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3". If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Reconcile git commits and JIRA tickets
Jira (PDB-3345) Push tag (PDB 4.3.2)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3345 Push tag (PDB 4.3.2) Issue Type: Sub-task Assignee: Melissa Stone Created: 2017/03/08 12:59 PM Priority: Normal Reporter: Russell Mull (Initial planned release date: 2017-03-08) The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb. Dependencies: Go / No Go meeting (except where it's required to push the tag to build packages - MSIs) Add Comment
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
Further
autopsy
troubleshooting showed the following:
#1. Hiera v3 +hiera_include
Settings: /etc/puppetlabs/puppet/puppet.conf is using hiera v3 configured with deeper merge behavior and merge_hash_arrays in it. /etc/puppetlabs/code/environments/corporate/manifests/site.pp is using hiera_include('classes')
srv01 fails with Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, can't convert true into String; discussed above;
dev_vm01 fails with:
Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, Lookup of key 'sudo::configs' failed: 'alias' interpolation is only permitted if the _expression_ is equal to the entire string at /etc/puppetlabs/code/modules/sudo/manifests/configs.pp:20:14
#2. Hiera v3 +unique lookup
Settings: Hiera v3 /etc/puppetlabs/code/environments/corporate/manifests/site.pp:
include lookup('classes', { 'merge' => 'unique' })
same errors.
#3. Hiera v3 +deep merge lookup
Settings: Hiera v3 /etc/puppetlabs/code/environments/corporate/manifests/site.pp:
lookup({ 'name' => 'classes',
'merge' => {
Jira (PDB-3350) Close all resolved tickets in Jira (PDB 4.3.2)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3350 Close all resolved tickets in Jira (PDB 4.3.2) Issue Type: Sub-task Assignee: Russell Mull Created: 2017/03/08 1:00 PM Priority: Normal Reporter: Russell Mull (Initial planned release date: 2017-03-08) Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%224.3.2%22%20AND%20status%20%3D%20Resolved There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: Select Bulk Change - All # issues Step 1 - choose all relevant issues (likely all of them) Step 2 - Select "Transition Issues" Step 3 - Select "Closed" Step 4 - Select "Fixed" in Change Resolution. View what is about to change and confirm it. Then commit the change. Dependencies:
Jira (PDB-3344) Go/no-go meeting (before noon PST) (PDB 4.3.2)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3344 Go/no-go meeting (before noon PST) (PDB 4.3.2) Issue Type: Sub-task Assignee: Russell Mull Created: 2017/03/08 12:59 PM Priority: Normal Reporter: Russell Mull (Initial planned release date: 2017-03-08) This should happen Monday-Thursday, before noon PST. We should not be shipping anything after noon PST or on a Friday both for our users, and because shipping takes time. Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: Smoke testing Participants: Russell Mull Nicholas Fagerlund Eric Sorenson Russell Mull Melissa Stone
Jira (PDB-3339) Merge master into stable (PDB 4.3.2)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3339 Merge master into stable (PDB 4.3.2) Issue Type: Sub-task Assignee: Russell Mull Created: 2017/03/08 12:59 PM Priority: Normal Reporter: Russell Mull (Initial planned release date: 2017-03-08) For some releases, the code base will need to be merged down to stable. NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: git fetch upstream git rebase upstream/master
Jira (PDB-3343) Smoke test packages (PDB 4.3.2)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3343 Smoke test packages (PDB 4.3.2) Issue Type: Sub-task Assignee: Russell Mull Created: 2017/03/08 12:59 PM Priority: Normal Reporter: Russell Mull (Initial planned release date: 2017-03-08) Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be limited to other package formats than deb and rpm. For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems. Lighter testing of Z releases is acceptable. Add a link to the Packages repository that you receive from the "Tag and create packages" subtask Ping folks on your team for help with different platforms. When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output.
Jira (PDB-3341) Prepare long form release notes and short form release story (PDB 4.3.2)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3341 Prepare long form release notes and short form release story (PDB 4.3.2) Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2017/03/08 12:59 PM Priority: Normal Reporter: Russell Mull (Initial planned release date: 2017-03-08) Collaborating with product for release story Dependencies: Reconcile git commits and JIRA tickets Add Comment This message was sent by
Jira (PDB-3348) Send out announcements (PDB 4.3.2)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3348 Send out announcements (PDB 4.3.2) Issue Type: Sub-task Assignee: Eric Sorenson Created: 2017/03/08 12:59 PM Priority: Normal Reporter: Russell Mull (Initial planned release date: 2017-03-08) Melissa Stone: update the release google spreadsheet. Update the MSI build targets in the Puppet repo in ext/build_defaults.yaml. This needs to be done for any projects that are to get into the MSI (facter and hiera as of 8/2014) Send the drafted release notes email. If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users & puppet-dev). If this release has security implications, also send the release announcement to puppet-security-announce Make a PSA on IRC letting those kiddos know about the new release. Something along the lines of "PSA: facter 1.7.3 now available"
Jira (PDB-3335) PuppetDB 4.3.2 2017-03-08 Release
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3335 PuppetDB 4.3.2 2017-03-08 Release Issue Type: Task Assignee: Russell Mull Created: 2017/03/08 12:58 PM Priority: Normal Reporter: Russell Mull PuppetDB 4.3.2 2017-03-08 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.
Jira (PDB-3291) KahaDB: Some journal files are missing - lost of connection to puppet master
Title: Message Title David Chou [FE] commented on PDB-3291 Re: KahaDB: Some journal files are missing - lost of connection to puppet master I found that the JAVA_ARGS in /etc/default/pe-puppetdb somehow flipped back. Is there something else (maybe puppet) that manages this file? webadmin@devpuppet4[~]$ cat /etc/default/pe-puppetdb |grep -i Xmx JAVA_ARGS="-Xmx256m -Xms256m" i found that JAVA_ARGS flipped back to 256m and also pe-puppetdb.service was restarted because the process is using 256m 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-3053) Create Index on certname latest_report_id
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-3053
Create Index on certname latest_report_id
Change By:
Nick Walker
h1. The ProblemEvent Inspector is incredibly slow with large amounts of nodes. h1. The Solution{code}CREATE UNIQUE INDEX certnames_latest_report_id ON idx_certnames_latest_report_id on certnames(latest_report_id) ; {code}h1. Query Plans Before Index ( 5+ mins ) : https://explain.depesz.com/s/1EvAfter index ( ~ 8 seconds ):https://explain.depesz.com/s/btLSh1. Pull Requesthttps://github.com/puppetlabs/puppetdb/pull/2171
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-7044) Add Japanese Windows to Puppet spec testing matrices
Title: Message Title Josh Cooper commented on PUP-7044 Re: Add Japanese Windows to Puppet spec testing matrices We've started testing puppet specs on Windows Japanese for 4.10.x and master branches. Testing facter and pxp-agent would be harder as those happen during the build process (since you need the native libraries/exe). We're not testing hiera on Windows (at all) for historical reasons, but to adding at least one English and Japanese Windows to the spec matrix. 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-556) Acceptance: Switch to new SPARC hardware
Title: Message Title Maggie Dreyer updated an issue Hiera / HI-556 Acceptance: Switch to new SPARC hardware Change By: Maggie Dreyer Fix Version/s: HI 3.3.1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1576) Acceptance: Switch to new SPARC hardware
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1576 Acceptance: Switch to new SPARC hardware Change By: Maggie Dreyer 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 (PUP-7250) Acceptance: Switch to new SPARC hardware
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7250 Acceptance: Switch to new SPARC hardware Change By: Maggie Dreyer Fix Version/s: PUP 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-7280) Optimise pacman execution time by running fewer commands
Title: Message Title Moses Mendoza commented on PUP-7280 Re: Optimise pacman execution time by running fewer commands Hi Victor Engmark - thanks for filing this! I'm afraid given the prioritization we're up against, it's unlikely we're going to be able to get to this request soon. I'm going to close it for now as won't-fix, but we can re-open it of course if we're able to pick it up. Please feel free to propose the changes you outline here as a pull request against https://github.com/puppetlabs/puppet - as you noted this should be a fairly lightweight change to the pacman provider. 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-7063) Handle incompatible encodings in Puppet::Util::Log when rendering to console
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7063 Handle incompatible encodings in Puppet::Util::Log when rendering to console Change By: Geoff Nichols Sprint: Agent 2017- 03 04 - 22 05 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-6060) Change node_cache_terminus default to nil
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6060 Change node_cache_terminus default to nil Change By: Geoff Nichols Sprint: Agent 2017- 03 04 - 22 05 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-7042) Mark non-debug messages for externalization
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7042 Mark non-debug messages for externalization Change By: Geoff Nichols Sprint: AP 2017-01-11, AP 2017-01-25, AP 2017-02-08, AP 2017-03-08, Agent 2017- 03 04 - 22 05 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-7144) Review error string marking and externalization
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7144 Review error string marking and externalization Change By: Geoff Nichols Sprint: AP 2017-02-22, AP 2017-03-08, Agent 2017- 03 04 - 22 05 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-7321) Update API schema docs
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7321 Update API schema docs Change By: Josh Cooper Sprint: Agent 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-7021) Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7021 Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module Change By: Geoff Nichols Sprint: AP 2017-01-25, AP 2017-02-08, AP 2017-02-22, AP 2017-03-08 , Agent 2017-03-22 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 Geoff Nichols updated an issue Facter / FACT-1583 Facter fails to build on fedora 24 (libfacter tests fail) Change By: Geoff Nichols Sprint: AP 2017-03-08 , Agent 2017-03-22 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-7246) Plan PSON to JSON work
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7246 Plan PSON to JSON work Change By: Geoff Nichols Sprint: AP 2017-03-08 , Agent 2017-03-22 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-1574) Add acceptance tests for supported agent fact directories
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1574 Add acceptance tests for supported agent fact directories Change By: Geoff Nichols Sprint: AP 2017-03-08 , Agent 2017-03-22 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-7251) gzip decompression mangles utf-8 content in catalog
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7251 gzip decompression mangles utf-8 content in catalog Change By: Geoff Nichols Sprint: AP 2017-03-08 , Agent 2017-03-22 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-7042) Mark non-debug messages for externalization
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7042 Mark non-debug messages for externalization Change By: Geoff Nichols Sprint: AP 2017-01-11, AP 2017-01-25, AP 2017-02-08, AP 2017-03-08 , Agent 2017-03-22 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-7310) Fix interpolation in externalized strings
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7310 Fix interpolation in externalized strings Change By: Geoff Nichols Sprint: AP 2017-03-08 , Agent 2017-03-22 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-7144) Review error string marking and externalization
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7144 Review error string marking and externalization Change By: Geoff Nichols Sprint: AP 2017-02-22, AP 2017-03-08 , Agent 2017-03-22 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-1582) Need to add tests for TestRail C64580 facter as non-root user should honor fact paths $HOME/.facter/facts.d and $HOME/.puppetlabs/opt/facter/facts.d
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1582 Need to add tests for TestRail C64580 facter as non-root user should honor fact paths $HOME/.facter/facts.d and $HOME/.puppetlabs/opt/facter/facts.d Change By: Geoff Nichols Sprint: AP 2017-03-08 , Agent 2017-03-22 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Geoff Nichols Sprint: AP 2017-01-11, AP 2017-03-08 , Agent 2017-03-22 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 commented on FACT-1583
Re: Facter fails to build on fedora 24 (libfacter tests fail)
The error showed up in the adhoc pipeline:
18:02:43 1: /var/tmp/tmp.TqG51Yxf7X/facter/lib/tests/ruby/ruby_dirfacts.cc:29: FAILED:
18:02:43 1: REQUIRE( ruby_value_to_string(facts.get("sometest")) == "\"Yay\"" )
18:02:43 1: with expansion:
18:02:43 1: ""getaddrinfo: Name or service not known""
18:02:43 1: ==
18:02:43 1: ""Yay""
So for some reason, fedora24 couldn't resolve www.puppet.com
Add Comment
Jira (PUP-7248) Convert initial CA cert (and CRL) fetching operation to state machine
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-7248 Convert initial CA cert (and CRL) fetching operation to state machine Change By: Karen Van der Veer Sprint: SE 2017-03-08 , SE 2017-03-22 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 Karen Van der Veer updated an issue PuppetDB / PDB-3323 Checking if a report exists before inserting it is SLOW Change By: Karen Van der Veer Sprint: SE 2017-03-08 , SE 2017-03-22 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-3107) new-command-schema validation prevents PDB/NewRelic integration
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3107 new-command-schema validation prevents PDB/NewRelic integration Change By: Karen Van der Veer Sprint: SE 2017-03-08 , SE 2017-03-22 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-3254) Test performance after undeduplicating fact_values
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3254 Test performance after undeduplicating fact_values Change By: Karen Van der Veer Sprint: SE 2017-03-08 , SE 2017-03-22 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.
