When starting work for a graceful takeover, I was careless when picking the new master database. I chose a host that was behind an intermediate master. So I had replication like so:

M
  > R1
    > R2
  > R3
...

I ran orchestrator-client -c relocate-replicas -i M -d R2. After I did this we ended up with

M

R1 <> R2
        > R3
        ...

This is obviously not what I was wanting.

Can we please put in a safeguard to save me from myself. If the -d host is not a direct descendant of the -i host, this command should fail without taking any action.