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

Charm sets status from init instead of relying on CollectStatus event #173

Closed
dariofaccin opened this issue Apr 24, 2024 · 0 comments · Fixed by #174
Closed

Charm sets status from init instead of relying on CollectStatus event #173

dariofaccin opened this issue Apr 24, 2024 · 0 comments · Fixed by #174
Labels
bug Something isn't working

Comments

@dariofaccin
Copy link
Contributor

Bug Description

During charm __init__, the validation of config is performed: if any of the options is invalid, the charm will set the status to Blocked without relying on the CollectStatus event callback.

To Reproduce

  1. Navigate to src/charm.py, line 110
  2. Unit status should not be handled here

Environment

Juju version (output from juju --version): 3.4.2-genericlinux-amd64
Cloud Environment: MicroK8s v1.28.7 revision 6532

Relevant log output

No relevant log is required.

Additional context

No response
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: handle charm status only from CollectStatus event callback canonical/sdcore-upf-k8s-operator
1 participant
@dariofaccin