Overwritten config settings breaks kafka service CLIs.
joerg84 opened this issue · 1 comments
DC/OS 1.10 on OSX
tl;dr Only setting export DCOS_SSL_VERIFY=false
without setting dcos config set core.ssl_verify False
breaks the kafka cli.
I had to set export DCOS_SSL_VERIFY=false (see #1103 for reason).
This confuses the kafka service cli: dcos kafka endpoints broker Unable to read from CA certificate file false # overwritten by environment var DCOS_SSL_VERIFY; config file value: /Users/joergschad/.dcos/clusters/9e500174-57b2-4c91-b445-ef7ee99fcb5a/dcos_ca.crt: open false # overwritten by environment var DCOS_SSL_VERIFY; config file value: /Users/joergschad/.dcos/clusters/9e500174-57b2-4c91-b445-ef7ee99fcb5a/dcos_ca.crt: no such file or directory
According to Nick the service CLI is confused by the debug output
cluster.name joerg-tf654d
core.dcos_acs_token ********
core.dcos_url https://joerg-tf654d-pub-mas-elb-1131462485.us-west-2.elb.amazonaws.com
core.ssl_verify False # overwritten by environment var DCOS_SSL_VERIFY; config file value: /Users/joergschad/.dcos/clusters/9e500174-57b2-4c91-b445-ef7ee99fcb5a/dcos_ca.crt```
After explicitly setting `dcos config set core.ssl_verify False` everything works as expected (i.e., kafka cli command show the broker information).
FYI:This will fix future versions of the SDK services (but not current): mesosphere/dcos-commons#1859