Changed volume retention - current running job is waiting to create a new volume

[Jeff Lawrence]

It seems like this should work automatically or with just a command or two, but here is the situation:

Jobs have been running fine but I recently introduced a new client and so my Full pool has been filling up.  I am using file based backup so  I have been increasing the max volumes in the pool and if a job is hung, waiting for a volume, I then create and mount a new volume and the job will continue.  But I have now reached the point were I have more volumes than I would like so I don't want to keep increasing the max volumes for that pool.  So I decided to decrease the volume retention instead.  So I edited dir/pool/full.conf, then performed a reload, and updated "all volumes from pool".  In the webui it now shows that I indeed have "Expired" volumes, so I would think that it would reuse one of those for the running job, however the storage-daemon still reports 

Device is BLOCKED waiting to create a volume for:

Pool: Full

Media type: File1

If I create a new volume and mount it, it will continue, but like I said I don't want to do that, I want it to use one of the now expired volumes instead.

Also, if I cancel the job and then re-run it, it happily grabs one of the "Expired" volumes.  So it's just when it encounters that there are no volumes available while the job is running and I make them available by decreasing the volume retentions.

So it seems like the workflow is 

1) check for appendable volume, but if none then

2) check for expired volume, but if none then

3) create new volume, but if pool already at max volumes then

4) wait for the user to create and label a new volume

Hopefully I have made my explanation clear, so the question is, how do you get it from being stuck at step 4 to find an expired volume and continue with the job? 

Thank you!