Rancher metadata / confd issue with creating logstash from catalog

Rancher 1.x
1

On creating the log stash stack from the catalog, the logstash-indexer config sidekick fails to create the config with confd + rancher-metadata service. There appears to be an error with TLS, any suggestions for getting this working?

May 10, 2016 11:56:10 AM EDT2016-05-10T15:56:10Z logstash_logstash-indexer_logstash-indexer-config_1 /confd[1]: INFO Starting confd
May 10, 2016 11:56:10 AM EDT2016-05-10T15:56:10Z logstash_logstash-indexer_logstash-indexer-config_1 /confd[1]: INFO Backend nodes set to
May 10, 2016 11:56:10 AM EDT2016-05-10T15:56:10Z logstash_logstash-indexer_logstash-indexer-config_1 /confd[1]: INFO Using Rancher Metadata URL: http://rancher-metadata
May 10, 2016 11:56:41 AM EDT2016-05-10T15:56:41Z logstash_logstash-indexer_logstash-indexer-config_1 /confd[1]: FATAL Get https://rancher-metadata/: x509: failed to load system roots and no roots provided

2

This still happens on the latest release of rancher 1.1.0-dev4

3

There was a log-driver issue that was fixed in the most recent release v1.1.0-dev5. This affects catalog entries as it uses rancher-compose to launch services into Rancher.Could you try with the most recent release?

4

Just tried on dev-5 and it seems to be doing the same thing with the collector service vs. the indexer from before.

logstash_logstash-collector_logstash-collector-config_1 /confd[1]: INFO Backend set to rancher 6/21/2016 3:01:41 PM2016-06-21T19:01:41Z logstash_logstash-collector_logstash-collector-config_1 /confd[1]: INFO Starting confd 6/21/2016 3:01:41 PM2016-06-21T19:01:41Z logstash_logstash-collector_logstash-collector-config_1 /confd[1]: INFO Backend nodes set to 6/21/2016 3:01:41 PM2016-06-21T19:01:41Z logstash_logstash-collector_logstash-collector-config_1 /confd[1]: INFO Using Rancher Metadata URL: http://rancher-metadata 6/21/2016 3:02:12 PM2016-06-21T19:02:12Z logstash_logstash-collector_logstash-collector-config_1 /confd[1]: FATAL Get https://rancher-metadata/: x509: failed to load system roots and no roots provided

5

Can’t reproduce the issue with build-master v0.20.0 the logstash-indexer didn’t give this error, and the elk stack seems to be working correctly, the next version will be 1.1.0 which should be out shortly.