Fixed running ansible in check mode (#701)

Co-authored-by: Julien Mailleret <[email protected]>
elastic · Jun 29, 2020 · d99c0c8 · d99c0c8
1 parent 9539712
commit d99c0c8
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/tasks/elasticsearch-RedHat.yml b/tasks/elasticsearch-RedHat.yml
@@ -45,7 +45,7 @@
     state: present
     update_cache: yes
     allow_downgrade: '{{ allow_downgrade }}'
-  when: es_use_repository
+  when: es_use_repository and not ansible_check_mode
   register: redhat_elasticsearch_install_from_repo
   notify: restart elasticsearch
   until: redhat_elasticsearch_install_from_repo.rc == 0

diff --git a/tasks/elasticsearch-parameters.yml b/tasks/elasticsearch-parameters.yml
@@ -12,7 +12,7 @@
 #If the user attempts to lock memory they must specify a heap size
 - name: fail when heap size is not specified when using memory lock
   fail: msg="If locking memory with bootstrap.memory_lock a heap size must be specified"
-  when: es_config['bootstrap.memory_lock'] is defined and es_config['bootstrap.memory_lock'] == True and es_heap_size is not defined
+  when: es_config['bootstrap.memory_lock'] is defined and es_config['bootstrap.memory_lock'] == True and es_heap_size is not defined and not ansible_check_mode
 
 #Check if working with security we have an es_api_basic_auth_username and es_api_basic_auth_username - otherwise any http calls wont work
 - name: fail when api credentials are not declared when using security