Introduce a "failed" state for resource allocation.
If a background resource allocation fails, we put the lease in the "failed" state instead of destroying it. There were some ripple effects, specifically, the lease_daemon now checks for "failed" leases and send messages to us at the same frequency as for "unapproved" leases. The correct response here is almost certainly to destroy the lease, though you can put it back in the "unapproved" state (via modlease) and try to approve it to see what happened. Also add background mode to approvelease since it can do time consuming resource allocation. Nit: cleanup logfiles used in backgroud operation.
Showing with 143 additions and 36 deletions