[
https://issues.apache.org/jira/browse/AMBARI-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srimanth Gunturi resolved AMBARI-2506.
--------------------------------------
Resolution: Fixed
Committed to trunk.
> Host Check UI: Issues should be grouped by Issue Type
> -----------------------------------------------------
>
> Key: AMBARI-2506
> URL: https://issues.apache.org/jira/browse/AMBARI-2506
> Project: Ambari
> Issue Type: Task
> Components: client
> Affects Versions: 1.2.5
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Fix For: 1.2.5
>
> Attachments: AMBARI-2506_branch-1.2.5.patch, AMBARI-2506.patch,
> Screen Shot 2013-06-20 at 5.38.23 PM.png, Screen Shot 2013-07-02 at 3.52.59
> PM.png
>
>
> Attached is an image about how the sections in Hosts check dialog should look
> like. There should be 5 major sections (more to come later):
> Example:
> * 3 file or folder issue
> * 2 process issues
> * 1 service issues
> * 0 user issues
> * 3 package issues
> Each of the above should have the following labels in them respectively
> * The following files or folders should not exist
> * The following processes should not be running
> * The following services should be up
> * The following users should be removed
> * The following packages should be uninstalled
> Currently we model host->issue-type->issues. We should reverse that map in
> code to be issue-type->issues->hosts. Generally an issue might exist in
> multiple hosts (like /etc/hadoop/conf existing in 10 hosts). So in that case
> we need to have the 10 hosts in an array for the issue of /etc/hadoop/conf
> path.
--
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
