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

Problem with the states Sablier fetches for the deployments #468

Open
geosaglio opened this issue Dec 5, 2024 · 2 comments
Open

Problem with the states Sablier fetches for the deployments #468

geosaglio opened this issue Dec 5, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@geosaglio
Copy link

Describe the bug
Sablier sometimes returns the wrong state for the deployments of the group. In the theme that is sent to the user, all the deployments are marked as ready, but you get stuck on the page. This is due to the fact that some deployments that are in the group don't change their replica count from 0 to 1. Manually changing the replica count temporarily fixes the issue, but it still happens quite often.

Context

  • Sablier version: 1.8.1
  • Provider: kubernetes v1.30.5]
  • Reverse proxy: traefik v2.11.4
  • Sablier is running inside a container

Expected behavior

The deployments in a group should all either be up (at least 1 replica) or down (0 replicas) but that isn't the case.

Additional context
The timeout for the group is 2 hours, but there is a curl that is sent every 2 hours, could this be the cause of the unpredictable behavior?
I also get logs where a deployment is starting and stopping at the same time from sablier.
Capture d’écran 2024-12-05 à 17 34 44
Capture d’écran 2024-12-05 à 17 34 52

@geosaglio geosaglio added the bug Something isn't working label Dec 5, 2024
@acouvreur
Copy link
Member

This might happen when the session duration is invalid, are you sure that the session_duration is long enough ? An invalid value may result in 0s session duration which would shut it down instantly

@geosaglio
Copy link
Author

Hey!
Thanks for your quick reply, the session_duration is set to 2 hours and seems to be valid as I'm getting these logs at the same time:
Capture d’écran 2024-12-09 à 11 59 57

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants