When querying the services API, state running is returned after only 1 jruby instance is ready, not starting. I've never been able to get starting to show. I'm running 31 jruby instances.
Expected Behavior
All the states should be exposed according to the actual state of the service.
Steps to Reproduce
Configure more than 1 jruby instance in the config
Start puppetserver
Query the API while watching the logfile
It will take 1-2 seconds for each jruby instance to start until max instances are reached.
During this time it is expected that state would be starting but running is returned instead.
Environment
Version puppetserver 7.16.0
Platform:
Dockerized Ubuntu 22.04
Custom docker image using deb from apt.puppetlabs.com with openjdk-jre-17-headless
Describe the Bug
According to API docs here https://www.puppet.com/docs/puppet/7/server/status-api/v1/services#get-statusv1services the status should return multiple different states, but it seems only
runningis ever returned.When querying the services API, state
runningis returned after only 1 jruby instance is ready, notstarting. I've never been able to getstartingto show. I'm running 31 jruby instances.Expected Behavior
All the states should be exposed according to the actual state of the service.
Steps to Reproduce
startingbutrunningis returned instead.Environment