honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/x-pack/qa/multi-node/build.gradle

20 lines
637 B
Groovy
Raw Normal View History

Backport: convert x pack qa (#43763) * Revert "Revert "Test clusters: convert x-pack qa tests (#43283)" (#43549)" This reverts commit 8d9a971259bdbcec0a68894c64bea61675f05ada. * Fix failing test
2019-07-01 03:38:56 -04:00
apply plugin: 'elasticsearch.testclusters'
Replace global checkpoint sync test This commit replaces the REST test that the global checkpoint sync action runs successfully as a privileged user. The test needs to be replaced because it has a small race condition. Namely, the check that the post-operation global checkpoint sync was successful could run before the sync finishes running. To address this, we replace the REST test with a test where we have a little more control and can assert busy to avoid this race from failing the test. Relates elastic/x-pack-elasticsearch#2749 Original commit: elastic/x-pack-elasticsearch@ea585b843cdcc6a0509e720061056ea241b125c7
2017-10-13 10:05:59 -04:00
apply plugin: 'elasticsearch.standalone-rest-test'
apply plugin: 'elasticsearch.rest-test'
Add test for global checkpoint sync with security After a write operation on an index, a post-operation global checkpoint sync fires. Previously, this action fired on the same user as executed the write action. If the user did not have priviledges for this action, the global checkpoint sync would fail. With an upstream change in core, this action now fires as the system user. This commit adds a test that create a user that has minimal write permissions on an index, but none that would imply it could execute the global checkpoint sync. This then serves as a test that the upstream change to fire the global checkpoint sync as the system user is correct. This test must run as a mulit-node test so that a replica is a assigned so that the global checkpoint sync fires in the first place. This test does indeed fail without the upstream change, and passes with it. Relates elastic/x-pack-elasticsearch#2744 Original commit: elastic/x-pack-elasticsearch@bf7e77175690a1306da004711ce51b41a14c155f
2017-10-12 09:19:17 -04:00
dependencies {
Remove xpack dependencies from qa rest modules (#41134) (7.x backport) (#41202) This commit removes xpack dependencies of many xpack qa modules. (for some qa modules this will require some more work) The reason behind this change is that qa rest modules should not depend on the x-pack plugins, because the plugins are an implementation detail and the tests should only know about the rest interface and qa cluster that is being tested. Also some qa modules rely on xpack plugins and hlrc (which is a valid dependency for rest qa tests) creates a cyclic dependency and this is something that we should avoid. Also Eclipse can't handle gradle cyclic dependencies (see #41064). * don't copy xpack-core's plugin property into the test resource of qa modules. Otherwise installing security manager fails, because it tries to find the XPackPlugin class.
2019-04-15 13:14:43 -04:00
testCompile project(':x-pack:qa')
Add test for global checkpoint sync with security After a write operation on an index, a post-operation global checkpoint sync fires. Previously, this action fired on the same user as executed the write action. If the user did not have priviledges for this action, the global checkpoint sync would fail. With an upstream change in core, this action now fires as the system user. This commit adds a test that create a user that has minimal write permissions on an index, but none that would imply it could execute the global checkpoint sync. This then serves as a test that the upstream change to fire the global checkpoint sync as the system user is correct. This test must run as a mulit-node test so that a replica is a assigned so that the global checkpoint sync fires in the first place. This test does indeed fail without the upstream change, and passes with it. Relates elastic/x-pack-elasticsearch#2744 Original commit: elastic/x-pack-elasticsearch@bf7e77175690a1306da004711ce51b41a14c155f
2017-10-12 09:19:17 -04:00
}
Backport: convert x pack qa (#43763) * Revert "Revert "Test clusters: convert x-pack qa tests (#43283)" (#43549)" This reverts commit 8d9a971259bdbcec0a68894c64bea61675f05ada. * Fix failing test
2019-07-01 03:38:56 -04:00
testClusters.integTest {
Convert testclusters to use distro download plugin (#44253) (#44362) Test clusters currently has its own set of logic for dealing with finding different versions of Elasticsearch, downloading them, and extracting them. This commit converts testclusters to use the DistributionDownloadPlugin.
2019-07-15 20:53:05 -04:00
testDistribution = 'DEFAULT'
Backport: convert x pack qa (#43763) * Revert "Revert "Test clusters: convert x-pack qa tests (#43283)" (#43549)" This reverts commit 8d9a971259bdbcec0a68894c64bea61675f05ada. * Fix failing test
2019-07-01 03:38:56 -04:00
numberOfNodes = 2
Disable security for trial licenses by default (elastic/x-pack-elasticsearch#4120) This change disables security for trial licenses unless security is explicitly enabled in the settings. This is done to facilitate users getting started and not having to deal with some of the complexities involved in getting security configured. In order to do this and avoid disabling security for existing users that have gold or platinum licenses, we have to disable security after cluster formation so that the license can be retrieved. relates elastic/x-pack-elasticsearch#4078 Original commit: elastic/x-pack-elasticsearch@96bdb889fc74d4871c43df71354a21549cc53a3e
2018-03-21 23:09:44 -04:00
setting 'xpack.security.enabled', 'true'
Add test for global checkpoint sync with security After a write operation on an index, a post-operation global checkpoint sync fires. Previously, this action fired on the same user as executed the write action. If the user did not have priviledges for this action, the global checkpoint sync would fail. With an upstream change in core, this action now fires as the system user. This commit adds a test that create a user that has minimal write permissions on an index, but none that would imply it could execute the global checkpoint sync. This then serves as a test that the upstream change to fire the global checkpoint sync as the system user is correct. This test must run as a mulit-node test so that a replica is a assigned so that the global checkpoint sync fires in the first place. This test does indeed fail without the upstream change, and passes with it. Relates elastic/x-pack-elasticsearch#2744 Original commit: elastic/x-pack-elasticsearch@bf7e77175690a1306da004711ce51b41a14c155f
2017-10-12 09:19:17 -04:00
setting 'xpack.watcher.enabled', 'false'
setting 'xpack.ml.enabled', 'false'
Test: use trial license in qa tests with security QA tests that use security need to use a trial license instead of a basic license. Basic licenses do not enable security so these tests are not running in the expected configuration. This can also lead to issues that seem completely unrelated such as authentication failures right after cluster formation. The authentication failure right after cluster formation happens since a request makes it past the authentication license checks and the request starts the authentication process. During authentication the cluster forms and the license is updated to a basic license, which disables all realms. The request that is being authenticated then tries to iterate over the realms, but the realms are empty and the request cannot be authenticated. This results in a authentication failure even though the credentials provided are correct. Closes #30306
2018-05-03 12:33:08 -04:00
setting 'xpack.license.self_generated.type', 'trial'
Backport: convert x pack qa (#43763) * Revert "Revert "Test clusters: convert x-pack qa tests (#43283)" (#43549)" This reverts commit 8d9a971259bdbcec0a68894c64bea61675f05ada. * Fix failing test
2019-07-01 03:38:56 -04:00
extraConfigFile 'roles.yml', file('roles.yml')
user username: "test-user", password: "x-pack-test-password", role: "test"
user username: "super-user", password: "x-pack-super-password"
Add test for global checkpoint sync with security After a write operation on an index, a post-operation global checkpoint sync fires. Previously, this action fired on the same user as executed the write action. If the user did not have priviledges for this action, the global checkpoint sync would fail. With an upstream change in core, this action now fires as the system user. This commit adds a test that create a user that has minimal write permissions on an index, but none that would imply it could execute the global checkpoint sync. This then serves as a test that the upstream change to fire the global checkpoint sync as the system user is correct. This test must run as a mulit-node test so that a replica is a assigned so that the global checkpoint sync fires in the first place. This test does indeed fail without the upstream change, and passes with it. Relates elastic/x-pack-elasticsearch#2744 Original commit: elastic/x-pack-elasticsearch@bf7e77175690a1306da004711ce51b41a14c155f
2017-10-12 09:19:17 -04:00
}