jfrog / jfrog-azure-devops-extension

Apache License 2.0
47 stars 63 forks source link

Artifactory Generic Upload failing #233

Open vin4git opened 3 years ago

vin4git commented 3 years ago

Artifact Generic Upload task is failing due to the below errors:

[Error] [Thread 2] Artifactory response: 404 Not Found { "status": 404, "message": "Checksum deploy failed. No existing file with SHA-1: " } ] } [Error] Failed uploading 1 artifacts. { "status": "failure", "totals": { "success": 0, "failure": 1 } }

[error]Error: Command failed: C:\hostedtoolcache\windows\jfrog\1.42.3\x64\jfrog.exe rt u --url="https://XXX/artifactory" --spec="D:\a\1\s\uploadSpec1614784091734.json" --user= --password=

Expected behavior Artifact should upload without any errors.

Versions

eyalbe4 commented 3 years ago

@vin4git, Does this error repeat itself every time you try uploading the file or did this happen once? Does this happen with a specific file only or with any file you try to upload? To test and troubleshoot this, you can also run this upload command outside of Azure DevOps with jfrog-cli directly.

vin4git commented 3 years ago

@eyalbe4 , It is happening every time the build is triggered and for any file trying to upload.

I just tried downloading the artifact in local (using curl) and it is working fine.

eyalbe4 commented 3 years ago

Thanks @vin4git. In that case, my guess is that this is a permission issue for the user attempting to upload the file, although the error message received is not the best. Here's what I suggest: Try uploading a file using jfrog-cli with the same user from the terminal. I would expect you get the same result. Then see if this user has deploy permissions on Artifactory. If it doesn't, add the permission and try again. Feel free to share your findings here.

vin4git commented 3 years ago

@eyalbe4 ,

That's the "admin" user and have full privileges. :)

eyalbe4 commented 3 years ago

I see @vin4git. Will you be able to verify that you're uploading the file to a local repository? If you are, then I suggest you open a ticket to JFrog Support, so that we can help you pinpoint and solve the problem.

eyalbe4 commented 3 years ago

@vin4git - were you able to get this issue resolved?