A user complaining with the usual 'gatherkeys fails' showed up on IRC the other night and I finally tracked it down to a stray keyring file in /etc/ceph that was present prior to mon create. Because the keyring file was there, ceph-create-keys skips creating a new keyring. And then it can't do the next step because the keyring is wrong. I suspect the fix here is to make mon create complain and fail if there is a keyring already present in /etc/ceph? Maybe with a force flag? The sequences we should consider: - fresh install, creating initial monitors (no conf or keyring should be there) - adding a new mon to an existing cluster. conf might be there, keyring usually won't. but it could be, if they did the 'ceph admin HOST' or whatever it is to push out the keyring and config on that host at some point previously. Probably a check and force option similar to the config will do the trick? sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
