Comment 2 for bug 1455158

The service-destory command will eventually also destroy the machine on which it is hosted. That's why the machines does go away. When the destroy machine is run immediately after the service destroy, the service may still at that point be recorded as belonging to the machine (albeit likely in a dying state). So we need to either make the destroy machine a no-op (if practical) or improve/change the message printed under such circmstances.