Ah, my bad. I originally looked at --deregister-sc options and tried
both host and IP with what appeared to be success (but really was doing
nothing), filed the bug, and then tried --deregister-cluster IP,
thinking it would obey the same option...
Fixing description to reflect that this is a doc
Thierry,
It looks as if this may be a documentation bug: --deregister-cluster and
--deregister-sc takes the 'name' of the cluster, instead of the 'host'
of the component. I just tested with using the cluster name in both
cases, and de-registration is working. However, there are a few issues:
