Updated SRU template. ** Description changed:
[ Impact ] - * The puppetdb autopkgtests fail on noble after the FTBFS bug [1] is fixed. + + * This bug-report was originally reported puppetdb dep8 test failures on noble + after [1] was fixed. Many tests fail with HTTP 403 errors on + autopkgtest.ubuntu.com infra due to the presence of a squid proxy. + + Currently puppetdb also FTBFS on resolute, questing, plucky and noble, due + to build-time test failures. The failing tests fall into two of the + (upstream-defined) categories: + a. Command tests - related to a reported issue [2] in newer postgresql versions + b. Service tests - related to expiration of certificates + + While questing (like resolute) is affected by category (a) and noble by + category (b), plucky is affected by both (a) and (b). + + This SRU includes three changes: + A) Fix command test failures (category a), by simply disabling the upstream tests. + B) Fix service test failures (category b), by introducing a Ruby script that generates certificates during a build. + C) Fix the HTTP 403 autopkgtest failures by adding the (local) URLs to the no_proxy environment variable. + + All the current stable releases need change (C). Additionally, questing needs (A)and plucky needs (B). [ Test Plan ] + + * The build-time test failures can be reproduced at will during a + package build. The dep8 failures can be reproduced by requesting tests + on autopkgtest.ubuntu.com. The dep8 test failures DO NOT reproduce + locally using "autopkgtest" unless a proxy is configured. + + [ Where problems could occur ] + + * Change (A) disables a total of 3 upstream sub-tests under the "Command + Tests" category. Disabling tests could let new regressions escape + uncaught. It is a medium-risk change. + + [ Other Info ] + + * Further, the premise for (A) is [2] an open upstream issue. Though the + exception stack match what we observe (on rr, qq and pp), it is reported + for libpostgresql-jdbc-java 42.7.7 with postgresql 17.5-1. Plucky has + libpostgresql-jdbc-java 42.7.5 and postgresql 17.6. + + + [1] https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2069384 + [2] https://github.com/pgjdbc/pgjdbc/issues/3757 + + + + ------------ Previous template ------------ + Impact + * The puppetdb autopkgtests fail on noble after the FTBFS bug [1] is fixed. + + Test Plan * Running autopkgtests on noble reveals the failure. - [ Where problems could occur ] + Where problems could occur Currently, both tests under debian/test fail on oracular [2]. ==== autopkgtest [00:30:43]: @@@@@@@@@@@@@@@@@@@@ summary standalone FAIL stderr: warn: JDK 21.0.4-ea is neither tested nor supported. Please use JDK 17 with-puppetserver FAIL non-zero exit status 1 ==== Test "standalone" fails because of Java 21 usage warning appears on stderr. Test "with-puppetserver" is an integration test of puppetdb and puppetserver. The latter has been updated to 8.4.1-1 on noble. Use of a custom format named PSON was completely abandoned in puppetserver 8. Any use of PSON in puppetdb 7 on noble needs to be removed. - [ Other Info ] + Other Info PuppetDB 7.X is compatible with PuppetServer 8.X [3] - [1] https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2069384 - [2] https://paste.ubuntu.com/p/74h3nmKpXB/ - [3] https://www.puppet.com/docs/puppetdb/7/overview.html + -------------------------------------------------------------------------------- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072516 Title: puppetdb dep8 tests fail for multiple reasons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2072516/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
