Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title
Selvakumar Azhagarsami updated an issue
PuppetDB / PDB-4642
Puppet 2019.3 upgrade failure from 2019.2.2
Change By:
Selvakumar Azhagarsami
During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist. Please refer to the attached log file for more details.{code:java}[m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event [0m [1;31m2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed!journalctl log for pe-puppetdb:-- Logs begin at Mon 2019-12-23 23:25:01 AEDT, end at Fri 2020-01-31 12:44:13 AEDT. --Jan 31 12:43:02 harmony3-d1 puppetlabs . anu.edu.au com systemd[1]: Starting pe-puppetdb Service...Jan 31 12:43:37 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: WARNING: An illegal reflective access operation has occurredJan 31 12:43:37 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: WARNING: Illegal reflective access by dynapath.defaults$eval24067$fn__24068 to method java.net.URLClassLoader.addURL(java.net.URL)Jan 31 12:43:37 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: WARNING: Please consider reporting this to the maintainers of dynapath.defaults$eval24067$fn__24068Jan 31 12:43:37 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operationsJan 31 12:43:37 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: WARNING: All illegal access operations will be denied in a future releaseJan 31 12:43:52 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:13 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: Execution error (PSQLException) at org.postgresql.core.v3.QueryExecutorImpl/receiveErrorResponse (QueryExecutorImpl.java:2497).Jan 31 12:44:13 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: ERROR: relation "resource_events_20200123z" does not existJan 31 12:44:1
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Selvakumar Azhagarsami updated an issue PuppetDB / PDB-4642 Puppet 2019.3 upgrade failure from 2019.2.2 Change By: Selvakumar Azhagarsami Attachment: 2020-01-31T12.33.25 1100.install.log 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.344931.1580780081000.12439.1580780700367%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title
Selvakumar Azhagarsami updated an issue
PuppetDB / PDB-4642
Puppet 2019.3 upgrade failure from 2019.2.2
Change By:
Selvakumar Azhagarsami
During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist. Please refer to the attached log file for more details.{code:java}[m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event [0m [1;31m2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed!journalctl log for pe-puppetdb:-- Logs begin at Mon 2019-12-23 23:25:01 AEDT, end at Fri 2020-01-31 12:44:13 AEDT. --Jan 31 12:43:02 harmony3-d1.anu.edu.au systemd[1]: Starting pe-puppetdb Service...Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: An illegal reflective access operation has occurredJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Illegal reflective access by dynapath.defaults$eval24067$fn__24068 to method java.net.URLClassLoader.addURL(java.net.URL)Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Please consider reporting this to the maintainers of dynapath.defaults$eval24067$fn__24068Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operationsJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: All illegal access operations will be denied in a future releaseJan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Execution error (PSQLException) at org.postgresql.core.v3.QueryExecutorImpl/receiveErrorResponse (QueryExecutorImpl.java:2497).Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: ERROR: relation "resource_events_20200123z" does not existJan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Position: 13Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Full report at:Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: /tmp/clojure-986115849128723.ednJan 31 12:44:13 harmony3-d1.anu.edu.au systemd[1]: pe-puppet
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Austin Boyd updated an issue PuppetDB / PDB-4642 Puppet 2019.3 upgrade failure from 2019.2.2 Change By: Austin Boyd Labels: jira_escalated 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.344931.1580780081000.12433.1580780520455%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Austin Boyd updated an issue PuppetDB / PDB-4642 Puppet 2019.3 upgrade failure from 2019.2.2 Change By: Austin Boyd Zendesk Ticket IDs: 37911 Zendesk Ticket Count: 1 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.344931.1580780081000.12429.1580780520283%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Selvakumar Azhagarsami commented on PDB-4642 Re: Puppet 2019.3 upgrade failure from 2019.2.2 PE standard customer reported this issue. https://puppetlabs.zendesk.com/agent/tickets/37911 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.344931.1580780081000.12425.1580780460115%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title
Selvakumar Azhagarsami updated an issue
PuppetDB / PDB-4642
Puppet 2019.3 upgrade failure from 2019.2.2
Change By:
Selvakumar Azhagarsami
During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist. Please refer to the attached log file for more details.{code:java}[m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event [0m [1;31m2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed!journalctl log for pe-puppetdb:-- Logs begin at Mon 2019-12-23 23:25:01 AEDT, end at Fri 2020-01-31 12:44:13 AEDT. --Jan 31 12:43:02 harmony3-d1.anu.edu.au systemd[1]: Starting pe-puppetdb Service...Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: An illegal reflective access operation has occurredJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Illegal reflective access by dynapath.defaults$eval24067$fn__24068 to method java.net.URLClassLoader.addURL(java.net.URL)Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Please consider reporting this to the maintainers of dynapath.defaults$eval24067$fn__24068Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operationsJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: All illegal access operations will be denied in a future releaseJan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Execution error (PSQLException) at org.postgresql.core.v3.QueryExecutorImpl/receiveErrorResponse (QueryExecutorImpl.java:2497).Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: ERROR: relation "resource_events_20200123z" does not existJan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Position: 13Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Full report at:Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: /tmp/clojure-986115849128723.ednJan 31 12:44:13 harmony3-d1.anu.edu.au systemd[1]: pe-puppet
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title
Selvakumar Azhagarsami updated an issue
PuppetDB / PDB-4642
Puppet 2019.3 upgrade failure from 2019.2.2
Change By:
Selvakumar Azhagarsami
During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist. Please refer to the attached log file for more details.{code:java}[m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event [0m [1;31m2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed!journalctl log for pe-puppetdb:-- Logs begin at Mon 2019-12-23 23:25:01 AEDT, end at Fri 2020-01-31 12:44:13 AEDT. --Jan 31 12:43:02 harmony3-d1.anu.edu.au systemd[1]: Starting pe-puppetdb Service...Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: An illegal reflective access operation has occurredJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Illegal reflective access by dynapath.defaults$eval24067$fn__24068 to method java.net.URLClassLoader.addURL(java.net.URL)Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Please consider reporting this to the maintainers of dynapath.defaults$eval24067$fn__24068Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operationsJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: All illegal access operations will be denied in a future releaseJan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Execution error (PSQLException) at org.postgresql.core.v3.QueryExecutorImpl/receiveErrorResponse (QueryExecutorImpl.java:2497).Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: ERROR: relation "resource_events_20200123z" does not existJan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Position: 13Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Full report at:Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: /tmp/clojure-986115849128723.ednJan 31 12:44:13 harmony3-d1.anu.edu.au systemd[1]: pe-puppet
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title
Selvakumar Azhagarsami updated an issue
PuppetDB / PDB-4642
Puppet 2019.3 upgrade failure from 2019.2.2
Change By:
Selvakumar Azhagarsami
During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist.{code:java} [m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event [0m [1;31m2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed!journalctl log for pe-puppetdb:-- Logs begin at Mon 2019-12-23 23:25:01 AEDT, end at Fri 2020-01-31 12:44:13 AEDT. --Jan 31 12:43:02 harmony3-d1.anu.edu.au systemd[1]: Starting pe-puppetdb Service...Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: An illegal reflective access operation has occurredJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Illegal reflective access by dynapath.defaults$eval24067$fn__24068 to method java.net.URLClassLoader.addURL(java.net.URL)Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Please consider reporting this to the maintainers of dynapath.defaults$eval24067$fn__24068Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operationsJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: All illegal access operations will be denied in a future releaseJan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Execution error (PSQLException) at org.postgresql.core.v3.QueryExecutorImpl/receiveErrorResponse (QueryExecutorImpl.java:2497).Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: ERROR: relation "resource_events_20200123z" does not existJan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Position: 13Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Full report at:Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: /tmp/clojure-986115849128723.ednJan 31 12:44:13 harmony3-d1.anu.edu.au systemd[1]: pe-puppetdb.service: control process exited, code=exited status
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title
Selvakumar Azhagarsami updated an issue
PuppetDB / PDB-4642
Puppet 2019.3 upgrade failure from 2019.2.2
Change By:
Selvakumar Azhagarsami
During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist. Please refer to the attached log file for more details. {code:java}[m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event [0m [1;31m2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed!journalctl log for pe-puppetdb:-- Logs begin at Mon 2019-12-23 23:25:01 AEDT, end at Fri 2020-01-31 12:44:13 AEDT. --Jan 31 12:43:02 harmony3-d1.anu.edu.au systemd[1]: Starting pe-puppetdb Service...Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: An illegal reflective access operation has occurredJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Illegal reflective access by dynapath.defaults$eval24067$fn__24068 to method java.net.URLClassLoader.addURL(java.net.URL)Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Please consider reporting this to the maintainers of dynapath.defaults$eval24067$fn__24068Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operationsJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: All illegal access operations will be denied in a future releaseJan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Execution error (PSQLException) at org.postgresql.core.v3.QueryExecutorImpl/receiveErrorResponse (QueryExecutorImpl.java:2497).Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: ERROR: relation "resource_events_20200123z" does not existJan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Position: 13Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Full report at:Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: /tmp/clojure-986115849128723.ednJan 31 12:44:13 harmony3-d1.anu.edu.au systemd[1]: pe-pupp
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Selvakumar Azhagarsami created an issue PuppetDB / PDB-4642 Puppet 2019.3 upgrade failure from 2019.2.2 Issue Type: Bug Assignee: Unassigned Attachments: 2020-01-31T12.33.25 1100.install.log Components: PuppetDB Created: 2020/02/03 5:34 PM Priority: Normal Reporter: Selvakumar Azhagarsami During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist. [m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event [0m [1;31m2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed! journalctl log for pe-puppetdb: -- Logs begin at
Jira (PUP-10247) Support ruby 2.7
Title: Message Title Anthony Sottile commented on PUP-10247 Re: Support ruby 2.7 hitting this as well, for those that want to land here on a stacktrace from google here's one I'm running into: $ puppet parser validate ../personal-puppet/manifests/site.pp /tmp/x/renv/lib/ruby/gems/2.7.0/gems/puppet-6.12.0/lib/puppet/indirector.rb:49: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call /tmp/x/renv/lib/ruby/gems/2.7.0/gems/puppet-6.12.0/lib/puppet/indirector/indirection.rb:95: warning: The called method `initialize' is defined here /tmp/x/renv/lib/ruby/gems/2.7.0/gems/puppet-6.12.0/lib/puppet/util.rb:463: warning: URI.escape is obsolete /tmp/x/renv/lib/ruby/gems/2.7.0/gems/puppet-6.12.0/lib/puppet.rb:7: warning: already initialized constant Puppet::OLDEST_RECOMMENDED_RUBY_VERSION /tmp/x/renv/lib/ruby/gems/2.7.0/gems/puppet-6.12.0/lib/puppet.rb:7: warning: previous definition of OLDEST_RECOMMENDED_RUBY_VERSION was here /tmp/x/renv/lib/ruby/gems/2.7.0/gems/puppet-6.12.0/lib/puppet.rb:7: warning: already initialized constant Puppet::OLDEST_RECOMMENDED_RUBY_VERSION /tmp/x/renv/lib/ruby/gems/2.7.0/gems/puppet-6.12.0/lib/puppet.rb:7: warning: previous definition of OLDEST_RECOMMENDED_RUBY_VERSION was here /tmp/x/renv/lib/ruby/gems/2.7.0/gems/puppet-6.12.0/lib/puppet.rb:7: warning: already initialized constant Puppet::OLDEST_RECOMMENDED_RUBY_VERSION /tmp/
Jira (PUP-10266) Ensure environment cache is not invalidated during a lockless deploy
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10266 Ensure environment cache is not invalidated during a lockless deploy Change By: Maggie Dreyer Summary: Ensure environment cache works is not invalidated during a lockless deploy 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.344927.1580776369000.12357.1580776440219%40Atlassian.JIRA.
Jira (PUP-10266) Ensure environment cache works
Title: Message Title Molly Waggett created an issue Puppet / PUP-10266 Ensure environment cache works Issue Type: Bug Assignee: Unassigned Created: 2020/02/03 4:32 PM Priority: Normal Reporter: Molly Waggett We need to ensure that the environment cache persists throughout a compile. If we re-create an environment during each deploy, a compile running with an old version of the environment could then be accessing new settings/info from cache. One potential solution would be to create brand new environments for each deploy, e.g. production_, production_, etc. as opposed to recreating production on each deploy. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4641) resource_events partitioning migration failure
Title: Message Title Reinhard Vicinus created an issue PuppetDB / PDB-4641 resource_events partitioning migration failure Issue Type: Bug Affects Versions: PDB 6.8.1 Assignee: Unassigned Created: 2020/02/03 11:55 AM Priority: Normal Reporter: Reinhard Vicinus Trying to upgrade from puppetdb 6.7.3 to puppetdb 6.8.1 and as far as I can tell I still get the same error as described in PDB-4626: ERROR [p.p.s.migrate] Caught SQLException during migration java.sql.BatchUpdateException: Batch entry 0 INSERT INTO resource_events_20200124Z ( event_hash, report_id, certname_id, status, timestamp, resource_type, resource_title, property, new_value, old_value, message, file, line, containment_path, containing_class, corrective_change, name ) VALUES (...) was aborted: ERROR: relation "resource_events_20200124z" does not exist Add Comment
Jira (PUP-10265) Add 'site-modules' to the environment default modulepath
Title: Message Title
Sean McDonald updated an issue
Puppet / PUP-10265
Add 'site-modules' to the environment default modulepath
Change By:
Sean McDonald
By default, an environment's modulepath does not contain {{site-modules}}. In bolt, that is a default path available to bolt projects, and when users want to migrate their bolt projects to PE it would be nice if the defaults default modulepaths were the same.
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.344733.1580758475000.11492.1580758560123%40Atlassian.JIRA.
Jira (PUP-10265) Add 'site-modules' to the environment default modulepath
Title: Message Title
Sean McDonald updated an issue
Puppet / PUP-10265
Add 'site-modules' to the environment default modulepath
Change By:
Sean McDonald
By default, an environment's modulepath does not contain {{site-modules}}. In bolt, that is a default path available to Boltdirs bolt projects , and when users want to migrate their bolt projects to PE it would be nice if the defaults modulepaths were the same.
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.344733.1580758475000.11491.1580758560081%40Atlassian.JIRA.
Jira (PUP-10265) Add 'site-modules' to the environment default modulepath
Title: Message Title
Sean McDonald updated an issue
Puppet / PUP-10265
Add 'site-modules' to the environment default modulepath
Change By:
Sean McDonald
By default, an environment's modulepath does not contain { { site-modules} } . In bolt, that is a default path available to Boltdirs, and when users want to migrate their bolt projects to PE it would be nice if the defaults modulepaths were the same.
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.344733.1580758475000.11490.1580758500187%40Atlassian.JIRA.
Jira (PUP-10265) Add 'site-modules' to the environment default modulepath
Title: Message Title
Sean McDonald created an issue
Puppet / PUP-10265
Add 'site-modules' to the environment default modulepath
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2020/02/03 11:34 AM
Priority:
Normal
Reporter:
Sean McDonald
By default, an environment's modulepath does not contain {site-modules} . In bolt, that is a default path available to Boltdirs, and when users want to migrate their bolt projects to PE it would be nice if the defaults modulepaths were the same.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10264) Puppet agent status command
Title: Message Title Lucas Young updated an issue Puppet / PUP-10264 Puppet agent status command Change By: Lucas Young Currently there isn't a user-friendly way of checking the Puppet service status without manually inspecting the PID / Lock file from the agent. Previously there was the ability to check the status of the Master by using the now deprecated *Puppet Status* command: *[https://puppet.com/docs/puppet/latest/man/status.html]* Would like to have a command that would allow a user to check the status of the Puppet service running on an agent. Ideally the command would do two things: # If the service is disabled: check for the disabled lock file and report that status and lock file # if the service is running check for the running lock file and report that status back and lock file 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 recei
Jira (PUP-10264) Puppet agent status command
Title: Message Title Lucas Young moved an issue Puppet / PUP-10264 Puppet agent status command Change By: Lucas Young Affects Version/s: 2018.1.11 Component/s: Puppet Server Key: ENTERPRISE PUP - 1313 10264 Project: Puppet Enterprise 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.3
Jira (PUP-8318) Allow client tools and classifier gem to support parameters
Title: Message Title Chris Denneen commented on PUP-8318 Re: Allow client tools and classifier gem to support parameters Sean McDonald I see you closed that issue but there was no comments on it... still would like the parameters or ENV variables to work if possible... think useful for CI/CD purposes rather than having to mock up a configuration file unnecessarily 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.229070.1515102987000.11198.1580754360144%40Atlassian.JIRA.
Jira (PUP-10228) Puppet 6 daemons do not release ssl_lockfile
Title: Message Title Josh Cooper commented on PUP-10228 Re: Puppet 6 daemons do not release ssl_lockfile The ssl lockfile was added in 6.5.0, so this doesn't need to go into 6.4.x, which will be EOL in this month. 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.341497.1578522774000.11192.1580754060103%40Atlassian.JIRA.
Jira (PUP-10228) Puppet 6 daemons do not release ssl_lockfile
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10228 Puppet 6 daemons do not release ssl_lockfile Change By: Josh Cooper Fix Version/s: PUP 6.13.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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341497.1578522774000.11190.1580754000131%40Atlassian.JIRA.
Jira (PUP-10228) Puppet 6 daemons do not release ssl_lockfile
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10228 Puppet 6 daemons do not release ssl_lockfile Change By: Josh Cooper Sprint: Coremunity Hopper 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.341497.1578522774000.11188.1580753940211%40Atlassian.JIRA.
Jira (PUP-9750) optionally add pe_serverversion to server_facts
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9750 optionally add pe_serverversion to server_facts Change By: Josh Cooper Summary: optionally add pe_version pe_serverversion to server_facts 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.312257.156036703.11179.1580753880411%40Atlassian.JIRA.
Jira (PUP-9750) optionally add pe_serverversion to server_facts
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9750 optionally add pe_serverversion to server_facts Change By: Josh Cooper Fix Version/s: PUP 6.4.6 Fix Version/s: PUP 5.5.19 Fix Version/s: PUP 6.13.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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312257.156036703.11183.1580753880595%40Atlassian.JIRA.
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Thomas Kishel commented on PDB-2487 Re: Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Nick Walker resource_events_ttl has been added to PuppetDB 6.8.0 via https://github.com/puppetlabs/puppetdb/pull/3027 So this can be closed, yes? PE 2019.3 ships with PuppetDB 6.8.1. I will submit a PR for PE-28222 to express this setting in PE. Could you close or merge https://github.com/npwalker/pe_databases/pull/32 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.119255.1456852336000.11174.1580753761441%40Atlassian.JIRA.
Jira (PUP-5069) Puppet's HTTP API does not allow callers to trust system cacerts
Title: Message Title Rob Braden updated an issue Puppet / PUP-5069 Puppet's HTTP API does not allow callers to trust system cacerts Change By: Rob Braden Sprint: Coremunity Hopper 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.94774.1440440148000.11134.1580753100243%40Atlassian.JIRA.
Jira (PUP-8968) Add http_compression setting
Title: Message Title Rob Braden updated an issue Puppet / PUP-8968 Add http_compression setting Change By: Rob Braden Sprint: Coremunity Hopper 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.262868.1530078961000.11131.1580753040595%40Atlassian.JIRA.
Jira (PUP-7931) Support HTTPS Compression on report upload
Title: Message Title Rob Braden updated an issue Puppet / PUP-7931 Support HTTPS Compression on report upload Change By: Rob Braden Sprint: Coremunity Hopper 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.210137.1505138923000.11129.1580753040507%40Atlassian.JIRA.
Jira (PUP-8338) Puppet apply doesn't stream file content
Title: Message Title Rob Braden updated an issue Puppet / PUP-8338 Puppet apply doesn't stream file content Change By: Rob Braden Sprint: Coremunity Hopper 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.229892.1515543111000.11122.1580752980175%40Atlassian.JIRA.
Jira (PUP-9566) Allow to send extra headers when requesting a catalog compilation
Title: Message Title Rob Braden updated an issue Puppet / PUP-9566 Allow to send extra headers when requesting a catalog compilation Change By: Rob Braden Sprint: Coremunity Hopper 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.300606.1552923936000.11109.1580752920379%40Atlassian.JIRA.
Jira (PUP-9750) optionally add pe_version to server_facts
Title: Message Title Rob Braden commented on PUP-9750 Re: optionally add pe_version to server_facts The final name is pe_serverversion 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.312257.156036703.11103.1580752740135%40Atlassian.JIRA.
Jira (PUP-8318) Allow client tools and classifier gem to support parameters
Title: Message Title Sean McDonald commented on PUP-8318 Re: Allow client tools and classifier gem to support parameters I'm going to close this due to inactivity. Go ahead and re-open if this is still important. 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.229070.1515102987000.11096.1580752680523%40Atlassian.JIRA.
Jira (PUP-9750) optionally add pe_version to server_facts
Title: Message Title Rob Braden updated an issue Puppet / PUP-9750 optionally add pe_version to server_facts Change By: Rob Braden Release Notes: Enhancement 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.312257.156036703.11099.1580752680615%40Atlassian.JIRA.
Jira (PUP-10261) X-Hub-Signature check
Title: Message Title Rob Braden updated an issue Puppet / PUP-10261 X-Hub-Signature check Change By: Rob Braden Team: Froyo 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.344469.1580475995000.11073.1580752260452%40Atlassian.JIRA.
Jira (PUP-8318) Allow client tools and classifier gem to support parameters
Title: Message Title Rob Braden updated an issue Puppet / PUP-8318 Allow client tools and classifier gem to support parameters Change By: Rob Braden Team: Skeletor 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.229070.1515102987000.11057.1580752020755%40Atlassian.JIRA.
Jira (PUP-10226) URL encode paths in http client
Title: Message Title Melissa Stone updated an issue Puppet / PUP-10226 URL encode paths in http client Change By: Melissa Stone Release Notes Summary: HTTP client encodes url paths Release Notes: Not Needed 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.341489.1578519209000.11041.1580751900152%40Atlassian.JIRA.
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Trevor Vaughan commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated Thomas Hallgren I may not have been clear. While it is crazy slow, it is no slower than if you remove the entire cache and run without an error. 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.302978.1554294806000.10715.1580743260267%40Atlassian.JIRA.
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Thomas Hallgren commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated Given that the patch makes things "crazy slow", I would avoid implementing the patch. I think there's a fair chance that the slowness hits a lot of customers and the reason for it is forgotten. Raise the priority on this ticket if needed, but the root cause must be dealt with. 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.302978.1554294806000.10704.1580742840391%40Atlassian.JIRA.
Jira (FACT-2334) Custom facts are resolved multiple times in a single run
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2334 Custom facts are resolved multiple times in a single run Change By: Oana Tanasoiu Assignee: Oana Tanasoiu 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.344212.1580387362000.10428.1580740560248%40Atlassian.JIRA.
Jira (FACT-2322) Extend Facter 4.x API with debugging?
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2322 Extend Facter 4.x API with debugging? Change By: Oana Tanasoiu Assignee: Oana Tanasoiu 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.344088.1580306192000.10426.1580740500191%40Atlassian.JIRA.
Jira (FACT-2344) Run PDK tests with Facter 4.x
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2344 Run PDK tests with Facter 4.x Issue Type: Task Assignee: Unassigned Created: 2020/02/03 6:29 AM Priority: Normal Reporter: Bogdan Irimie 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.344674.1580740179000.10422
Jira (FACT-2312) Run Bolt tests with Facter 4.x
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2312 Run Bolt tests with Facter 4.x Change By: Bogdan Irimie Summary: Run PDK and Bolt tests with Facter 4.x 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.344078.1580301623000.10420.1580740140667%40Atlassian.JIRA.
Jira (FACT-2341) Investigate weight error messages
Title: Message Title Bogdan Irimie assigned an issue to Florin Dragos Facter / FACT-2341 Investigate weight error messages Change By: Bogdan Irimie Assignee: Florin Dragos 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.344669.1580734421000.10417.1580740140531%40Atlassian.JIRA.
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Trevor Vaughan commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated While I completely agree with Henrik Lindberg's assessment that my patch is completely the wrong way to do things, if this isn't going to get much attention in the near future, could it be implemented just to prevent things from crashing? 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.302978.1554294806000.10398.1580739600291%40Atlassian.JIRA.
Jira (FACT-2343) Facter.to_hash returns a hash with symbol keys, they should be strings
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2343 Facter.to_hash returns a hash with symbol keys, they should be strings Change By: Bogdan Irimie Assignee: Bogdan Irimie 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.344672.1580735946000.10301.1580737080048%40Atlassian.JIRA.
Jira (FACT-2335) Investigate the usage of Facter-NG in Puppet as a gem
Title: Message Title Mihai Buzgau commented on FACT-2335 Re: Investigate the usage of Facter-NG in Puppet as a gem Modules have a dependency to litmus -> litmus has a dependecy to PDK -> PDK has facter locked to ~>2.5.1 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.344214.1580387639000.10290.1580736300038%40Atlassian.JIRA.
Jira (FACT-2343) Facter.to_hash returns a hash with symbol keys, they should be strings
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2343 Facter.to_hash returns a hash with symbol keys, they should be strings Issue Type: Bug Assignee: Unassigned Created: 2020/02/03 5:19 AM Priority: Normal Reporter: Bogdan Irimie 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/pup
Jira (FACT-2342) Add ruby version in gemfile
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2342 Add ruby version in gemfile Issue Type: Task Assignee: Unassigned Created: 2020/02/03 4:55 AM Priority: Normal Reporter: Bogdan Irimie 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.344670.1580734536000.10265.1
Jira (FACT-2341) Investigate weight error messages
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2341 Investigate weight error messages Issue Type: Bug Assignee: Unassigned Created: 2020/02/03 4:53 AM Priority: Normal Reporter: Bogdan Irimie Unable to add resolve nil for fact fqdn: Invalid resolution options [:weight] Unable to add resolve nil for fact domain: Invalid resolution options [:weight] Unable to add resolve nil for fact clientcert: Invalid resolution options [:weight] Unable to add resolve nil for fact ipaddress6: Invalid resolution options [:weight] Unable to add resolve nil for fact networking: Invalid resolution options [:weight] Unable to add resolve nil for fact clientversion: Invalid resolution options [:weight] Unable to add resolve nil for fact environment: Invalid resolution options [:weight] .Unable to add resolve nil for fact hostname: Invalid resolution options [:weight] Unable to add resolve nil for fact fqdn: Invalid resolution options [:weight] Unable to add resolve nil for fact domain: Invalid resolution options [:weight] Unable to add resolve nil for fact clientcert: Invalid resolution options [:weight] Unable to add resolve nil for fact ipaddress6: Invalid resolution options [:weight] Unable to add resolve nil for fact networking: Invalid resolution options [:weight] Unable to add resolve nil for fact clientversion: Invalid resolution options [:weight] Unable to add resolve nil for fact environment: Invalid resolution options [:weight] .Unable to add resolve nil for fact hostname: Invalid resolution options [:weight] Unable to add resolve nil for fact fqdn: Invalid resolution options [:weight] Unable to add resolve nil for fact domain: Invalid resolution options [:weight] Unable to add resolve nil for fact clientcert: Invalid resolution options [:weight] Unable to add resolve nil for fact ipaddress6: Invalid resolution options [:weight] Unable to add resolve nil for fact networking: Invalid resolution options [:weight] Unable to add resolve nil for fact clientversion: Invalid resolution options [:weight] Unable to add resolve nil for fact environment: Invalid resolution options [:weight] .Unable to add resolve nil for fact hostname: Invalid resolution options [:weight] Unable
Jira (FACT-2340) Remove incorrect error messages from facter output on Centos 6
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2340 Remove incorrect error messages from facter output on Centos 6 Issue Type: Task Assignee: Bogdan Irimie Created: 2020/02/03 4:51 AM Priority: Normal Reporter: Bogdan Irimie 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-
Jira (PUP-10263) Make FacterNg available on all platforms
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10263 Make FacterNg available on all platforms Change By: Gheorghe Popescu Sprint: NW - 2020-02-05 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.344653.1580715183000.9935.1580727480119%40Atlassian.JIRA.
Jira (PUP-10263) Make FacterNg available on all platforms
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10263 Make FacterNg available on all platforms Change By: Gheorghe Popescu Story Points: 1 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.344653.1580715183000.9934.1580727480075%40Atlassian.JIRA.
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Marty Ewings updated an issue Puppet / PUP-9602 puppet 6 apply fails if puppet types have been generated Change By: Marty Ewings CS Priority: Needs Priority 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.302978.1554294806000.9914.1580725920279%40Atlassian.JIRA.
Jira (FACT-2323) Extend Facter 4.x API with trace?
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2323 Extend Facter 4.x API with trace? Change By: Oana Tanasoiu Assignee: Oana Tanasoiu 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.344089.1580306221000.9688.1580722140347%40Atlassian.JIRA.
Jira (FACT-2325) Extend Facter 4.x API with debugging
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2325 Extend Facter 4.x API with debugging Change By: Oana Tanasoiu Assignee: Oana Tanasoiu 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.344091.158030628.9691.1580722140483%40Atlassian.JIRA.
Jira (FACT-2309) OS is detected incorrectly on redhat-8-x86_64
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2309 OS is detected incorrectly on redhat-8-x86_64 Change By: Oana Tanasoiu Assignee: Oana Tanasoiu 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.344075.1580301218000.9682.1580721720176%40Atlassian.JIRA.
Jira (FACT-2309) OS is detected incorrectly on redhat-8-x86_64
Title: Message Title Oana Tanasoiu assigned an issue to Unassigned Facter / FACT-2309 OS is detected incorrectly on redhat-8-x86_64 Change By: Oana Tanasoiu Assignee: Oana Tanasoiu 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.344075.1580301218000.9680.1580721720167%40Atlassian.JIRA.
