[
https://issues.apache.org/jira/browse/AMBARI-15682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224290#comment-15224290
]
Ashwin Rajeev commented on AMBARI-15682:
----------------------------------------
Seems to be a random failure in Ambari metrics, not related to patch
{code}
INFO] Ambari Main ....................................... SUCCESS [ 3.159 s]
[INFO] Apache Ambari Project POM ......................... SUCCESS [ 0.060 s]
[INFO] Ambari Web ........................................ SUCCESS [ 38.431 s]
[INFO] Ambari Views ...................................... SUCCESS [ 1.190 s]
[INFO] Ambari Admin View ................................. SUCCESS [01:57 min]
[INFO] ambari-metrics .................................... SUCCESS [ 0.067 s]
[INFO] Ambari Metrics Common ............................. SUCCESS [ 0.675 s]
[INFO] Ambari Metrics Hadoop Sink ........................ SUCCESS [ 0.511 s]
[INFO] Ambari Metrics Flume Sink ......................... SUCCESS [ 0.253 s]
[INFO] Ambari Metrics Kafka Sink ......................... SUCCESS [ 0.335 s]
[INFO] Ambari Metrics Storm Sink ......................... SUCCESS [ 0.418 s]
[INFO] Ambari Metrics Collector .......................... SUCCESS [ 9.736 s]
[INFO] Ambari Metrics Monitor ............................ SUCCESS [ 1.113 s]
[INFO] Ambari Metrics Grafana ............................ FAILURE [01:22 min]
ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project
ambari-metrics-grafana: An Ant BuildException has occured: Error while
expanding
/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-metrics/ambari-metrics-grafana/target/grafana/grafana.tgz
[ERROR] java.io.EOFException: Unexpected end of ZLIB input stream
[ERROR] around Ant part ...<untar
dest="/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-metrics/ambari-metrics-grafana/target/grafana"
src="/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-metrics/ambari-metrics-grafana/target/grafana/grafana.tgz"
compression="gzip"/>... @ 6:299 in
/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-metrics/ambari-metrics-grafana/target/antrun/build-Download
Ambari Grafana.xml
[ERROR] -> [Help 1]
{code}
> Views: Provide refresh list of available views with newly deployed views w/o
> restart
> ------------------------------------------------------------------------------------
>
> Key: AMBARI-15682
> URL: https://issues.apache.org/jira/browse/AMBARI-15682
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.2.0
> Reporter: Ashwin Rajeev
> Assignee: Ashwin Rajeev
> Fix For: 2.4.0
>
> Attachments: AMBARI-15682.2.trunk.patch, AMBARI-15682.branch-2.2.patch
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Ambari is able to detect that there are new views available (dynamically).
> However, there does not appear to be a mechanism to perform a refresh.
> What makes the most sense is to refresh everytime the admin view page is
> accessed and also provide a manual refresh button
> User should be able to:
> 1) Place a new view package on Ambari Server
> 2) Do not restart Ambari Server
> 3) While in Admin View, user clicks refresh in browser on Views section
> 4) Newly deployed view is shown. User can create use the view to create
> instances, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
