Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cryptic error message during build-publish #1743

Open
s-geiger-si opened this issue Oct 29, 2022 · 6 comments
Open

Cryptic error message during build-publish #1743

s-geiger-si opened this issue Oct 29, 2022 · 6 comments
Labels
bug Something isn't working stale An outdated issue lacking engagement

Comments

@s-geiger-si
Copy link

Describe the bug

I just tried to publish a build using the JFrog CLI and received an error message together with a 403 error that contained a cryptic token %!F(MISSING) in the message that makes the message difficult to understand.

Current behavior

{
  "errors": [
    {
      "status": 403,
      "message": "User [REDACTED] is not permitted to deploy 'group%!F(MISSING)project/0-12345678901234.json' into 'artifactory-build-info:group%!F(MISSING)project/0-12345678901234.json'."
    }
  ]
}

The token %!F(MISSING) is what I do not understand. I would either expect a litteral / (slash) or a ansi escaped %2F instead of this cryptic character sequence.

The strangely formatted message makes it difficult to understand if my user is really missing a certain permission, or if there is something wrong with the path of the build info that I am using.

Reproduction steps

Invoke with:

./jfrog rt build-publish --build-url=[REDACTED] '--env-include=*CI_*' '--env-exclude=*KEY*;*PASSWORD*;*TOKEN*;*SECRET*' group/project 0

Expected behavior

I would expect to see an error message which does not include the cryptic character sequence %!F(MISSING) and instead shows the actual url to which I am trying to deploy either with a literal / or an ansi escaped %2F

JFrog CLI version

2.28.1

Operating system type and version

Ubuntu 22.04

JFrog Artifactory version

7.41.7

JFrog Xray version

@s-geiger-si s-geiger-si added the bug Something isn't working label Oct 29, 2022
@s-geiger-si
Copy link
Author

FYI, seems other go projects such as eksctl have had similar issues. For reference see eksctl-io/eksctl#836 (comment)

@s-geiger-si
Copy link
Author

I have recently also seen this message in another context:

10:15:33 [Info] Deploying build info...
10:15:33 [Error] server response: 403 Forbidden
{
  "errors": [
    {
      "status": 403,
      "message": "Not enough permissions to delete/overwrite artifact 'artifactory-build-info:<MODULE_NAME>%!F(MISSING)<MODULE_NAME>/123456789-12345678901234.json' (user: 'xxxxxxxx' needs DELETE permission)."
    }
  ]
}

@lharzenetter
Copy link

I had the same issue. You need to grant your user/group permissions to builds:

image

Select the Include All Builds in the By Pattern if you do not have any builds yet.

Next, give your user/group the permission to deploy builds:

image

@eric-gonzalez-tfs
Copy link

@s-geiger-si - Were you able to figure this out? I am encountering the same issue with the JFrog CLI.

Copy link
Contributor

This issue has been marked as stale due to 6 months of inactivity. As part of our effort to address every issue properly, please feel free to remove the stale label or keep this issue active by leaving a comment. Otherwise, it will be closed in 7 days

@github-actions github-actions bot added the stale An outdated issue lacking engagement label Feb 28, 2025
@s-geiger-si
Copy link
Author

@eric-gonzalez-tfs The answer from @lharzenetter describes the solution well, its a permission issue with the build metadata and the user is lacking the delete permission for builds, but the issue here for me is the cryptic error message that inserts a this strange %!F(MISSING) sequence and can cause the impression that something else might be causing the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale An outdated issue lacking engagement
Projects
None yet
Development

No branches or pull requests

3 participants