Closed saravanan30erd closed 2 years ago
/review @peterzhuamazon
Hi @saravanan30erd this one probably will take some time as we are currently in the process of 1.2.0 release. I will probably start reviewing next week.
Thanks.
@peterzhuamazon any updates?
@peterzhuamazon any possibility to check in this week?
Very sorry @saravanan30erd I spent most of my time on 1.2.0 and it finally gets out last week.
I will definitely test this week and could you look into #15 as well?
Again, very sorry for the delay and I will test and reply results.
Thanks.
Interesting bug, os1 node I did not get a clean one, I just manually delete /usr/share/opensearch and it didnt recreate the directory and results in
fatal: [os1]: FAILED! => {"changed": false, "checksum": "910e2cbdc3648ada4609703321200d3a32223f17", "msg": "Destination directory /usr/share/opensearch/config does not exist"}
I am not fully familiar with Ansible but is there a cleanup task you can create so people can safely uninstall older version of opensearch if they need to?
Not able to start the process: errors_multinode_ansible.log
TASK [centos7/opensearch : Wait for opensearch to startup] *****************************************************************************************************************************************************************************************************************************************************************
fatal: [os2]: FAILED! => {"changed": false, "elapsed": 300, "msg": "Timeout when waiting for 0.0.0.0:9200"}
fatal: [os4]: FAILED! => {"changed": false, "elapsed": 300, "msg": "Timeout when waiting for 0.0.0.0:9200"}
fatal: [os3]: FAILED! => {"changed": false, "elapsed": 300, "msg": "Timeout when waiting for 0.0.0.0:9200"}
fatal: [os1]: FAILED! => {"changed": false, "elapsed": 300, "msg": "Timeout when waiting for 0.0.0.0:9200"}
fatal: [os5]: FAILED! => {"changed": false, "elapsed": 300, "msg": "Timeout when waiting for 0.0.0.0:9200"}
PLAY RECAP *****************************************************************************************************************************************************************************************************************************************************************************************************************
os1 : ok=21 changed=11 unreachable=0 failed=1 skipped=13 rescued=0 ignored=0
os2 : ok=16 changed=5 unreachable=0 failed=1 skipped=7 rescued=0 ignored=0
os3 : ok=16 changed=5 unreachable=0 failed=1 skipped=7 rescued=0 ignored=0
os4 : ok=16 changed=5 unreachable=0 failed=1 skipped=7 rescued=0 ignored=0
os5 : ok=16 changed=5 unreachable=0 failed=1 skipped=7 rescued=0 ignored=0
Are you using opensearch
user to start the process?
Interesting bug, os1 node I did not get a clean one, I just manually delete /usr/share/opensearch and it didnt recreate the directory and results
@peterzhuamazon Installation using RPM packages(via yum, etc..) will have proper cleanup steps. But here Opensearch doesn't have RPM, .deb packages yet. so I think we need to do proper cleanup (all the related files).
I am not fully familiar with Ansible but is there a cleanup task you can create so people can safely uninstall older version of opensearch if they need to?
Yeah, we can do this. I will create tasks for cleanup.
As of now, its better to do the installation on fresh nodes. I think we can have a call to close this PR. Let me know your availability so we can have a session.
Interesting bug, os1 node I did not get a clean one, I just manually delete /usr/share/opensearch and it didnt recreate the directory and results
@peterzhuamazon Installation using RPM packages(via yum, etc..) will have proper cleanup steps. But here Opensearch doesn't have RPM, .deb packages yet. so I think we need to do proper cleanup (all the related files).
I am not fully familiar with Ansible but is there a cleanup task you can create so people can safely uninstall older version of opensearch if they need to?
Yeah, we can do this. I will create tasks for cleanup.
As of now, its better to do the installation on fresh nodes. I think we can have a call to close this PR. Let me know your availability so we can have a session.
Sent email. Thanks.
After calling @saravanan30erd we are able to get it run
One issue is that on local machine where we run the ansible-playbook command will then create a temporary/tmp/opensearch-nodecerts
folder to host all the certs and configs. Ansible will skip these copies if a previous old folder with the same name exist.
@saravanan30erd will send a new commit to fix it.
Thanks.
@peterzhuamazon pushed the fix for cleanup.
Description
Until now this playbook supports only single node opensearch installation, I am adding the feature to support multi-node cluster installation.
Check List