Comment 7 for bug 1506226

This error means magnum is not able to communicate with the k8s cluster. There could be many reasons:

1. The k8s processes doesn't start properly in the cluster.
2. The k8s processes start properly, but magnum and k8s cluster is disconnected (due to nova, neutron, etc.).
3. Magnum is able to communicate with k8s API server, but not able to pass authentication due to issue on the TLS certificates.

To verify #1, you can ssh to the nova instances and verify k8s is started properly. Reference: https://github.com/kubernetes/kubernetes/wiki/Debugging-FAQ

To verify #3, you can disable TLS and check if it works:

$ magnum baymodel-delete k8sbaymodel # delete the old baymodel
$ magnum baymodel-create --name k8sbaymodel \
                       --image-id fedora-21-atomic-5 \
                       --keypair-id testkey \
                       --external-network-id public \
                       --dns-nameserver 8.8.8.8 \
                       --flavor-id m1.small \
                       --docker-volume-size 5 \
                       --network-driver flannel \
                       --coe kubernetes \
                       --tls-disabled

Then, create a new bay based on the new baymodel.