Closed afeefghannam89 closed 1 year ago
afeefghannam89
commented
1 year ago Check for cluster status with elastic password always fails with full_satck scenarios for Logstash, Kibana and Beats. This happens in the idempotent check phase, while the cluster status is yellow. I raised the retries to 20, but it does not help. For more information see the debug and fix pipelines actions.
On the other hand, this task works fine for elasticsearch pipelines Do you have a solution @widhalmt ?
widhalmt
commented
1 year ago Unfortunately the failing checks are hidden when the linter doesn't run through. I don't know why the cluster stays yellow. I just can assume that there's been a minor problem with the prepare.yml playbooks. Maybe the nodes can't connect and every node only checks it's local instance?
afeefghannam89
commented
1 year ago @widhalmt I have created a new test branch from the actual main branch. I have removed one empty line in every role and pushed to let the pipelines run for all roles. So the prepare.yml and the complete collection code is unchanged and actual. Anyway the same pipelines for logstash and beats fail with the same reason. That means the changes in this PR are not reason why the pipelines fails, see https://github.com/NETWAYS/ansible-collection-elasticstack/actions/runs/4616563045/jobs/8161826518#step:6:1129
Remove the installation of OpenSSL from Elasticsearch role. Fix #138 Rework prapare.yml for all molecule workflows and remove unneeded task to speed up the pipelines little bit.