Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1148644

Summary: "[ERROR] Operation failed: Error status 401 Unauthorized returned" when pusing the unsupported locale
Product: [Retired] Zanata Reporter: Ding-Yi Chen <dchen>
Component: Component-MavenAssignee: Damian Jansen <djansen>
Status: CLOSED DUPLICATE QA Contact: Zanata-QA Mailling List <zanata-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5CC: zanata-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-02 03:46:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ding-Yi Chen 2014-10-02 02:21:34 UTC
Description of problem:
maintainer without admin role cannot push the translations.

Version-Release number of selected component (if applicable):
Zanata 3.5.0-SNAPSHOT (git-jenkins-zanata-server-github-pull-requests-2120) 

How reproducible:
Always

Steps to Reproduce:
1. Login as a non-admin user
2. Create a project and a version
3. Push the source and translation with following command:
mvn -e -B zanata:push -Dzanata.pushType=both

Actual results:
[==   ][ERROR] Operation failed: Error status 401 Unauthorized returned

    To retry from the last document, please set the following option(s):

        -Dzanata.fromDoc="About_Fedora"


Expected results:
Push successfully.

Additional info:

Comment 1 Ding-Yi Chen 2014-10-02 03:46:44 UTC
It turns out that the locale I was pushing is not supported by the server.

And it seems like a duplicate of Bug 1064093.

I modify the title into 

"[ERROR] Operation failed: Error status 401 Unauthorized returned" when pusing the unsupported locale

So it will be easier for user that encounter the error message.

*** This bug has been marked as a duplicate of bug 1064093 ***