[
https://issues.apache.org/jira/browse/AMBARI-18542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Judy Nash updated AMBARI-18542:
-------------------------------
Summary: Ambari API request returns 500 when no stale service need to be
restarted (was: Ambari API request returns unexpected error code when no stale
service need to be restarted)
> Ambari API request returns 500 when no stale service need to be restarted
> -------------------------------------------------------------------------
>
> Key: AMBARI-18542
> URL: https://issues.apache.org/jira/browse/AMBARI-18542
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Judy Nash
> Priority: Minor
>
> Bug related to a recent API addition to Ambari at this JIRA:
> https://issues.apache.org/jira/browse/AMBARI-14394
> At Ambari 2.4, a new API is introduced to restart all stale services in one
> call.
> When API is called and there is no stale service needed to restart, APi
> returns the following status:
> {
> "status" : 500,
> "message" : "An internal system exception occurred: Command execution
> cannot proceed without a resource filter."
> }
> A legit but no ops needed operations shouldn't return a 500 status. 200 seems
> more appropriate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
