Issue Summary

When a synchronized mirror is deleted, it registers itself again on the primary Bitbucket instance. If the system admin authorizes the mirror after it is restarted, the mirror doesn't go to SYNCHRONIZED state.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Setup and primary and mirror instance.
2. Add one or more projects and wait for mirror to be in SYNCHRONIZED state
3. Delete the mirror from primary.
4. Wait for new registration request to show up on the mirror admin page on primary.
5. Leave the mirror in "AWAITING AUTHORIZATION" state and restart it.
6. After the mirror is started, authorize the mirror and observe the mirror status.

Expected Results

Mirror should go to SYNCHRONIZED state after few minutes.

Actual Results

Mirror remains in AUTHORIZED state.

Workaround

Restart the mirror and then it will go to SYNCHRONIZED state