You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Chris Lambert (JIRA)" <ji...@apache.org> on 2014/10/06 22:30:34 UTC
[jira] [Updated] (AURORA-786) Client does not log
Response.messageDEPRECATED errors
[ https://issues.apache.org/jira/browse/AURORA-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Lambert updated AURORA-786:
---------------------------------
Sprint: Aurora Q4 Sprint 1
> Client does not log Response.messageDEPRECATED errors
> -----------------------------------------------------
>
> Key: AURORA-786
> URL: https://issues.apache.org/jira/browse/AURORA-786
> Project: Aurora
> Issue Type: Bug
> Components: Client
> Reporter: Maxim Khutornenko
> Assignee: Maxim Khutornenko
>
> The implementation of context.py:log_response() checks only the new {{details}} field but not the old {{messageDEPRECATED}} one. This leads to ignoring unhandled updater errors wrapped into a synthetic Response object:
> {noformat}
> ...
> log(info): Cleaning up
> Error: Update failed; see log for details.
> log(info): Error executing command: Update failed; see log for details.
> Error executing command: Update failed; see log for details.
> {noformat}
> The "Update failed; see log for details." message is misleading as there will be nothing in the log in this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)