Enhance Installation class for Packaging Tests with multiple nodes #79688
Labels
:Delivery/Build
Build or test infrastructure
Team:Delivery
Meta label for Delivery team
>test
Issues or PRs that are addressing/adding tests
Comments
jkakavas
added
>test
|
Pinging @elastic/es-delivery (Team:Delivery) |
pugnascotia
added a commit
that referenced
this issue
Jan 13, 2022
Fixes #81999. Change `EnrollmentProcessTests` and the testing infrastructure so that `ServerUtils` can send requests to the correct local port. This is also a step towards addressing #79688. Also change the Iron Bank build to that it works on aarch64. This isn't currently a supported configuration, but it's useful for testing.
pugnascotia
added a commit
that referenced
this issue
Jan 13, 2022
Fixes #81999. Change `EnrollmentProcessTests` and the testing infrastructure so that `ServerUtils` can send requests to the correct local port. This is also a step towards addressing #79688. Also change the Iron Bank build to that it works on aarch64. This isn't currently a supported configuration, but it's useful for testing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now that we have packaging tests that start multiple nodes ( EnrollmentProcessTests ) some of the assumptions that we are making throughout the packaging test code base are no longer valid.
For instance, the
http/transportports that the installation are bound to is not necessarily9200/9300, but could be9201/9301etc depending on how many nodes we start. What's more, the assumption that we have a singleinstallationin the entire PackagingTestCase class is not strictly valid any more.I added an ugly hack for this in #77718 so I'm opening this issue here to discuss about more robust and maintainable solutions
The text was updated successfully, but these errors were encountered: