subnet&network delete API errors on failed VM creation

Created by: garloff

Due to a cloud config change (flavor name cleanup), the JumpHost VM creation would fail (on PCO and gxscs). The script correctly reports this and then starts the cleanup process. Volume and Port for the JH are properly removed and then the already created Loadbalancer is deleted. This fails, as the LB is still in PENDING_CREATE. The script retries a few times, but the LB is not in ACTIVE (or ERROR) yet, so this is as futile as the the first LB deletion attempt. The polling to wait for the LB to vanish does not succeed and when it times out, the LB is still there. The subsequent attempt to delete the subnet and net with the still existing LB does not succeed, resulting in further failed API calls.