Jira (PDB-4339) massive failures connecting to puppetdb
Title: Message Title Luis Ramirez commented on PDB-4339 Re: massive failures connecting to puppetdb 2019-04-18T17:31:43.527-07:00 ERROR [qtp853282096-1040] [c.p.h.c.i.PersistentSyncHttpClient] Error executing http request 2019-04-18T17:31:43.543-07:00 WARN [qtp853282096-1040] [puppetserver] Puppet Error connecting to puppetdb on 8081 at route /pdb/cmd/v1?checksum=f0173d7686071f91c04be589c5b605ee7d0a40f2=8=dev-kjeon1=store_report=2019-04-19T00:31:43.460Z, error message received was 'Error executing http request'. Failing over to the next PuppetDB server_url in the 'server_urls' list 2019-04-18T17:31:43.551-07:00 ERROR [qtp853282096-1040] [puppetserver] Puppet Failed to execute '/pdb/cmd/v1?checksum=f0173d7686071f91c04be589c5b605ee7d0a40f2=8=dev-kjeon1=store_report=2019-04-19T00:31:43.460Z' on at least 1 of the following 'server_urls': https://puppetdb:8081 2019-04-18T17:31:43.552-07:00 ERROR [qtp853282096-1040] [puppetserver] Puppet /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb/http.rb:115:in `raise_request_error' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb/http.rb:156:in `failover_action' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb/http.rb:216:in `action' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb/command.rb:64:in `block in submit' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in `profile' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in `profile' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb.rb:99:in `profile' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb/command.rb:63:in `submit' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb.rb:62:in `block in submit_command' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in `profile' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in `profile' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb.rb:99:in `profile' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb.rb:59:in `submit_command' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/reports/puppetdb.rb:24:in `block in process' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in `profile' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in `profile' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/puppetdb.rb:99:in `profile' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/reports/puppetdb.rb:21:in `process' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:37:in `block in process' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:53:in `block in processors' org/jruby/RubyArray.java:1801:in `each' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:51:in `processors' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:30:in `process' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:14:in `save' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:285:in `save' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:187:in `do_save' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:54:in `block in call' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:264:in `override'
Jira (BOLT-1244) SELinux management does not work on localhost
Title: Message Title Barr Iserloth commented on BOLT-1244 Re: SELinux management does not work on localhost Cas Donoghue This might be a dumb question, but did you intend for these changes to land in the PE z's/Kearney release that's happening? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-843) Generate a "rerun" file after every command
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-843 Generate a "rerun" file after every command Change By: Melissa Amos Labels: docs docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1244) SELinux management does not work on localhost
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1244 SELinux management does not work on localhost Change By: Melissa Amos Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4339) massive failures connecting to puppetdb
Title: Message Title
Austin Blatt commented on PDB-4339
Re: massive failures connecting to puppetdb
Luis Ramirez Are you seeing a warning message along with the Puppetserver error you first attached? There are two warnings you could see
"Error connecting to #{server_url.host} on #{server_url.port} at route #{route}, " \
"error message received was '#{response.message}'. #{SERVER_URL_FAIL_MSG}"
and
"Error connecting to #{server_url.host} on #{server_url.port} at route #{route}, " \
"error message received was '#{response.message}'. #{SERVER_URL_FAIL_MSG}"
If you don't see one of those, then enable debug logging for Puppetserver and look for a message like
"HTTP 404 (probably normal) when connecting to #{server_url.host} on #{server_url.port} " \
"at route #{route}, error message received was '#{response.message}'. #{SERVER_URL_FAIL_MSG}"
Jira (BOLT-1244) SELinux management does not work on localhost
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1244 SELinux management does not work on localhost Change By: Cas Donoghue Release Notes Summary: Previously some components that shipped with the puppet-agent were not included with bolt-runtime causing discrepancies between using a puppet-agent to apply puppet code locally versus using Bolt's puppet. Bolt now ships with components similar to puppet agent. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1244) SELinux management does not work on localhost
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1244 SELinux management does not work on localhost Change By: Cas Donoghue Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4339) massive failures connecting to puppetdb
Title: Message Title Luis Ramirez commented on PDB-4339 Re: massive failures connecting to puppetdb Austin Blatt what log level would you recommend me? I tried INFO but I am having a hard time trying to get the error. I have 3 puppet servers and I am using a load balancer, the puppet1 has setup puppetdb and has more resources than puppet2 and puppet3 , I get these puppetdb errors in the puppetserverlog in sporadic times in the puppet[1-3] servers but I do not see anything relevant in the puppetdb in puppet1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1232) Document experimental v2 Inventory
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1232 Document experimental v2 Inventory Change By: Alex Dreyer Assignee: Cas Donoghue Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9646) Return parsed yaml plan without instantiating
Title: Message Title David Kramer assigned an issue to Unassigned Puppet / PUP-9646 Return parsed yaml plan without instantiating Change By: David Kramer Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9646) Return parsed yaml plan without instantiating
Title: Message Title David Kramer updated an issue Puppet / PUP-9646 Return parsed yaml plan without instantiating Change By: David Kramer Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1196) bolt-inventory-pdb examples in public documentation are incorrect
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1196 bolt-inventory-pdb examples in public documentation are incorrect Change By: Melissa Amos Labels: docs docs_reviewd docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1196) bolt-inventory-pdb examples in public documentation are incorrect
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1196 bolt-inventory-pdb examples in public documentation are incorrect Change By: Melissa Amos Labels: docs docs_reviewd Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1244) SELinux management does not work on localhost
Title: Message Title Cas Donoghue commented on BOLT-1244 Re: SELinux management does not work on localhost While adding this change we noticed some other components in puppet-runtime that will be nice to include in bolt-runtime. (see pupet-runtime PR) For el-7 including the extra components bumps bolt `.rpm` size from 28M to 30M. This should be the largest change in that it includes all the linux specific components (augeas, linux specific gems, AND selinux gem). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7537) Agent/Master Separation
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7537 Agent/Master Separation Change By: Josh Cooper Team/s: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6719) Phase 2 Puppet Unicode User Facing Improvements
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6719 Phase 2 Puppet Unicode User Facing Improvements Change By: Josh Cooper Team/s: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6720) Phase 1 Puppet Unicode Support For Non-English Development
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6720 Phase 1 Puppet Unicode Support For Non-English Development Change By: Josh Cooper Team/s: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3460) Improve puppet's error handling and exit code correctness.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3460 Improve puppet's error handling and exit code correctness. Change By: Josh Cooper Team/s: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9564) Puppet upgrades debian packages with pending updates when setting them on hold
Title: Message Title Alexandru Popa commented on PUP-9564 Re: Puppet upgrades debian packages with pending updates when setting them on hold PR: https://github.com/puppetlabs/puppet/pull/7489 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9642) puppet device permissions preventing reading dirs
Title: Message Title Dimitri Tischenko commented on PUP-9642 Re: puppet device permissions preventing reading dirs David Schmitt As per the docs at https://puppet.com/docs/pe/2018.1/component_versions_in_recent_pe_releases.html, the current LTS release of PE uses agent 5.5.10, so customers currently using this version (including Deutsche Telekom) have this issue. Do we have a work-around for them short of upgrading to PE 2019.0? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9642) puppet device permissions preventing reading dirs
Title: Message Title David Schmitt updated an issue Puppet / PUP-9642 puppet device permissions preventing reading dirs While I was able to reproduce this on 5.5, the effect is not reproducible on 6.4.1. Change By: David Schmitt Affects Version/s: PUP 5.5.13 Affects Version/s: PUP 5.5.1 Fix Version/s: PUP 6.4.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You
Jira (PUP-9645) User Rights Management SIP issue on MacOS 10.14.x
Title: Message Title Gheorghe Popescu commented on PUP-9645 Re: User Rights Management SIP issue on MacOS 10.14.x Seems like that, because it was user management which was failing Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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.
