Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/status/v1/services only reports running status #2844

Open
Alives opened this issue Apr 3, 2024 · 0 comments
Open

/status/v1/services only reports running status #2844

Alives opened this issue Apr 3, 2024 · 0 comments
Labels

Comments

@Alives
Copy link

Alives commented Apr 3, 2024

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 running is ever returned.

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

  1. Configure more than 1 jruby instance in the config
  2. Start puppetserver
  3. Query the API while watching the logfile
  4. It will take 1-2 seconds for each jruby instance to start until max instances are reached.
  5. 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant