Zen2: Move all mixed-version REST tests to Zen2#36398
Zen2: Move all mixed-version REST tests to Zen2#36398ywelsch merged 8 commits intoelastic:masterfrom
Conversation
|
Pinging @elastic/es-distributed |
DaveCTurner
left a comment
There was a problem hiding this comment.
Mostly looks good but I have questioned a couple of the test fixes.
...a/org/elasticsearch/action/admin/cluster/bootstrap/TransportBootstrapClusterActionTests.java
Outdated
Show resolved
Hide resolved
...org/elasticsearch/action/admin/cluster/bootstrap/TransportGetDiscoveredNodesActionTests.java
Outdated
Show resolved
Hide resolved
|
packaging-sample failed because auto-bootstrapping failed with and ci-2 failed because of #36380 For the first failure, I've tried making that action internal and see if that helps. |
| public class GetDiscoveredNodesAction extends Action<GetDiscoveredNodesResponse> { | ||
| public static final GetDiscoveredNodesAction INSTANCE = new GetDiscoveredNodesAction(); | ||
| public static final String NAME = "cluster:monitor/discovered_nodes"; | ||
| public static final String NAME = "internal:cluster/discovered_nodes"; |
There was a problem hiding this comment.
I don't immediately see how this would help, since both are covered by system privileges:
Not that it won't help, just that I don't understand the mechanism.
Review comments addressed, but need another look
|
@DaveCTurner I figured out the issue: The system context which we set in |
|
Good catch. Does a similar issue exist in |
|
Just after a quick look. it seems to me that |
Moves all remaining (rolling-upgrade and mixed-version) REST tests to use Zen2. To avoid adding extra configuration, it relies on Zen2 being set as the default discovery type. This required a few smaller changes in other tests. I've removed AzureMinimumMasterNodesTests which tests Zen1 functionality and dates from a time where host providers were not configurable and each cloud plugin had its own
discovery.type, subclassing the ZenDiscovery class. I've also adapted a few tests which were unnecessarily addingaddTestZenDiscovery = falsefor the same legacy reasons. Finally, this also moves the unconfigured-node-name REST test to Zen2, testing the auto-bootstrapping functionality in development mode when no discovery configuration is provided.