We have a cluster repository service bound to two machines. bin/repository clusterize ran successfully, but subsequent attempts to browse the repository in Diffusion result in errors like this:

ERR-CONDUIT-CORE: Repository "rREPO" exists on more than one device, but no device has any repository version information. Phabricator can not guess which copy of the existing data is authoritative. Remove all but one device from service to mark the remaining device as the authority.

/config/cluster/repositories indicates that the repository "has an ambiguous leader."

Following the instructions in the error (disabling the bindings to all but one device, then reenabling) resolved the error.

From the Diviner documentation and the command's help text, it's not clear to me whether clusterizing is supposed to work cleanly with multiple devices. If it's not supposed to work, I'd expect the clusterize command to result in an error instead, or emit a warning that further operations are necessary.