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.

Sign up for GitHub

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

Jump to bottom

SMF does not go to blocked status when mongo is removed #28

Closed
ghislainbourgeois opened this issue Nov 15, 2023 · 0 comments · Fixed by #29
Closed

SMF does not go to blocked status when mongo is removed #28

ghislainbourgeois opened this issue Nov 15, 2023 · 0 comments · Fixed by #29
Labels
bug Something isn't working

Comments

@ghislainbourgeois
Copy link
Contributor

Describe the bug

Charm does not go to blocked status when mongo is removed.

To Reproduce

  1. Deploy sdcore
  2. juju remove-application mongodb-k8s

Expected behavior

Unit goes to blocked status

Environment

  • Charm / library version (if relevant): latest/edge
  • Juju version (output from juju --version): 3.1.6
  • Cloud Environment: MicroK8s
  • Kubernetes version (output from kubectl version --short): MicroK8s v1.27.7 revision 6101
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: go into blocked status when database relation is removed canonical/sdcore-smf-k8s-operator
1 participant
@ghislainbourgeois