[Swift-devel] proxy expiration whilst jobs are running through GRAM4

[Ben Clifford]

If the user proxy expires whilst a job is running from Swift through 
GRAM4, that job will hang in the swift runtime.

This is reproducable by running a 5 minutes sleep job with a 2 minute 
proxy.

I think (though I haven't looked at gram server side logs to check) what 
is happening here is that status notifications cannot be delivered because 
of the expired credential; and the job then sits forever waiting for the 
notification that will never come.

If so, then probably it would be better to refresh the credential if 
possible; and fail the job if we know that we cannot get notifications 
because the local proxy has expired.

--