Who found the bug? jplindquist Where was the bug found?
- System: Open Source Puppet Server with PuppetDB
- Version: CentOS 7, PostgreSQL 14
- Operating system(s): CentOS 7
- Puppet version: 7.15
What is malfunctioning? Unable to upgrade PuppetDB from 7.9.2-1.el7 7.10.0-1.el7 due to error on the read database
2022-04-13 13:20:29.295 MST [25657] ERROR: cannot set transaction read-write mode during recovery |
2022-04-13 13:20:29.295 MST [25657] STATEMENT: set transaction read write |
It seems to be coming from here (https://github.com/puppetlabs/puppetdb/compare/7.9.2...7.10.0#diff-2c460cab69fb9759dca82e8ddcb35006c25939e621c2fdbcd9fe97be96e7692fR651). I'm no Clojure expert, but I'm wondering if that when read-only? is correct when it should not be setting read write on a read only replica. I've downgraded back to 7.9 in the meantime to restore service, but we're unable to update past this for the time being. What does success look like? Successfully upgrading to the latest PuppetDB 7.10+ How will success be validated? yum upgrade puppetdb && systemctl restart puppetdb without failure or logged errors on the database server Should anyone be contacted after this is fixed? jplindquist |
