Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Solved this problem. As embarrassing as this sounds, it was the following configuration error (I found no others):

in /etc/default/etcd, the line:

ETC_INITIAL_CLUSTER='default=http://controller:2380'

was to be changed to match your configuration. Unfortunately, I read that as it was telling me to put:

ETC_INITIAL_CLUSTER='default=http://hpccloud:2380'

Where "hpccloud" was my controller. It actually wants the configuration to say:

ETC_INITIAL_CLUSTER='hpccloud=http://hpccloud:2380'

I suppose I read it wrong, or it actually still does not make sense to me why someone would write a configuration line that way, but whatever, my instance does spawn to completion now... I now have to solve a networking issue as the instance is not accessible, but it is spawning with an IP assigned to it from the dhcp range and it is showing up active.

Thanks for all of the help so far.