Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3E524200C28 for ; Mon, 13 Mar 2017 14:00:48 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3CEF7160B6C; Mon, 13 Mar 2017 13:00:48 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 73FF1160B60 for ; Mon, 13 Mar 2017 14:00:47 +0100 (CET) Received: (qmail 14930 invoked by uid 500); 13 Mar 2017 13:00:46 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 14898 invoked by uid 99); 13 Mar 2017 13:00:46 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Mar 2017 13:00:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 073C91AF914 for ; Mon, 13 Mar 2017 13:00:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.651 X-Spam-Level: ** X-Spam-Status: No, score=2.651 tagged_above=-999 required=6.31 tests=[KAM_BADIPHTTP=2, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id IpcaATLgs0sg for ; Mon, 13 Mar 2017 13:00:45 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 722C35F2EF for ; Mon, 13 Mar 2017 13:00:44 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A36C2E0146 for ; Mon, 13 Mar 2017 13:00:43 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5826B24369 for ; Mon, 13 Mar 2017 13:00:43 +0000 (UTC) Date: Mon, 13 Mar 2017 13:00:43 +0000 (UTC) From: "DIPAYAN BHOWMICK (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-20383) Not able to view the error log details on UI MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 13 Mar 2017 13:00:48 -0000 [ https://issues.apache.org/jira/browse/AMBARI-20383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-20383: -------------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5, trunk. > Not able to view the error log details on UI > --------------------------------------------- > > Key: AMBARI-20383 > URL: https://issues.apache.org/jira/browse/AMBARI-20383 > Project: Ambari > Issue Type: Bug > Components: ambari-views > Affects Versions: 2.5.0 > Reporter: Supreeth Sharma > Assignee: Padma Priya Nagaraj > Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20383_trunk.patch > > > Not able to view the error logs on UI. When user clicks on 'Details' link, UI is failing with below error: > {code} > Uncaught TypeError: Cannot read property 'nodes' of null > at n.isWorkflowValid (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-89dda89e1533d3f32ee5166954811095.js:8:25204) > at n.validate (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-89dda89e1533d3f32ee5166954811095.js:58:12130) > at http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:30047 > at Array.map (native) > at n. (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:29848) > at n. (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:24894) > at d.p.get (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:9:31289) > at s (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3104) > at c (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3694) > at s (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3093) > {code} > Steps to reproduce : > 1) Try to import a workflow which user doesn't have read permission. > 2) 'Permission Denied' message is shown on the UI. But when user clicks on 'Details' link, UI is failing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)