You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Maxim Khutornenko (JIRA)" <ji...@apache.org> on 2015/01/26 23:59:53 UTC
[jira] [Updated] (AURORA-937) Response.serverInfo is not always
populated
[ https://issues.apache.org/jira/browse/AURORA-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Khutornenko updated AURORA-937:
-------------------------------------
Fix Version/s: 0.7.0
> Response.serverInfo is not always populated
> -------------------------------------------
>
> Key: AURORA-937
> URL: https://issues.apache.org/jira/browse/AURORA-937
> Project: Aurora
> Issue Type: Bug
> Components: Client, Scheduler
> Reporter: Maxim Khutornenko
> Assignee: Bill Farner
> Priority: Critical
> Fix For: 0.7.0
>
>
> The {{LoggingInterceptor}} replies with ERROR response that is not augmented by the {{ServerInfoInterceptor}}. As a result, the client fails with an error like:
> {noformat}
> Error during thrift call getTasksStatus to devcluster: 'NoneType' object has no attribute 'thriftAPIVersion'
> {noformat}
> The fix should address the AOP change on the scheduler as well as scheduler_client.py accessing {{serverInfo}} field in a safe fashion (i.e. checking {{resp.serverInfo}} is not None).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)