[jira] [Commented] (AMBARI-20358) NPE during Ambari server schema upgrade while updating hbase_master_cpu alert definition
[
https://issues.apache.org/jira/browse/AMBARI-20358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901253#comment-15901253
]
Hudson commented on AMBARI-20358:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1210 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1210/])
AMBARI-20358. NPE during Ambari server schema upgrade while updating (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8eaaf8086502890ef5d1c3ad88ca5fee8311f599])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
> NPE during Ambari server schema upgrade while updating hbase_master_cpu alert
> definition
>
>
> Key: AMBARI-20358
> URL: https://issues.apache.org/jira/browse/AMBARI-20358
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20358_branch-2.5_01.patch,
> AMBARI-20358_trunk_01.patch
>
>
> Probably caused by this commit:
> https://github.com/hortonworks/ambari/commit/6be4a18dd00f9d23d63410b748d67c952a6240c8
> *STR*
> # Deploy HDP-2.3.6 with Ambari-2.2.2.0
> # Upgrade Ambari to 2.5.0.1-13 (hash:
> 52b820b0c899a0246061c51245aca231c63583d7) - this includes executing 'yum
> upgrade ambari-server' followed by 'ambari-server upgrade'
> *Result*
> Error during DB schema upgrade
> {code}
> 08 Mar 2017 04:52:22,059 INFO [main] AbstractUpgradeCatalog:609 - cluster
> 'cl1' changed by: 'ambari-upgrade'; type='ranger-kafka-security'
> tag='version1488948741867' from='version1488942647954'
> 08 Mar 2017 04:52:23,469 INFO [main] UpgradeCatalog250:214 - Updating alert
> definition hbase_master_cpu in cluster 2
> 08 Mar 2017 04:52:23,471 ERROR [main] SchemaUpgradeHelper:239 - Upgrade
> failed.
> java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.fixHBaseMasterCPUUtilizationAlertDefinition(UpgradeCatalog250.java:229)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.executeDMLUpdates(UpgradeCatalog250.java:197)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:952)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> 08 Mar 2017 04:52:23,474 ERROR [main] SchemaUpgradeHelper:443 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.fixHBaseMasterCPUUtilizationAlertDefinition(UpgradeCatalog250.java:229)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.executeDMLUpdates(UpgradeCatalog250.java:197)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:952)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> ... 1 more
> 08 Mar 2017 04:52:27,829 INFO [main] Configuration:2906 - Reading password
> from existing file
> 08 Mar 2017 04:52:27,863 INFO [main] Configuration:3382 - Hosts Mapping File
> null
> 08 Mar 2017 04:52:27,864 INFO [main] HostsMap:60 - Using hostsmap file null
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20337) Need to show timer while loading coordinator name while bundle creation
[ https://issues.apache.org/jira/browse/AMBARI-20337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901204#comment-15901204 ] Hudson commented on AMBARI-20337: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6973 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6973/]) AMBARI-20337.Need to show timer while loading coordinator name while (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=17323e0d73d11eb27f3203ae6f2319e43e6ef9cd]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-coord-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/bundle-coord-config.js > Need to show timer while loading coordinator name while bundle creation > --- > > Key: AMBARI-20337 > URL: https://issues.apache.org/jira/browse/AMBARI-20337 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20337_trunk.patch > > > Need to show timer while loading coordinator name while bundle creation. > Issue 1 : Some times coordinator name is not fetch even after 5secs. So its > better to show timer to indicate that name is getting loaded. > Issue 2: If user provides invalid coordinator path, then appropriate error > message should be shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20358) NPE during Ambari server schema upgrade while updating hbase_master_cpu alert definition
[
https://issues.apache.org/jira/browse/AMBARI-20358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-20358:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit f39207a53df94433ca0ac39ffde6f5fb9f7994c6
Author: Robert Levas
Date: Wed Mar 8 07:49:32 2017 -0500
{noformat}
Committed to branch-2.5
{noformat}
commit 8eaaf8086502890ef5d1c3ad88ca5fee8311f599
Author: Robert Levas
Date: Wed Mar 8 07:50:13 2017 -0500
{noformat}
> NPE during Ambari server schema upgrade while updating hbase_master_cpu alert
> definition
>
>
> Key: AMBARI-20358
> URL: https://issues.apache.org/jira/browse/AMBARI-20358
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20358_branch-2.5_01.patch,
> AMBARI-20358_trunk_01.patch
>
>
> Probably caused by this commit:
> https://github.com/hortonworks/ambari/commit/6be4a18dd00f9d23d63410b748d67c952a6240c8
> *STR*
> # Deploy HDP-2.3.6 with Ambari-2.2.2.0
> # Upgrade Ambari to 2.5.0.1-13 (hash:
> 52b820b0c899a0246061c51245aca231c63583d7) - this includes executing 'yum
> upgrade ambari-server' followed by 'ambari-server upgrade'
> *Result*
> Error during DB schema upgrade
> {code}
> 08 Mar 2017 04:52:22,059 INFO [main] AbstractUpgradeCatalog:609 - cluster
> 'cl1' changed by: 'ambari-upgrade'; type='ranger-kafka-security'
> tag='version1488948741867' from='version1488942647954'
> 08 Mar 2017 04:52:23,469 INFO [main] UpgradeCatalog250:214 - Updating alert
> definition hbase_master_cpu in cluster 2
> 08 Mar 2017 04:52:23,471 ERROR [main] SchemaUpgradeHelper:239 - Upgrade
> failed.
> java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.fixHBaseMasterCPUUtilizationAlertDefinition(UpgradeCatalog250.java:229)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.executeDMLUpdates(UpgradeCatalog250.java:197)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:952)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> 08 Mar 2017 04:52:23,474 ERROR [main] SchemaUpgradeHelper:443 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.fixHBaseMasterCPUUtilizationAlertDefinition(UpgradeCatalog250.java:229)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.executeDMLUpdates(UpgradeCatalog250.java:197)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:952)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> ... 1 more
> 08 Mar 2017 04:52:27,829 INFO [main] Configuration:2906 - Reading password
> from existing file
> 08 Mar 2017 04:52:27,863 INFO [main] Configuration:3382 - Hosts Mapping File
> null
> 08 Mar 2017 04:52:27,864 INFO [main] HostsMap:60 - Using hostsmap file null
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20337) Need to show timer while loading coordinator name while bundle creation
[ https://issues.apache.org/jira/browse/AMBARI-20337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901196#comment-15901196 ] Hudson commented on AMBARI-20337: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1209 (See [https://builds.apache.org/job/Ambari-branch-2.5/1209/]) AMBARI-20337.Need to show timer while loading coordinator name while (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=934f3f18277b3cb48e1e8c9a16836aebdec1d1b0]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-coord-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/bundle-coord-config.js > Need to show timer while loading coordinator name while bundle creation > --- > > Key: AMBARI-20337 > URL: https://issues.apache.org/jira/browse/AMBARI-20337 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20337_trunk.patch > > > Need to show timer while loading coordinator name while bundle creation. > Issue 1 : Some times coordinator name is not fetch even after 5secs. So its > better to show timer to indicate that name is getting loaded. > Issue 2: If user provides invalid coordinator path, then appropriate error > message should be shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20358) NPE during Ambari server schema upgrade while updating hbase_master_cpu alert definition
[
https://issues.apache.org/jira/browse/AMBARI-20358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901190#comment-15901190
]
Hadoop QA commented on AMBARI-20358:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856799/AMBARI-20358_trunk_01.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10926//console
This message is automatically generated.
> NPE during Ambari server schema upgrade while updating hbase_master_cpu alert
> definition
>
>
> Key: AMBARI-20358
> URL: https://issues.apache.org/jira/browse/AMBARI-20358
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20358_branch-2.5_01.patch,
> AMBARI-20358_trunk_01.patch
>
>
> Probably caused by this commit:
> https://github.com/hortonworks/ambari/commit/6be4a18dd00f9d23d63410b748d67c952a6240c8
> *STR*
> # Deploy HDP-2.3.6 with Ambari-2.2.2.0
> # Upgrade Ambari to 2.5.0.1-13 (hash:
> 52b820b0c899a0246061c51245aca231c63583d7) - this includes executing 'yum
> upgrade ambari-server' followed by 'ambari-server upgrade'
> *Result*
> Error during DB schema upgrade
> {code}
> 08 Mar 2017 04:52:22,059 INFO [main] AbstractUpgradeCatalog:609 - cluster
> 'cl1' changed by: 'ambari-upgrade'; type='ranger-kafka-security'
> tag='version1488948741867' from='version1488942647954'
> 08 Mar 2017 04:52:23,469 INFO [main] UpgradeCatalog250:214 - Updating alert
> definition hbase_master_cpu in cluster 2
> 08 Mar 2017 04:52:23,471 ERROR [main] SchemaUpgradeHelper:239 - Upgrade
> failed.
> java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.fixHBaseMasterCPUUtilizationAlertDefinition(UpgradeCatalog250.java:229)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.executeDMLUpdates(UpgradeCatalog250.java:197)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:952)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> 08 Mar 2017 04:52:23,474 ERROR [main] SchemaUpgradeHelper:443 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.fixHBaseMasterCPUUtilizationAlertDefinition(UpgradeCatalog250.java:229)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.executeDMLUpdates(UpgradeCatalog250.java:197)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:952)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> ... 1 more
> 08 Mar 2017 04:52:27,829 INFO [main] Configuration:2906 - Reading password
> from existing file
> 08 Mar 2017 04:52:27,863 INFO [main] Configuration:3382 - Hosts Mapping File
> null
> 08 Mar 2017 04:52:27,864 INFO [main] HostsMap:60 - Using hostsmap file null
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20360) Need to show appropriate error message in cases of UI failures
Supreeth Sharma created AMBARI-20360: Summary: Need to show appropriate error message in cases of UI failures Key: AMBARI-20360 URL: https://issues.apache.org/jira/browse/AMBARI-20360 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Supreeth Sharma Priority: Critical Fix For: 2.5.0 Need to show appropriate error message in cases of UI failures. Scenario 1 : When user tries to import invalid workflow xml. For example, if user imports coordinator xml instead of workflow, then appropriate error message should be displayed. Same should be handled for bundles and coordinators. Scenario 2 : When user tries to import larger workflows. Currently workflow manager supports workflows with 400 nodes. If user imports workflows with more nodes, then appropriate error message should be shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20342) WFM:Performance improvement for adding node on a decision node in large workflow.
[ https://issues.apache.org/jira/browse/AMBARI-20342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901177#comment-15901177 ] Hudson commented on AMBARI-20342: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6972 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6972/]) AMBARI-20342. WFM:Performance improvement for adding node on a decision (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fdb12d4800a620c44940b72c43dd4c499e80d829]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/cytoscape-flow-renderer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/styles/app.less * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/flow-designer.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/flow-designer.js > WFM:Performance improvement for adding node on a decision node in large > workflow. > - > > Key: AMBARI-20342 > URL: https://issues.apache.org/jira/browse/AMBARI-20342 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20342_trunk.patch > > > Performance improvement on adding node to large workflow on lower part of > decision path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20353) Log error while importing the workflow from encrypted path
[ https://issues.apache.org/jira/browse/AMBARI-20353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901178#comment-15901178 ] Hudson commented on AMBARI-20353: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6972 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6972/]) AMBARI-20353. Log error while importing the workflow from encrypted (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=78e038a8098200c58b425c7cd6b5e87e75da0ea8]) * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/Utils.java * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/OozieProxyImpersonator.java > Log error while importing the workflow from encrypted path > -- > > Key: AMBARI-20353 > URL: https://issues.apache.org/jira/browse/AMBARI-20353 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20353_trunk.patch > > > Facing issue while importing workflow where api > /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/WFM/resources/proxy/readWorkflow?workflowPath=/tmp/encrypt/workflow.xml=WORKFLOW > is failing with 500 status code. > Steps to reproduce : > Try to import workflow /tmp/encrypt/workflow.xml and its failing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20353) Log error while importing the workflow from encrypted path
[ https://issues.apache.org/jira/browse/AMBARI-20353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901165#comment-15901165 ] Hudson commented on AMBARI-20353: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1208 (See [https://builds.apache.org/job/Ambari-branch-2.5/1208/]) AMBARI-20353. Log error while importing the workflow from encrypted (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ba04d2211c1db5f6f7ca2feeede1b5667410344d]) * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/OozieProxyImpersonator.java * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/Utils.java > Log error while importing the workflow from encrypted path > -- > > Key: AMBARI-20353 > URL: https://issues.apache.org/jira/browse/AMBARI-20353 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20353_trunk.patch > > > Facing issue while importing workflow where api > /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/WFM/resources/proxy/readWorkflow?workflowPath=/tmp/encrypt/workflow.xml=WORKFLOW > is failing with 500 status code. > Steps to reproduce : > Try to import workflow /tmp/encrypt/workflow.xml and its failing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20342) WFM:Performance improvement for adding node on a decision node in large workflow.
[ https://issues.apache.org/jira/browse/AMBARI-20342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901164#comment-15901164 ] Hudson commented on AMBARI-20342: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1208 (See [https://builds.apache.org/job/Ambari-branch-2.5/1208/]) AMBARI-20342. WFM:Performance improvement for adding node on a decision (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3fd1c24442f4c90becff35c004290e829f136318]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/cytoscape-flow-renderer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/flow-designer.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/styles/app.less * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/flow-designer.js > WFM:Performance improvement for adding node on a decision node in large > workflow. > - > > Key: AMBARI-20342 > URL: https://issues.apache.org/jira/browse/AMBARI-20342 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20342_trunk.patch > > > Performance improvement on adding node to large workflow on lower part of > decision path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20359) Not able to import workflow with fs action node
Supreeth Sharma created AMBARI-20359:
Summary: Not able to import workflow with fs action node
Key: AMBARI-20359
URL: https://issues.apache.org/jira/browse/AMBARI-20359
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.5.0
Reporter: Supreeth Sharma
Priority: Critical
Fix For: 2.5.0
Not able to import workflow with fs action node.
Seeing below error in UI console log :
{code}
Uncaught TypeError: Cannot read property '0' of undefined
at n.handleImport
(http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:7:28237)
at n [as handleImport]
(http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:18180)
at n.handleImportNode
(http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:13846)
at
http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:27314
at Array.forEach (native)
at
http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:27286
at Array.forEach (native)
at n.setupNodeMap
(http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:27188)
at n.processWorkflowXml
(http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:26231)
at n.importWorkflow
(http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:25548)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20337) Need to show timer while loading coordinator name while bundle creation
[ https://issues.apache.org/jira/browse/AMBARI-20337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20337: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Need to show timer while loading coordinator name while bundle creation > --- > > Key: AMBARI-20337 > URL: https://issues.apache.org/jira/browse/AMBARI-20337 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20337_trunk.patch > > > Need to show timer while loading coordinator name while bundle creation. > Issue 1 : Some times coordinator name is not fetch even after 5secs. So its > better to show timer to indicate that name is getting loaded. > Issue 2: If user provides invalid coordinator path, then appropriate error > message should be shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20358) NPE during Ambari server schema upgrade while updating hbase_master_cpu alert definition
[
https://issues.apache.org/jira/browse/AMBARI-20358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-20358:
--
Attachment: AMBARI-20358_trunk_01.patch
AMBARI-20358_branch-2.5_01.patch
> NPE during Ambari server schema upgrade while updating hbase_master_cpu alert
> definition
>
>
> Key: AMBARI-20358
> URL: https://issues.apache.org/jira/browse/AMBARI-20358
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20358_branch-2.5_01.patch,
> AMBARI-20358_trunk_01.patch
>
>
> Probably caused by this commit:
> https://github.com/hortonworks/ambari/commit/6be4a18dd00f9d23d63410b748d67c952a6240c8
> *STR*
> # Deploy HDP-2.3.6 with Ambari-2.2.2.0
> # Upgrade Ambari to 2.5.0.1-13 (hash:
> 52b820b0c899a0246061c51245aca231c63583d7) - this includes executing 'yum
> upgrade ambari-server' followed by 'ambari-server upgrade'
> *Result*
> Error during DB schema upgrade
> {code}
> 08 Mar 2017 04:52:22,059 INFO [main] AbstractUpgradeCatalog:609 - cluster
> 'cl1' changed by: 'ambari-upgrade'; type='ranger-kafka-security'
> tag='version1488948741867' from='version1488942647954'
> 08 Mar 2017 04:52:23,469 INFO [main] UpgradeCatalog250:214 - Updating alert
> definition hbase_master_cpu in cluster 2
> 08 Mar 2017 04:52:23,471 ERROR [main] SchemaUpgradeHelper:239 - Upgrade
> failed.
> java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.fixHBaseMasterCPUUtilizationAlertDefinition(UpgradeCatalog250.java:229)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.executeDMLUpdates(UpgradeCatalog250.java:197)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:952)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> 08 Mar 2017 04:52:23,474 ERROR [main] SchemaUpgradeHelper:443 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.fixHBaseMasterCPUUtilizationAlertDefinition(UpgradeCatalog250.java:229)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.executeDMLUpdates(UpgradeCatalog250.java:197)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:952)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> ... 1 more
> 08 Mar 2017 04:52:27,829 INFO [main] Configuration:2906 - Reading password
> from existing file
> 08 Mar 2017 04:52:27,863 INFO [main] Configuration:3382 - Hosts Mapping File
> null
> 08 Mar 2017 04:52:27,864 INFO [main] HostsMap:60 - Using hostsmap file null
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20358) NPE during Ambari server schema upgrade while updating hbase_master_cpu alert definition
[
https://issues.apache.org/jira/browse/AMBARI-20358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-20358:
--
Status: Patch Available (was: In Progress)
> NPE during Ambari server schema upgrade while updating hbase_master_cpu alert
> definition
>
>
> Key: AMBARI-20358
> URL: https://issues.apache.org/jira/browse/AMBARI-20358
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20358_branch-2.5_01.patch,
> AMBARI-20358_trunk_01.patch
>
>
> Probably caused by this commit:
> https://github.com/hortonworks/ambari/commit/6be4a18dd00f9d23d63410b748d67c952a6240c8
> *STR*
> # Deploy HDP-2.3.6 with Ambari-2.2.2.0
> # Upgrade Ambari to 2.5.0.1-13 (hash:
> 52b820b0c899a0246061c51245aca231c63583d7) - this includes executing 'yum
> upgrade ambari-server' followed by 'ambari-server upgrade'
> *Result*
> Error during DB schema upgrade
> {code}
> 08 Mar 2017 04:52:22,059 INFO [main] AbstractUpgradeCatalog:609 - cluster
> 'cl1' changed by: 'ambari-upgrade'; type='ranger-kafka-security'
> tag='version1488948741867' from='version1488942647954'
> 08 Mar 2017 04:52:23,469 INFO [main] UpgradeCatalog250:214 - Updating alert
> definition hbase_master_cpu in cluster 2
> 08 Mar 2017 04:52:23,471 ERROR [main] SchemaUpgradeHelper:239 - Upgrade
> failed.
> java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.fixHBaseMasterCPUUtilizationAlertDefinition(UpgradeCatalog250.java:229)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.executeDMLUpdates(UpgradeCatalog250.java:197)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:952)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> 08 Mar 2017 04:52:23,474 ERROR [main] SchemaUpgradeHelper:443 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.fixHBaseMasterCPUUtilizationAlertDefinition(UpgradeCatalog250.java:229)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog250.executeDMLUpdates(UpgradeCatalog250.java:197)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:952)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> ... 1 more
> 08 Mar 2017 04:52:27,829 INFO [main] Configuration:2906 - Reading password
> from existing file
> 08 Mar 2017 04:52:27,863 INFO [main] Configuration:3382 - Hosts Mapping File
> null
> 08 Mar 2017 04:52:27,864 INFO [main] HostsMap:60 - Using hostsmap file null
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20337) Need to show timer while loading coordinator name while bundle creation
[
https://issues.apache.org/jira/browse/AMBARI-20337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901140#comment-15901140
]
Hadoop QA commented on AMBARI-20337:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856789/AMBARI-20337_trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10925//console
This message is automatically generated.
> Need to show timer while loading coordinator name while bundle creation
> ---
>
> Key: AMBARI-20337
> URL: https://issues.apache.org/jira/browse/AMBARI-20337
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: M Madhan Mohan Reddy
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20337_trunk.patch
>
>
> Need to show timer while loading coordinator name while bundle creation.
> Issue 1 : Some times coordinator name is not fetch even after 5secs. So its
> better to show timer to indicate that name is getting loaded.
> Issue 2: If user provides invalid coordinator path, then appropriate error
> message should be shown.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20340) Issue with toggling of Execute/Stop button in query page while successful and failure execution of query.
[ https://issues.apache.org/jira/browse/AMBARI-20340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901135#comment-15901135 ] Hudson commented on AMBARI-20340: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6971 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6971/]) AMBARI-20340.Issue with toggling of Execute/Stop button in query page (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0e56ae78e768a6d54392fc9d8c91f4c46c4645ea]) * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/styles/app.scss > Issue with toggling of Execute/Stop button in query page while successful and > failure execution of query. > - > > Key: AMBARI-20340 > URL: https://issues.apache.org/jira/browse/AMBARI-20340 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20340.branch-2.5.patch > > > Create two tabs in query page and execute query in first tab and switch to > second tab. > The stop button of first tab is visible in second tab. > This scenario have to be handled while successful and failure execution of > query. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20357) [Hive2] JS error in udf delete
[
https://issues.apache.org/jira/browse/AMBARI-20357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901130#comment-15901130
]
Hadoop QA commented on AMBARI-20357:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856793/AMBARI-20357-branch-2-5.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10924//console
This message is automatically generated.
> [Hive2] JS error in udf delete
> --
>
> Key: AMBARI-20357
> URL: https://issues.apache.org/jira/browse/AMBARI-20357
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.0
>
> Attachments: AMBARI-20357-branch-2-5.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20340) Issue with toggling of Execute/Stop button in query page while successful and failure execution of query.
[ https://issues.apache.org/jira/browse/AMBARI-20340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901129#comment-15901129 ] Hudson commented on AMBARI-20340: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1207 (See [https://builds.apache.org/job/Ambari-branch-2.5/1207/]) AMBARI-20340.Issue with toggling of Execute/Stop button in query page (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=267c98fb8afdb32dae3ae192f12324b040e55880]) * (edit) contrib/views/hive20/src/main/resources/ui/app/styles/app.scss * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query.js > Issue with toggling of Execute/Stop button in query page while successful and > failure execution of query. > - > > Key: AMBARI-20340 > URL: https://issues.apache.org/jira/browse/AMBARI-20340 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20340.branch-2.5.patch > > > Create two tabs in query page and execute query in first tab and switch to > second tab. > The stop button of first tab is visible in second tab. > This scenario have to be handled while successful and failure execution of > query. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20353) Log error while importing the workflow from encrypted path
[ https://issues.apache.org/jira/browse/AMBARI-20353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20353: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Log error while importing the workflow from encrypted path > -- > > Key: AMBARI-20353 > URL: https://issues.apache.org/jira/browse/AMBARI-20353 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20353_trunk.patch > > > Facing issue while importing workflow where api > /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/WFM/resources/proxy/readWorkflow?workflowPath=/tmp/encrypt/workflow.xml=WORKFLOW > is failing with 500 status code. > Steps to reproduce : > Try to import workflow /tmp/encrypt/workflow.xml and its failing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20342) WFM:Performance improvement for adding node on a decision node in large workflow.
[ https://issues.apache.org/jira/browse/AMBARI-20342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20342: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > WFM:Performance improvement for adding node on a decision node in large > workflow. > - > > Key: AMBARI-20342 > URL: https://issues.apache.org/jira/browse/AMBARI-20342 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20342_trunk.patch > > > Performance improvement on adding node to large workflow on lower part of > decision path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20353) Log error while importing the workflow from encrypted path
[ https://issues.apache.org/jira/browse/AMBARI-20353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Madhan Mohan Reddy updated AMBARI-20353: -- Attachment: (was: AMBARI-20353_trunk.patch) > Log error while importing the workflow from encrypted path > -- > > Key: AMBARI-20353 > URL: https://issues.apache.org/jira/browse/AMBARI-20353 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20353_trunk.patch > > > Facing issue while importing workflow where api > /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/WFM/resources/proxy/readWorkflow?workflowPath=/tmp/encrypt/workflow.xml=WORKFLOW > is failing with 500 status code. > Steps to reproduce : > Try to import workflow /tmp/encrypt/workflow.xml and its failing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20353) Log error while importing the workflow from encrypted path
[ https://issues.apache.org/jira/browse/AMBARI-20353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Madhan Mohan Reddy updated AMBARI-20353: -- Attachment: AMBARI-20353_trunk.patch > Log error while importing the workflow from encrypted path > -- > > Key: AMBARI-20353 > URL: https://issues.apache.org/jira/browse/AMBARI-20353 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20353_trunk.patch > > > Facing issue while importing workflow where api > /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/WFM/resources/proxy/readWorkflow?workflowPath=/tmp/encrypt/workflow.xml=WORKFLOW > is failing with 500 status code. > Steps to reproduce : > Try to import workflow /tmp/encrypt/workflow.xml and its failing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20358) NPE during Ambari server schema upgrade while updating hbase_master_cpu alert definition
Robert Levas created AMBARI-20358:
-
Summary: NPE during Ambari server schema upgrade while updating
hbase_master_cpu alert definition
Key: AMBARI-20358
URL: https://issues.apache.org/jira/browse/AMBARI-20358
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Blocker
Fix For: 2.5.0
Probably caused by this commit:
https://github.com/hortonworks/ambari/commit/6be4a18dd00f9d23d63410b748d67c952a6240c8
*STR*
# Deploy HDP-2.3.6 with Ambari-2.2.2.0
# Upgrade Ambari to 2.5.0.1-13 (hash: 52b820b0c899a0246061c51245aca231c63583d7)
- this includes executing 'yum upgrade ambari-server' followed by
'ambari-server upgrade'
*Result*
Error during DB schema upgrade
{code}
08 Mar 2017 04:52:22,059 INFO [main] AbstractUpgradeCatalog:609 - cluster
'cl1' changed by: 'ambari-upgrade'; type='ranger-kafka-security'
tag='version1488948741867' from='version1488942647954'
08 Mar 2017 04:52:23,469 INFO [main] UpgradeCatalog250:214 - Updating alert
definition hbase_master_cpu in cluster 2
08 Mar 2017 04:52:23,471 ERROR [main] SchemaUpgradeHelper:239 - Upgrade failed.
java.lang.NullPointerException
at
org.apache.ambari.server.upgrade.UpgradeCatalog250.fixHBaseMasterCPUUtilizationAlertDefinition(UpgradeCatalog250.java:229)
at
org.apache.ambari.server.upgrade.UpgradeCatalog250.executeDMLUpdates(UpgradeCatalog250.java:197)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:952)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
08 Mar 2017 04:52:23,474 ERROR [main] SchemaUpgradeHelper:443 - Exception
occurred during upgrade, failed
org.apache.ambari.server.AmbariException
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
Caused by: java.lang.NullPointerException
at
org.apache.ambari.server.upgrade.UpgradeCatalog250.fixHBaseMasterCPUUtilizationAlertDefinition(UpgradeCatalog250.java:229)
at
org.apache.ambari.server.upgrade.UpgradeCatalog250.executeDMLUpdates(UpgradeCatalog250.java:197)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:952)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
... 1 more
08 Mar 2017 04:52:27,829 INFO [main] Configuration:2906 - Reading password
from existing file
08 Mar 2017 04:52:27,863 INFO [main] Configuration:3382 - Hosts Mapping File
null
08 Mar 2017 04:52:27,864 INFO [main] HostsMap:60 - Using hostsmap file null
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20357) [Hive2] JS error in udf delete
[ https://issues.apache.org/jira/browse/AMBARI-20357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20357: - Status: Patch Available (was: Open) > [Hive2] JS error in udf delete > -- > > Key: AMBARI-20357 > URL: https://issues.apache.org/jira/browse/AMBARI-20357 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-20357-branch-2-5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20357) [Hive2] JS error in udf delete
[ https://issues.apache.org/jira/browse/AMBARI-20357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20357: - Attachment: AMBARI-20357-branch-2-5.patch > [Hive2] JS error in udf delete > -- > > Key: AMBARI-20357 > URL: https://issues.apache.org/jira/browse/AMBARI-20357 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-20357-branch-2-5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20337) Need to show timer while loading coordinator name while bundle creation
[ https://issues.apache.org/jira/browse/AMBARI-20337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Madhan Mohan Reddy updated AMBARI-20337: -- Status: Patch Available (was: In Progress) > Need to show timer while loading coordinator name while bundle creation > --- > > Key: AMBARI-20337 > URL: https://issues.apache.org/jira/browse/AMBARI-20337 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20337_trunk.patch > > > Need to show timer while loading coordinator name while bundle creation. > Issue 1 : Some times coordinator name is not fetch even after 5secs. So its > better to show timer to indicate that name is getting loaded. > Issue 2: If user provides invalid coordinator path, then appropriate error > message should be shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20349) When SPNEGO authentication is enabled for Hadoop in a cluster with NN HA, PXF Process alert fails
[
https://issues.apache.org/jira/browse/AMBARI-20349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901023#comment-15901023
]
Hadoop QA commented on AMBARI-20349:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856735/AMBARI-20349_trunk_01.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10923//console
This message is automatically generated.
> When SPNEGO authentication is enabled for Hadoop in a cluster with NN HA, PXF
> Process alert fails
> -
>
> Key: AMBARI-20349
> URL: https://issues.apache.org/jira/browse/AMBARI-20349
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: PHD, PXF, kerberos
> Fix For: 2.5.0
>
> Attachments: AMBARI-20349_branch-2.5_01.patch,
> AMBARI-20349_trunk_01.patch
>
>
> When SPNEGO authentication is enabled for Hadoop in a cluster where NN HA is
> enabled, PXF Process alert fails with the following errors in the
> ambari-agent.log file
> {noformat}
> ERROR 2017-03-07 18:03:58,417 jmx.py:44 - Getting jmx metrics from NN failed.
> URL:
> http://c6401.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesy
> stem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 41, in get_value_from_jmx
> data_dict = json.loads(data)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> INFO 2017-03-07 18:04:02,769 logger.py:71 - call['ambari-sudo.sh su hdfs -l
> -s /bin/bash -c 'curl --negotiate -u : -s
> '"'"'http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'"'"'
> 1>/tmp/tmphTXg76 2>/tmp/tmp5bm2nM''] {'quiet': False}
> INFO 2017-03-07 18:04:02,797 logger.py:71 - call returned (0, '')
> ERROR 2017-03-07 18:04:02,798 jmx.py:44 - Getting jmx metrics from NN failed.
> URL:
> http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 41, in get_value_from_jmx
> data_dict = json.loads(data)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> {noformat}
> *Cause*
> During the test for the {{PXF Process}} alert, the Active NN is found using a
> JMX call. This call requires SPNEGO authentication since SPNEGO
> authentication is turned on for the Hadoop web interfaces. However, a valid
> Kerberos ticket is not found in the configured user's Kerberos ticket cache.
> In this case, the configured users is the HDFS user - which technically is
> not necessary.
> This occurs in
> {code:title=common-services/PXF/3.0.0/package/alerts/api_status.py:137}
> if CLUSTER_ENV_SECURITY in configurations and
> configurations[CLUSTER_ENV_SECURITY].lower() == "true":
> if 'dfs.nameservices' in configurations[HDFS_SITE]:
> namenode_address =
> get_active_namenode(ConfigDictionary(configurations[HDFS_SITE]),
> configurations[CLUSTER_ENV_SECURITY], configurations[HADOOP_ENV_HDFS_USER])[1]
> else:
> namenode_address =
> configurations[HDFS_SITE]['dfs.namenode.http-address']
> token = _get_delegation_token(namenode_address,
> configurations[HADOOP_ENV_HDFS_USER],
>
> configurations[HADOOP_ENV_HDFS_USER_KEYTAB],
>
> configurations[HADOOP_ENV_HDFS_PRINCIPAL_NAME],
> None)
> commonPXFHeaders.update({"X-GP-TOKEN": token})
> {code}
>
[jira] [Updated] (AMBARI-20337) Need to show timer while loading coordinator name while bundle creation
[ https://issues.apache.org/jira/browse/AMBARI-20337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Madhan Mohan Reddy updated AMBARI-20337: -- Attachment: AMBARI-20337_trunk.patch > Need to show timer while loading coordinator name while bundle creation > --- > > Key: AMBARI-20337 > URL: https://issues.apache.org/jira/browse/AMBARI-20337 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20337_trunk.patch > > > Need to show timer while loading coordinator name while bundle creation. > Issue 1 : Some times coordinator name is not fetch even after 5secs. So its > better to show timer to indicate that name is getting loaded. > Issue 2: If user provides invalid coordinator path, then appropriate error > message should be shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20355) WFM. Import/Export asset label changes.
[ https://issues.apache.org/jira/browse/AMBARI-20355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901019#comment-15901019 ] Hudson commented on AMBARI-20355: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6970 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6970/]) AMBARI-20355 : WFM view : Import/Export asset label changes(Venkata (nitiraj.rathore: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=769fb723a86971c2b825e42f19e31e71a51e0b6b]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/flow-designer.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-actions.hbs > WFM. Import/Export asset label changes. > --- > > Key: AMBARI-20355 > URL: https://issues.apache.org/jira/browse/AMBARI-20355 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20355_branch-2.5.patch > > > This is to happen on both on clicking on transition or on action node. > Original > Import Asset > Import Assets to HDFS > Publish Asset > Publish Asset to HDFS > Can we change it to: > Import Asset from Local Ambari Database > Import Asset from Shared File System > Save Asset to Local Ambari Database > Save Asset to Shared File System > Workflow menu label "Import from HDFS" should be changed to "Import from > Shared File System" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20355) WFM. Import/Export asset label changes.
[ https://issues.apache.org/jira/browse/AMBARI-20355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901016#comment-15901016 ] Hudson commented on AMBARI-20355: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1206 (See [https://builds.apache.org/job/Ambari-branch-2.5/1206/]) AMBARI-20355 : WFM view : Import/Export asset label changes(Venkata (nitiraj.rathore: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f66a663ad9722d808a1b656939fab9a7ae269d17]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/flow-designer.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-actions.hbs > WFM. Import/Export asset label changes. > --- > > Key: AMBARI-20355 > URL: https://issues.apache.org/jira/browse/AMBARI-20355 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20355_branch-2.5.patch > > > This is to happen on both on clicking on transition or on action node. > Original > Import Asset > Import Assets to HDFS > Publish Asset > Publish Asset to HDFS > Can we change it to: > Import Asset from Local Ambari Database > Import Asset from Shared File System > Save Asset to Local Ambari Database > Save Asset to Shared File System > Workflow menu label "Import from HDFS" should be changed to "Import from > Shared File System" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20352) WFM: Page numbers on workflow dashboard are not calculated correctly
[
https://issues.apache.org/jira/browse/AMBARI-20352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900997#comment-15900997
]
Hadoop QA commented on AMBARI-20352:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856760/AMBARI-20352.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10922//console
This message is automatically generated.
> WFM: Page numbers on workflow dashboard are not calculated correctly
>
>
> Key: AMBARI-20352
> URL: https://issues.apache.org/jira/browse/AMBARI-20352
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: trunk, 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-20352.patch, WFMDashboardPageNum.jpg
>
>
> When the number of workflows exceeds 15, you can see additional pages in the
> workflow dashboard.
> The pag number calculation is not correct. On page 2, the page number is
> displayed as 1.665 (see attachment)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20353) Log error while importing the workflow from encrypted path
[
https://issues.apache.org/jira/browse/AMBARI-20353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900984#comment-15900984
]
Hadoop QA commented on AMBARI-20353:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856765/AMBARI-20353_trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10921//console
This message is automatically generated.
> Log error while importing the workflow from encrypted path
> --
>
> Key: AMBARI-20353
> URL: https://issues.apache.org/jira/browse/AMBARI-20353
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20353_trunk.patch
>
>
> Facing issue while importing workflow where api
> /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/WFM/resources/proxy/readWorkflow?workflowPath=/tmp/encrypt/workflow.xml=WORKFLOW
> is failing with 500 status code.
> Steps to reproduce :
> Try to import workflow /tmp/encrypt/workflow.xml and its failing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-20355) WFM. Import/Export asset label changes.
[ https://issues.apache.org/jira/browse/AMBARI-20355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore resolved AMBARI-20355. Resolution: Fixed committed to branch-2.5 and trunk > WFM. Import/Export asset label changes. > --- > > Key: AMBARI-20355 > URL: https://issues.apache.org/jira/browse/AMBARI-20355 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20355_branch-2.5.patch > > > This is to happen on both on clicking on transition or on action node. > Original > Import Asset > Import Assets to HDFS > Publish Asset > Publish Asset to HDFS > Can we change it to: > Import Asset from Local Ambari Database > Import Asset from Shared File System > Save Asset to Local Ambari Database > Save Asset to Shared File System > Workflow menu label "Import from HDFS" should be changed to "Import from > Shared File System" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20356) description incorrect for result class
[ https://issues.apache.org/jira/browse/AMBARI-20356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-20356: Description: ambari-server/src/main/java/org/apache/ambari/server/api/services/Result.java "the results of the request a a Tree structure" should be "the results of the request as a Tree structure" > description incorrect for result class > --- > > Key: AMBARI-20356 > URL: https://issues.apache.org/jira/browse/AMBARI-20356 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-20356.patch, ambari.png > > > ambari-server/src/main/java/org/apache/ambari/server/api/services/Result.java > > "the results of the request a a Tree structure" should be "the results of the > request as a Tree structure" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20356) description incorrect for result class
[ https://issues.apache.org/jira/browse/AMBARI-20356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-20356: Attachment: ambari.png > description incorrect for result class > --- > > Key: AMBARI-20356 > URL: https://issues.apache.org/jira/browse/AMBARI-20356 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-20356.patch, ambari.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20356) description incorrect for result class
[ https://issues.apache.org/jira/browse/AMBARI-20356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-20356: Attachment: AMBARI-20356.patch > description incorrect for result class > --- > > Key: AMBARI-20356 > URL: https://issues.apache.org/jira/browse/AMBARI-20356 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-20356.patch, ambari.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20356) description incorrect for result class
[ https://issues.apache.org/jira/browse/AMBARI-20356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-20356: Component/s: ambari-server > description incorrect for result class > --- > > Key: AMBARI-20356 > URL: https://issues.apache.org/jira/browse/AMBARI-20356 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20356) description incorrect for result class
wangyaoxin created AMBARI-20356: --- Summary: description incorrect for result class Key: AMBARI-20356 URL: https://issues.apache.org/jira/browse/AMBARI-20356 Project: Ambari Issue Type: Improvement Reporter: wangyaoxin Assignee: wangyaoxin Fix For: trunk -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20355) WFM. Import/Export asset label changes.
[ https://issues.apache.org/jira/browse/AMBARI-20355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-20355: Attachment: AMBARI-20355_branch-2.5.patch > WFM. Import/Export asset label changes. > --- > > Key: AMBARI-20355 > URL: https://issues.apache.org/jira/browse/AMBARI-20355 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20355_branch-2.5.patch > > > This is to happen on both on clicking on transition or on action node. > Original > Import Asset > Import Assets to HDFS > Publish Asset > Publish Asset to HDFS > Can we change it to: > Import Asset from Local Ambari Database > Import Asset from Shared File System > Save Asset to Local Ambari Database > Save Asset to Shared File System > Workflow menu label "Import from HDFS" should be changed to "Import from > Shared File System" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
