Bug 874983
Summary: | Misleading error message when server returns 503 error | ||
---|---|---|---|
Product: | [Retired] Zanata | Reporter: | Pravin Satpute <psatpute> |
Component: | Component-Maven, Usability | Assignee: | Patrick Huang <pahuang> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Zanata-QA Mailling List <zanata-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | dchen, pahuang, sflaniga, sshedmak, zanata-bugs |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | 3.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 3.2-SNAPSHOT (20131127-0039) | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-02-18 06:46:07 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
Pravin Satpute
2012-11-09 09:15:42 UTC
The said error could be reproduced with zanata-maven-plugin version 1.7.5 . Also, the error is similar to following RH bz: Bug 805775 - confusing error: failed to upload glossary due to wrong an API key Please run with the '-e' option and give us the stack trace. Thanks. $ mvn -e zanata:push -Dzanata.pushType=both working with mentioned command. Thanks. Actually -e just tells Maven to generate longer error messages, it wouldn't fix anything. I think this happened because the server was down, the Apache proxy returned 503, and the client produced an unhelpful error message. I think we still need to improve the error handling in the case of a 503. Should we mark this ON_QA now? VERIFIED with Zanata version 3.2-SNAPSHOT (20131127-0039) zanata-maven-plugin:3.1.2 |