I will start off by saying I realize deleting Heat-managed resources outside of Heat is not a good thing to be doing. However, it does happen and it used to be okay - the resource was deleted so when you deleted the stack it was basically a noop. Now the stack is stuck in the following state:
| stack_status | DELETE_FAILED |
| stack_status_reason | Resource DELETE failed: NotFound: resources.baremetal_e |
| | nv.resources.openstack_baremetal_servers.resources[0].r |
| | esources.baremetal_server: Unable to find port with |
| | name or id '3fbd424e-3d62-4ea8-9233-3a6beb2c4cdc'
That port was indeed deleted by an external script, so the error is not incorrect. It does cause a problem though in that now I can't do anything with the stack. Delete fails as above, and trying to update to recreate the missing resource isn't allowed either after the deletion has started.
I hacked the code a bit to expose the underlying exception, and it looks like this is happening in the translation framework. I'll attach the traceback to the bug.
Oh, I forgot to mention this is on a devstack install from a few weeks ago. Specifically commit 93a446a9650c9e7 e35a73353840694 ae01e73280 It doesn't look to me like anything has changed since then that would affect this, but I could be wrong.