incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-1859) Cannot load Nagios Alerts due to 400 Bad Request
Date Tue, 09 Apr 2013 20:14:16 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sumit Mohanty updated AMBARI-1859:
----------------------------------

    Attachment: AMBARI-1859.patch
    
> Cannot load Nagios Alerts due to 400 Bad Request
> ------------------------------------------------
>
>                 Key: AMBARI-1859
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1859
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.3.0
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 1.3.0
>
>         Attachments: AMBARI-1859.patch
>
>
> Given the API call: http://dev.hortonworks.com:8080/api/v1/clusters/test403_2/host_components?HostRoles/component_name=NAGIOS_SERVER&fields=HostRoles/nagios_alerts
> The feedback is:
> { "status" : 400, "message" : "The properties [HostRoles/nagios_alerts] specified in
the request or predicate are not supported for the resource type HostComponent." }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message