When creating a job that launches multiple slaves openstack plugin always fails to clean up the slaves after successfully destroying the 1st slave and throws the following error message:

FATAL: ActionResponse

{success=false, fault=Instance 3a58a111-5c89-4a20-aadb-abd94a36b1f8 could not be found., code=404}
jenkins.plugins.openstack.compute.internal.Openstack$ActionFailed: ActionResponse{success=false, fault=Instance 3a58a111-5c89-4a20-aadb-abd94a36b1f8 could not be found., code=404}

It appears that the 1st slave created actually successfully gets destroyed despite the error message above stating that it failed and then the job fails and does not continue to destroy the remaining slaves.

To reproduce:

1. create new freestyle job
2. configure openstack instance configuration
3. configure at least 2 instances to be launched as part of the job
4. run job

Ideally the job should always destroy all slaves that was started by the job and should not keep slaves around event if failure occurred to destroy one of the slaves.