-
Notifications
You must be signed in to change notification settings - Fork 97
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
Update cluster by ansible 2.13 to 2.17.1 #170
Comments
This same problem i have when im trying to update from 2.13 to 2.14
|
Sorry i click by mistake close :) |
Im trying to check in logs enabled debug logs
|
Adding @saravanan30erd to take a look. |
Usually jar hell happens due to jar conflicts on same lib and removing the old lib can solve these issues sometimes. But what I didn't understand is why its not the problem until now and after 2.13 we are getting this issues. @dzaczek Can you please give it a try by removing the old lib version and start the service?
|
@saravanan30erd after remove
|
@dzaczek looks like conflict continues on other libs. Could you please try to remove all the files in this folder |
I addded top playbbok remove ../lib dir and after tahat problem with plugins
|
then i tied remove plugins and lib
Ok so propably i will do update manually :) |
I prepared a workaround script to handle each node manually and preserve the config and data directories.
And also converted this same script into an Ansible playbook.
|
Describe the bug
Im trying to use ansible playbook to update opensearch 2.13 to to 2.17.1 on ubuntu 22.04 LTS
2.13 was installed also by playbook few month ago .
Playbook failing during restart open search waiting , geeting timeout.
To Reproduce
Steps to reproduce the behavior:
Install version 2.13 by ansible playbook (iac_enable: false)
Install version 2.17.1 by ansible playbook (iac_enable: true, copy_custom_security_configs: true)
)
Expected behavior
Working able to start cluster
LOGS
gc log:
Host/Environment (please complete the following information):
·
The text was updated successfully, but these errors were encountered: