Correct clustered gating job

The cluster gatting job was failing due to memory locking, which is
impossible due to limited resources in the CI environment. This change
disables memory locking in the clustered gate test.

Change-Id: I0a146c41a1b82425539e014b1baee2011d464e05
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This commit is contained in:
Kevin Carter 2018-11-20 10:25:19 -06:00
parent 3f70fc76d9
commit 6797da6b1e
No known key found for this signature in database
GPG Key ID: 9443251A787B9FB3
1 changed files with 2 additions and 4 deletions

View File

@ -27,6 +27,8 @@ all_containers:
address: "{{ ansible_host }}"
netmask: "255.255.255.0"
bridge: "{{ hostvars[physical_host]['ansible_default_ipv4']['alias'] }}"
# CI nodes havee limited resources, locking the memory is impossible.
elastic_memory_lock: false
children:
elastic-logstash:
@ -43,10 +45,6 @@ all_containers:
ansible_host: 172.29.236.102
ansible_user: root
elastic3:
ansible_host: 172.29.236.103
ansible_user: root
kibana:
hosts:
kibana0: