Skip to content

Do not lose provisioning gateways on restart #2887

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

Merged
merged 1 commit into from
Jul 10, 2025

Conversation

jvstme
Copy link
Collaborator

@jvstme jvstme commented Jul 9, 2025

  • Split processing submitted and provisioning gateways into two processing iterations, so that gateways in the provisioning status are not lost on server restarts.
  • Decrease the number of gateway configuration attempts during server startup. 50 attempts are only necessary when processing a provisioning gateway.
  • Make gateway processing logging more comprehensive and consistent.

Fixes #2677

- Split processing `submitted` and `provisioning`
  gateways into two processing iterations, so that
  gateways in the `provisioning` status are not
  lost on server restarts.
- Decrease the number of gateway configuration
  attempts during server startup. 50 attempts are
  only necessary when processing a provisioning
  gateway.
- Make gateway processing logging more
  comprehensive and consistent.
@jvstme jvstme requested a review from r4victor July 9, 2025 21:08
@jvstme jvstme merged commit a8ee724 into master Jul 10, 2025
26 checks passed
@jvstme jvstme deleted the issue_2677_refactor_gateway_provisioning branch July 10, 2025 08:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Gateway stuck in provisioning after server restart
2 participants