Skip to content

Conversation

@jsoriano
Copy link
Member

@jsoriano jsoriano commented Jan 26, 2023

Add also some options to try to reduce flakiness in elastic-package stack up:

  • retry limits have been replaced with start periods.
  • fleet-server and elastic-agent healthcheck retries have been increased.
  • if docker-compose up fails and elastic-agent container is the one failing, retry once, this may happen if it tries to enroll while fleet-server is being restarted or reconfigured.

@jsoriano jsoriano requested a review from a team January 26, 2023 17:41
@jsoriano jsoriano self-assigned this Jan 26, 2023
@elasticmachine
Copy link
Collaborator

elasticmachine commented Jan 26, 2023

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-01-29T22:27:49.589+0000

  • Duration: 33 min 4 sec

Test stats 🧪

Test Results
Failed 0
Passed 878
Skipped 0
Total 878

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@elasticmachine
Copy link
Collaborator

elasticmachine commented Jan 26, 2023

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (35/35) 💚
Files 65.909% (87/132) 👍
Classes 61.376% (116/189) 👍
Methods 48.582% (394/811) 👎 -0.06
Lines 31.645% (3555/11234) 👎 -0.062
Conditionals 100.0% (0/0) 💚

@jsoriano
Copy link
Member Author

/test

@jsoriano
Copy link
Member Author

/test

Comment on lines 128 to 129
start_period: 60s
retries: 360
Copy link
Contributor

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

@jsoriano
Copy link
Member Author

/test

@jsoriano
Copy link
Member Author

/test

1 similar comment
@jsoriano
Copy link
Member Author

/test

@jsoriano
Copy link
Member Author

/test

@jsoriano jsoriano marked this pull request as draft January 28, 2023 19:01
@jsoriano
Copy link
Member Author

/test

@jsoriano
Copy link
Member Author

/test

@jsoriano jsoriano marked this pull request as ready for review January 29, 2023 22:26
@jsoriano
Copy link
Member Author

/test

@jsoriano jsoriano requested a review from mrodm January 29, 2023 22:28
Copy link
Contributor

@mrodm mrodm left a 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!

Comment on lines +69 to +72
if onlyElasticAgentFailed() {
fmt.Println("Elastic Agent failed to start, trying again.")
err = dockerComposeUp(options)
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants