Inconsistent (sub)request states in the RMS

[atsareg]

Inconsistent (sub)request states in the RMS

[fstagni]

Just to clarify a bit. What I see now in the LHCb certification, based on DIRAC v5r13p6 is the following:

mysql> SELECT RequestID, Status FROM Requests WHERE JobID = 482285;
+-----------+--------+
| RequestID | Status |
+-----------+--------+
| 35305 | Done |
+-----------+--------+

mysql> SELECT SubRequestID, Status, RequestType, Operation FROM SubRequests WHERE RequestID = 35305;
+--------------+----------+-------------+----------------------+
| SubRequestID | Status | RequestType | Operation |
+--------------+----------+-------------+----------------------+
| 175991 | Done | transfer | replicateAndRegister |
| 175992 | Assigned | removal | replicaRemoval |
+--------------+----------+-------------+----------------------+

so, the Request is in status "Done" even if one of its subRequest is not "Done". If the replicaRemoval operation does not complete, after a week the RequestManagement/RequestCleaningAgent will clean the requests in "Done" state.

[atsareg]

This problem should be solved in v6r2 with the new request agents. If it will show up again, it will be reopen