401 Error when a specific user submits a commit

bryan.parsons September 13, 2017

A user is trying to commit a change into Bitbucket, the project has the Yet Another Commit Checker plugin enabled. The commit fails and the error points towards Jira rejecting the request. The Jira incident referenced is valid and the user has permission to the repository they are trying to commit to. 

Here is the error message

m-*****:loco-spark-ergc *****$ git push 
Counting objects: 11, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (11/11), 1.31 KiB | 0 bytes/s, done.
Total 11 (delta 4), reused 0 (delta 0)
remote: 
remote: (c).-.(c) (c).-.(c) (c).-.(c) (c).-.(c) (c).-.(c) 
remote: / ._. \ / ._. \ / ._. \ / ._. \ / ._. \ 
remote: __( Y )/__ __( Y )/__ __( Y )/__ __( Y )/__ __( Y )/__
remote: (_.-/'-'-._)(_.-/'-'-._)(_.-/'-'-._)(_.-/'-'-._)(_.-/'-'-._)
remote: || E || || R || || R || || O || || R ||
remote: _.' `-' '._ _.' `-' '._ _.' `-' '._ _.' `-' '._ _.' `-' '.
remote: (.-./`-'\.-.)(.-./`-`\.-.)(.-./`-`\.-.)(.-./`-'\.-.)(.-./`-`\.-.)
remote: `-' `-' `-' `-' `-' `-' `-' `-' `-' `-' 
remote: 
remote: 
remote: Push rejected.
remote: 
remote: refs/heads/feature/LOC-2113-remove-toseq-from-home-parcel-lookup: d862d8140f0bb10394fde395bff43b9f3a5628ea: Unable to validate JIRA issues due to an unexpected exception. Please see stack trace in logs.
remote: 
To https://bitbucket.*********.com/scm/loc/loco-spark-ergc.git\\ ! [remote rejected] feature/LOC-2113-remove-toseq-from-home-parcel-lookup -> feature/LOC-2113-remove-toseq-from-home-parcel-lookup (pre-receive hook declined)
error: failed to push some refs to 'https://*****@bitbucket.********.com/scm/loc/loco-spark-ergc.git'
m-*****:loco-spark-ergc *****$

According to Atlassian "Based on Stack Trace Analysis, the plugin is trying to call JIRA on a way that an unauthorized (401) error code is returned."

1 answer

0 votes
martin.pantaleon October 13, 2022

any solution to this issue?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events