srmMv returns SRM_SUCCESS instead of SRM_FILE_BUSY

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • 1.11.2
    • Affects Version/s: 1.11.1
    • Component/s: None
    • Security Level: Public (Visbile by non-authn users.)
    • None

      As you can see from the SRMv.2.2 specification, srmMv has to retrieve SRM_FILE_BUSY when on fromSurl there's an active PtP (or PtG), but this doesn't happen:

      Move file with active ptg                                             | FAIL |
      '============================================================
      Sending Mv request to: omii004-vm02.cnaf.infn.it:8444
      Before execute:
      Afer execute:
      Request Status Code 0
      Poll Flag 0
      ============================================================
      Request status:
        statusCode="SRM_SUCCESS"(0)
        explanation="SURL moved with success"
      ============================================================
      SRM Response:
      ============================================================' does not contain 'SRM_FILE_BUSY'
      Move file with active ptp                                             | FAIL |
      '============================================================
      Sending Mv request to: omii004-vm02.cnaf.infn.it:8444
      Before execute:
      Afer execute:
      Request Status Code 0
      Poll Flag 0
      ============================================================
      Request status:
        statusCode="SRM_SUCCESS"(0)
        explanation="SURL moved with success"
      ============================================================
      SRM Response:
      ============================================================' does not contain 'SRM_FILE_BUSY'
      

      Test done with storm-testsuite and clientSRM.
      User is allowed to transfer a resource with a ptp (or ptg) active and this shouldn't happen.

            Assignee:
            Enrico Vianello
            Reporter:
            Enrico Vianello
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: