AM deleted from Expedient results in stopped VMs from another AM

[CarolinaFernandez]

Removing the CNIT-Catania VT AM resulted in the VMs from our VT AM located at the first slice in the first project being stopped.

A similar behavior was reported almost a month ago by a user whose VMs (in our VT AM too) where hard-stopped. Seems to be the same case...

Is this what we want?

As seen in the log:

    Success 2013-07-05  08:23:16    Action hardStop on VM <VM_5> succeed
    Success 2013-07-05  08:23:15    Action hardStop on VM <VM_4> succeed
    Success 2013-07-05  08:23:15    Action hardStop on VM <VM_3> succeed
    Success 2013-07-05  08:23:14    Action hardStop on VM <VM_2> succeed
    Success 2013-07-05  08:23:14    Action hardStop on VM <VM_1> succeed
    Success 2013-07-05  08:23:11    Successfully deleted aggregate <AM_1>

PS: Also might be useful to look into the aggregate model class. When this is to be removed from either a project or a slice, if a NoReverseMatch exception is raised, the slice is stopped.