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

31 lines
1.2 KiB
Groovy
Raw Normal View History

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 {
Build: Rework shadow plugin configuration (#32409) This reworks how we configure the `shadow` plugin in the build. The major change is that we no longer bundle dependencies in the `compile` configuration, instead we bundle dependencies in the new `bundle` configuration. This feels more right because it is a little more "opt in" rather than "opt out" and the name of the `bundle` configuration is a little more obvious. As an neat side effect of this, the `runtimeElements` configuration used when one project depends on another now contains exactly the dependencies needed to run the project so you no longer need to reference projects that use the shadow plugin like this: ``` testCompile project(path: ':client:rest-high-level', configuration: 'shadow') ``` You can instead use the much more normal: ``` testCompile "org.elasticsearch.client:elasticsearch-rest-high-level-client:${version}" ```
2018-08-21 20:03:28 -04:00
testCompile "org.elasticsearch.plugin:x-pack-core:${version}"
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
}
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
integTestCluster {
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
numNodes = 2
clusterName = 'multi-node'
Rename ILM, ILM endpoints and drop _xpack (#32564) This commit does the following: - renames index-lifecycle plugin to ilm - modifies the endpoints to ilm instead of index_lifecycle - drops _xpack from the endpoints - drops a few duplicate endpoints
2018-08-02 13:05:11 -04:00
setting 'xpack.ilm.enabled', 'false'
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.monitoring.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'
Build: Split distributions into oss and default This commit makes x-pack a module and adds it to the default distrubtion. It also creates distributions for zip, tar, deb and rpm which contain only oss code.
2018-02-23 11:03:17 -05:00
extraConfigFile 'roles.yml', 'roles.yml'
Rename users This commit renames users to elasticsearch-users.
2018-04-11 11:36:12 -04:00
setupCommand 'setup-test-user', 'bin/elasticsearch-users', 'useradd', 'test-user', '-p', 'x-pack-test-password', '-r', 'test'
setupCommand 'setup-super-user', 'bin/elasticsearch-users', 'useradd', 'super-user', '-p', 'x-pack-super-password', '-r', 'superuser'
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
waitCondition = { node, ant ->
File tmpFile = new File(node.cwd, 'wait.success')
ant.get(src: "http://${node.httpUri()}/_cluster/health?wait_for_nodes=>=${numNodes}&wait_for_status=yellow",
dest: tmpFile.toString(),
username: 'super-user',
password: 'x-pack-super-password',
ignoreerrors: true,
retries: 10)
return tmpFile.exists()
}
}