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

Package fails re-reconcile on upgrade #649

Closed
rjferguson21 opened this issue Aug 7, 2024 · 0 comments · Fixed by #650
Closed

Package fails re-reconcile on upgrade #649

rjferguson21 opened this issue Aug 7, 2024 · 0 comments · Fixed by #650
Assignees
Labels
possible-bug Something may not be working
Milestone

Comments

@rjferguson21
Copy link
Contributor

rjferguson21 commented Aug 7, 2024

Environment

App version: 0.25.0
Kubernetes distro being used: k3d
Other: uds-k3d-demo

We've seen intermittent issues where on upgrades Packages fail to reconcile because Keycloak is temporarily unresponsive.

Steps to reproduce

  1. Install uds-k3d-demo
  2. Delete the keycloak pod
  3. Immediately delete the pepr-watcher pod

Expected result

The operator would re-reconcile all Packages, and they would end up in a status=Ready state.

Actual Result

The operator tries to reconcile the Packages, triggering an HTTP request to Keycloak as part of the reconciliation process for packages that leverage SSO. This request fails and the operator immediately retries 5 times in short succession and subsequently sets the Package to status=Failed.

Visual Proof (screenshots, videos, text, etc)

2024-08-06_09-08-1722955694

Severity/Priority

Critical

Additional Context

We debated a couple of solutions:

  • Adding a retry mechanism in the operator, specially for the Keycloak requests.
  • Adding a check to ensure Keycloak is healthy prior to making requests.
  • Adding a global operator delay on retries.
@rjferguson21 rjferguson21 added the possible-bug Something may not be working label Aug 7, 2024
@mjnagel mjnagel added this to the 0.26.0 milestone Aug 7, 2024
@mjnagel mjnagel modified the milestones: 0.26.0, 0.25.2 Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible-bug Something may not be working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants