Comment 1 for bug 1389602

I disagree with the premise that it doesn't make sense to allow an Admin to delete a node that is owned by a user. The problem with releasing first is that releasing the node powers the node off, and that breaks at least one existing customer's use case. I think it's always a useful option to delete a node at any time without having any affect on the node itself, and the issue here is just one of needing to make the admin aware that the node is allocated to a user.

I think the better fix here would be to remove the restriction on deleting the node the Allocated state, and make the warning clearer about what's going on.