[
https://issues.apache.org/jira/browse/AMBARI-14257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046316#comment-15046316
]
Hudson commented on AMBARI-14257:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.2 #31 (See
[https://builds.apache.org/job/Ambari-branch-2.2/31/])
AMBARI-14257 : Storm metrics do not work after upgrading Ambari to (swagle:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cbd2e896475c2d28bd7dd5613451eb8ff5f3354b])
* ambari-common/src/main/python/resource_management/core/providers/system.py
*
ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/storm.py
> Storm metrics do not work after upgrading Ambari to 2.1.2.
> ----------------------------------------------------------
>
> Key: AMBARI-14257
> URL: https://issues.apache.org/jira/browse/AMBARI-14257
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.1.2
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-14257.patch
>
>
> Problem
> Storm metrics do not work after upgrading Ambari to 2.1.2. ClassNotFound
> exception seen in the logs when storm metrics reporter class is accessed.
> Bug
> Storm lib directory is usually found in /usr/hdp/current/storm-nimbus/lib. In
> the code we try to delete the link from /usr/lib/storm/lib which is not
> present. Hence, we never update the symlink in the actual location thus
> causing a stale symlink.
> Fix
> Change the symlink deletion logic to look at the correct location. Also fix a
> bug in resource_management.system module where the action='delete' for Links
> must call the os.path.lexists rather than os.path.exists to return true for
> broken symlinks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
