[RTFACT-16416] "201 created" is returned even when Artifactory cannot reach the filestore (Not _pre) Created: 13/Apr/18  Updated: 10/Feb/19  Resolved: 19/Nov/18

Status: Resolved
Project: Artifactory Binary Repository
Component/s: Filestore
Affects Version/s: None
Fix Version/s: 6.6.0

Type: Bug Priority: Normal
Reporter: Patrick Russell Assignee: Yoaz Menda (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Trigger
triggered RTFACT-18467 False "Failed to move file from _pre ... Resolved
triggered RTFACT-18486 upload followed by cancel to HA trigg... Resolved
Assigned QA: Barak Hacham
Sprint: Leap 35

 Description   

If Artifactory has a non-local filestore system (Such as NFS), as well as a local cache for the _pre folder, losing connection to the non-local filestore causes incorrect success messages to be sent on deployment.

Steps to reproduce:

  1. On a regular Artifactory installation, disable write access on the 2 character subfolders within the standard $ARTIFACTORY_HOME/data/filestore directory. This must be done for the uploaded file's folder.
    chmod 000 9c
  2. Deploy a file to Artifactory as normal
    curl -uadmin:password -T foo.txt http://localhost:8081/artifactory/testRepo
  3. Observe the "201 created" message, and note the filestore is still empty:

ls -R filestore/
filestore/:
7d 9c _pre

filestore/7d:

filestore/9c:

filestore/_pre:

dbRecord2057601553899952181.bin 



 Comments   
Comment by Yoaz Menda (Inactive) [ 18/Oct/18 ]

For QA:
Besides making sure that OK status is not returned to the user, please also verify that after the fix, there are no leaks in the _pre folder as well as the failed artifact didn't make it's way to the database.

Generated at Sun Jan 19 11:20:30 UTC 2020 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.