Bug 1012138
Summary: | parallel operations on Broker does not coalesce exit codes | ||
---|---|---|---|
Product: | OpenShift Online | Reporter: | Jhon Honce <jhonce> |
Component: | Pod | Assignee: | Abhishek Gupta <abhgupta> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.x | CC: | jhou, rchopra |
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: | 2013-10-17 13:31:20 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: | 981780 |
Description
Jhon Honce
2013-09-25 19:42:26 UTC
Fixed with --> https://github.com/openshift/origin-server/pull/3708 Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/604cea57e0b15a70e73c86fa6109b5eaf17c51ea Fix for bug 1012138 Tested on devenv_3832, issue still reproducible steps: 1. Create a diy app with mysql and postgresql-8.2 2. Edit bin/control of mysql, add "testing error" and exit 255 to start function 3. Stop and start the app, still got: Unable to complete the requested operation due to: Failed to correctly execute all parallel operations. Reference ID: 82dfcaab7c58fbd4f844cdfb1c17a361 The failure messages need to be added using "client_error" to be treated as a client failure and be displayed to the user. (In reply to Abhishek Gupta from comment #4) > The failure messages need to be added using "client_error" to be treated as > a client failure and be displayed to the user. Is this bug fixed? Didn't see any github commits updated to this bug, and I still got the same result with comment 3. My test env is devenv_3871 @jhou - comment#3 suggests that 'testing error' needs to be encapsulated as 'CLIENT_ERROR: testing error..' for it to be shown by the broker appropriately. When the failure happens, anything reported under 'CLIENT_ERROR' is reported back. Not the rest. @rajat Thank you, this bug is now verified on devenv_3874, the 'CLIENT_ERROR' can be reported to the end user RESULT: d1 stopped testing error.. |