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

Stuck on BlockedStatus even after maximum_retention_size config option changed to valid #560

Closed
sed-i opened this issue Jan 17, 2024 · 0 comments · Fixed by #561
Closed

Comments

@sed-i
Copy link
Contributor

sed-i commented Jan 17, 2024

If we provide an invalid string to maximum_retention_size, the charm goes into BlockedStatus. Then, when it is corrected, there is no code in place to revert the status back to active.

try:
ratio = self._percent_string_to_ratio(config.get("maximum_retention_size", ""))
except ValueError as e:
logger.warning(e)
self.unit.status = BlockedStatus(f"Invalid retention size: {e}")

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 a pull request may close this issue.

1 participant