Deployment Target requiring containers not acquiring them during Health Checks #8621
Assignees
Labels
kind/bug
This issue represents a verified problem we are committed to solving
Comments
scme0
added
the
kind/bug
|
Release Note: Resolved an issue where deployment target health checks would not correctly use specified action containers |
|
🎉 The fix for this issue has been released in:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Severity
Deployed onto several Customer instances, could block customers from deploying to certain targets
Version
2024.1.10065 - 2024.1.2024.1.10283 fixed in 2024.1.10284-hotfix.10558
Latest Version
I could reproduce the problem in the latest build
What happened?
When Octopus Server is trying to execute a health check for deployment targets which require a container on the worker, the health check would fail to acquire the container causing health checks to fail.
Reproduction
Create a Deployment Target like the Kubernetes API target and add a container to the target.
Run the health check, you will see that the logging says that it failed to acquire the container.
Error and Stacktrace
No response
More Information
No response
Workaround
No response
The text was updated successfully, but these errors were encountered: