Jira (PUP-9967) puppet plugin download doesn't respect the server variable in puppet.conf
Title: Message Title Tom Parker commented on PUP-9967 Re: puppet plugin download doesn't respect the server variable in puppet.conf Thanks 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321330.1565991716000.9875.1576267380219%40Atlassian.JIRA.
Jira (PUP-9967) puppet plugin download doesn't respect the server variable in puppet.conf
Title: Message Title Josh Cooper commented on PUP-9967 Re: puppet plugin download doesn't respect the server variable in puppet.conf Adding them to the [main] section should work consistently for all applications. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321330.1565991716000.9748.1576265760263%40Atlassian.JIRA.
Jira (PUP-9967) puppet plugin download doesn't respect the server variable in puppet.conf
Title: Message Title Tom Parker commented on PUP-9967 Re: puppet plugin download doesn't respect the server variable in puppet.conf Is there a user section or a general section where server and proxy variables can be defined that would apply to all connections to the master? 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321330.1565991716000.9737.1576265460068%40Atlassian.JIRA.
Jira (PUP-9967) puppet plugin download doesn't respect the server variable in puppet.conf
Title: Message Title Josh Cooper commented on PUP-9967 Re: puppet plugin download doesn't respect the server variable in puppet.conf This is because the plugin application uses user run mode instead of agent. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321330.1565991716000.9709.1576263840107%40Atlassian.JIRA.
Jira (PDB-4602) Guard PuppetDB migrations against simultaneous writers
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-4602 Guard PuppetDB migrations against simultaneous writers Change By: Nick Walker Team/s: HA 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.339273.1576193168000.9518.1576260300247%40Atlassian.JIRA.
Jira (PDB-4600) Investigate OOM errors during resource_events partitioning migration
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4600 Investigate OOM errors during resource_events partitioning migration Change By: Zachary Kent Assignee: Zachary Kent 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.339229.1576177499000.9471.1576258800480%40Atlassian.JIRA.
Jira (PUP-10165) puppetdb_query doesn't respect hostprivkey & hostcert settings
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10165 puppetdb_query doesn't respect hostprivkey & hostcert settings Change By: Josh Cooper Fix Version/s: PUP 6.y Fix Version/s: PUP 6.4.z 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338500.1575710302000.9464.1576258200147%40Atlassian.JIRA.
Jira (PUP-10165) puppetdb_query doesn't respect hostprivkey & hostcert settings
Title: Message Title Josh Cooper commented on PUP-10165 Re: puppetdb_query doesn't respect hostprivkey & hostcert settings The new CertProvider code assumes the certname and hostprivkey/hostcert settings are consistent, but there are cases where hostprivkey/hostcert may be overridden. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338500.1575710302000.9458.1576258020140%40Atlassian.JIRA.
Jira (PUP-10041) Switch PMT to use puppet's http client
Title: Message Title Josh Cooper commented on PUP-10041 Re: Switch PMT to use puppet's http client Passed CI in f331cc7cc49111eaa41deacaf931bab72d8fa510 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326146.1569368826000.9453.1576257780455%40Atlassian.JIRA.
Jira (PUP-10160) Puppet should not load types and providers during environment convergence
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10160 Puppet should not load types and providers during environment convergence Change By: Josh Cooper Release Notes Summary: Previously puppet agents could fail to apply a catalog if the agent switched environments based on node classification and there were different versions of a module in those environments. As a result of this change, an agent should converge to its server-assigned environment more quickly and will only update its cached catalog if the environment converges. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.337880.157548855.9452.1576257780411%40Atlassian.JIRA.
Jira (PUP-9391) HP-UX usermod syntax is incorrect
Title: Message Title Carla Curtis commented on PUP-9391 Re: HP-UX usermod syntax is incorrect Thank you! Is there a target version(s) for this? We'd like to plan to pick it up at the next opportunity in our schedule. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.290075.1546446054000.9447.1576257720107%40Atlassian.JIRA.
Jira (PUP-10041) Switch PMT to use puppet's http client
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10041 Switch PMT to use puppet's http client Change By: Josh Cooper Release Notes Summary: The puppet module tool now uses puppet's http client to connect to the forge. The only user visible change should be that the "puppet module install" command will now observe the "Puppet[:sourceaddress]" setting. This is useful when running the install command on a puppetserver with multiple network interfaces and the puppet forge is only routable on some interfaces. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326146.1569368826000.9399.1576257060299%40Atlassian.JIRA.
Jira (PUP-10161) Regresssion: puppet 6.11 can't manage selinux on centos/redhat 8
Title: Message Title Michael Watters commented on PUP-10161 Re: Regresssion: puppet 6.11 can't manage selinux on centos/redhat 8 This error can also cause management of resources that do not depend on selinux to fail as well. For example, on a node running CentOS 8 custom types are not applied due to the agent failures. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338022.1575566536000.9396.1576257000423%40Atlassian.JIRA.
Jira (PDB-2398) PuppetDB should enable emergency deletion of historical data
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-2398
PuppetDB should enable emergency deletion of historical data
Change By:
Nick Walker
When a disk fills up on a database server, it is useful to have an option for reducing the disk space used without deleting data used by catalog compilation or requiring an increase in disk space. Disk increases can be infeasible or may require a long change cycle during which the Puppet infrastructure is inoperative. It's also useful to TRUNCATE the reports table before a major upgrade that will need to migrate the reports table or if the upgrade contains a PostgreSQL upgrade that will copy the entire database. h2. Historical ContextIn PuppetDB 2.x disk usage could be reduced in an emergency by truncating the reports table, which is often the largest table in the database by several orders of magnitude. This would return large amounts of space to the operating system, enabling further maintenance operations, while keeping exported resources intact for catalog compilation:{noformat}# PE 3.8.x# sudo -u pe-postgres /opt/puppet/bin/psql -d pe-puppetdbcould not change directory to "/root"psql (9.2.14)Type "help" for help.pe-puppetdb=# SELECT count(*) FROM catalog_resources WHERE exported = true; count--- 5(1 row)pe-puppetdb=# TRUNCATE TABLE reports CASCADE;NOTICE: truncate cascades to table "resource_events"NOTICE: truncate cascades to table "latest_reports"TRUNCATE TABLEpe-puppetdb=# SELECT count(*) FROM catalog_resources WHERE exported = true; count--- 5(1 row){noformat}In 2015.3.x, the TRUNCATE operation now cascades beyond the tables related to reporting and wipes out exported resources, which negatively impacts catalog compilation:{noformat}# PE 2015.x# sudo -u pe-postgres /opt/puppetlabs/server/bin/psql -d pe-puppetdbcould not change directory to "/root": Permission deniedpsql (9.4.5)Type "help" for help.pe-puppetdb=# SELECT count(*) FROM catalog_resources WHERE exported = true; count--- 6(1 row)pe-puppetdb=# TRUNCATE TABLE reports CASCADE;NOTICE: truncate cascades to table "certnames"NOTICE: truncate cascades to table "resource_events"NOTICE: truncate cascades to table "factsets"NOTICE: truncate cascades to table "catalogs"NOTICE: truncate cascades to table "facts"NOTICE: truncate cascades to table "catalog_resources"TRUNCATE TABLEpe-puppetdb=# SELECT count(*) FROM catalog_resources WHERE exported = true; count--- 0(1 row){noformat}h2. Desired FunctionalityPuppetDB should allow for emergency removal of historical data without impacting catalog compilation or requiring changes to disk space allocation.h1. Workaround / Proposed Implementation {code}echo "BEGIN TRANSACTION;ALTER TABLE certnames DROP CONSTRAINT IF EXISTS certnames_reports_id_fkey;UPDATE certnames SET latest_report_id = NULL;TRUNCATE TABLE reports CASCADE;ALTER TABLE certnames ADD CONSTRAINT "certnames_reports_id_fkey" FOREIGN KEY (latest_report_id) REFERENCES reports(id) ON DELETE SET NULL;COMMIT TRANSACTION;" >
Jira (FACT-2251) Present fact creation
Title: Message Title Gheorghe Campean created an issue Facter / FACT-2251 Present fact creation Issue Type: Task Assignee: Gheorghe Campean Created: 2019/12/13 5:30 AM Priority: Normal Reporter: Gheorghe Campean 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 view this discussion on the web visit
