Jira (PUP-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8409 Puppet config print lists invalid value for environment_timeout when set to unlimited Change By: Josh Cooper Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8378) Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8378 Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages Change By: Josh Cooper Acceptance Criteria: Puppet acceptance test pass against the redhat fips image in vmpooler. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8378) Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8378 Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8114) Service provider 'redhat' does not correctly detect enabled state of 'boot.*' services on SLES 11.
Title: Message Title Jennifer Solman commented on PUP-8114 Re: Service provider 'redhat' does not correctly detect enabled state of 'boot.*' services on SLES 11. This passed CI Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8114) Service provider 'redhat' does not correctly detect enabled state of 'boot.*' services on SLES 11.
Title: Message Title Jennifer Solman commented on PUP-8114 Re: Service provider 'redhat' does not correctly detect enabled state of 'boot.*' services on SLES 11. Jacob Helwig Jacob Helwig please add release notes if needed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3321) config set adds a preceding newline to value if previous value was empty
Title: Message Title Melissa Stone assigned an issue to Jorie Tappa Puppet / PUP-3321 config set adds a preceding newline to value if previous value was empty Change By: Melissa Stone Assignee: Jorie Tappa Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3321) config set adds a preceding newline to value if previous value was empty
Title: Message Title Jennifer Solman commented on PUP-3321 Re: config set adds a preceding newline to value if previous value was empty Jorie Tappa Please add Docs and QA tab to indicate if this requires manual testing Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3829) (maint) Test default, not HEAD when PUPPETSERVER_VERSION unset
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3829 (maint) Test default, not HEAD when PUPPETSERVER_VERSION unset Issue Type: Bug Assignee: Unassigned Created: 2018/02/02 3:51 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (BOLT-323) Add tests for --run-as as a non-root user
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-323 Add tests for --run-as as a non-root user Issue Type: Sub-task Assignee: Unassigned Created: 2018/02/02 3:48 PM Priority: Normal Reporter: Nick Lewis Currently we have tests for connecting as non-root and running tasks, etc as root, but we don't have tests for connecting as either root or a non-root user and then running as a different non-root user, which are the versions that are more prone to error. These tests should wait until we have a docker setup working, so that we can more easily create multiple environments to test in. Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-123) Better fail function for plans
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-123 Better fail function for plans Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1916) puppet cert clean cannot remove signing requests
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-1916 puppet cert clean cannot remove signing requests Change By: Jacob Helwig Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-255) Refactor 'nodes' into 'transport's
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-255 Refactor 'nodes' into 'transport's Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-596) Bump beaker-puppet and use common ci rake tasks and utilities
Title: Message Title Melissa Stone created an issue Hiera / HI-596 Bump beaker-puppet and use common ci rake tasks and utilities Issue Type: Task Assignee: Unassigned Created: 2018/02/02 2:28 PM Priority: Normal Reporter: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-3828) test travis
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3828 test travis Issue Type: Bug Assignee: Unassigned Created: 2018/02/02 2:26 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8416) Remove old acceptance code that now lives in beaker-puppet
Title: Message Title Melissa Stone created an issue Puppet / PUP-8416 Remove old acceptance code that now lives in beaker-puppet Issue Type: Task Assignee: Unassigned Created: 2018/02/02 2:23 PM Priority: Normal Reporter: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-8416) Remove old acceptance code that now lives in beaker-puppet
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8416 Remove old acceptance code that now lives in beaker-puppet Change By: Melissa Stone Sub-team: Coremunity Team: Platform Core Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8416) Remove old acceptance code that now lives in beaker-puppet
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8416 Remove old acceptance code that now lives in beaker-puppet Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3827) Test deps in travis, among other things
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3827 Test deps in travis, among other things Issue Type: Bug Assignee: Unassigned Created: 2018/02/02 2:13 PM Priority: Normal Reporter: gepetto-bot Nothing to see here... Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3824) Duplicate unordered structured facts violates unique constraint
Title: Message Title Owen Rodabaugh updated an issue PuppetDB / PDB-3824 Duplicate unordered structured facts violates unique constraint Change By: Owen Rodabaugh CS Priority: Major Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-322) Document inventoryfile
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-322 Document inventoryfile Issue Type: Sub-task Assignee: Unassigned Created: 2018/02/02 1:00 PM Priority: Normal Reporter: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-3251) Man page for puppet is useless
Title: Message Title Josh Cooper commented on PUP-3251 Re: Man page for puppet is useless Current status as of 5.3.4: puppet --help works: [root@p4bogq51z35gxq4 ~]# puppet --help Usage: puppet [options] [options] Available subcommands: agent The puppet agent daemon apply Apply Puppet manifests locally ... puppet man does not because you either need to specify --help or the name of an application, e.g. puppet man catalog.
Jira (PDB-3824) Duplicate unordered structured facts violates unique constraint
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-3824 Duplicate unordered structured facts violates unique constraint Change By: Jarret Lavallee Environment: Puppet 5.3.3 with PuppetDB 5.1.3 and duplicate Duplicate structured facts in the same agent replace_facts payload with a different order. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3824) Duplicate unordered structured facts violates unique constraint
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-3824 Duplicate unordered structured facts violates unique constraint Change By: Jarret Lavallee Affects Version/s: PDB 4.2.3.7 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3824) Duplicate unordered structured facts violates unique constraint
Title: Message Title
Jarret Lavallee updated an issue
PuppetDB / PDB-3824
Duplicate unordered structured facts violates unique constraint
Change By:
Jarret Lavallee
Duplicate custom structured facts that in the same payload which are not ordered cause replace_facts to fail with the following error message. {code}2018-01-30 16:10:11,844 ERROR [p.p.command] [10,612] [replace facts] Retrying after attempt 0 for testing.example.com, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "fact_values_value_hash_key" Detail: Key (value_hash)=(\x88680eb39ee03249046efa1c51598d865afc7519) already exists.org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "fact_values_value_hash_key" Detail: Key (value_hash)=(\x88680eb39ee03249046efa1c51598d865afc7519) already exists.{code}The hash is not currently in the database. {code}pe-puppetdb=# select * from fact_values where value_hash = '\x88680eb39ee03249046efa1c51598d865afc7519'; id | value_hash | value_type_id | value_integer | value_float | value_string | value_boolean | value++---+---+-+--+---+---(0 rows){code}This occurs when there are two structured facts in the payload with the same contents, but not in the same order. Below is a basic facts payload to reproduce the issue. {code:json}{ "certname": "testing.example.com", "values": {"a_structured_fact": { "element2": {"somevalue": "2" }, "element1": {"somevalue": "1" }},"another_structured_fact": { "element1": {"somevalue": "1" }, "element2": {"somevalue": "2" }} }, "environment": "production", "producer_timestamp": "2018-01-29T15:34:59.792-08:00", "producer": "somemaster.example.com"}{code} To simulate this, one can run the following command after populating payload.json with the content above. {code}curl -X POST -H 'Content-Type:application/json' -H 'Accept:application/json' -d @payload.json "http://localhost:8080/pdb/cmd/v1?command=replace_facts=5=testing.example.com"{code} If I put both facts in the same order, we do not encounter the error. It sounds like the fix is to sort the structured facts when checking if they already exist. The end result of this issue is that we get continual retries and discards. The facts are never updated in PuppetDB for these nodes, unless the value_hash already exists in the database. _Workaround_Sort the hash prior to setting the fact. Hash[myhash.sort] worked in testing.
Add Comment
Jira (PDB-3824) Duplicate unordered structured facts violates unique constraint
Title: Message Title
Jarret Lavallee updated an issue
PuppetDB / PDB-3824
Duplicate unordered structured facts violates unique constraint
Change By:
Jarret Lavallee
Duplicate custom structured facts that are not ordered cause replace_facts to fail with the following error message. {code}2018-01-30 16:10:11,844 ERROR [p.p.command] [10,612] [replace facts] Retrying after attempt 0 for testing.example.com, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "fact_values_value_hash_key" Detail: Key (value_hash)=(\x88680eb39ee03249046efa1c51598d865afc7519) already exists.org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "fact_values_value_hash_key" Detail: Key (value_hash)=(\x88680eb39ee03249046efa1c51598d865afc7519) already exists.{code}The hash is not currently in the database. {code}pe-puppetdb=# select * from fact_values where value_hash = '\x88680eb39ee03249046efa1c51598d865afc7519'; id | value_hash | value_type_id | value_integer | value_float | value_string | value_boolean | value++---+---+-+--+---+---(0 rows){code}This occurs when there are two structured facts with the same contents, but not in the same order. Below is a basic facts payload to reproduce the issue. {code:json}{ "certname": "testing.example.com", "values": {"a_structured_fact": { "element2": {"somevalue": "2" }, "element1": {"somevalue": "1" }},"another_structured_fact": { "element1": {"somevalue": "1" }, "element2": {"somevalue": "2" }} }, "environment": "production", "producer_timestamp": "2018-01-29T15:34:59.792-08:00", "producer": "somemaster.example.com"}{code} To simulate this, one can run the following command after populating payload.json with the content above. {code}curl -X POST -H 'Content-Type:application/json' -H 'Accept:application/json' -d @payload.json "http://localhost:8080/pdb/cmd/v1?command=replace_facts=5=testing.example.com"{code} If I put both facts in the same order, we do not encounter the error. It sounds like the fix is to sort the structured facts when checking if they already exist. The end result of this issue is that we get continual retries and discards. The facts are never updated in PuppetDB for these nodes, unless the value_hash already exists in the database. _Workaround_Sort the hash prior to setting the fact. Hash[myhash.sort] worked in testing.
Add Comment
Jira (PUP-5494) Proper manual pages are nonexistent
Title: Message Title Craig Gomes updated an issue Puppet / PUP-5494 Proper manual pages are nonexistent Change By: Craig Gomes Team: Platform Core OS Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6507) Puppet help: Hide bad subcommands, and sort remainder by usefulness
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6507 Puppet help: Hide bad subcommands, and sort remainder by usefulness Change By: Craig Gomes Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4644) puppet tells you to read man pages that aren't installed
Title: Message Title Craig Gomes updated an issue Puppet / PUP-4644 puppet tells you to read man pages that aren't installed Change By: Craig Gomes Team: Platform Core OS Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3251) Man page for puppet is useless
Title: Message Title Craig Gomes updated an issue Puppet / PUP-3251 Man page for puppet is useless Change By: Craig Gomes Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7931) Support HTTPS Compression on report upload
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7931 Support HTTPS Compression on report upload Change By: Craig Gomes Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8232) Re-add the puppet facts upload face and REST facts terminus
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8232 Re-add the puppet facts upload face and REST facts terminus Change By: Craig Gomes Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3821) [from nodes [= [fact fact-name] fact-val]] queries generate slow sql
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3821 [from nodes [= [fact fact-name] fact-val]] queries generate slow sql Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-194) Gracefully handle Ctrl-C
Title: Message Title Alex Dreyer commented on BOLT-194 Re: Gracefully handle Ctrl-C I'm still getting stack traces clavelin:bolt adreyer$ bolt task run bolt_test::sleep --nodes=dev-agent1 --no-host-key-check Started on dev-agent1... ^C/usr/local/var/rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `sleep': Interrupt from /usr/local/var/rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `wait' from /usr/local/var/rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `ns_wait' from /usr/local/var/rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/abstract_lockable_object.rb:43:in `ns_wait_until' from /usr/local/var/rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/concurrent-ruby-1.0.5/lib/concurrent/atomic/event.rb:87:in `block in wait' from /usr/local/var/rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `block in synchronize'
Jira (BOLT-321) include more content 'out of the box' in a stdlib
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-321 include more content 'out of the box' in a stdlib Issue Type: New Feature Assignee: Unassigned Created: 2018/02/02 8:42 AM Priority: Normal Reporter: Alex Dreyer Bolt is very powerful but users cannot access that power without writing quite a bit of puppet and ruby code or finding and installing modules. Types of content: Stdlib like puppet utility functions(puppetlabs-stdlib doesn't support bolt) Utility control flow plans for common paths like canary and batch execution Task specific functions to retry until, sleep etc. Core tasks to manage services install packages, collect facts etc Distribution questions: 1. Can we get wider adoption of something like the task-modules control repo that provides a lot of content quickly if not immediately 2. Should 'stdlib' modules be at the front or back of the modulepath? Can users update them without updating bolt? 3. Should development of stdlib code be in the bolt repo or in standalone repo[s]? 4. How do we balance long term stability with stdlib. Add Comment
Jira (BOLT-253) Set up containers for ssh unit and integration tests
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-253 Set up containers for ssh unit and integration tests Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8415) Error is optional parameter is missing
Title: Message Title Henrik Lindberg commented on PUP-8415 Re: Error is optional parameter is missing Optional only means that it is acceptable to assign undef. If you want users to not have to give a value you must use a default value _expression_. For example: Optional[String] $password = undef, ... if you want your default to be undef. This is by design. Closing this ticket. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8415) Error is optional parameter is missing
Title: Message Title PU created an issue Puppet / PUP-8415 Error is optional parameter is missing Issue Type: Bug Affects Versions: PUP 4.10.9 Assignee: Unassigned Components: Puppet Server Created: 2018/02/02 7:32 AM Environment: Ubuntu 16.04 Labels: parameter Priority: Major Reporter: PU I create a defined resource which has optional parameters. But if one of the parameters isn't specified I get the following error:
Jira (FACT-1815) Add numa facts
Title: Message Title Pat Riehecky created an issue Facter / FACT-1815 Add numa facts Issue Type: New Feature Assignee: Unassigned Created: 2018/02/02 7:18 AM Priority: Trivial Reporter: Pat Riehecky Desired Behavior: Facter should provide some facts to help identify NUMA aware systems and which NUMA zones are viable for a given system. At the minimum two facts are useful: Are there NUMA zones What NUMA zones exist Actual Behavior: No facts provided Linux systems can identify this via: /sys/devices/system/node/possible Examples: numa_aware = true numa_zones = 0-1 numa_aware = false numa_zones = 0 Add Comment
Jira (FACT-1814) Mountpoints Fact available space does not accurately reflect disk usage
Title: Message Title
Martin Ewings updated an issue
Facter / FACT-1814
Mountpoints Fact available space does not accurately reflect disk usage
Change By:
Martin Ewings
PE 2017.2.2 ( facter 3.6.5) RHEL 6.8The customer is using mountpoints.(parition).available_bytes in conditional logic to determine if software should be installed on a system during Puppet Runs.In testing it appears that there is around a 400mb discrepancy between what is reported by facter as available, and what is actually available, which is backed up by df -h.In a test where by continual facter outputs and df outputs where collected during a large file transfer to the target partition, both facter and df -h tracked upwards in consumed disk space, but never agreed with each other, full attachments below, however a snippet can be seen here:{code:java}facter25687531522.39 GiB58.62%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 3.4G 2.1G 62% /varfacter25687531522.39 GiB58.62%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 3.4G 2.1G 62% /varfacter846790656773.65 MiB87.52%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 5.1G 431M 93% /varfacter415592448396.34 MiB93.30%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 5.4G 90M 99% /varfacter415592448396.34 MiB93.30%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 5.4G 90M 99% /varfacter415592448396.34 MiB93.30%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 5.4G 90M 99% /varfacter421269504401.75 MiB93.21%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 5.4G 95M 99% /varfacter421269504401.75 MiB93.21%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 5.4G 95M 99% /var{code}It could be that facter is failing to take into consideration the blocksize for the partition, in which case i have provided the output below: blockdev --getbsz /dev/mapper/vg_root-lv_var 4096 Used space seems also to agree where available does not: used => "5.39 GiB", for facter and 5.4G in df -h
Add Comment
Jira (FACT-1814) Mountpoints Fact available space does not accurately reflect disk usage
Title: Message Title
Martin Ewings updated an issue
Facter / FACT-1814
Mountpoints Fact available space does not accurately reflect disk usage
Change By:
Martin Ewings
PE 2017.2.2 ( facter 3.6.5) RHEL 6.8The customer is using mountpoints.(parition).available_bytes in conditional logging logic to determine if software should be installed on a system during Puppet Runs.In testing it appears that there is around a 400mb discrepancy between what is reported by facter as available, and what is actually available, which is backed up by df -h.In a test where by continual facter outputs and df outputs where collected during a large file transfer to the target partition, both facter and df -h tracked upwards in consumed disk space, but never agreed with each other, full attachments below, however a snippet can be seen here:{code:java}facter25687531522.39 GiB58.62%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 3.4G 2.1G 62% /varfacter25687531522.39 GiB58.62%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 3.4G 2.1G 62% /varfacter846790656773.65 MiB87.52%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 5.1G 431M 93% /varfacter415592448396.34 MiB93.30%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 5.4G 90M 99% /varfacter415592448396.34 MiB93.30%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 5.4G 90M 99% /varfacter415592448396.34 MiB93.30%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 5.4G 90M 99% /varfacter421269504401.75 MiB93.21%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 5.4G 95M 99% /varfacter421269504401.75 MiB93.21%systemFilesystem Type Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_var ext4 5.8G 5.4G 95M 99% /var{code}It could be that facter is failing to take into consideration the blocksize for the partition, in which case i have provided the output below: blockdev --getbsz /dev/mapper/vg_root-lv_var 4096
Add Comment
Jira (FACT-1814) Mountpoints Fact available space does not accurately reflect disk usage
Title: Message Title Martin Ewings created an issue Facter / FACT-1814 Mountpoints Fact available space does not accurately reflect disk usage Issue Type: Bug Affects Versions: FACT 3.6.5 Assignee: Unassigned Attachments: output.txt Created: 2018/02/02 6:56 AM Priority: Normal Reporter: Martin Ewings PE 2017.2.2 ( facter 3.6.5) RHEL 6.8 The customer is using mountpoints.(parition).available_bytes in conditional logging to determine if software should be installed on a system during Puppet Runs. In testing it appears that there is around a 400mb discrepancy between what is reported by facter as available, and what is actually available, which is backed up by df -h. In a test where by continual facter outputs and df outputs where collected during a large file transfer to the target partition, both facter and df -h tracked upwards in consumed disk space, but never agreed with each other, full attachments below, however a snippet can be seen here:
