Bug 1032906
| Summary: | [origin_node_331]The application is not started after deploying an invalid binary file by artifact_url | |||
|---|---|---|---|---|
| Product: | OpenShift Online | Reporter: | chunchen <chunchen> | |
| Component: | Image | Assignee: | Dan Mace <dmace> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 2.x | CC: | agoldste, dmace, wsun | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1033768 (view as bug list) | Environment: | ||
| Last Closed: | 2014-01-24 03:33:59 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1033768 | |||
|
Description
chunchen
2013-11-21 08:45:52 UTC
https://github.com/openshift/origin-server/pull/4220 Fixed the error reporting. The state of the application is not something we can control in this case due to the deployments/builds being non-transactional (as a design decision). Moving this ON_QA for the improved error handling; we'll need to discuss whether to treat the transaction issue as a bug or an RFE. Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/70fc1810e4cb781543466d79905206392513e6aa Bug 1032906: Fix generic error handling in Openshift agent Checked on devenv_4067, we can get friendly messages for this issue now, but also meet new problem, so assign it back.
1. The new problem is that: the app can not start/restart any more after deploying an invalid binary file by artifact_url, please refer to the following results:
$ rhc app start cphp00
Unable to complete the requested operation due to: Failed to correctly execute all parallel operations - ["StartCompOp"].
Reference ID: 3421b8b95d71423a63fc45c12b876fc6
$ rhc app restart cphp00
Unable to complete the requested operation due to: Failed to correctly execute all parallel operations - ["RestartCompOp"].
Reference ID: 22cf36d21a4c05bff6bdf03692c392e8
2. The friendly messages for the issue are like below:
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>internal_server_error</status>
<type nil="true"></type>
<data>
<datum nil="true"></datum>
</data>
<messages>
<message>
<severity>debug</severity>
<text>Error: Unable to extract deployment archive using command: /usr/bin/curl http://cphp-ccyd.rhcloud.com/cp1.tar.gz | /bin/tar -xz</text>
<exit-code>2</exit-code>
<field nil="true"></field>
<index nil="true"></index>
</message>
<message>
<severity>error</severity>
<text>Unable to complete the requested operation due to: An invalid exit code (2) was returned from the server ip-10-60-87-20. This indicates an unexpected problem during the execution of your request..
Reference ID: 5bbd9bfcc2e183cedae64ab90138bd36</text>
<exit-code>2</exit-code>
<field nil="true"></field>
<index nil="true"></index>
</message>
</messages>
<version>1.6</version>
<api-version>1.6</api-version>
<supported-api-versions>
<supported-api-version>1.0</supported-api-version>
<supported-api-version>1.1</supported-api-version>
<supported-api-version>1.2</supported-api-version>
<supported-api-version>1.3</supported-api-version>
<supported-api-version>1.4</supported-api-version>
<supported-api-version>1.5</supported-api-version>
<supported-api-version>1.6</supported-api-version>
</supported-api-versions>
</response>
If you deploy a bad artifact, you have to deploy something valid afterwards to get the app working again. There's nothing we can do to fix a bad deployment. |