-
Notifications
You must be signed in to change notification settings - Fork 124
Update default stack version to 8.6.1 #1118
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
Conversation
🌐 Coverage report
|
/test |
/test |
start_period: 60s | ||
retries: 360 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even using these settings, there are some cases where elastic_agent_is_ready container still has unhealthy status 😞
ERROR: for elastic-agent_is_ready Container "066fd24a8fc6" is unhealthy.
Not sure if at least those will help us to make it a bit better
I've not been able to reproduce it locally to check what it is the output of the healthchecks using docker inspect
/test |
/test |
1 similar comment
/test |
/test |
/test |
/test |
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great! I see that the latest builds run in Jenkins have been successful 💪
Thanks!
if onlyElasticAgentFailed() { | ||
fmt.Println("Elastic Agent failed to start, trying again.") | ||
err = dockerComposeUp(options) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Add also some options to try to reduce flakiness in
elastic-package stack up
: