[Bug]: puppetdb service can fail to start after upgrade to OpenVoxDB 8.14.1

[Sharpie]

Is this a critical security issue?

• This is not a security issue.

Describe the Bug

The 8.14.1 release contains a major update to the Jetty component, moving from version 10 to 12. This is accompanied by a change in the /etc/puppetlabs/puppetdb/bootstrap.cfg file that instructs the puppetdb service to load jetty-service instead of the older jetty10-service.

The bootstrap.cfg file is marked as a "configuration file", which means package managers will skip updating it with new content if the file has been modified. If the update is skipped, the old configuration specifying jetty10-service is retained and the puppetdb service fails to start or restart after the upgrade.

When this occurs, the following warning is printed to /var/log/puppetlabs/puppetdb/puppetdb.log:

2026-06-26T16:41:56.598Z WARN  [p.t.bootstrap] Unable to load service 'puppetlabs.trapperkeeper.services.webserver.jetty10-service/jetty10-service' from /etc/puppetlabs/puppetdb/bootstrap.cfg:7

The service start failure can be fixed by editing bootstrap.cfg and replacing jetty10-service with jetty-service:

# diff -u /etc/puppetlabs/puppetdb/bootstrap.cfg*
--- /etc/puppetlabs/puppetdb/bootstrap.cfg      2026-06-26 16:38:50.416748668 +0000
+++ /etc/puppetlabs/puppetdb/bootstrap.cfg.rpmnew       2026-06-24 21:10:12.000000000 +0000
@@ -4,7 +4,7 @@
 #  https://github.com/puppetlabs/trapperkeeper/wiki/Bootstrapping

 # Web Server
-puppetlabs.trapperkeeper.services.webserver.jetty10-service/jetty10-service
+puppetlabs.trapperkeeper.services.webserver.jetty-service/jetty-service

 # Webrouting
 puppetlabs.trapperkeeper.services.webrouting.webrouting-service/webrouting-service

Expected Behavior

Service starts after upgrade, even if bootstrap configuration has been customized.

Steps to Reproduce

1. Set up OpenVox 8 repositories on an EL 8 server:

dnf install -y https://yum.voxpupuli.org/openvox8-release-el-8.noarch.rpm

2. Install the 8.13.0 release of OpenVoxDB:

dnf install openvoxdb-8.13.0-1.el8

3. Modify the bootstrap.cfg file:

echo '# hello, world' >>/etc/puppetlabs/puppetdb/bootstrap.cfg

4. Upgrade OpenVoxDB to the latest version:

dnf upgrade openvoxdb

5. Attempt to start the service:

systemctl start openvoxdb

Environment

Version 8.14.1
Platform any

Additional Context

No response

Relevant log output

[Sharpie]

OpenVox Server/Puppet Server made a change nearly a decade ago to avoid this issue:

• /etc/puppetlabs/puppetserver/bootstrap.cfg is no longer used
• User customization is added to individual .cfg files in the /etc/puppetlabs/puppetserver/services.d/ directory. The package managers ignore this directory by default.
• Required services, with no options or choices, are listed in /opt/puppetlabs/server/apps/puppetserver/config/services.d/bootstrap.cfg. This is not marked as a configuration file, so package managers overwrite it on upgrade.

We should consider implementing the same pattern in OpenVoxDB 9.0.