I should note that I was able to slowly work through this by adding
the node to the engine, running the hosted-engine setup from within
the node, removing the node via the Engine's WebUI when the conflict
messages comes up, letting the hosted-engine setup finish. That's not
ideal, but it works.
Thanks for the advice. This DID work, however I've run into more
(what I consider to be) ridiculousness:
Running hosted-engine setup seems to assume that the host is not
already added to the Default cluster (had an issue previously where I
had renamed the cluster and that messed up the
On Tue, Feb 23, 2016 at 8:29 PM, Christopher Young
> So, I have what I think should be a standard setup where I have
> dedicated NICs (to be bonded via LACP for storage) and well are NICs
> for various VLANS, etc.
> As typical, I have the main
So, I have what I think should be a standard setup where I have
dedicated NICs (to be bonded via LACP for storage) and well are NICs
for various VLANS, etc.
As typical, I have the main system interfaces for the usual system IPs
(em1 in this case).
A couple of observations (and a "chicken and the
Mail list logo