Closed ckauf closed 6 years ago
Any workaround?
I downgraded my Rancher Cluster to 1.6.14 as described in the section "Important - Upgrade" that can be found here. Unfortunately I do not know enough about the rancher-compose format to fix this, yet.
I fixed this by tweaking a few things on the latest version of elasticsearch in my company published public catalog: https://github.com/INTLFCStone/Rancher-Catalog
Take a look see @krisanalfa @ckauf
Same issue for version 6.2.3
+1 on the issue. still there on 6.2.3
+1 is there a fix or workaround ??
+1
Hi all,
issue is related to #10563 and merged PR #143 included at rancher v1.6.15. It avoid the use same sidekick for distinct services, like es-storage
is defined at es-cluster catalog package.
The solution is redefine storage sidekick es-storage
to single storage sidekick for every es-cluster service, es-master-storage
, es-data-storage
and es-client-storage
. Created and merged PR https://github.com/rancher/community-catalog/pull/789 that address it.
es-cluster versions should be filtered correctly for rancher version. 5.5.1-rancher2
and 6.2.3-rancher2
would be deployed at rancher v1.6.15 and higher.
Feel free to reopen if still have issues.
Hi *,
when trying to deploy the ES community template 5.5.1-rancher1 (and also 5.4.0-rancher1 and 5.4.2-rancher1) I get the following error:
I guess this is the problem in the compose file:
I am running this software stack:
I have another rancher cluster where the same template can be deployed just fine. Software Versions:
I've checked the changelog, but could not find any hints what may explain this issue. Is there anything I can add?
Regards, Chris