[jboss-jira] [JBoss JIRA] (WFCORE-1902) Error messages from CLI batch should be more informative
Brian Stansberry (JIRA)
issues at jboss.org
Mon Oct 31 11:16:00 EDT 2016
[ https://issues.jboss.org/browse/WFCORE-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13314225#comment-13314225 ]
Brian Stansberry commented on WFCORE-1902:
------------------------------------------
Trying to figure out what line in a script sounds like more trouble than it is worth. If it's possible to report the batch step number and the operation invoked by that step, I think that would provide most of the value. Seeing that :readAttribute(name=nonsence) failed should provide enough insight to let people figure out what line in a script was at fault.
Side note: be cautious about using DMR syntax to report high level failures that aren't simply showing the output of the low level failure. AFAIK we don't do that elsewhere and it's probably not something we should do on a case by case basis without an overall strategy.
> Error messages from CLI batch should be more informative
> --------------------------------------------------------
>
> Key: WFCORE-1902
> URL: https://issues.jboss.org/browse/WFCORE-1902
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI
> Affects Versions: 3.0.0.Alpha10
> Reporter: Marek Kopecký
> Assignee: Jean-Francois Denise
>
> *Description of problem:*
> Error messages from CLI batch should be more informative
> *Steps to Reproduce:*
> {noformat}
> cat <<EOF >a
> batch
> :read-attribute(name=product-version)
> :read-attribute(name=product-name)
> :read-attribute(name=nonsence)
> :read-attribute(name=product-name)
> run-batch
> EOF
> ./jboss-cli.sh -c --file=a
> {noformat}
> *Actual results:*
> {noformat}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-3" => "WFLYCTL0201: Unknown attribute 'nonsence'"}}
> {noformat}
> *Expected results:*
> I can imagine content like following could be helpful for troubleshooting:
> {noformat}
> {
> "WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {
> "Operation step-3" => {
> "line number" => 4
> "operation" => ":read-attribute(name=nonsence)"
> "response" => "WFLYCTL0201: Unknown attribute 'nonsence'"
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
More information about the jboss-jira
mailing list