Comment 7 for bug 1825034

I would have been in favor of the last option of hard deleting the fake instance record via direct DB access upon completion of the online data migration, but it doesn't help in the case where multiple runs of the migration are needed.

With that, so far it seems like option 2 (exclude the fake uuid server) is the least bad in that it catches all cases.

I don't like option 1 at all because I agree, I don't think we should show the fake instance in the API.