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

Unlock layer when locked by a runner that does not exist anymore #238

Open
LucasMrqes opened this issue Feb 6, 2024 · 1 comment
Open
Labels
planned planned in a future release
Milestone

Comments

@LucasMrqes
Copy link
Collaborator

LucasMrqes commented Feb 6, 2024

For unknown reasons, it happens that Burrito locks a layer and never unlocks it (probably because a pod was killed due to a spot instance reclaim). That causes all the next runs to fail, as the layer is locked.
To prevent this behavior, we could implement a way to unlock the layer before starting a plan / apply operation only if the following conditions are met:

  • The layer was locked by a Burrito run
  • The pod that locked the layer is not running anymore
@blblbly blblbly added this to the V0.5.0 milestone Mar 18, 2024
@blblbly blblbly added the planned planned in a future release label Mar 18, 2024
@LucasMrqes
Copy link
Collaborator Author

LucasMrqes commented Apr 24, 2024

Furthermore, show in the UI when a layer is locked, that could be useful if somebody (or an automated process) left a lock on a layer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
planned planned in a future release
Projects
None yet
Development

No branches or pull requests

2 participants