Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Elasticsearch module functions should pass hosts and profile to index_exists() #41162

Closed
onlyanegg opened this issue May 10, 2017 · 1 comment
Labels
Bug broken, incorrect, or confusing behavior Execution-Module P2 Priority 2 RIoT Relates to integration with cloud providers, hypervisors, API-based services, etc. severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Milestone

Comments

@onlyanegg
Copy link
Contributor

The Elasticsearch index_delete execution module is broken when passing a profile in through the arguments. It fails with Exception: Could not connect to Elasticsearch host/ cluster ['127.0.0.1:9200'], is it unhealthy?.
The index_delete() method calls the index_exists() method without passing hosts and profile causing _get_instance() to fail when attempting to ping the ES node.

Setup

delete__index:
   module.run:
     - name: elasticsearch.index_delete
     - index: index_name
     - profile:
         hosts:
           - 'https://{{ user }}:{{ passwd}}@{{ host }}:9243'
@Ch3LL
Copy link
Contributor

Ch3LL commented May 10, 2017

@onlyanegg thanks for the PR! Since this PR seems to resolve the issue I will close the issue but please let us know if there is an issue with the PR and the issue needs to be re-opened. Thanks once again.

@Ch3LL Ch3LL closed this as completed May 10, 2017
@Ch3LL Ch3LL added Bug broken, incorrect, or confusing behavior Execution-Module severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around P2 Priority 2 RIoT Relates to integration with cloud providers, hypervisors, API-based services, etc. labels May 10, 2017
@Ch3LL Ch3LL added this to the Approved milestone May 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior Execution-Module P2 Priority 2 RIoT Relates to integration with cloud providers, hypervisors, API-based services, etc. severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Projects
None yet
Development

No branches or pull requests

2 participants