canonical / canonical/namespace-node-affinity-operator
Charm goes to Active/Idle before workload is active
Open
bug
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The charm will go to Active/Idle before the workload has successfully stood up. This could result in a race condition (charm active before workload active) that resolves itself, but can also hide other issues. If there is a problem with the deployment (ex: the image does not exist and the Pod goes to `ImagePullBackoff`) the charm will still be Active/Idle.
Contributor guide
Assessment
This issue has not been assessed yet.