Yaml errors in keystone-policy config not surfaced to the user

[Narinder Gupta]

after change in config for keystone policy getting error yaml to json conversionreactive/kubernetes_master.py:2266:generate_keystone_configmap
2019-11-01 17:01:27 INFO juju-log Executing ['kubectl', '--kubeconfig=/root/.kube/config', 'apply', '-f', '/root/cdk/keystone/keystone-policy.yaml']
2019-11-01 17:01:27 DEBUG config-changed error: error parsing /root/cdk/keystone/keystone-policy.yaml: error converting YAML to JSON: yaml: line 2: mapping values are not allowed in this context

[Narinder Gupta (narindergupta)]

knobby: i think this is real culprit 2019-11-01 08:27:07 INFO juju-log etcd:23: Executing ['kubectl', '--kubeconfig=/root/.kube/config', 'apply', '-f', '/root/cdk/keystone/keystone-policy.yaml']
(01:40:05 PM) narinderguptahome: 2019-11-01 08:27:13 DEBUG etcd-relation-joined error: unable to recognize "/root/cdk/keystone/keystone-policy.yaml": Get https://10.137.11.30:6443/api?timeout=32s: dial tcp 10.137.11.30:6443: connect: no route to host
(01:40:05 PM) narinderguptahome: 2019-11-01 08:27:13 DEBUG juju-log etcd:23: tracer: set flag keystone.credentials.configured
(01:40:05 PM) narinderguptahome: 2019-11-01 08:27:13 INFO juju-log etcd:23: Invoking reactive handler: reactive/hacluster.py:42:configure_hacluster
(01:40:33 PM) narinderguptahome: it configures once but does not check return status

[Narinder Gupta (narindergupta)]

This issue cuase me not have keystone authorization worked also no ceph volume was created. So manual workaround was to change the config after the deployment.

[George Kraft (cynerva)]

PR: https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/68