Comment 4 for bug 1825034

I don't really have many good ideas on how to handle this.

We could create the fake instance with a fake flavor but (a) we don't really want to be showing this fake instance in the API and (b) we could fail to lazy-load some other field and then this is a whack-a-mole issue.

We could specifically exclude showing this server with a fake uuid in the API code but that's also pretty gross (albeit something we could eventually remove).

We could hard delete the soft deleted fake instance record if fill_virtual_interface_list is run again and there is nothing else to migrate. There is no hard-delete API for the instance in Stein like this though: https://review.openstack.org/#/c/570202/ (but maybe we could just use the DB API directly).

Other ideas?