[
https://issues.apache.org/jira/browse/AURORA-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156719#comment-14156719
]
Bill Farner commented on AURORA-779:
------------------------------------
The relevant code is in
{{src/main/python//apache/aurora/client/cli/__init__.py}}:
{code}
except Exception as e:
print_aurora_log(logging.ERROR, "Internal error executing command: %s", e)
return EXIT_API_ERROR
{code}
[~mchucarroll] looks like the stack trace is lost in cases like this. Is that
intentional?
> v2 client has worse error message than v1
> -----------------------------------------
>
> Key: AURORA-779
> URL: https://issues.apache.org/jira/browse/AURORA-779
> Project: Aurora
> Issue Type: Bug
> Components: Client, Usability
> Reporter: Kevin Sweeney
>
> Copied from a user report at Twitter:
> I had a typo in an aurora config, where I was resolving a mustache variable
> outside of a string:
> {code}
> instances = {{profile.instances}}
> {code}
> where I should have been doing
> {code}
> instances = "{{profile.instances}}"
> {code}
> The error message on the v2 client was:
> {quote}
> Error executing command: Error loading configuration: name 'profile' is not
> defined
> {quote}
> The v1 client gave me a line number:
> {quote}
> File "router.aurora", line 90, in <module>
> instances = {{profile.instances}},
> NameError: name 'profile' is not defined
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
