-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Skip HealthNodeUpgradeIT for some rolling upgrades #119698
Skip HealthNodeUpgradeIT for some rolling upgrades #119698
Conversation
This excludes the `HealthNodeUpgradeIT` test for the rolling upgrade tests which use a cluster with a mix of either 8.5.3 or 8.6.2 nodes, which serve the health endpoint at `_internal/_health`, and 8.last nodes, which serve it at `_health_report`. There is no sensible and reliable way to test the endpoint in such clusters. Closes elastic#118157 Closes elastic#118158
Pinging @elastic/es-data-management (Team:Data Management) |
N.B. Before this PR, the test appears to have been muted entirely. After this PR, it is muted only for these two BWC rolling upgrade versions. So this does add some missing coverage. |
I was looking into the test:
And I am wondering, instead of adding these explicit mutes, shouldn't we just use |
Yeah, I think that should work. (It actually crossed my mind, I don't remember why I went this route.) I'll give it a go. |
…ig based on version numbers
Yeah, that works, and avoids hard-coding the version numbers in question. I've verified that the assertion does run and passes for |
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.
LGTM! Thanks for fixing this!
This excludes the
HealthNodeUpgradeIT
test for the rolling upgrade tests which use a cluster with a mix of either 8.5.3 or 8.6.2 nodes, which serve the health endpoint at_internal/_health
, and 8.last nodes, which serve it at_health_report
. There is no sensible and reliable way to test the endpoint in such clusters.Closes #118157
Closes #118158