[jira] [Commented] (AMBARI-19531) Ambari Hive View 'userhome' check fails when username is all numeric
[ https://issues.apache.org/jira/browse/AMBARI-19531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875553#comment-15875553 ] Xiaolu Zhao commented on AMBARI-19531: -- Ambari-view 2.4.1 Hive View 1.0 & Hive View 1.5 Found the same issue when username begins with numerical value. e.g. username: 1702smith, Ambari Hive View fails 'userhome' check though home directory exists and is properly owned by the user. Username begins with alphabet characters has no problem. Stack trace will show the following error: Service 'userhome' check failed: java.lang.IllegalArgumentException: Invalid value: "1702smith" does not belong to the domain ^[A-Za-z_][A-Za-z0-9._-]*[$]?$ at org.apache.hadoop.hdfs.web.resources.StringParam$Domain.parse(StringParam.java:53) at org.apache.hadoop.hdfs.web.resources.StringParam.(StringParam.java:25) at org.apache.hadoop.hdfs.web.resources.UserParam.(UserParam.java:68) at org.apache.hadoop.hdfs.web.resources.UserParam.(UserParam.java:75) An old issue on WebHDFS has similar problem in the past, see https://issues.apache.org/jira/browse/HDFS-4983 > Ambari Hive View 'userhome' check fails when username is all numeric > > > Key: AMBARI-19531 > URL: https://issues.apache.org/jira/browse/AMBARI-19531 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.1 > Environment: HDP 2.4.2 >Reporter: Hari Sekhon > Attachments: Ambari_Hive_View_UserID_invalid_value.png > > > Ambari Hive View does not expect all numeric username and fails 'userhome' > check even though the home directory exists and is properly owned by the user > because the regex does not have numbers permitted in the first char. > Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20086) Hive View 2.0: Code Refactoring. Removal of the database cache
[ https://issues.apache.org/jira/browse/AMBARI-20086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-20086: -- Attachment: AMBARI-20086.branch-2.5.patch > Hive View 2.0: Code Refactoring. Removal of the database cache > -- > > Key: AMBARI-20086 > URL: https://issues.apache.org/jira/browse/AMBARI-20086 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20086.branch-2.5.patch > > > The database cache was created to enable sending partial notification of > database, table changes when the artifacts were created and removed. But the > partial notification later on did not materialize because of Ambari not > supporting SSE or Websockets. Hence the code refactoring is required to > remove the unneeded code. > Options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20086) Hive View 2.0: Code Refactoring. Removal of the database cache
[ https://issues.apache.org/jira/browse/AMBARI-20086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-20086: -- Status: Patch Available (was: Open) > Hive View 2.0: Code Refactoring. Removal of the database cache > -- > > Key: AMBARI-20086 > URL: https://issues.apache.org/jira/browse/AMBARI-20086 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20086.branch-2.5.patch > > > The database cache was created to enable sending partial notification of > database, table changes when the artifacts were created and removed. But the > partial notification later on did not materialize because of Ambari not > supporting SSE or Websockets. Hence the code refactoring is required to > remove the unneeded code. > Options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20086) Hive View 2.0: Code Refactoring. Removal of the database cache
DIPAYAN BHOWMICK created AMBARI-20086: - Summary: Hive View 2.0: Code Refactoring. Removal of the database cache Key: AMBARI-20086 URL: https://issues.apache.org/jira/browse/AMBARI-20086 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: DIPAYAN BHOWMICK Assignee: DIPAYAN BHOWMICK Fix For: 2.5.0 The database cache was created to enable sending partial notification of database, table changes when the artifacts were created and removed. But the partial notification later on did not materialize because of Ambari not supporting SSE or Websockets. Hence the code refactoring is required to remove the unneeded code. Options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20084) Cut Node feature is broken in workflow manager
[
https://issues.apache.org/jira/browse/AMBARI-20084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padma Priya Nagaraj updated AMBARI-20084:
-
Status: Patch Available (was: Open)
> Cut Node feature is broken in workflow manager
> --
>
> Key: AMBARI-20084
> URL: https://issues.apache.org/jira/browse/AMBARI-20084
> 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-20084_trunk.patch
>
>
> Cut Node feature is broken in workflow manager. While cutting the node I am
> seeing below error in UI console.
> {code}
> TypeError: t is undefined
> d<.deleteNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:9
> e.default<.deleteWorkflowNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
> e.default<.cutNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
> a<._addEvents/<()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:8
> J.event.dispatch()
> vendor-415a6fd6db11ecd27aa07f5115312174.js:4
> J.event.add/g.handle()
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20084) Cut Node feature is broken in workflow manager
[
https://issues.apache.org/jira/browse/AMBARI-20084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padma Priya Nagaraj updated AMBARI-20084:
-
Attachment: AMBARI-20084_trunk.patch
> Cut Node feature is broken in workflow manager
> --
>
> Key: AMBARI-20084
> URL: https://issues.apache.org/jira/browse/AMBARI-20084
> 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-20084_trunk.patch
>
>
> Cut Node feature is broken in workflow manager. While cutting the node I am
> seeing below error in UI console.
> {code}
> TypeError: t is undefined
> d<.deleteNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:9
> e.default<.deleteWorkflowNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
> e.default<.cutNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
> a<._addEvents/<()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:8
> J.event.dispatch()
> vendor-415a6fd6db11ecd27aa07f5115312174.js:4
> J.event.add/g.handle()
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-20084) Cut Node feature is broken in workflow manager
[
https://issues.apache.org/jira/browse/AMBARI-20084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padma Priya Nagaraj reassigned AMBARI-20084:
Assignee: Padma Priya Nagaraj
> Cut Node feature is broken in workflow manager
> --
>
> Key: AMBARI-20084
> URL: https://issues.apache.org/jira/browse/AMBARI-20084
> 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
>
>
> Cut Node feature is broken in workflow manager. While cutting the node I am
> seeing below error in UI console.
> {code}
> TypeError: t is undefined
> d<.deleteNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:9
> e.default<.deleteWorkflowNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
> e.default<.cutNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
> a<._addEvents/<()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:8
> J.event.dispatch()
> vendor-415a6fd6db11ecd27aa07f5115312174.js:4
> J.event.add/g.handle()
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20085) Confusing AMS collector heap size validation loop
[
https://issues.apache.org/jira/browse/AMBARI-20085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875299#comment-15875299
]
Hadoop QA commented on AMBARI-20085:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853582/AMBARI-20085.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10660//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10660//console
This message is automatically generated.
> Confusing AMS collector heap size validation loop
> -
>
> Key: AMBARI-20085
> URL: https://issues.apache.org/jira/browse/AMBARI-20085
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20085.patch
>
>
> Upon clicking Next on Customize Services page of Install Wizard, stack
> advisor reports validation errors.
> It showed a warning on metrics_collector_size, that it should be 8704MB.
> So I hit cancel and set it to 8704MB.
> Upon hitting Next, now it showed a warning saying metrics_collector_size
> should instead be 10880MB.
> So I hit cancel again and set it to 10880MB.
> Upon hitting Next, now it showed a warning saying metrics_collector_size
> should instead be 12544MB.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20057) "NodeManagers Status" value is empty in Yarn Summary page
[
https://issues.apache.org/jira/browse/AMBARI-20057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875264#comment-15875264
]
Hadoop QA commented on AMBARI-20057:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853580/AMBARI-20057.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10659//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10659//console
This message is automatically generated.
> "NodeManagers Status" value is empty in Yarn Summary page
> -
>
> Key: AMBARI-20057
> URL: https://issues.apache.org/jira/browse/AMBARI-20057
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Reporter: Yesha Vora
>Assignee: Antonenko Alexander
> Attachments: AMBARI-20057.patch, Screen Shot 2017-02-16 at 1.36.27
> PM.png
>
>
> The value of "NodeManagers Status" is empty in Yarn Summary page. It should
> have printed node manager status such as "3 live/0 dead/0 decommissioned".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20055) Add Upgrade Logic For Removal of clusterconfigmapping
[
https://issues.apache.org/jira/browse/AMBARI-20055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875238#comment-15875238
]
Hadoop QA commented on AMBARI-20055:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853615/AMBARI-20055.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10658//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10658//console
This message is automatically generated.
> Add Upgrade Logic For Removal of clusterconfigmapping
> -
>
> Key: AMBARI-20055
> URL: https://issues.apache.org/jira/browse/AMBARI-20055
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-20055.patch
>
>
> The Ambari upgrade scripts should now perform the following operations:
> - Adding the following columns / constraints to the {{clusterconfig}} table:
> -- {{selected SMALLINT NOT NULL DEFAULT 0}} - whether or not the
> configuration is currently selected
> -- {{selected_timestamp BIGINT NOT NULL DEFAULT 0}} - the last time that the
> configuration was marked as {{selected}}
> - Finding all {{selected}} mappings in {{clusterconfigmapping}} and marked
> their associated entry in {{clusterconfig}} as {{selected}}
> - Removal of the {{clusterconfigmapping}} table.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20069) hive.enforce.bucketing=true
[ https://issues.apache.org/jira/browse/AMBARI-20069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875228#comment-15875228 ] Hudson commented on AMBARI-20069: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6790 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6790/]) AMBARI-20069. hive.enforce.bucketing=true.(vbrodetskyi) (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=60aaaeab5e2e9c7581f982525950bf6290db3018]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml > hive.enforce.bucketing=true > --- > > Key: AMBARI-20069 > URL: https://issues.apache.org/jira/browse/AMBARI-20069 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-upgrade >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20069.patch > > > 1) set the value to be always true > 2) add HDP upgrade pack changes to set it to true when going to > HDP-2.3/2.4/2.5/2.6 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20069) hive.enforce.bucketing=true
[ https://issues.apache.org/jira/browse/AMBARI-20069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875218#comment-15875218 ] Hudson commented on AMBARI-20069: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1037 (See [https://builds.apache.org/job/Ambari-branch-2.5/1037/]) AMBARI-20069. hive.enforce.bucketing=true.(vbrodetskyi) (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5e8f9dc3d47f15d157f24dfc67c47b7488b5535f]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml > hive.enforce.bucketing=true > --- > > Key: AMBARI-20069 > URL: https://issues.apache.org/jira/browse/AMBARI-20069 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-upgrade >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20069.patch > > > 1) set the value to be always true > 2) add HDP upgrade pack changes to set it to true when going to > HDP-2.3/2.4/2.5/2.6 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20069) hive.enforce.bucketing=true
[ https://issues.apache.org/jira/browse/AMBARI-20069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-20069: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > hive.enforce.bucketing=true > --- > > Key: AMBARI-20069 > URL: https://issues.apache.org/jira/browse/AMBARI-20069 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-upgrade >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20069.patch > > > 1) set the value to be always true > 2) add HDP upgrade pack changes to set it to true when going to > HDP-2.3/2.4/2.5/2.6 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20055) Add Upgrade Logic For Removal of clusterconfigmapping
[
https://issues.apache.org/jira/browse/AMBARI-20055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20055:
-
Status: Patch Available (was: Open)
> Add Upgrade Logic For Removal of clusterconfigmapping
> -
>
> Key: AMBARI-20055
> URL: https://issues.apache.org/jira/browse/AMBARI-20055
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-20055.patch
>
>
> The Ambari upgrade scripts should now perform the following operations:
> - Adding the following columns / constraints to the {{clusterconfig}} table:
> -- {{selected SMALLINT NOT NULL DEFAULT 0}} - whether or not the
> configuration is currently selected
> -- {{selected_timestamp BIGINT NOT NULL DEFAULT 0}} - the last time that the
> configuration was marked as {{selected}}
> - Finding all {{selected}} mappings in {{clusterconfigmapping}} and marked
> their associated entry in {{clusterconfig}} as {{selected}}
> - Removal of the {{clusterconfigmapping}} table.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20055) Add Upgrade Logic For Removal of clusterconfigmapping
[
https://issues.apache.org/jira/browse/AMBARI-20055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20055:
-
Attachment: AMBARI-20055.patch
> Add Upgrade Logic For Removal of clusterconfigmapping
> -
>
> Key: AMBARI-20055
> URL: https://issues.apache.org/jira/browse/AMBARI-20055
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-20055.patch
>
>
> The Ambari upgrade scripts should now perform the following operations:
> - Adding the following columns / constraints to the {{clusterconfig}} table:
> -- {{selected SMALLINT NOT NULL DEFAULT 0}} - whether or not the
> configuration is currently selected
> -- {{selected_timestamp BIGINT NOT NULL DEFAULT 0}} - the last time that the
> configuration was marked as {{selected}}
> - Finding all {{selected}} mappings in {{clusterconfigmapping}} and marked
> their associated entry in {{clusterconfig}} as {{selected}}
> - Removal of the {{clusterconfigmapping}} table.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-20057) "NodeManagers Status" value is empty in Yarn Summary page
[ https://issues.apache.org/jira/browse/AMBARI-20057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874954#comment-15874954 ] Antonenko Alexander edited comment on AMBARI-20057 at 2/20/17 6:59 PM: --- pushed to 2.5 and trunk was (Author: aantonenko): pushed to 2.5 and master > "NodeManagers Status" value is empty in Yarn Summary page > - > > Key: AMBARI-20057 > URL: https://issues.apache.org/jira/browse/AMBARI-20057 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Yesha Vora >Assignee: Antonenko Alexander > Attachments: AMBARI-20057.patch, Screen Shot 2017-02-16 at 1.36.27 > PM.png > > > The value of "NodeManagers Status" is empty in Yarn Summary page. It should > have printed node manager status such as "3 live/0 dead/0 decommissioned". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20055) Add Upgrade Logic For Removal of clusterconfigmapping
[
https://issues.apache.org/jira/browse/AMBARI-20055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20055:
-
Description:
The Ambari upgrade scripts should now perform the following operations:
- Adding the following columns / constraints to the {{clusterconfig}} table:
-- {{selected SMALLINT NOT NULL DEFAULT 0}} - whether or not the configuration
is currently selected
-- {{selected_timestamp BIGINT NOT NULL DEFAULT 0}} - the last time that the
configuration was marked as {{selected}}
- Finding all {{selected}} mappings in {{clusterconfigmapping}} and marked
their associated entry in {{clusterconfig}} as {{selected}}
- Removal of the {{clusterconfigmapping}} table.
was:
The Ambari upgrade scripts should now perform the following operations:
- Adding the following columns / constraints to the {{clusterconfig}} table:
-- {{selected SMALLINT NOT NULL DEFAULT 0}} - whether or not the configuration
is currently selected
-- {{selected_timestamp BIGINT NOT NULL DEFAULT 0}} - the last time that the
configuration was marked as {{selected}}
-- A constraint preventing the same type to have more than 1 selected rows
- Finding all {{selected}} mappings in {{clusterconfigmapping}} and marked
their associated entry in {{clusterconfig}} as {{selected}}
- Removal of the {{clusterconfigmapping}} table.
> Add Upgrade Logic For Removal of clusterconfigmapping
> -
>
> Key: AMBARI-20055
> URL: https://issues.apache.org/jira/browse/AMBARI-20055
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
>
> The Ambari upgrade scripts should now perform the following operations:
> - Adding the following columns / constraints to the {{clusterconfig}} table:
> -- {{selected SMALLINT NOT NULL DEFAULT 0}} - whether or not the
> configuration is currently selected
> -- {{selected_timestamp BIGINT NOT NULL DEFAULT 0}} - the last time that the
> configuration was marked as {{selected}}
> - Finding all {{selected}} mappings in {{clusterconfigmapping}} and marked
> their associated entry in {{clusterconfig}} as {{selected}}
> - Removal of the {{clusterconfigmapping}} table.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20057) "NodeManagers Status" value is empty in Yarn Summary page
[ https://issues.apache.org/jira/browse/AMBARI-20057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874954#comment-15874954 ] Antonenko Alexander commented on AMBARI-20057: -- pushed to 2.5 and master > "NodeManagers Status" value is empty in Yarn Summary page > - > > Key: AMBARI-20057 > URL: https://issues.apache.org/jira/browse/AMBARI-20057 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Yesha Vora >Assignee: Antonenko Alexander > Attachments: AMBARI-20057.patch, Screen Shot 2017-02-16 at 1.36.27 > PM.png > > > The value of "NodeManagers Status" is empty in Yarn Summary page. It should > have printed node manager status such as "3 live/0 dead/0 decommissioned". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20057) "NodeManagers Status" value is empty in Yarn Summary page
[
https://issues.apache.org/jira/browse/AMBARI-20057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874875#comment-15874875
]
Hadoop QA commented on AMBARI-20057:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853580/AMBARI-20057.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10657//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10657//console
This message is automatically generated.
> "NodeManagers Status" value is empty in Yarn Summary page
> -
>
> Key: AMBARI-20057
> URL: https://issues.apache.org/jira/browse/AMBARI-20057
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Reporter: Yesha Vora
>Assignee: Antonenko Alexander
> Attachments: AMBARI-20057.patch, Screen Shot 2017-02-16 at 1.36.27
> PM.png
>
>
> The value of "NodeManagers Status" is empty in Yarn Summary page. It should
> have printed node manager status such as "3 live/0 dead/0 decommissioned".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20083) Grafana Dashboard for Log Search
[
https://issues.apache.org/jira/browse/AMBARI-20083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874844#comment-15874844
]
Hadoop QA commented on AMBARI-20083:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853561/AMBARI-20083.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10656//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10656//console
This message is automatically generated.
> Grafana Dashboard for Log Search
>
>
> Key: AMBARI-20083
> URL: https://issues.apache.org/jira/browse/AMBARI-20083
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-20083.patch
>
>
> Add a Grafana dashboard for the Log Search Service.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20085) Confusing AMS collector heap size validation loop
[ https://issues.apache.org/jira/browse/AMBARI-20085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-20085: Status: Patch Available (was: Open) > Confusing AMS collector heap size validation loop > - > > Key: AMBARI-20085 > URL: https://issues.apache.org/jira/browse/AMBARI-20085 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20085.patch > > > Upon clicking Next on Customize Services page of Install Wizard, stack > advisor reports validation errors. > It showed a warning on metrics_collector_size, that it should be 8704MB. > So I hit cancel and set it to 8704MB. > Upon hitting Next, now it showed a warning saying metrics_collector_size > should instead be 10880MB. > So I hit cancel again and set it to 10880MB. > Upon hitting Next, now it showed a warning saying metrics_collector_size > should instead be 12544MB. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20057) "NodeManagers Status" value is empty in Yarn Summary page
[ https://issues.apache.org/jira/browse/AMBARI-20057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874816#comment-15874816 ] Aleksandr Kovalenko commented on AMBARI-20057: -- +1 for the patch > "NodeManagers Status" value is empty in Yarn Summary page > - > > Key: AMBARI-20057 > URL: https://issues.apache.org/jira/browse/AMBARI-20057 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Yesha Vora >Assignee: Antonenko Alexander > Attachments: AMBARI-20057.patch, Screen Shot 2017-02-16 at 1.36.27 > PM.png > > > The value of "NodeManagers Status" is empty in Yarn Summary page. It should > have printed node manager status such as "3 live/0 dead/0 decommissioned". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20085) Confusing AMS collector heap size validation loop
[ https://issues.apache.org/jira/browse/AMBARI-20085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-20085: Attachment: AMBARI-20085.patch > Confusing AMS collector heap size validation loop > - > > Key: AMBARI-20085 > URL: https://issues.apache.org/jira/browse/AMBARI-20085 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20085.patch > > > Upon clicking Next on Customize Services page of Install Wizard, stack > advisor reports validation errors. > It showed a warning on metrics_collector_size, that it should be 8704MB. > So I hit cancel and set it to 8704MB. > Upon hitting Next, now it showed a warning saying metrics_collector_size > should instead be 10880MB. > So I hit cancel again and set it to 10880MB. > Upon hitting Next, now it showed a warning saying metrics_collector_size > should instead be 12544MB. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20085) Confusing AMS collector heap size validation loop
Dmytro Sen created AMBARI-20085: --- Summary: Confusing AMS collector heap size validation loop Key: AMBARI-20085 URL: https://issues.apache.org/jira/browse/AMBARI-20085 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.5.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.5.0 Upon clicking Next on Customize Services page of Install Wizard, stack advisor reports validation errors. It showed a warning on metrics_collector_size, that it should be 8704MB. So I hit cancel and set it to 8704MB. Upon hitting Next, now it showed a warning saying metrics_collector_size should instead be 10880MB. So I hit cancel again and set it to 10880MB. Upon hitting Next, now it showed a warning saying metrics_collector_size should instead be 12544MB. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20057) "NodeManagers Status" value is empty in Yarn Summary page
[ https://issues.apache.org/jira/browse/AMBARI-20057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-20057: - Status: Patch Available (was: Open) > "NodeManagers Status" value is empty in Yarn Summary page > - > > Key: AMBARI-20057 > URL: https://issues.apache.org/jira/browse/AMBARI-20057 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Yesha Vora >Assignee: Antonenko Alexander > Attachments: AMBARI-20057.patch, Screen Shot 2017-02-16 at 1.36.27 > PM.png > > > The value of "NodeManagers Status" is empty in Yarn Summary page. It should > have printed node manager status such as "3 live/0 dead/0 decommissioned". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20057) "NodeManagers Status" value is empty in Yarn Summary page
[ https://issues.apache.org/jira/browse/AMBARI-20057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-20057: - Attachment: AMBARI-20057.patch > "NodeManagers Status" value is empty in Yarn Summary page > - > > Key: AMBARI-20057 > URL: https://issues.apache.org/jira/browse/AMBARI-20057 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Yesha Vora >Assignee: Antonenko Alexander > Attachments: AMBARI-20057.patch, Screen Shot 2017-02-16 at 1.36.27 > PM.png > > > The value of "NodeManagers Status" is empty in Yarn Summary page. It should > have printed node manager status such as "3 live/0 dead/0 decommissioned". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20069) hive.enforce.bucketing=true
[
https://issues.apache.org/jira/browse/AMBARI-20069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874803#comment-15874803
]
Hadoop QA commented on AMBARI-20069:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853568/AMBARI-20069.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10655//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10655//console
This message is automatically generated.
> hive.enforce.bucketing=true
> ---
>
> Key: AMBARI-20069
> URL: https://issues.apache.org/jira/browse/AMBARI-20069
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20069.patch
>
>
> 1) set the value to be always true
> 2) add HDP upgrade pack changes to set it to true when going to
> HDP-2.3/2.4/2.5/2.6
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-20057) "NodeManagers Status" value is empty in Yarn Summary page
[ https://issues.apache.org/jira/browse/AMBARI-20057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-20057: Assignee: Antonenko Alexander > "NodeManagers Status" value is empty in Yarn Summary page > - > > Key: AMBARI-20057 > URL: https://issues.apache.org/jira/browse/AMBARI-20057 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Yesha Vora >Assignee: Antonenko Alexander > Attachments: Screen Shot 2017-02-16 at 1.36.27 PM.png > > > The value of "NodeManagers Status" is empty in Yarn Summary page. It should > have printed node manager status such as "3 live/0 dead/0 decommissioned". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20084) Cut Node feature is broken in workflow manager
Supreeth Sharma created AMBARI-20084:
Summary: Cut Node feature is broken in workflow manager
Key: AMBARI-20084
URL: https://issues.apache.org/jira/browse/AMBARI-20084
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.5.0
Reporter: Supreeth Sharma
Priority: Critical
Fix For: 2.5.0
Cut Node feature is broken in workflow manager. While cutting the node I am
seeing below error in UI console.
{code}
TypeError: t is undefined
d<.deleteNode()
oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:9
e.default<.deleteWorkflowNode()
oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
e.default<.cutNode()
oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
a<._addEvents/<()
oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:8
J.event.dispatch()
vendor-415a6fd6db11ecd27aa07f5115312174.js:4
J.event.add/g.handle()
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20047) Repository config user needs to set customized service user in Ranger when service plugin is enabled
[
https://issues.apache.org/jira/browse/AMBARI-20047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874769#comment-15874769
]
Hadoop QA commented on AMBARI-20047:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853570/AMBARI-20047.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10654//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10654//console
This message is automatically generated.
> Repository config user needs to set customized service user in Ranger when
> service plugin is enabled
>
>
> Key: AMBARI-20047
> URL: https://issues.apache.org/jira/browse/AMBARI-20047
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-20047.1.patch, AMBARI-20047.patch
>
>
> The property {{REPOSITORY_CONFIG_USERNAME}} in Advanced
> ranger-*-plugin-properties is not updated to the custom user-name when
> services are using custom users.
> This causes issues especially in cases of Test connection, and policy user
> which is given default permissions in Ranger.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20047) Repository config user needs to set customized service user in Ranger when service plugin is enabled
[
https://issues.apache.org/jira/browse/AMBARI-20047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-20047:
Attachment: AMBARI-20047.1.patch
revised code to optimize logic.
> Repository config user needs to set customized service user in Ranger when
> service plugin is enabled
>
>
> Key: AMBARI-20047
> URL: https://issues.apache.org/jira/browse/AMBARI-20047
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-20047.1.patch, AMBARI-20047.patch
>
>
> The property {{REPOSITORY_CONFIG_USERNAME}} in Advanced
> ranger-*-plugin-properties is not updated to the custom user-name when
> services are using custom users.
> This causes issues especially in cases of Test connection, and policy user
> which is given default permissions in Ranger.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20052) Spark2 service check is failing in secure cluster
[
https://issues.apache.org/jira/browse/AMBARI-20052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874712#comment-15874712
]
Hudson commented on AMBARI-20052:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6789 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6789/])
AMBARI-20052. Spark2 service check is failing in secure cluster (echekanskiy:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1ecdee0d559540204c66634871e6252d622552cd])
* (edit)
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/service_check.py
* (edit)
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/params.py
> Spark2 service check is failing in secure cluster
> -
>
> Key: AMBARI-20052
> URL: https://issues.apache.org/jira/browse/AMBARI-20052
> Project: Ambari
> Issue Type: Bug
>Reporter: Yesha Vora
>Assignee: Eugene Chekanskiy
> Attachments: AMBARI-20052.patch
>
>
> Spark2 Service check is failing in secure cluster.
> {code:title=errors-411.txt}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/service_check.py",
> line 62, in
> SparkServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 313, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/service_check.py",
> line 36, in service_check
> livy_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
> {smokeuser_principal}; ")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 571, in _vformat
> obj, arg_used = self.get_field(field_name, args, kwargs)
> File "/usr/lib64/python2.7/string.py", line 632, in get_field
> obj = self.get_value(first, args, kwargs)
> File "/usr/lib64/python2.7/string.py", line 591, in get_value
> return kwargs[key]
> File "/usr/lib/python2.6/site-packages/resource_management/core/utils.py",
> line 57, in __getitem__
> return self._convert_value(self._dict[name])
> KeyError: 'smoke_user_keytab'{code}
> {code:title=output-411.txt}
> 2017-02-16 18:52:44,887 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2017-02-16 18:52:44,904 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/spark2.headless.keytab sp...@example.com; '] {'user':
> 'spark'}
> Command failed after 1 tries{code}
> As per above logs, kinit operation failed on a host. I was able to run same
> kinit command successfully from same host manually.
> {code}
> [root@xxx ~]$ sudo su spark
> bash-4.2$ /usr/bin/kinit -kt /etc/security/keytabs/spark2.headless.keytab
> sp...@example.com
> bash-4.2$ echo $?
> 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20052) Spark2 service check is failing in secure cluster
[
https://issues.apache.org/jira/browse/AMBARI-20052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874689#comment-15874689
]
Hudson commented on AMBARI-20052:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1036 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1036/])
AMBARI-20052. Spark2 service check is failing in secure cluster (echekanskiy:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1169694ecdc77c5f317d105a0c17da6b0b806bdf])
* (edit)
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/service_check.py
> Spark2 service check is failing in secure cluster
> -
>
> Key: AMBARI-20052
> URL: https://issues.apache.org/jira/browse/AMBARI-20052
> Project: Ambari
> Issue Type: Bug
>Reporter: Yesha Vora
>Assignee: Eugene Chekanskiy
> Attachments: AMBARI-20052.patch
>
>
> Spark2 Service check is failing in secure cluster.
> {code:title=errors-411.txt}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/service_check.py",
> line 62, in
> SparkServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 313, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/service_check.py",
> line 36, in service_check
> livy_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
> {smokeuser_principal}; ")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 571, in _vformat
> obj, arg_used = self.get_field(field_name, args, kwargs)
> File "/usr/lib64/python2.7/string.py", line 632, in get_field
> obj = self.get_value(first, args, kwargs)
> File "/usr/lib64/python2.7/string.py", line 591, in get_value
> return kwargs[key]
> File "/usr/lib/python2.6/site-packages/resource_management/core/utils.py",
> line 57, in __getitem__
> return self._convert_value(self._dict[name])
> KeyError: 'smoke_user_keytab'{code}
> {code:title=output-411.txt}
> 2017-02-16 18:52:44,887 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2017-02-16 18:52:44,904 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/spark2.headless.keytab sp...@example.com; '] {'user':
> 'spark'}
> Command failed after 1 tries{code}
> As per above logs, kinit operation failed on a host. I was able to run same
> kinit command successfully from same host manually.
> {code}
> [root@xxx ~]$ sudo su spark
> bash-4.2$ /usr/bin/kinit -kt /etc/security/keytabs/spark2.headless.keytab
> sp...@example.com
> bash-4.2$ echo $?
> 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20069) hive.enforce.bucketing=true
[ https://issues.apache.org/jira/browse/AMBARI-20069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-20069: --- Attachment: AMBARI-20069.patch > hive.enforce.bucketing=true > --- > > Key: AMBARI-20069 > URL: https://issues.apache.org/jira/browse/AMBARI-20069 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-upgrade >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20069.patch > > > 1) set the value to be always true > 2) add HDP upgrade pack changes to set it to true when going to > HDP-2.3/2.4/2.5/2.6 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20069) hive.enforce.bucketing=true
[ https://issues.apache.org/jira/browse/AMBARI-20069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-20069: --- Attachment: (was: AMBARI-20069.patch) > hive.enforce.bucketing=true > --- > > Key: AMBARI-20069 > URL: https://issues.apache.org/jira/browse/AMBARI-20069 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-upgrade >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20069.patch > > > 1) set the value to be always true > 2) add HDP upgrade pack changes to set it to true when going to > HDP-2.3/2.4/2.5/2.6 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20079) Unable to filter by job id
[
https://issues.apache.org/jira/browse/AMBARI-20079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874661#comment-15874661
]
Hadoop QA commented on AMBARI-20079:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853548/AMBARI-20079_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/wfmanager/src/main/resources/ui
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10653//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10653//console
This message is automatically generated.
> Unable to filter by job id
> --
>
> Key: AMBARI-20079
> URL: https://issues.apache.org/jira/browse/AMBARI-20079
> 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-20079_trunk.patch, Screen Shot 2017-02-16.png
>
>
> After attempting to resume a random SUSPENDED existing workflow
> 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via
> hrt_qa user), the workflow went into RUNNING state. I wanted to see that
> workflow by itself on the dashboard, so I used filter criteria with the
> following syntax:
> jobid=078-170215133231623-oozie-oozi-W
> jobid:078-170215133231623-oozie-oozi-W
> The first one returned:
> Remote api failed
> The second one showed the same error message but also a perptual animated
> busy loading icon.
> I expected that if my syntax was incorrect, it would say so like "jobid:..."
> is not correct, do you mean "Job Id=" or something to that effect. Also, for
> the second case, there should be a fast fail, rather than a perpetual hanging.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20052) Spark2 service check is failing in secure cluster
[
https://issues.apache.org/jira/browse/AMBARI-20052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Chekanskiy updated AMBARI-20052:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Spark2 service check is failing in secure cluster
> -
>
> Key: AMBARI-20052
> URL: https://issues.apache.org/jira/browse/AMBARI-20052
> Project: Ambari
> Issue Type: Bug
>Reporter: Yesha Vora
>Assignee: Eugene Chekanskiy
> Attachments: AMBARI-20052.patch
>
>
> Spark2 Service check is failing in secure cluster.
> {code:title=errors-411.txt}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/service_check.py",
> line 62, in
> SparkServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 313, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/service_check.py",
> line 36, in service_check
> livy_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
> {smokeuser_principal}; ")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 571, in _vformat
> obj, arg_used = self.get_field(field_name, args, kwargs)
> File "/usr/lib64/python2.7/string.py", line 632, in get_field
> obj = self.get_value(first, args, kwargs)
> File "/usr/lib64/python2.7/string.py", line 591, in get_value
> return kwargs[key]
> File "/usr/lib/python2.6/site-packages/resource_management/core/utils.py",
> line 57, in __getitem__
> return self._convert_value(self._dict[name])
> KeyError: 'smoke_user_keytab'{code}
> {code:title=output-411.txt}
> 2017-02-16 18:52:44,887 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2017-02-16 18:52:44,904 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/spark2.headless.keytab sp...@example.com; '] {'user':
> 'spark'}
> Command failed after 1 tries{code}
> As per above logs, kinit operation failed on a host. I was able to run same
> kinit command successfully from same host manually.
> {code}
> [root@xxx ~]$ sudo su spark
> bash-4.2$ /usr/bin/kinit -kt /etc/security/keytabs/spark2.headless.keytab
> sp...@example.com
> bash-4.2$ echo $?
> 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20052) Spark2 service check is failing in secure cluster
[
https://issues.apache.org/jira/browse/AMBARI-20052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874647#comment-15874647
]
Eugene Chekanskiy commented on AMBARI-20052:
Committed to trunk and branch-2.5
f96d43c..1169694 branch-2.5 -> branch-2.5
ece4d36..1ecdee0 trunk -> trunk
> Spark2 service check is failing in secure cluster
> -
>
> Key: AMBARI-20052
> URL: https://issues.apache.org/jira/browse/AMBARI-20052
> Project: Ambari
> Issue Type: Bug
>Reporter: Yesha Vora
>Assignee: Eugene Chekanskiy
> Attachments: AMBARI-20052.patch
>
>
> Spark2 Service check is failing in secure cluster.
> {code:title=errors-411.txt}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/service_check.py",
> line 62, in
> SparkServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 313, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/service_check.py",
> line 36, in service_check
> livy_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
> {smokeuser_principal}; ")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 571, in _vformat
> obj, arg_used = self.get_field(field_name, args, kwargs)
> File "/usr/lib64/python2.7/string.py", line 632, in get_field
> obj = self.get_value(first, args, kwargs)
> File "/usr/lib64/python2.7/string.py", line 591, in get_value
> return kwargs[key]
> File "/usr/lib/python2.6/site-packages/resource_management/core/utils.py",
> line 57, in __getitem__
> return self._convert_value(self._dict[name])
> KeyError: 'smoke_user_keytab'{code}
> {code:title=output-411.txt}
> 2017-02-16 18:52:44,887 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2017-02-16 18:52:44,904 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/spark2.headless.keytab sp...@example.com; '] {'user':
> 'spark'}
> Command failed after 1 tries{code}
> As per above logs, kinit operation failed on a host. I was able to run same
> kinit command successfully from same host manually.
> {code}
> [root@xxx ~]$ sudo su spark
> bash-4.2$ /usr/bin/kinit -kt /etc/security/keytabs/spark2.headless.keytab
> sp...@example.com
> bash-4.2$ echo $?
> 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20080) WFM does not issue confirmation message when workflow is suspended or killed
[
https://issues.apache.org/jira/browse/AMBARI-20080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874606#comment-15874606
]
Hadoop QA commented on AMBARI-20080:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853550/AMBARI-20080_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/wfmanager/src/main/resources/ui
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10652//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10652//console
This message is automatically generated.
> WFM does not issue confirmation message when workflow is suspended or killed
>
>
> Key: AMBARI-20080
> URL: https://issues.apache.org/jira/browse/AMBARI-20080
> 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-20080_trunk.patch
>
>
> Steps:
> 1. log into ambari ui
> 2. go to wfm
> 3. upload workflow from file system:
> 4. submit the workflow
> 5. kill or suspend the workflow from WFM ui
> Issue:
> workflow ui is not giving any confirmation message when wf is killed or
> suspended
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20082) Wizard 'Assign Master ' step is showing inconsistent Select view
[ https://issues.apache.org/jira/browse/AMBARI-20082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874597#comment-15874597 ] Hudson commented on AMBARI-20082: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6788 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6788/]) AMBARI-20082. Wizard 'Assign Master ' step is showing inconsistent (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ece4d36cb32a0a4b60025e9d54ba4131105a794b]) * (edit) ambari-web/app/templates/common/assign_master_components.hbs * (edit) ambari-web/app/views.js * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/styles/wizard.less * (add) ambari-web/app/views/common/form/dropdown.js * (add) ambari-web/app/templates/common/form/dropdown.hbs * (edit) ambari-web/app/views/common/assign_master_components_view.js > Wizard 'Assign Master ' step is showing inconsistent Select view > > > Key: AMBARI-20082 > URL: https://issues.apache.org/jira/browse/AMBARI-20082 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 3.0.0 > > Attachments: AMBARI-20082.patch > > > In Wizard > Assign Mater step, the select host menu is not consistent with > the whole style guide. Should make it looks like a normal dropdown. > As investigated, it is impossible to customize the "Option" menu, so would > consider replacing that with dropdown button and dropdown menu. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20013) Add Solr authorization settings during LogSearch/Atlas/Ranger startup
[ https://issues.apache.org/jira/browse/AMBARI-20013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874596#comment-15874596 ] Hudson commented on AMBARI-20013: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6788 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6788/]) AMBARI-20013. Appendum - add infra-solr keytabs to atlas in HDP2.6 as (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6feb46a33ee448d25a35616c39b85144908f4ced]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/kerberos.json * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/kerberos.json > Add Solr authorization settings during LogSearch/Atlas/Ranger startup > - > > Key: AMBARI-20013 > URL: https://issues.apache.org/jira/browse/AMBARI-20013 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-20013-appendum1.patch, > AMBARI-20013-appendum2.patch, AMBARI-20013.patch > > > During ranger/logsearch/atlas startup, we need to make sure these services > have permission to access for specific collections. > Also ranger plugins should be able to write into ranger collection as well. > There will be a new solr_cloud_util function to add user-roles to solr, which > will update security.json on the zookeeper znode. > For newly added services with ranger plugins, solr will need to be restarted > to generate the correct security.json on zookeeper. > Also this task will introduce a new custom security.json which can override > that is used by default. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20013) Add Solr authorization settings during LogSearch/Atlas/Ranger startup
[ https://issues.apache.org/jira/browse/AMBARI-20013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874591#comment-15874591 ] Hudson commented on AMBARI-20013: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1035 (See [https://builds.apache.org/job/Ambari-branch-2.5/1035/]) AMBARI-20013. Appendum - add infra-solr keytabs to atlas in HDP2.6 as (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f96d43cccef9b25f9162e067cf66580539119802]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/kerberos.json * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/kerberos.json > Add Solr authorization settings during LogSearch/Atlas/Ranger startup > - > > Key: AMBARI-20013 > URL: https://issues.apache.org/jira/browse/AMBARI-20013 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-20013-appendum1.patch, > AMBARI-20013-appendum2.patch, AMBARI-20013.patch > > > During ranger/logsearch/atlas startup, we need to make sure these services > have permission to access for specific collections. > Also ranger plugins should be able to write into ranger collection as well. > There will be a new solr_cloud_util function to add user-roles to solr, which > will update security.json on the zookeeper znode. > For newly added services with ranger plugins, solr will need to be restarted > to generate the correct security.json on zookeeper. > Also this task will introduce a new custom security.json which can override > that is used by default. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20082) Wizard 'Assign Master ' step is showing inconsistent Select view
[
https://issues.apache.org/jira/browse/AMBARI-20082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874561#comment-15874561
]
Hadoop QA commented on AMBARI-20082:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853554/AMBARI-20082.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10651//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10651//console
This message is automatically generated.
> Wizard 'Assign Master ' step is showing inconsistent Select view
>
>
> Key: AMBARI-20082
> URL: https://issues.apache.org/jira/browse/AMBARI-20082
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20082.patch
>
>
> In Wizard > Assign Mater step, the select host menu is not consistent with
> the whole style guide. Should make it looks like a normal dropdown.
> As investigated, it is impossible to customize the "Option" menu, so would
> consider replacing that with dropdown button and dropdown menu.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20083) Grafana Dashboard for Log Search
[ https://issues.apache.org/jira/browse/AMBARI-20083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-20083: Status: Patch Available (was: In Progress) > Grafana Dashboard for Log Search > > > Key: AMBARI-20083 > URL: https://issues.apache.org/jira/browse/AMBARI-20083 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-20083.patch > > > Add a Grafana dashboard for the Log Search Service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20083) Grafana Dashboard for Log Search
[ https://issues.apache.org/jira/browse/AMBARI-20083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-20083: Attachment: AMBARI-20083.patch > Grafana Dashboard for Log Search > > > Key: AMBARI-20083 > URL: https://issues.apache.org/jira/browse/AMBARI-20083 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-20083.patch > > > Add a Grafana dashboard for the Log Search Service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20082) Wizard 'Assign Master ' step is showing inconsistent Select view
[ https://issues.apache.org/jira/browse/AMBARI-20082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20082: - Resolution: Fixed Status: Resolved (was: Patch Available) > Wizard 'Assign Master ' step is showing inconsistent Select view > > > Key: AMBARI-20082 > URL: https://issues.apache.org/jira/browse/AMBARI-20082 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 3.0.0 > > Attachments: AMBARI-20082.patch > > > In Wizard > Assign Mater step, the select host menu is not consistent with > the whole style guide. Should make it looks like a normal dropdown. > As investigated, it is impossible to customize the "Option" menu, so would > consider replacing that with dropdown button and dropdown menu. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20082) Wizard 'Assign Master ' step is showing inconsistent Select view
[ https://issues.apache.org/jira/browse/AMBARI-20082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874543#comment-15874543 ] Aleksandr Kovalenko commented on AMBARI-20082: -- committed to trunk > Wizard 'Assign Master ' step is showing inconsistent Select view > > > Key: AMBARI-20082 > URL: https://issues.apache.org/jira/browse/AMBARI-20082 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 3.0.0 > > Attachments: AMBARI-20082.patch > > > In Wizard > Assign Mater step, the select host menu is not consistent with > the whole style guide. Should make it looks like a normal dropdown. > As investigated, it is impossible to customize the "Option" menu, so would > consider replacing that with dropdown button and dropdown menu. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20013) Add Solr authorization settings during LogSearch/Atlas/Ranger startup
[
https://issues.apache.org/jira/browse/AMBARI-20013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874541#comment-15874541
]
Olivér Szabó commented on AMBARI-20013:
---
applied appendum 2 to
trunk:
{code:java}
commit 6feb46a33ee448d25a35616c39b85144908f4ced
Author: oleewere
Date: Mon Feb 20 14:33:01 2017 +0100
AMBARI-20013. Appendum - add infra-solr keytabs to atlas in HDP2.6 as well
(oleewere)
{code}
branch-2.5:
{code:java}
commit f96d43cccef9b25f9162e067cf66580539119802
Author: oleewere
Date: Mon Feb 20 14:33:01 2017 +0100
AMBARI-20013. Appendum - add infra-solr keytabs to atlas in HDP2.6 as well
(oleewere)
{code}
> Add Solr authorization settings during LogSearch/Atlas/Ranger startup
> -
>
> Key: AMBARI-20013
> URL: https://issues.apache.org/jira/browse/AMBARI-20013
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-20013-appendum1.patch,
> AMBARI-20013-appendum2.patch, AMBARI-20013.patch
>
>
> During ranger/logsearch/atlas startup, we need to make sure these services
> have permission to access for specific collections.
> Also ranger plugins should be able to write into ranger collection as well.
> There will be a new solr_cloud_util function to add user-roles to solr, which
> will update security.json on the zookeeper znode.
> For newly added services with ranger plugins, solr will need to be restarted
> to generate the correct security.json on zookeeper.
> Also this task will introduce a new custom security.json which can override
> that is used by default.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20083) Grafana Dashboard for Log Search
Miklos Gergely created AMBARI-20083: --- Summary: Grafana Dashboard for Log Search Key: AMBARI-20083 URL: https://issues.apache.org/jira/browse/AMBARI-20083 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.5.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 2.5.0 Add a Grafana dashboard for the Log Search Service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20013) Add Solr authorization settings during LogSearch/Atlas/Ranger startup
[ https://issues.apache.org/jira/browse/AMBARI-20013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-20013: -- Attachment: AMBARI-20013-appendum2.patch > Add Solr authorization settings during LogSearch/Atlas/Ranger startup > - > > Key: AMBARI-20013 > URL: https://issues.apache.org/jira/browse/AMBARI-20013 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-20013-appendum1.patch, > AMBARI-20013-appendum2.patch, AMBARI-20013.patch > > > During ranger/logsearch/atlas startup, we need to make sure these services > have permission to access for specific collections. > Also ranger plugins should be able to write into ranger collection as well. > There will be a new solr_cloud_util function to add user-roles to solr, which > will update security.json on the zookeeper znode. > For newly added services with ranger plugins, solr will need to be restarted > to generate the correct security.json on zookeeper. > Also this task will introduce a new custom security.json which can override > that is used by default. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20013) Add Solr authorization settings during LogSearch/Atlas/Ranger startup
[ https://issues.apache.org/jira/browse/AMBARI-20013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-20013: -- Attachment: AMBARI-20013-appendum1.patch > Add Solr authorization settings during LogSearch/Atlas/Ranger startup > - > > Key: AMBARI-20013 > URL: https://issues.apache.org/jira/browse/AMBARI-20013 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-20013-appendum1.patch, > AMBARI-20013-appendum2.patch, AMBARI-20013.patch > > > During ranger/logsearch/atlas startup, we need to make sure these services > have permission to access for specific collections. > Also ranger plugins should be able to write into ranger collection as well. > There will be a new solr_cloud_util function to add user-roles to solr, which > will update security.json on the zookeeper znode. > For newly added services with ranger plugins, solr will need to be restarted > to generate the correct security.json on zookeeper. > Also this task will introduce a new custom security.json which can override > that is used by default. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20081) Install actions fail when switching from root to non-root.
[ https://issues.apache.org/jira/browse/AMBARI-20081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874538#comment-15874538 ] Hudson commented on AMBARI-20081: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1034 (See [https://builds.apache.org/job/Ambari-branch-2.5/1034/]) AMBARI-20081. Install actions fail when switching from root to non-root. (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b7f3713a21a8cf17e323f68e4d23590ed507084f]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py * (edit) ambari-server/src/test/python/stacks/2.0.6/hooks/before-ANY/test_before_any.py > Install actions fail when switching from root to non-root. > -- > > Key: AMBARI-20081 > URL: https://issues.apache.org/jira/browse/AMBARI-20081 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-20081.patch > > > 1\. Deploy cluster with ambari-agent running as root and umask 027 > 2\. Switch to non-root > 3\. Trigger install action > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 35, in > BeforeAnyHook().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 313, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 32, in hook > setup_java() > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py", > line 218, in setup_java > Execute(install_cmd, > File > "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line > 155, in __init__ > self.env.run() > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", > line 262, in action_run > tries=self.resource.tries, try_sleep=self.resource.try_sleep) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > resource_management.core.exceptions.ExecutionFailed: Execution of 'cd > /var/lib/ambari-agent/tmp/jdk_tmp_CN9C5F && tar -xf > /var/lib/ambari-agent/tmp/jdk-8u112-linux-x64.tar.gz && ambari-sudo.sh cp -rp > /var/lib/ambari-agent/tmp/jdk_tmp_CN9C5F/* /usr/jdk64' returned 2. tar: > /var/lib/ambari-agent/tmp/jdk-8u112-linux-x64.tar.gz: Cannot open: Permission > denied > tar: Error is not recoverable: exiting now > Error: Error: Unable to run the custom hook script ['/usr/bin/python', > '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py', > 'ANY', '/var/lib/ambari-agent/data/command-145.json', > '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY', > '/var/lib/ambari-agent/data/structured-out-145.json', 'INFO', > '/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1'] > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20082) Wizard 'Assign Master ' step is showing inconsistent Select view
[
https://issues.apache.org/jira/browse/AMBARI-20082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874522#comment-15874522
]
Hadoop QA commented on AMBARI-20082:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853554/AMBARI-20082.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10650//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10650//console
This message is automatically generated.
> Wizard 'Assign Master ' step is showing inconsistent Select view
>
>
> Key: AMBARI-20082
> URL: https://issues.apache.org/jira/browse/AMBARI-20082
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20082.patch
>
>
> In Wizard > Assign Mater step, the select host menu is not consistent with
> the whole style guide. Should make it looks like a normal dropdown.
> As investigated, it is impossible to customize the "Option" menu, so would
> consider replacing that with dropdown button and dropdown menu.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20081) Install actions fail when switching from root to non-root.
[ https://issues.apache.org/jira/browse/AMBARI-20081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874514#comment-15874514 ] Hudson commented on AMBARI-20081: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6787 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6787/]) AMBARI-20081. Install actions fail when switching from root to non-root. (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=709bf6ef3261e609bec1161d02ae6787911e2919]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py * (edit) ambari-server/src/test/python/stacks/2.0.6/hooks/before-ANY/test_before_any.py > Install actions fail when switching from root to non-root. > -- > > Key: AMBARI-20081 > URL: https://issues.apache.org/jira/browse/AMBARI-20081 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-20081.patch > > > 1\. Deploy cluster with ambari-agent running as root and umask 027 > 2\. Switch to non-root > 3\. Trigger install action > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 35, in > BeforeAnyHook().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 313, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 32, in hook > setup_java() > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py", > line 218, in setup_java > Execute(install_cmd, > File > "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line > 155, in __init__ > self.env.run() > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", > line 262, in action_run > tries=self.resource.tries, try_sleep=self.resource.try_sleep) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > resource_management.core.exceptions.ExecutionFailed: Execution of 'cd > /var/lib/ambari-agent/tmp/jdk_tmp_CN9C5F && tar -xf > /var/lib/ambari-agent/tmp/jdk-8u112-linux-x64.tar.gz && ambari-sudo.sh cp -rp > /var/lib/ambari-agent/tmp/jdk_tmp_CN9C5F/* /usr/jdk64' returned 2. tar: > /var/lib/ambari-agent/tmp/jdk-8u112-linux-x64.tar.gz: Cannot open: Permission > denied > tar: Error is not recoverable: exiting now > Error: Error: Unable to run the custom hook script ['/usr/bin/python', > '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py', > 'ANY', '/var/lib/ambari-agent/data/command-145.json', > '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY', > '/var/lib/ambari-agent/data/structured-out-145.json', 'INFO', > '/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1'] > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20082) Wizard 'Assign Master ' step is showing inconsistent Select view
[ https://issues.apache.org/jira/browse/AMBARI-20082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20082: - Attachment: AMBARI-20082.patch > Wizard 'Assign Master ' step is showing inconsistent Select view > > > Key: AMBARI-20082 > URL: https://issues.apache.org/jira/browse/AMBARI-20082 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 3.0.0 > > Attachments: AMBARI-20082.patch > > > In Wizard > Assign Mater step, the select host menu is not consistent with > the whole style guide. Should make it looks like a normal dropdown. > As investigated, it is impossible to customize the "Option" menu, so would > consider replacing that with dropdown button and dropdown menu. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20082) Wizard 'Assign Master ' step is showing inconsistent Select view
[ https://issues.apache.org/jira/browse/AMBARI-20082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20082: - Status: Patch Available (was: Open) > Wizard 'Assign Master ' step is showing inconsistent Select view > > > Key: AMBARI-20082 > URL: https://issues.apache.org/jira/browse/AMBARI-20082 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 3.0.0 > > Attachments: AMBARI-20082.patch > > > In Wizard > Assign Mater step, the select host menu is not consistent with > the whole style guide. Should make it looks like a normal dropdown. > As investigated, it is impossible to customize the "Option" menu, so would > consider replacing that with dropdown button and dropdown menu. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20081) Install actions fail when switching from root to non-root.
[ https://issues.apache.org/jira/browse/AMBARI-20081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-20081: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Install actions fail when switching from root to non-root. > -- > > Key: AMBARI-20081 > URL: https://issues.apache.org/jira/browse/AMBARI-20081 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-20081.patch > > > 1\. Deploy cluster with ambari-agent running as root and umask 027 > 2\. Switch to non-root > 3\. Trigger install action > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 35, in > BeforeAnyHook().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 313, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 32, in hook > setup_java() > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py", > line 218, in setup_java > Execute(install_cmd, > File > "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line > 155, in __init__ > self.env.run() > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", > line 262, in action_run > tries=self.resource.tries, try_sleep=self.resource.try_sleep) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > resource_management.core.exceptions.ExecutionFailed: Execution of 'cd > /var/lib/ambari-agent/tmp/jdk_tmp_CN9C5F && tar -xf > /var/lib/ambari-agent/tmp/jdk-8u112-linux-x64.tar.gz && ambari-sudo.sh cp -rp > /var/lib/ambari-agent/tmp/jdk_tmp_CN9C5F/* /usr/jdk64' returned 2. tar: > /var/lib/ambari-agent/tmp/jdk-8u112-linux-x64.tar.gz: Cannot open: Permission > denied > tar: Error is not recoverable: exiting now > Error: Error: Unable to run the custom hook script ['/usr/bin/python', > '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py', > 'ANY', '/var/lib/ambari-agent/data/command-145.json', > '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY', > '/var/lib/ambari-agent/data/structured-out-145.json', 'INFO', > '/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1'] > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20082) Wizard 'Assign Master ' step is showing inconsistent Select view
Aleksandr Kovalenko created AMBARI-20082: Summary: Wizard 'Assign Master ' step is showing inconsistent Select view Key: AMBARI-20082 URL: https://issues.apache.org/jira/browse/AMBARI-20082 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 In Wizard > Assign Mater step, the select host menu is not consistent with the whole style guide. Should make it looks like a normal dropdown. As investigated, it is impossible to customize the "Option" menu, so would consider replacing that with dropdown button and dropdown menu. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20081) Install actions fail when switching from root to non-root.
[
https://issues.apache.org/jira/browse/AMBARI-20081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874461#comment-15874461
]
Hadoop QA commented on AMBARI-20081:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853551/AMBARI-20081.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10649//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10649//console
This message is automatically generated.
> Install actions fail when switching from root to non-root.
> --
>
> Key: AMBARI-20081
> URL: https://issues.apache.org/jira/browse/AMBARI-20081
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-20081.patch
>
>
> 1\. Deploy cluster with ambari-agent running as root and umask 027
> 2\. Switch to non-root
> 3\. Trigger install action
>
>
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py",
> line 35, in
> BeforeAnyHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 313, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py",
> line 32, in hook
> setup_java()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py",
> line 218, in setup_java
> Execute(install_cmd,
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line
> 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'cd
> /var/lib/ambari-agent/tmp/jdk_tmp_CN9C5F && tar -xf
> /var/lib/ambari-agent/tmp/jdk-8u112-linux-x64.tar.gz && ambari-sudo.sh cp -rp
> /var/lib/ambari-agent/tmp/jdk_tmp_CN9C5F/* /usr/jdk64' returned 2. tar:
> /var/lib/ambari-agent/tmp/jdk-8u112-linux-x64.tar.gz: Cannot open: Permission
> denied
> tar: Error is not recoverable: exiting now
> Error: Error: Unable to run the custom hook script ['/usr/bin/python',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py',
> 'ANY', '/var/lib/ambari-agent/data/command-145.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY',
> '/var/lib/ambari-agent/data/structured-out-145.json', 'INFO',
> '/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1']
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20078) When uploading a file using the WFM, need a message to say that either the file upload succeeded or failed
[
https://issues.apache.org/jira/browse/AMBARI-20078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874441#comment-15874441
]
Hadoop QA commented on AMBARI-20078:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853544/AMBARI-20078_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/wfmanager/src/main/resources/ui
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10648//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10648//console
This message is automatically generated.
> When uploading a file using the WFM, need a message to say that either the
> file upload succeeded or failed
> --
>
> Key: AMBARI-20078
> URL: https://issues.apache.org/jira/browse/AMBARI-20078
> 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-20078_trunk.patch
>
>
> Steps to repo:
> 1. Create a WF
> 2. Add a java action
> 3. Go to Advanced Properties, and under File - click on Browse and use the
> File Browser to upload a file from local machine.
> 4. Need to receive a message whether the file upload is successful or failed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
[
https://issues.apache.org/jira/browse/AMBARI-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874435#comment-15874435
]
Hudson commented on AMBARI-19076:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6786 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6786/])
AMBARI-19076. Broken link in ambari-server/docs/api/v1/schemas.md (adoroszlai:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2744ae82af2816222807b0066a4ae60771147e1c])
* (edit) ambari-server/docs/api/v1/schemas.md
> Broken links in ambari-server/docs/api/v1/schemas.md
>
>
> Key: AMBARI-19076
> URL: https://issues.apache.org/jira/browse/AMBARI-19076
> Project: Ambari
> Issue Type: Documentation
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Trivial
> Fix For: trunk
>
> Attachments: AMBARI-19076.patch
>
>
> This is very trivial thing. When I see API document on
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
> I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the
> link.
> We can jump to there by using
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md#postputdelete-resource.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20081) Install actions fail when switching from root to non-root.
[ https://issues.apache.org/jira/browse/AMBARI-20081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-20081: - Status: Patch Available (was: Open) > Install actions fail when switching from root to non-root. > -- > > Key: AMBARI-20081 > URL: https://issues.apache.org/jira/browse/AMBARI-20081 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-20081.patch > > > 1\. Deploy cluster with ambari-agent running as root and umask 027 > 2\. Switch to non-root > 3\. Trigger install action > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 35, in > BeforeAnyHook().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 313, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 32, in hook > setup_java() > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py", > line 218, in setup_java > Execute(install_cmd, > File > "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line > 155, in __init__ > self.env.run() > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", > line 262, in action_run > tries=self.resource.tries, try_sleep=self.resource.try_sleep) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > resource_management.core.exceptions.ExecutionFailed: Execution of 'cd > /var/lib/ambari-agent/tmp/jdk_tmp_CN9C5F && tar -xf > /var/lib/ambari-agent/tmp/jdk-8u112-linux-x64.tar.gz && ambari-sudo.sh cp -rp > /var/lib/ambari-agent/tmp/jdk_tmp_CN9C5F/* /usr/jdk64' returned 2. tar: > /var/lib/ambari-agent/tmp/jdk-8u112-linux-x64.tar.gz: Cannot open: Permission > denied > tar: Error is not recoverable: exiting now > Error: Error: Unable to run the custom hook script ['/usr/bin/python', > '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py', > 'ANY', '/var/lib/ambari-agent/data/command-145.json', > '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY', > '/var/lib/ambari-agent/data/structured-out-145.json', 'INFO', > '/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1'] > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20081) Install actions fail when switching from root to non-root.
[ https://issues.apache.org/jira/browse/AMBARI-20081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-20081: - Attachment: AMBARI-20081.patch > Install actions fail when switching from root to non-root. > -- > > Key: AMBARI-20081 > URL: https://issues.apache.org/jira/browse/AMBARI-20081 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-20081.patch > > > 1\. Deploy cluster with ambari-agent running as root and umask 027 > 2\. Switch to non-root > 3\. Trigger install action > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 35, in > BeforeAnyHook().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 313, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 32, in hook > setup_java() > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py", > line 218, in setup_java > Execute(install_cmd, > File > "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line > 155, in __init__ > self.env.run() > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", > line 262, in action_run > tries=self.resource.tries, try_sleep=self.resource.try_sleep) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > resource_management.core.exceptions.ExecutionFailed: Execution of 'cd > /var/lib/ambari-agent/tmp/jdk_tmp_CN9C5F && tar -xf > /var/lib/ambari-agent/tmp/jdk-8u112-linux-x64.tar.gz && ambari-sudo.sh cp -rp > /var/lib/ambari-agent/tmp/jdk_tmp_CN9C5F/* /usr/jdk64' returned 2. tar: > /var/lib/ambari-agent/tmp/jdk-8u112-linux-x64.tar.gz: Cannot open: Permission > denied > tar: Error is not recoverable: exiting now > Error: Error: Unable to run the custom hook script ['/usr/bin/python', > '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py', > 'ANY', '/var/lib/ambari-agent/data/command-145.json', > '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY', > '/var/lib/ambari-agent/data/structured-out-145.json', 'INFO', > '/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1'] > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20081) Install actions fail when switching from root to non-root.
Andrew Onischuk created AMBARI-20081: Summary: Install actions fail when switching from root to non-root. Key: AMBARI-20081 URL: https://issues.apache.org/jira/browse/AMBARI-20081 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.5.0 Attachments: AMBARI-20081.patch 1\. Deploy cluster with ambari-agent running as root and umask 027 2\. Switch to non-root 3\. Trigger install action Traceback (most recent call last): File "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", line 35, in BeforeAnyHook().execute() File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 313, in execute method(env) File "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", line 32, in hook setup_java() File "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py", line 218, in setup_java Execute(install_cmd, File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 155, in __init__ self.env.run() File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 160, in run self.run_action(resource, action) File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 124, in run_action provider_action() File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 262, in action_run tries=self.resource.tries, try_sleep=self.resource.try_sleep) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 72, in inner result = function(command, **kwargs) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102, in checked_call tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150, in _call_wrapper result = _call(command, **kwargs_copy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 303, in _call raise ExecutionFailed(err_msg, code, out, err) resource_management.core.exceptions.ExecutionFailed: Execution of 'cd /var/lib/ambari-agent/tmp/jdk_tmp_CN9C5F && tar -xf /var/lib/ambari-agent/tmp/jdk-8u112-linux-x64.tar.gz && ambari-sudo.sh cp -rp /var/lib/ambari-agent/tmp/jdk_tmp_CN9C5F/* /usr/jdk64' returned 2. tar: /var/lib/ambari-agent/tmp/jdk-8u112-linux-x64.tar.gz: Cannot open: Permission denied tar: Error is not recoverable: exiting now Error: Error: Unable to run the custom hook script ['/usr/bin/python', '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py', 'ANY', '/var/lib/ambari-agent/data/command-145.json', '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY', '/var/lib/ambari-agent/data/structured-out-145.json', 'INFO', '/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1'] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20080) WFM does not issue confirmation message when workflow is suspended or killed
[ https://issues.apache.org/jira/browse/AMBARI-20080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20080: - Status: Patch Available (was: Open) > WFM does not issue confirmation message when workflow is suspended or killed > > > Key: AMBARI-20080 > URL: https://issues.apache.org/jira/browse/AMBARI-20080 > 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-20080_trunk.patch > > > Steps: > 1. log into ambari ui > 2. go to wfm > 3. upload workflow from file system: > 4. submit the workflow > 5. kill or suspend the workflow from WFM ui > Issue: > workflow ui is not giving any confirmation message when wf is killed or > suspended -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20080) WFM does not issue confirmation message when workflow is suspended or killed
[ https://issues.apache.org/jira/browse/AMBARI-20080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20080: - Attachment: AMBARI-20080_trunk.patch > WFM does not issue confirmation message when workflow is suspended or killed > > > Key: AMBARI-20080 > URL: https://issues.apache.org/jira/browse/AMBARI-20080 > 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-20080_trunk.patch > > > Steps: > 1. log into ambari ui > 2. go to wfm > 3. upload workflow from file system: > 4. submit the workflow > 5. kill or suspend the workflow from WFM ui > Issue: > workflow ui is not giving any confirmation message when wf is killed or > suspended -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20079) Unable to filter by job id
[ https://issues.apache.org/jira/browse/AMBARI-20079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20079: - Status: Patch Available (was: Open) > Unable to filter by job id > -- > > Key: AMBARI-20079 > URL: https://issues.apache.org/jira/browse/AMBARI-20079 > 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-20079_trunk.patch, Screen Shot 2017-02-16.png > > > After attempting to resume a random SUSPENDED existing workflow > 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via > hrt_qa user), the workflow went into RUNNING state. I wanted to see that > workflow by itself on the dashboard, so I used filter criteria with the > following syntax: > jobid=078-170215133231623-oozie-oozi-W > jobid:078-170215133231623-oozie-oozi-W > The first one returned: > Remote api failed > The second one showed the same error message but also a perptual animated > busy loading icon. > I expected that if my syntax was incorrect, it would say so like "jobid:..." > is not correct, do you mean "Job Id=" or something to that effect. Also, for > the second case, there should be a fast fail, rather than a perpetual hanging. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20080) WFM does not issue confirmation message when workflow is suspended or killed
Padma Priya Nagaraj created AMBARI-20080: Summary: WFM does not issue confirmation message when workflow is suspended or killed Key: AMBARI-20080 URL: https://issues.apache.org/jira/browse/AMBARI-20080 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Priority: Critical Fix For: 2.5.0 Steps: 1. log into ambari ui 2. go to wfm 3. upload workflow from file system: 4. submit the workflow 5. kill or suspend the workflow from WFM ui Issue: workflow ui is not giving any confirmation message when wf is killed or suspended -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20079) Unable to filter by job id
[ https://issues.apache.org/jira/browse/AMBARI-20079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20079: - Labels: WFD WFM (was: ) > Unable to filter by job id > -- > > Key: AMBARI-20079 > URL: https://issues.apache.org/jira/browse/AMBARI-20079 > 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-20079_trunk.patch, Screen Shot 2017-02-16.png > > > After attempting to resume a random SUSPENDED existing workflow > 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via > hrt_qa user), the workflow went into RUNNING state. I wanted to see that > workflow by itself on the dashboard, so I used filter criteria with the > following syntax: > jobid=078-170215133231623-oozie-oozi-W > jobid:078-170215133231623-oozie-oozi-W > The first one returned: > Remote api failed > The second one showed the same error message but also a perptual animated > busy loading icon. > I expected that if my syntax was incorrect, it would say so like "jobid:..." > is not correct, do you mean "Job Id=" or something to that effect. Also, for > the second case, there should be a fast fail, rather than a perpetual hanging. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20077) Server Error when trying to save and not overwrite
[ https://issues.apache.org/jira/browse/AMBARI-20077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874406#comment-15874406 ] Hudson commented on AMBARI-20077: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1033 (See [https://builds.apache.org/job/Ambari-branch-2.5/1033/]) AMBARI-20077. Server Error when trying to save and not overwrite. (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a4fb9ec11c2dfcd1d10eea2e67a87a71a7a9c321]) * (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/workflowmanager/WorkflowsRepo.java * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/coord-config.js * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/Utils.java * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/bundle-config.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/flow-designer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/save-wf.js * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/workflowmanager/WorkflowManagerService.java * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/OozieUtils.java * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/WorkflowFilesService.java * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/workflowmanager/WorkflowsManagerResource.java > Server Error when trying to save and not overwrite > -- > > Key: AMBARI-20077 > URL: https://issues.apache.org/jira/browse/AMBARI-20077 > 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-20077_trunk.patch > > > When file path exists, typo error in response "Worfklow path exists.". > Expected is "Workflow Path exists" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20048) Hive View 2.0: Visual Explain-The operators are being shown out of order.
[ https://issues.apache.org/jira/browse/AMBARI-20048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874407#comment-15874407 ] Hudson commented on AMBARI-20048: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1033 (See [https://builds.apache.org/job/Ambari-branch-2.5/1033/]) AMBARI-20048. Hive View 2.0: Visual Explain-The operators are being (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=361f225d85a869c78fa0bfe954f852e8951b566c]) * (add) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/renderer-force.js * (add) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/transformer.js * (add) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/fallback.js * (add) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/index.js * (edit) contrib/views/hive20/src/main/resources/ui/app/styles/app.scss * (delete) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer.js * (edit) contrib/views/hive20/src/main/resources/ui/ember-cli-build.js * (add) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/processor.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/visual-explain.js * (add) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/renderer.js * (add) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/enhancer.js * (edit) contrib/views/hive20/src/main/resources/ui/bower.json > Hive View 2.0: Visual Explain-The operators are being shown out of order. > - > > Key: AMBARI-20048 > URL: https://issues.apache.org/jira/browse/AMBARI-20048 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar > Fix For: 2.5.0 > > Attachments: AMBARI-20048-trunk.patch > > > The operators are being shown out of order. It’s hard to think about what to > do with the plan output when the operators are out of order, so this needs to > be fixed first. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20048) Hive View 2.0: Visual Explain-The operators are being shown out of order.
[ https://issues.apache.org/jira/browse/AMBARI-20048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874404#comment-15874404 ] Hudson commented on AMBARI-20048: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6785 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6785/]) AMBARI-20048. Hive View 2.0: Visual Explain-The operators are being (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=812397d3a054f2be8bb7c7c172bf59255b95a341]) * (add) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/renderer.js * (edit) contrib/views/hive20/src/main/resources/ui/ember-cli-build.js * (edit) contrib/views/hive20/src/main/resources/ui/bower.json * (add) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/processor.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/visual-explain.js * (edit) contrib/views/hive20/src/main/resources/ui/app/styles/app.scss * (add) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/enhancer.js * (add) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/fallback.js * (add) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/index.js * (add) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/transformer.js * (delete) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer.js * (add) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/renderer-force.js > Hive View 2.0: Visual Explain-The operators are being shown out of order. > - > > Key: AMBARI-20048 > URL: https://issues.apache.org/jira/browse/AMBARI-20048 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar > Fix For: 2.5.0 > > Attachments: AMBARI-20048-trunk.patch > > > The operators are being shown out of order. It’s hard to think about what to > do with the plan output when the operators are out of order, so this needs to > be fixed first. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20077) Server Error when trying to save and not overwrite
[ https://issues.apache.org/jira/browse/AMBARI-20077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874403#comment-15874403 ] Hudson commented on AMBARI-20077: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6785 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6785/]) AMBARI-20077. Server Error when trying to save and not overwrite. (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=07342bc6e4a0e9ba2b2f850f5d8cbf38a948b50c]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/coord-config.js * (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/workflowmanager/WorkflowsRepo.java * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/OozieProxyImpersonator.java * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/flow-designer.js * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/WorkflowFilesService.java * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/bundle-config.js * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/workflowmanager/WorkflowsManagerResource.java * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/workflowmanager/WorkflowManagerService.java * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/save-wf.js * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/OozieUtils.java > Server Error when trying to save and not overwrite > -- > > Key: AMBARI-20077 > URL: https://issues.apache.org/jira/browse/AMBARI-20077 > 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-20077_trunk.patch > > > When file path exists, typo error in response "Worfklow path exists.". > Expected is "Workflow Path exists" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20079) Unable to filter by job id
[ https://issues.apache.org/jira/browse/AMBARI-20079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20079: - Attachment: AMBARI-20079_trunk.patch > Unable to filter by job id > -- > > Key: AMBARI-20079 > URL: https://issues.apache.org/jira/browse/AMBARI-20079 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20079_trunk.patch, Screen Shot 2017-02-16.png > > > After attempting to resume a random SUSPENDED existing workflow > 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via > hrt_qa user), the workflow went into RUNNING state. I wanted to see that > workflow by itself on the dashboard, so I used filter criteria with the > following syntax: > jobid=078-170215133231623-oozie-oozi-W > jobid:078-170215133231623-oozie-oozi-W > The first one returned: > Remote api failed > The second one showed the same error message but also a perptual animated > busy loading icon. > I expected that if my syntax was incorrect, it would say so like "jobid:..." > is not correct, do you mean "Job Id=" or something to that effect. Also, for > the second case, there should be a fast fail, rather than a perpetual hanging. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20079) Unable to filter by job id
[ https://issues.apache.org/jira/browse/AMBARI-20079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20079: - Attachment: Screen Shot 2017-02-16.png > Unable to filter by job id > -- > > Key: AMBARI-20079 > URL: https://issues.apache.org/jira/browse/AMBARI-20079 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Fix For: 2.5.0 > > Attachments: Screen Shot 2017-02-16.png > > > After attempting to resume a random SUSPENDED existing workflow > 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via > hrt_qa user), the workflow went into RUNNING state. I wanted to see that > workflow by itself on the dashboard, so I used filter criteria with the > following syntax: > jobid=078-170215133231623-oozie-oozi-W > jobid:078-170215133231623-oozie-oozi-W > The first one returned: > Remote api failed > The second one showed the same error message but also a perptual animated > busy loading icon. > I expected that if my syntax was incorrect, it would say so like "jobid:..." > is not correct, do you mean "Job Id=" or something to that effect. Also, for > the second case, there should be a fast fail, rather than a perpetual hanging. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20079) Unable to filter by job id
Padma Priya Nagaraj created AMBARI-20079: Summary: Unable to filter by job id Key: AMBARI-20079 URL: https://issues.apache.org/jira/browse/AMBARI-20079 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Priority: Critical Fix For: 2.5.0 After attempting to resume a random SUSPENDED existing workflow 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via hrt_qa user), the workflow went into RUNNING state. I wanted to see that workflow by itself on the dashboard, so I used filter criteria with the following syntax: jobid=078-170215133231623-oozie-oozi-W jobid:078-170215133231623-oozie-oozi-W The first one returned: Remote api failed The second one showed the same error message but also a perptual animated busy loading icon. I expected that if my syntax was incorrect, it would say so like "jobid:..." is not correct, do you mean "Job Id=" or something to that effect. Also, for the second case, there should be a fast fail, rather than a perpetual hanging. LOGS: http://qelog.hortonworks.com/log/bugbash-r6-oozie-unsecure/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20079) Unable to filter by job id
[ https://issues.apache.org/jira/browse/AMBARI-20079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20079: - Description: After attempting to resume a random SUSPENDED existing workflow 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via hrt_qa user), the workflow went into RUNNING state. I wanted to see that workflow by itself on the dashboard, so I used filter criteria with the following syntax: jobid=078-170215133231623-oozie-oozi-W jobid:078-170215133231623-oozie-oozi-W The first one returned: Remote api failed The second one showed the same error message but also a perptual animated busy loading icon. I expected that if my syntax was incorrect, it would say so like "jobid:..." is not correct, do you mean "Job Id=" or something to that effect. Also, for the second case, there should be a fast fail, rather than a perpetual hanging. was: After attempting to resume a random SUSPENDED existing workflow 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via hrt_qa user), the workflow went into RUNNING state. I wanted to see that workflow by itself on the dashboard, so I used filter criteria with the following syntax: jobid=078-170215133231623-oozie-oozi-W jobid:078-170215133231623-oozie-oozi-W The first one returned: Remote api failed The second one showed the same error message but also a perptual animated busy loading icon. I expected that if my syntax was incorrect, it would say so like "jobid:..." is not correct, do you mean "Job Id=" or something to that effect. Also, for the second case, there should be a fast fail, rather than a perpetual hanging. LOGS: http://qelog.hortonworks.com/log/bugbash-r6-oozie-unsecure/ > Unable to filter by job id > -- > > Key: AMBARI-20079 > URL: https://issues.apache.org/jira/browse/AMBARI-20079 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Fix For: 2.5.0 > > > After attempting to resume a random SUSPENDED existing workflow > 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via > hrt_qa user), the workflow went into RUNNING state. I wanted to see that > workflow by itself on the dashboard, so I used filter criteria with the > following syntax: > jobid=078-170215133231623-oozie-oozi-W > jobid:078-170215133231623-oozie-oozi-W > The first one returned: > Remote api failed > The second one showed the same error message but also a perptual animated > busy loading icon. > I expected that if my syntax was incorrect, it would say so like "jobid:..." > is not correct, do you mean "Job Id=" or something to that effect. Also, for > the second case, there should be a fast fail, rather than a perpetual hanging. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
[
https://issues.apache.org/jira/browse/AMBARI-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19076:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to
[trunk|http://git-wip-us.apache.org/repos/asf/ambari/commit/2744ae82].
> Broken links in ambari-server/docs/api/v1/schemas.md
>
>
> Key: AMBARI-19076
> URL: https://issues.apache.org/jira/browse/AMBARI-19076
> Project: Ambari
> Issue Type: Documentation
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Trivial
> Fix For: trunk
>
> Attachments: AMBARI-19076.patch
>
>
> This is very trivial thing. When I see API document on
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
> I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the
> link.
> We can jump to there by using
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md#postputdelete-resource.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20070) Agent heartbeat lost due to subprocess.Popen race condition
[
https://issues.apache.org/jira/browse/AMBARI-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874331#comment-15874331
]
Hudson commented on AMBARI-20070:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1032 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1032/])
AMBARI-20070. Agent heartbeat loop stuck in subprocess.Popen (adoroszlai:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a9951bad101fef5c5449260ff7589b220edc5b13])
* (edit) ambari-agent/src/main/python/ambari_agent/main.py
> Agent heartbeat lost due to subprocess.Popen race condition
> ---
>
> Key: AMBARI-20070
> URL: https://issues.apache.org/jira/browse/AMBARI-20070
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
> Environment: Python 2.7
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-20070.patch
>
>
> Workaround for http://bugs.python.org/issue19809 that probably causes
> {{subprocess.Popen}} call to get stuck in:
> {noformat}
> File: "/usr/lib/python2.7/subprocess.py", line 679, in __init__
> errread, errwrite)
> File: "/usr/lib/python2.7/subprocess.py", line 1244, in _execute_child
> data = _eintr_retry_call(os.read, errpipe_read, 1048576)
> File: "/usr/lib/python2.7/subprocess.py", line 478, in _eintr_retry_call
> return func(*args)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20078) When uploading a file using the WFM, need a message to say that either the file upload succeeded or failed
[ https://issues.apache.org/jira/browse/AMBARI-20078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20078: - Status: Patch Available (was: Open) > When uploading a file using the WFM, need a message to say that either the > file upload succeeded or failed > -- > > Key: AMBARI-20078 > URL: https://issues.apache.org/jira/browse/AMBARI-20078 > 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-20078_trunk.patch > > > Steps to repo: > 1. Create a WF > 2. Add a java action > 3. Go to Advanced Properties, and under File - click on Browse and use the > File Browser to upload a file from local machine. > 4. Need to receive a message whether the file upload is successful or failed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20048) Hive View 2.0: Visual Explain-The operators are being shown out of order.
[ https://issues.apache.org/jira/browse/AMBARI-20048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20048: - Resolution: Fixed Status: Resolved (was: Patch Available) > Hive View 2.0: Visual Explain-The operators are being shown out of order. > - > > Key: AMBARI-20048 > URL: https://issues.apache.org/jira/browse/AMBARI-20048 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar > Fix For: 2.5.0 > > Attachments: AMBARI-20048-trunk.patch > > > The operators are being shown out of order. It’s hard to think about what to > do with the plan output when the operators are out of order, so this needs to > be fixed first. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20078) When uploading a file using the WFM, need a message to say that either the file upload succeeded or failed
[ https://issues.apache.org/jira/browse/AMBARI-20078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20078: - Attachment: AMBARI-20078_trunk.patch > When uploading a file using the WFM, need a message to say that either the > file upload succeeded or failed > -- > > Key: AMBARI-20078 > URL: https://issues.apache.org/jira/browse/AMBARI-20078 > 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-20078_trunk.patch > > > Steps to repo: > 1. Create a WF > 2. Add a java action > 3. Go to Advanced Properties, and under File - click on Browse and use the > File Browser to upload a file from local machine. > 4. Need to receive a message whether the file upload is successful or failed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20070) Agent heartbeat lost due to subprocess.Popen race condition
[
https://issues.apache.org/jira/browse/AMBARI-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874319#comment-15874319
]
Hudson commented on AMBARI-20070:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6784 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6784/])
AMBARI-20070. Agent heartbeat loop stuck in subprocess.Popen (adoroszlai:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ac4f3d11f05637639638daf204cb9405ab9fe198])
* (edit) ambari-agent/src/main/python/ambari_agent/main.py
> Agent heartbeat lost due to subprocess.Popen race condition
> ---
>
> Key: AMBARI-20070
> URL: https://issues.apache.org/jira/browse/AMBARI-20070
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
> Environment: Python 2.7
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-20070.patch
>
>
> Workaround for http://bugs.python.org/issue19809 that probably causes
> {{subprocess.Popen}} call to get stuck in:
> {noformat}
> File: "/usr/lib/python2.7/subprocess.py", line 679, in __init__
> errread, errwrite)
> File: "/usr/lib/python2.7/subprocess.py", line 1244, in _execute_child
> data = _eintr_retry_call(os.read, errpipe_read, 1048576)
> File: "/usr/lib/python2.7/subprocess.py", line 478, in _eintr_retry_call
> return func(*args)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20078) When uploading a file using the WFM, need a message to say that either the file upload succeeded or failed
Padma Priya Nagaraj created AMBARI-20078: Summary: When uploading a file using the WFM, need a message to say that either the file upload succeeded or failed Key: AMBARI-20078 URL: https://issues.apache.org/jira/browse/AMBARI-20078 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Priority: Critical Fix For: 2.5.0 Steps to repo: 1. Create a WF 2. Add a java action 3. Go to Advanced Properties, and under File - click on Browse and use the File Browser to upload a file from local machine. 4. Need to receive a message whether the file upload is successful or failed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19938) Hive2: Invalid query execution not handled properly
[ https://issues.apache.org/jira/browse/AMBARI-19938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19938: - Resolution: Fixed Status: Resolved (was: Patch Available) > Hive2: Invalid query execution not handled properly > --- > > Key: AMBARI-19938 > URL: https://issues.apache.org/jira/browse/AMBARI-19938 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.5.0 > > > - Type "xxx;" > - hit execute > - wait forever -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19938) Hive2: Invalid query execution not handled properly
[ https://issues.apache.org/jira/browse/AMBARI-19938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19938: - Attachment: (was: AMBARI-19938_trunk.patch) > Hive2: Invalid query execution not handled properly > --- > > Key: AMBARI-19938 > URL: https://issues.apache.org/jira/browse/AMBARI-19938 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.5.0 > > > - Type "xxx;" > - hit execute > - wait forever -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20077) Server Error when trying to save and not overwrite
[ https://issues.apache.org/jira/browse/AMBARI-20077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20077: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Server Error when trying to save and not overwrite > -- > > Key: AMBARI-20077 > URL: https://issues.apache.org/jira/browse/AMBARI-20077 > 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-20077_trunk.patch > > > When file path exists, typo error in response "Worfklow path exists.". > Expected is "Workflow Path exists" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20076) Hive View 2: Results of one query reflected in other
[ https://issues.apache.org/jira/browse/AMBARI-20076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874303#comment-15874303 ] Hudson commented on AMBARI-20076: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1031 (See [https://builds.apache.org/job/Ambari-branch-2.5/1031/]) AMBARI-20076. Hive View 2: Results of one query reflected in other (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0d68935c1843c4b2cf25ce18668bbcca12f4639e]) * (edit) contrib/views/hive20/src/main/resources/ui/app/components/query-result-table.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query.hbs * (add) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query/log.hbs * (add) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query/log.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/visual-explain.hbs * (add) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query/visual-explain.js * (add) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query/tez-ui.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/models/worksheet.js * (add) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query/loading.js * (edit) contrib/views/hive20/src/main/resources/ui/config/environment.js * (add) contrib/views/hive20/src/main/resources/ui/app/configs/result-tabs.js * (add) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query/results.js * (add) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query/tez-ui.js * (add) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query/results.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/query-result-table.hbs * (add) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query/visual-explain.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/router.js * (add) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query/loading.hbs > Hive View 2: Results of one query reflected in other > > > Key: AMBARI-20076 > URL: https://issues.apache.org/jira/browse/AMBARI-20076 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20076-trunk.patch > > > Multiple query execution is not handled correctly.If we execute multiple > queries in different tabs simultaneously, their results gets mismatched with > query and some of the queries never finishes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20048) Hive View 2.0: Visual Explain-The operators are being shown out of order.
[ https://issues.apache.org/jira/browse/AMBARI-20048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated AMBARI-20048: Attachment: (was: AMBARI-20048_trunk.patch) > Hive View 2.0: Visual Explain-The operators are being shown out of order. > - > > Key: AMBARI-20048 > URL: https://issues.apache.org/jira/browse/AMBARI-20048 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar > Fix For: 2.5.0 > > Attachments: AMBARI-20048-trunk.patch > > > The operators are being shown out of order. It’s hard to think about what to > do with the plan output when the operators are out of order, so this needs to > be fixed first. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20048) Hive View 2.0: Visual Explain-The operators are being shown out of order.
[ https://issues.apache.org/jira/browse/AMBARI-20048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated AMBARI-20048: Attachment: AMBARI-20048-trunk.patch > Hive View 2.0: Visual Explain-The operators are being shown out of order. > - > > Key: AMBARI-20048 > URL: https://issues.apache.org/jira/browse/AMBARI-20048 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar > Fix For: 2.5.0 > > Attachments: AMBARI-20048-trunk.patch > > > The operators are being shown out of order. It’s hard to think about what to > do with the plan output when the operators are out of order, so this needs to > be fixed first. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-19180) Service Flume failed to start with "cannot open /grid/0/log/flume/a1.out for reading: Permission denied"
[
https://issues.apache.org/jira/browse/AMBARI-19180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen resolved AMBARI-19180.
-
Resolution: Won't Fix
It happens if
Steps :
{code}
1. install Flume with some user (user1)
2. configure a1 agent
3. delete flume
4. install Flume with different user (user2)
5. configure a1 agent
{code}
Appropriate access should be given to user2
> Service Flume failed to start with "cannot open /grid/0/log/flume/a1.out for
> reading: Permission denied"
>
>
> Key: AMBARI-19180
> URL: https://issues.apache.org/jira/browse/AMBARI-19180
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
>
> STR:
> -> Delete the following services on the cluster : Flume, Atlas, Hbase, Sqoop,
> Storm, Knox, AMS
> -> Add them back using add service wizard
> Flume fails to start with
> {noformat}
> 2016-12-12 03:47:12,640 - Execute['ambari-sudo.sh -H -E pgrep -o -u
> cstm-flume -f '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
> /var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0'] {'logoutput': True,
> 'tries': 20, 'try_sleep': 10}
> 2016-12-12 03:47:12,667 - Retrying after 10 seconds. Reason: Execution of
> 'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
> '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
> /var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
> 2016-12-12 03:47:22,706 - Retrying after 10 seconds. Reason: Execution of
> 'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
> '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
> /var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
> 2016-12-12 03:47:32,748 - Retrying after 10 seconds. Reason: Execution of
> 'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
> '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
> /var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
> 2016-12-12 03:47:42,791 - Retrying after 10 seconds. Reason: Execution of
> 'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
> '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
> /var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
> 2016-12-12 03:47:52,835 - Retrying after 10 seconds. Reason: Execution of
> 'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
> '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
> /var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
> 2016-12-12 03:48:02,880 - Retrying after 10 seconds. Reason: Execution of
> 'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
> '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
> /var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
> 2016-12-12 03:48:12,926 - Retrying after 10 seconds. Reason: Execution of
> 'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
> '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
> /var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
> 2016-12-12 03:48:22,974 - Retrying after 10 seconds. Reason: Execution of
> 'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
> '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
> /var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
> 2016-12-12 03:48:33,021 - Retrying after 10 seconds. Reason: Execution of
> 'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
> '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
> /var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
> 2016-12-12 03:48:43,063 - Retrying after 10 seconds. Reason: Execution of
> 'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
> '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
> /var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
> 2016-12-12 03:48:53,104 - Retrying after 10 seconds. Reason: Execution of
> 'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
> '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
> /var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
> 2016-12-12 03:49:03,153 - Retrying after 10 seconds. Reason: Execution of
> 'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
> '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
> /var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
> 2016-12-12 03:49:13,191 - Retrying after 10 seconds. Reason: Execution of
> 'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
> '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
> /var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
> 2016-12-12 03:49:23,237 - Retrying after 10 seconds. Reason: Execution of
> 'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
> '^/usr
[jira] [Updated] (AMBARI-20070) Agent heartbeat lost due to subprocess.Popen race condition
[
https://issues.apache.org/jira/browse/AMBARI-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-20070:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to
[trunk|http://git-wip-us.apache.org/repos/asf/ambari/commit/ac4f3d11] and
[branch-2.5|http://git-wip-us.apache.org/repos/asf/ambari/commit/a9951bad].
> Agent heartbeat lost due to subprocess.Popen race condition
> ---
>
> Key: AMBARI-20070
> URL: https://issues.apache.org/jira/browse/AMBARI-20070
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
> Environment: Python 2.7
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-20070.patch
>
>
> Workaround for http://bugs.python.org/issue19809 that probably causes
> {{subprocess.Popen}} call to get stuck in:
> {noformat}
> File: "/usr/lib/python2.7/subprocess.py", line 679, in __init__
> errread, errwrite)
> File: "/usr/lib/python2.7/subprocess.py", line 1244, in _execute_child
> data = _eintr_retry_call(os.read, errpipe_read, 1048576)
> File: "/usr/lib/python2.7/subprocess.py", line 478, in _eintr_retry_call
> return func(*args)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20064) Hive view 2.0 upload table feature does not show error notifications when errors occurs during the process.
[ https://issues.apache.org/jira/browse/AMBARI-20064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874267#comment-15874267 ] Hudson commented on AMBARI-20064: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6783 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6783/]) AMBARI-20064 : hive20 view : added notification on error of preview or (nitiraj.rathore: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fad8f2745b8e39c51800fede563e170d30ddf9f3]) * (edit) contrib/views/hive20/src/main/resources/ui/app/components/upload-table.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/upload-table.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/services/alert-messages.js * (edit) contrib/views/hive20/src/main/resources/ui/app/mixins/ui-logger.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/upload-table.js > Hive view 2.0 upload table feature does not show error notifications when > errors occurs during the process. > --- > > Key: AMBARI-20064 > URL: https://issues.apache.org/jira/browse/AMBARI-20064 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-20064_branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20076) Hive View 2: Results of one query reflected in other
[ https://issues.apache.org/jira/browse/AMBARI-20076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874268#comment-15874268 ] Hudson commented on AMBARI-20076: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6783 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6783/]) AMBARI-20076. Hive View 2: Results of one query reflected in other (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=316d33a9b7f95610dc2f603c3140e1dda695ed04]) * (add) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query/loading.js * (add) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query/loading.hbs * (add) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query/visual-explain.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/visual-explain.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/query-result-table.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/services/query.js * (add) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query/log.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query.js * (edit) contrib/views/hive20/src/main/resources/ui/config/environment.js * (add) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query/tez-ui.hbs * (add) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query/visual-explain.js * (add) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query/results.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/models/worksheet.js * (add) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query/results.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/query-result-table.js * (add) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query/tez-ui.js * (add) contrib/views/hive20/src/main/resources/ui/app/configs/result-tabs.js * (edit) contrib/views/hive20/src/main/resources/ui/app/router.js * (add) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query/log.js > Hive View 2: Results of one query reflected in other > > > Key: AMBARI-20076 > URL: https://issues.apache.org/jira/browse/AMBARI-20076 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20076-trunk.patch > > > Multiple query execution is not handled correctly.If we execute multiple > queries in different tabs simultaneously, their results gets mismatched with > query and some of the queries never finishes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20064) Hive view 2.0 upload table feature does not show error notifications when errors occurs during the process.
[ https://issues.apache.org/jira/browse/AMBARI-20064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874259#comment-15874259 ] Hudson commented on AMBARI-20064: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1030 (See [https://builds.apache.org/job/Ambari-branch-2.5/1030/]) AMBARI-20064 : hive20 view : added notification on error of preview or (nitiraj.rathore: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c69a52b9169dcfea958c9732614a2d777d13f172]) * (edit) contrib/views/hive20/src/main/resources/ui/app/components/upload-table.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/alert-messages.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/upload-table.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/mixins/ui-logger.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/upload-table.js > Hive view 2.0 upload table feature does not show error notifications when > errors occurs during the process. > --- > > Key: AMBARI-20064 > URL: https://issues.apache.org/jira/browse/AMBARI-20064 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-20064_branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20077) Server Error when trying to save and not overwrite
[ https://issues.apache.org/jira/browse/AMBARI-20077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Madhan Mohan Reddy updated AMBARI-20077: -- Status: Patch Available (was: In Progress) > Server Error when trying to save and not overwrite > -- > > Key: AMBARI-20077 > URL: https://issues.apache.org/jira/browse/AMBARI-20077 > 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-20077_trunk.patch > > > When file path exists, typo error in response "Worfklow path exists.". > Expected is "Workflow Path exists" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20077) Server Error when trying to save and not overwrite
[ https://issues.apache.org/jira/browse/AMBARI-20077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Madhan Mohan Reddy updated AMBARI-20077: -- Attachment: AMBARI-20077_trunk.patch > Server Error when trying to save and not overwrite > -- > > Key: AMBARI-20077 > URL: https://issues.apache.org/jira/browse/AMBARI-20077 > 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-20077_trunk.patch > > > When file path exists, typo error in response "Worfklow path exists.". > Expected is "Workflow Path exists" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20076) Hive View 2: Results of one query reflected in other
[ https://issues.apache.org/jira/browse/AMBARI-20076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20076: - Resolution: Fixed Status: Resolved (was: Patch Available) > Hive View 2: Results of one query reflected in other > > > Key: AMBARI-20076 > URL: https://issues.apache.org/jira/browse/AMBARI-20076 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20076-trunk.patch > > > Multiple query execution is not handled correctly.If we execute multiple > queries in different tabs simultaneously, their results gets mismatched with > query and some of the queries never finishes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20077) Server Error when trying to save and not overwrite
M Madhan Mohan Reddy created AMBARI-20077: - Summary: Server Error when trying to save and not overwrite Key: AMBARI-20077 URL: https://issues.apache.org/jira/browse/AMBARI-20077 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: M Madhan Mohan Reddy Assignee: M Madhan Mohan Reddy Fix For: 2.5.0 When file path exists, typo error in response "Worfklow path exists.". Expected is "Workflow Path exists" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20043) Don't rerender all widgets when on of them is changed
[
https://issues.apache.org/jira/browse/AMBARI-20043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874232#comment-15874232
]
Oleg Nechiporenko commented on AMBARI-20043:
Build failed not because of this patch
{noformat}
[INFO] Ambari Web . SUCCESS [04:19 min]
{noformat}
> Don't rerender all widgets when on of them is changed
> -
>
> Key: AMBARI-20043
> URL: https://issues.apache.org/jira/browse/AMBARI-20043
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20043.patch
>
>
> Dashboard widgets are rerendered if some of them is changed. Actually only
> this one should be updated and not other
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
