Running riak-admin wait-for-service riak_kv with a bad node name (i.e. localhost) return:
riak_kv is not up: 
No indication that this is a bad node name. Suggest putting logic in to check node name for cluster membership or ability to ping.
Identified in 1045 during upgrade from 0.14 to 1.1.1 (https://help.basho.com/tickets/1045)
verified this still occurs on master today. I've actually been bit by this working on some automated perf testing. this should be fixed in the next release or two so it will be left open.
@jrwest @bsparrow435 @deanproctor Hrm, since Dean's recent PR #385 was recently withdrawn without merging, what's the New Plan?
@slfritchie @deanproctor opened basho/riak#394 to handle the case where no node name is provided. I agree w/ @evanmcc that handling the invalid node-name should probably be handled here in core. I don't think we have plans for 2.0 (although maybe we will get to it right now its on the "Next Release + 1" milestone)
not happening for 2.0-* but moving to 2.0.1 since I still think this is a good/quick/easy/etc fix.