[RTFACT-16072]  Restored file from trash-can prevent it from resolving a file from virtual repo Created: 09/Mar/18  Updated: 18/Nov/18

Status: Open
Project: Artifactory Binary Repository
Component/s: Trash Can
Affects Version/s: 5.4.5, 5.9.0
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: David Shin Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relationship
relates to RTFACT-14085 Nuget repository is not re indexed af... Resolved

 Description   

Restored file from trash-can prevent it from resolving a file from virtual repo

Steps to produce

1. create each local (maven) and virtual (maven) repository which aggregate local repository

2. upload a file x.pom (A byte) to local repo and then delete it. which means it goes to trash-can

3. At this time, upload a file x.pom (B byte) to local repo (it should be different size and same file name)

4. download x.pom (B byte) from virtual repo.

5. restore x.pom (A byte) from trash-can to local repo, which means overwrite previous x.pom (B byte) in local repo. so now x.pom (A byte) exist in local repo.

6. try to download x.pom (A byte) from virtual repo, however, in result, we get x.pom (B byte) problematically.

In order to resolve this issue, as a workaround, if we zap cache on virtual repository in step 5, and then try to download it again, we should get it x.pom (A byte) which is in local repository.



 Comments   
Comment by Atlassian Build Team [ 07/Jun/18 ]

In our case, I believe the scenario is:

1. the artifact was pulled from a remote repository

2. We add a local repository that contains artifat of the same gav(But different content) into the virutal

3. Artifactory still serve the artifact from the remote repo.

Generated at Tue Dec 10 09:38:06 UTC 2019 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.