[jira] [Updated] (AMBARI-19959) Allow skipping view extraction in ambari-server setup
[
https://issues.apache.org/jira/browse/AMBARI-19959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19959:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to
[trunk|http://git-wip-us.apache.org/repos/asf/ambari/commit/d797c7eb] and
[branch-2.5|http://git-wip-us.apache.org/repos/asf/ambari/commit/706a3dfe].
> Allow skipping view extraction in ambari-server setup
> -
>
> Key: AMBARI-19959
> URL: https://issues.apache.org/jira/browse/AMBARI-19959
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19959.patch
>
>
> The goal of this change is to allow skipping the view extraction step to save
> time during cluster creation in sysprepped environment.
> {{ambari-server setup}} extracts system views on each call. This can take a
> 5-25 seconds depending on the environment. In sysprepped environment the
> views are extracted during preparation phase. Running the setup command
> after VM creation is necessary to configure DB-related properties.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19871) Config version switch/compare/revert doesn't work
[
https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865280#comment-15865280
]
Hadoop QA commented on AMBARI-19871:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852472/AMBARI-19871_fix2.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/10557//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10557//console
This message is automatically generated.
> Config version switch/compare/revert doesn't work
> -
>
> Key: AMBARI-19871
> URL: https://issues.apache.org/jira/browse/AMBARI-19871
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19871_fix1.patch, AMBARI-19871_fix2.patch,
> AMBARI-19871.patch
>
>
> *Steps to reproduce:*
> 1. Go to any service with multiple config versions.
> 2. On the bottom left of the config history bar(the cross button), select an
> older version and click View.
> *Actual result:*
> Now direct clicking on other config version block will not be able to switch
> version. Only through the cross button can you switch to other version.
> Compare configs also does not work, it always compare to the current version
> and end up with empty diff.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19985) Workflow Manager Styling changes
[ https://issues.apache.org/jira/browse/AMBARI-19985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865252#comment-15865252 ] Hudson commented on AMBARI-19985: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #984 (See [https://builds.apache.org/job/Ambari-branch-2.5/984/]) AMBARI-19985. Workflow Manager Styling changes (Madhan Mohan Reddy via (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a8f72002418742f833fc05dcabdf7aa0cae4a9f9]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-actions.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/job-details.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/save-wf.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/flow-designer.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/search-table.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/utils/constants.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-job-details.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/job-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/job-details.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/search-create-new-bar.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-workspace.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/flow-designer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/styles/app.less > Workflow Manager Styling changes > > > Key: AMBARI-19985 > URL: https://issues.apache.org/jira/browse/AMBARI-19985 > 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-19985_trunk.patch > > > Workflow Manager Styling changes- Blue coloured fonts for action items. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19985) Workflow Manager Styling changes
[ https://issues.apache.org/jira/browse/AMBARI-19985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865204#comment-15865204 ] Hudson commented on AMBARI-19985: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6730 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6730/]) AMBARI-19985. Workflow Manager Styling changes (Madhan Mohan Reddy via (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fcf396f3d9bf774c89af8d683e9e22fa1e9188c0]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/save-wf.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/job-details.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/search-table.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/flow-designer.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/styles/app.less * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-job-details.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/job-details.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/search-create-new-bar.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/job-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/utils/constants.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-workspace.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-actions.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/flow-designer.js > Workflow Manager Styling changes > > > Key: AMBARI-19985 > URL: https://issues.apache.org/jira/browse/AMBARI-19985 > 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-19985_trunk.patch > > > Workflow Manager Styling changes- Blue coloured fonts for action items. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19981) Hive View 2.0: Enable Notifications
[ https://issues.apache.org/jira/browse/AMBARI-19981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865202#comment-15865202 ] DIPAYAN BHOWMICK commented on AMBARI-19981: --- Added a new patch. Forgot to add license in one of the new files in the old patch. > Hive View 2.0: Enable Notifications > --- > > Key: AMBARI-19981 > URL: https://issues.apache.org/jira/browse/AMBARI-19981 > 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-19981.2.branch-2.5.patch, > AMBARI-19981.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19980) Hive1 View in Ambari shows wrong status
[ https://issues.apache.org/jira/browse/AMBARI-19980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865205#comment-15865205 ] Hudson commented on AMBARI-19980: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6730 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6730/]) AMBARI-19980. Hive1.5 View in Ambari shows wrong status.(gauravn7) (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=069ad4d7a239c356fb6cd35b45f80aa3ea36a296]) * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/index/history-query/logs.js > Hive1 View in Ambari shows wrong status > --- > > Key: AMBARI-19980 > URL: https://issues.apache.org/jira/browse/AMBARI-19980 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-19980_branch-2.5.patch, Screen Shot 2017-02-13 at > 1.06.40 PM.png > > > When running a query from hive view, the status of the query shows as RUNNING > even though the query actually failed. > RUNNING status never changes in Hive view. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19981) Hive View 2.0: Enable Notifications
[ https://issues.apache.org/jira/browse/AMBARI-19981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-19981: -- Attachment: AMBARI-19981.2.branch-2.5.patch > Hive View 2.0: Enable Notifications > --- > > Key: AMBARI-19981 > URL: https://issues.apache.org/jira/browse/AMBARI-19981 > 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-19981.2.branch-2.5.patch, > AMBARI-19981.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19981) Hive View 2.0: Enable Notifications
[ https://issues.apache.org/jira/browse/AMBARI-19981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-19981: -- Status: Patch Available (was: Reopened) > Hive View 2.0: Enable Notifications > --- > > Key: AMBARI-19981 > URL: https://issues.apache.org/jira/browse/AMBARI-19981 > 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-19981.2.branch-2.5.patch, > AMBARI-19981.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19980) Hive1 View in Ambari shows wrong status
[ https://issues.apache.org/jira/browse/AMBARI-19980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865197#comment-15865197 ] Hudson commented on AMBARI-19980: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #983 (See [https://builds.apache.org/job/Ambari-branch-2.5/983/]) AMBARI-19980. Hive1.5 View in Ambari shows wrong status.(gauravn7) (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2eeb0a0ac4cafebba75789de786af7af774dda64]) * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/index/history-query/logs.js > Hive1 View in Ambari shows wrong status > --- > > Key: AMBARI-19980 > URL: https://issues.apache.org/jira/browse/AMBARI-19980 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-19980_branch-2.5.patch, Screen Shot 2017-02-13 at > 1.06.40 PM.png > > > When running a query from hive view, the status of the query shows as RUNNING > even though the query actually failed. > RUNNING status never changes in Hive view. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19998) Unable to stop service when master components is down
[
https://issues.apache.org/jira/browse/AMBARI-19998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865171#comment-15865171
]
Hadoop QA commented on AMBARI-19998:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852485/AMBARI-19998.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-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10556//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10556//console
This message is automatically generated.
> Unable to stop service when master components is down
> -
>
> Key: AMBARI-19998
> URL: https://issues.apache.org/jira/browse/AMBARI-19998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk
>Reporter: WangJie
> Fix For: trunk
>
> Attachments: AMBARI-19998.patch, AMBARI-19998.png
>
>
> Unable to stop service when master component is down
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19990) Unable to delete config group.
[ https://issues.apache.org/jira/browse/AMBARI-19990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865155#comment-15865155 ] Rahul Pathak commented on AMBARI-19990: --- [~arborkar] I have replicated this in latest ambari version 2.4.2 Rahul > Unable to delete config group. > -- > > Key: AMBARI-19990 > URL: https://issues.apache.org/jira/browse/AMBARI-19990 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Rahul Pathak > > Currently deleting config group from Ambari does not work. > Deleting and saving will show it is gone however on checking again it will > show up with name Deleted. > Following can be seen in ambari-server.log if trying to rename deleted config > group: > org.apache.ambari.server.AmbariException: Config group not found, clusterName > = xyz, groupId = 2 > Workaround is to delete all references of group id from ambari database > manually. > Backup ambari-server database and run below queries. > delete from ambari."serviceconfighosts" where service_config_id in (select > service_config_id from serviceconfig where group_id=2); > delete from ambari."serviceconfigmapping" where service_config_id in (select > service_config_id from serviceconfig where group_id=2); > delete from ambari.serviceconfig where group_id=2; > Here 2 is group id for which ambari is throwing error. > Restart ambari-server. It will not display Deleted config group anymore. > Rahul -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19985) Workflow Manager Styling changes
[ https://issues.apache.org/jira/browse/AMBARI-19985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-19985: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Workflow Manager Styling changes > > > Key: AMBARI-19985 > URL: https://issues.apache.org/jira/browse/AMBARI-19985 > 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-19985_trunk.patch > > > Workflow Manager Styling changes- Blue coloured fonts for action items. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-14977) View: Capacity Scheduler View - Provide a more guided form to define queue mapping assignments
[ https://issues.apache.org/jira/browse/AMBARI-14977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated AMBARI-14977: -- Priority: Minor (was: Major) > View: Capacity Scheduler View - Provide a more guided form to define queue > mapping assignments > -- > > Key: AMBARI-14977 > URL: https://issues.apache.org/jira/browse/AMBARI-14977 > Project: Ambari > Issue Type: Task >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Minor > > h4. Cluster wide scheduling - Default mapping > Provide a more guided form to define default mapping assignments. Account for > mapping types, and for order in which assignments are applied. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19980) Hive1 View in Ambari shows wrong status
[ https://issues.apache.org/jira/browse/AMBARI-19980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-19980: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Hive1 View in Ambari shows wrong status > --- > > Key: AMBARI-19980 > URL: https://issues.apache.org/jira/browse/AMBARI-19980 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-19980_branch-2.5.patch, Screen Shot 2017-02-13 at > 1.06.40 PM.png > > > When running a query from hive view, the status of the query shows as RUNNING > even though the query actually failed. > RUNNING status never changes in Hive view. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19938) Hive2: Invalid query execution not handled properly
[
https://issues.apache.org/jira/browse/AMBARI-19938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865126#comment-15865126
]
Hadoop QA commented on AMBARI-19938:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852475/AMBARI-19938_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/hive20
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10555//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10555//console
This message is automatically generated.
> 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
>
> Attachments: AMBARI-19938_trunk.patch
>
>
> - Type "xxx;"
> - hit execute
> - wait forever
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19897) Provide user-warning while upgrading clusters to move certificates/keystores/truststores out of conf folder
[ https://issues.apache.org/jira/browse/AMBARI-19897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865115#comment-15865115 ] Hudson commented on AMBARI-19897: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #982 (See [https://builds.apache.org/job/Ambari-branch-2.5/982/]) AMBARI-19897 : Provide user-warning while upgrading clusters to move (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0392cabdab5ad6469e08f404370f35cd14cfd0bf]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (add) ambari-server/src/test/java/org/apache/ambari/server/checks/RangerSSLConfigCheckTest.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (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.4/upgrades/upgrade-2.6.xml * (add) ambari-server/src/main/java/org/apache/ambari/server/checks/RangerSSLConfigCheck.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml > Provide user-warning while upgrading clusters to move > certificates/keystores/truststores out of conf folder > --- > > Key: AMBARI-19897 > URL: https://issues.apache.org/jira/browse/AMBARI-19897 > 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-19897.1.patch, AMBARI-19897.patch > > > As certificates/ keystores/ truststores present in /etc/ranger/*/conf path, > this may affect the upgrade scenarios, where user needs to manually move the > files to new conf directories. > Hence users upgrading to new stacks should be warned on prior basis to do the > same manually (i.e move certificates/keystores/truststores out of conf > folder). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19999) Hive View 2.0 upload table issues
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-1: --- Attachment: AMBARI-1_branch-2.5.patch > Hive View 2.0 upload table issues > - > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > 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-1_branch-2.5.patch > > > following bugs in upload table feature: > 1. does not support to specify endlines in input file's fields > 2. if column datatype is char or varchar it gives error. > 3. temporary table does not get deleted if error occurs in table upload. > Options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19999) Hive View 2.0 upload table issues
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-1: --- Status: Patch Available (was: Open) > Hive View 2.0 upload table issues > - > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > 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-1_branch-2.5.patch > > > following bugs in upload table feature: > 1. does not support to specify endlines in input file's fields > 2. if column datatype is char or varchar it gives error. > 3. temporary table does not get deleted if error occurs in table upload. > Options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19897) Provide user-warning while upgrading clusters to move certificates/keystores/truststores out of conf folder
[ https://issues.apache.org/jira/browse/AMBARI-19897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19897: Resolution: Fixed Status: Resolved (was: Patch Available) committed to [branch-2.5|https://github.com/apache/ambari/commit/0392cabdab5ad6469e08f404370f35cd14cfd0bf] and [trunk|https://github.com/apache/ambari/commit/31944e382019482ee40e8ec4c691b6aea7fce230] > Provide user-warning while upgrading clusters to move > certificates/keystores/truststores out of conf folder > --- > > Key: AMBARI-19897 > URL: https://issues.apache.org/jira/browse/AMBARI-19897 > 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-19897.1.patch, AMBARI-19897.patch > > > As certificates/ keystores/ truststores present in /etc/ranger/*/conf path, > this may affect the upgrade scenarios, where user needs to manually move the > files to new conf directories. > Hence users upgrading to new stacks should be warned on prior basis to do the > same manually (i.e move certificates/keystores/truststores out of conf > folder). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19897) Provide user-warning while upgrading clusters to move certificates/keystores/truststores out of conf folder
[ https://issues.apache.org/jira/browse/AMBARI-19897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865091#comment-15865091 ] Hudson commented on AMBARI-19897: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6729 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6729/]) AMBARI-19897 : Provide user-warning while upgrading clusters to move (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=31944e382019482ee40e8ec4c691b6aea7fce230]) * (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/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (add) ambari-server/src/main/java/org/apache/ambari/server/checks/RangerSSLConfigCheck.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml * (add) ambari-server/src/test/java/org/apache/ambari/server/checks/RangerSSLConfigCheckTest.java > Provide user-warning while upgrading clusters to move > certificates/keystores/truststores out of conf folder > --- > > Key: AMBARI-19897 > URL: https://issues.apache.org/jira/browse/AMBARI-19897 > 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-19897.1.patch, AMBARI-19897.patch > > > As certificates/ keystores/ truststores present in /etc/ranger/*/conf path, > this may affect the upgrade scenarios, where user needs to manually move the > files to new conf directories. > Hence users upgrading to new stacks should be warned on prior basis to do the > same manually (i.e move certificates/keystores/truststores out of conf > folder). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19999) Hive View 2.0 upload table issues
Nitiraj Singh Rathore created AMBARI-1: -- Summary: Hive View 2.0 upload table issues Key: AMBARI-1 URL: https://issues.apache.org/jira/browse/AMBARI-1 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 following bugs in upload table feature: 1. does not support to specify endlines in input file's fields 2. if column datatype is char or varchar it gives error. 3. temporary table does not get deleted if error occurs in table upload. Options -- 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: - Summary: Hive2: Invalid query execution not handled properly (was: Hive2: Hive2: Invalid query execution not handled properly) > 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 > > Attachments: AMBARI-19938_trunk.patch > > > - Type "xxx;" > - hit execute > - wait forever -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19938) Hive2: 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: - Summary: Hive2: Hive2: Invalid query execution not handled properly (was: Hive2: xxx; never returns) > Hive2: 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 > > Attachments: AMBARI-19938_trunk.patch > > > - Type "xxx;" > - hit execute > - wait forever -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19998) Unable to stop service when master components is down
[ https://issues.apache.org/jira/browse/AMBARI-19998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-19998: - Description: Unable to stop service when master component is down (was: Unable to stop service when master components is down) > Unable to stop service when master components is down > - > > Key: AMBARI-19998 > URL: https://issues.apache.org/jira/browse/AMBARI-19998 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: WangJie > Fix For: trunk > > Attachments: AMBARI-19998.patch, AMBARI-19998.png > > > Unable to stop service when master component is down -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19998) Unable to stop service when master components is down
[ https://issues.apache.org/jira/browse/AMBARI-19998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-19998: - Attachment: AMBARI-19998.patch > Unable to stop service when master components is down > - > > Key: AMBARI-19998 > URL: https://issues.apache.org/jira/browse/AMBARI-19998 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: WangJie > Fix For: trunk > > Attachments: AMBARI-19998.patch, AMBARI-19998.png > > > Unable to stop service when master components is down -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19998) Unable to stop service when master components is down
[ https://issues.apache.org/jira/browse/AMBARI-19998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-19998: - Status: Patch Available (was: Open) > Unable to stop service when master components is down > - > > Key: AMBARI-19998 > URL: https://issues.apache.org/jira/browse/AMBARI-19998 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: WangJie > Fix For: trunk > > Attachments: AMBARI-19998.patch, AMBARI-19998.png > > > Unable to stop service when master components is down -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19997) Fix file permission issue of Livy recovery folder in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19997: --- Priority: Critical (was: Major) > Fix file permission issue of Livy recovery folder in Ambari > --- > > Key: AMBARI-19997 > URL: https://issues.apache.org/jira/browse/AMBARI-19997 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Saisai Shao >Assignee: Saisai Shao >Priority: Critical > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19997) Fix file permission issue of Livy recovery folder in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19997: --- Fix Version/s: 2.5.0 > Fix file permission issue of Livy recovery folder in Ambari > --- > > Key: AMBARI-19997 > URL: https://issues.apache.org/jira/browse/AMBARI-19997 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Saisai Shao >Assignee: Saisai Shao > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19998) Unable to stop service when master components is down
[ https://issues.apache.org/jira/browse/AMBARI-19998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-19998: - Attachment: AMBARI-19998.png > Unable to stop service when master components is down > - > > Key: AMBARI-19998 > URL: https://issues.apache.org/jira/browse/AMBARI-19998 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: WangJie > Fix For: trunk > > Attachments: AMBARI-19998.png > > > Unable to stop service when master components is down -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19998) Unable to stop service when master components is down
WangJie created AMBARI-19998: Summary: Unable to stop service when master components is down Key: AMBARI-19998 URL: https://issues.apache.org/jira/browse/AMBARI-19998 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: trunk Reporter: WangJie Fix For: trunk Unable to stop service when master components is down -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19997) Fix file permission issue of Livy recovery folder in Ambari
Saisai Shao created AMBARI-19997: Summary: Fix file permission issue of Livy recovery folder in Ambari Key: AMBARI-19997 URL: https://issues.apache.org/jira/browse/AMBARI-19997 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Saisai Shao Assignee: Saisai Shao -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19938) Hive2: xxx; never returns
[ 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: xxx; never returns > - > > 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 > > Attachments: AMBARI-19938_trunk.patch > > > - Type "xxx;" > - hit execute > - wait forever -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19938) Hive2: xxx; never returns
[ https://issues.apache.org/jira/browse/AMBARI-19938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19938: - Attachment: AMBARI-19938_trunk.patch > Hive2: xxx; never returns > - > > 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 > > Attachments: AMBARI-19938_trunk.patch > > > - Type "xxx;" > - hit execute > - wait forever -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19871: -- Status: Patch Available (was: Reopened) > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19871_fix1.patch, AMBARI-19871_fix2.patch, > AMBARI-19871.patch > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang reopened AMBARI-19871: --- > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19871_fix1.patch, AMBARI-19871_fix2.patch, > AMBARI-19871.patch > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19871: -- Attachment: AMBARI-19871_fix2.patch > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19871_fix1.patch, AMBARI-19871_fix2.patch, > AMBARI-19871.patch > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-19911) When yarn-site.xml is changed, MapReduce related components should be required to restart
[ https://issues.apache.org/jira/browse/AMBARI-19911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuanbo Liu reassigned AMBARI-19911: --- Assignee: Yuanbo Liu > When yarn-site.xml is changed, MapReduce related components should be > required to restart > - > > Key: AMBARI-19911 > URL: https://issues.apache.org/jira/browse/AMBARI-19911 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Yuanbo Liu >Assignee: Yuanbo Liu > Fix For: trunk > > Attachments: AMBARI-19911.001.patch > > > Some properties in yarn-site.xml are used by MR components, such as > "yarn.admin.acl", it's a good practice to have MR restart when yarn-site.xml > is modified. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19992) Hive metrics are not collected if AMS HTTPS is enabled.
[
https://issues.apache.org/jira/browse/AMBARI-19992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864909#comment-15864909
]
Hudson commented on AMBARI-19992:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6728 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6728/])
AMBARI-19992 : Hive metrics are not collected if AMS HTTPS is enabled.
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=399b70835fa076377018e6aa40de762df0c1e5fc])
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-llaptaskscheduler.j2
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-hivemetastore.properties.j2
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-llapdaemon.j2
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-hiveserver2.properties.j2
> Hive metrics are not collected if AMS HTTPS is enabled.
> ---
>
> Key: AMBARI-19992
> URL: https://issues.apache.org/jira/browse/AMBARI-19992
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19992.patch
>
>
> In Hive logs
> {code}
> 2017-02-13 21:20:04,316 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to
> send metrics to. Metrics to be sent will be discarded.
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(476))
> - Unable to connect to collector to find live nodes.
> 2017-02-13 21:20:14,313 INFO [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:refreshCollectorsFromConfigured(419)) -
> Collector ctr-e127-1486658464320-4990-01-05.hwx.site is not longer live.
> Removing it from list of know live collector hosts : []
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(399)) - Couldn't
> find any live collectors. Returning null
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to
> send metrics to. Metrics to be sent will be discarded.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-19871) Config version switch/compare/revert doesn't work
[
https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864905#comment-15864905
]
Richard Zang edited comment on AMBARI-19871 at 2/14/17 2:31 AM:
Found another problem caused by action parameter binding. Ember always invokes
action with the parameter bind in the first rendering. Only action parameter
from template is having this problem, direct text parameter binding is working
fine. So, right now if you click cross button and open the pulldown version
list, hover a version and click some action on its right popup. The following
action will alway be invoked with the first version you hovered as it's action
parameter. We did not have this problem on version pull down list or the
horizontal version box list because we had separate version popup generated for
each version box/item, yet now we are reusing a single box for all versions
from pulldown list.
{code}
{{action doAction view.parentView.hoveredServiceVersion
view.parentView.actionTypes.SWITCH target="view.parentView"}}
{code}
was (Author: rzang):
Found another problem caused by action parameter binding. Ember always invokes
action with the parameter bind in the first rendering. Only action parameter
from template is having this problem, direct text parameter binding is working
fine. So, right now if you click cross button and open the pulldown version
list. The following action will alway be invoked with the first version you
hovered as it's action parameter. We did not have this problem on version pull
down list or the horizontal version box list because we had separate version
popup generated for each version box/item, yet now we are reusing a single box
for all versions from pulldown list.
{code}
{{action doAction view.parentView.hoveredServiceVersion
view.parentView.actionTypes.SWITCH target="view.parentView"}}
{code}
> Config version switch/compare/revert doesn't work
> -
>
> Key: AMBARI-19871
> URL: https://issues.apache.org/jira/browse/AMBARI-19871
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19871_fix1.patch, AMBARI-19871.patch
>
>
> *Steps to reproduce:*
> 1. Go to any service with multiple config versions.
> 2. On the bottom left of the config history bar(the cross button), select an
> older version and click View.
> *Actual result:*
> Now direct clicking on other config version block will not be able to switch
> version. Only through the cross button can you switch to other version.
> Compare configs also does not work, it always compare to the current version
> and end up with empty diff.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19992) Hive metrics are not collected if AMS HTTPS is enabled.
[
https://issues.apache.org/jira/browse/AMBARI-19992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864906#comment-15864906
]
Hudson commented on AMBARI-19992:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #981 (See
[https://builds.apache.org/job/Ambari-branch-2.5/981/])
AMBARI-19992 : Hive metrics are not collected if AMS HTTPS is enabled.
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=809453d4d026481c412ec42c144618342601da5a])
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-llapdaemon.j2
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-hivemetastore.properties.j2
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-llaptaskscheduler.j2
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-hiveserver2.properties.j2
> Hive metrics are not collected if AMS HTTPS is enabled.
> ---
>
> Key: AMBARI-19992
> URL: https://issues.apache.org/jira/browse/AMBARI-19992
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19992.patch
>
>
> In Hive logs
> {code}
> 2017-02-13 21:20:04,316 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to
> send metrics to. Metrics to be sent will be discarded.
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(476))
> - Unable to connect to collector to find live nodes.
> 2017-02-13 21:20:14,313 INFO [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:refreshCollectorsFromConfigured(419)) -
> Collector ctr-e127-1486658464320-4990-01-05.hwx.site is not longer live.
> Removing it from list of know live collector hosts : []
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(399)) - Couldn't
> find any live collectors. Returning null
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to
> send metrics to. Metrics to be sent will be discarded.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-18952) Register BackupObserver and BackupHFileCleaner
[ https://issues.apache.org/jira/browse/AMBARI-18952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-18952: Description: Over in HBASE-14417, two new classes are added. org.apache.hadoop.hbase.backup.BackupHFileCleaner should be registered through hbase.master.hfilecleaner.plugins . It is responsible for keeping bulk loaded hfiles so that incremental backup can pick them up. org.apache.hadoop.hbase.backup.BackupObserver should be registered through hbase.coprocessor.region.classes It is notified when bulk load completes and writes records into hbase:backup table. was: Over in HBASE-14417, two new classes are added. org.apache.hadoop.hbase.backup.BackupHFileCleaner should be registered through hbase.master.hfilecleaner.plugins . It is responsible for keeping bulk loaded hfiles so that incremental backup can pick them up. org.apache.hadoop.hbase.backup.BackupObserver should be registered through hbase.coprocessor.region.classes It is notified when bulk load completes and writes records into hbase:backup table. > Register BackupObserver and BackupHFileCleaner > -- > > Key: AMBARI-18952 > URL: https://issues.apache.org/jira/browse/AMBARI-18952 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > Over in HBASE-14417, two new classes are added. > org.apache.hadoop.hbase.backup.BackupHFileCleaner should be registered > through hbase.master.hfilecleaner.plugins . It is responsible for keeping > bulk loaded hfiles so that incremental backup can pick them up. > org.apache.hadoop.hbase.backup.BackupObserver should be registered through > hbase.coprocessor.region.classes > It is notified when bulk load completes and writes records into hbase:backup > table. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19871) Config version switch/compare/revert doesn't work
[
https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864905#comment-15864905
]
Richard Zang commented on AMBARI-19871:
---
Found another problem caused by action parameter binding. Ember always invokes
action with the parameter bind in the first rendering. Only action parameter
from template is having this problem, direct text parameter binding is working
fine. So, right now if you click cross button and open the pulldown version
list. The following action will alway be invoked with the first version you
hovered as it's action parameter. We did not have this problem on version pull
down list or the horizontal version box list because we had separate version
popup generated for each version box/item, yet now we are reusing a single box
for all versions from pulldown list.
{code}
{{action doAction view.parentView.hoveredServiceVersion
view.parentView.actionTypes.SWITCH target="view.parentView"}}
{code}
> Config version switch/compare/revert doesn't work
> -
>
> Key: AMBARI-19871
> URL: https://issues.apache.org/jira/browse/AMBARI-19871
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19871_fix1.patch, AMBARI-19871.patch
>
>
> *Steps to reproduce:*
> 1. Go to any service with multiple config versions.
> 2. On the bottom left of the config history bar(the cross button), select an
> older version and click View.
> *Actual result:*
> Now direct clicking on other config version block will not be able to switch
> version. Only through the cross button can you switch to other version.
> Compare configs also does not work, it always compare to the current version
> and end up with empty diff.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19992) Hive metrics are not collected if AMS HTTPS is enabled.
[
https://issues.apache.org/jira/browse/AMBARI-19992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19992:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5 and trunk.
> Hive metrics are not collected if AMS HTTPS is enabled.
> ---
>
> Key: AMBARI-19992
> URL: https://issues.apache.org/jira/browse/AMBARI-19992
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19992.patch
>
>
> In Hive logs
> {code}
> 2017-02-13 21:20:04,316 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to
> send metrics to. Metrics to be sent will be discarded.
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(476))
> - Unable to connect to collector to find live nodes.
> 2017-02-13 21:20:14,313 INFO [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:refreshCollectorsFromConfigured(419)) -
> Collector ctr-e127-1486658464320-4990-01-05.hwx.site is not longer live.
> Removing it from list of know live collector hosts : []
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(399)) - Couldn't
> find any live collectors. Returning null
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to
> send metrics to. Metrics to be sent will be discarded.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19992) Hive metrics are not collected if AMS HTTPS is enabled.
[
https://issues.apache.org/jira/browse/AMBARI-19992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864849#comment-15864849
]
Sumit Mohanty commented on AMBARI-19992:
LGTM, +1
> Hive metrics are not collected if AMS HTTPS is enabled.
> ---
>
> Key: AMBARI-19992
> URL: https://issues.apache.org/jira/browse/AMBARI-19992
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19992.patch
>
>
> In Hive logs
> {code}
> 2017-02-13 21:20:04,316 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to
> send metrics to. Metrics to be sent will be discarded.
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(476))
> - Unable to connect to collector to find live nodes.
> 2017-02-13 21:20:14,313 INFO [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:refreshCollectorsFromConfigured(419)) -
> Collector ctr-e127-1486658464320-4990-01-05.hwx.site is not longer live.
> Removing it from list of know live collector hosts : []
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(399)) - Couldn't
> find any live collectors. Returning null
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to
> send metrics to. Metrics to be sent will be discarded.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19990) Unable to delete config group.
[ https://issues.apache.org/jira/browse/AMBARI-19990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864838#comment-15864838 ] Amruta Borkar commented on AMBARI-19990: Which version is causing this defect? > Unable to delete config group. > -- > > Key: AMBARI-19990 > URL: https://issues.apache.org/jira/browse/AMBARI-19990 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Rahul Pathak > > Currently deleting config group from Ambari does not work. > Deleting and saving will show it is gone however on checking again it will > show up with name Deleted. > Following can be seen in ambari-server.log if trying to rename deleted config > group: > org.apache.ambari.server.AmbariException: Config group not found, clusterName > = xyz, groupId = 2 > Workaround is to delete all references of group id from ambari database > manually. > Backup ambari-server database and run below queries. > delete from ambari."serviceconfighosts" where service_config_id in (select > service_config_id from serviceconfig where group_id=2); > delete from ambari."serviceconfigmapping" where service_config_id in (select > service_config_id from serviceconfig where group_id=2); > delete from ambari.serviceconfig where group_id=2; > Here 2 is group id for which ambari is throwing error. > Restart ambari-server. It will not display Deleted config group anymore. > Rahul -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19930) The service check status was set to TIMEOUT even if service check was failed
[
https://issues.apache.org/jira/browse/AMBARI-19930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864820#comment-15864820
]
Hudson commented on AMBARI-19930:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #980 (See
[https://builds.apache.org/job/Ambari-branch-2.5/980/])
AMBARI-19930. The service check status was set to TIMEOUT even if (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f8863d26be527c97d8884ae663c125802ec0])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionScheduler.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionScheduler.java
> The service check status was set to TIMEOUT even if service check was failed
>
>
> Key: AMBARI-19930
> URL: https://issues.apache.org/jira/browse/AMBARI-19930
> Project: Ambari
> Issue Type: Bug
>Reporter: Yesha Vora
>Assignee: Myroslav Papirkovskyi
>
> Steps to reproduce:
> * Install a cluster with Hadoop, Tez, Hbase , Hive, Spark
> * Enable Wire encryption
> * Run Tez service check
> Here, agent.service.check.task.timeout is set to 600 sec. Tez application was
> started in background. The service check then tries to find out SUCCESS file
> for couple of minutes only. In this particular instance, the application took
> 5 minutes to run. Thus, the check for SUCCESS file on HDFS failed.
> In this scenario, the status for service check should be failed instead
> Timeout.
> {code}
> stderr: /var/lib/ambari-agent/data/errors-370.txt
> stdout: /var/lib/ambari-agent/data/output-370.txt
> 2017-02-08 03:55:55,017 -
> HdfsResource['/hdp/apps/2.6.0.0-xxx/tez/tez.tar.gz'] {'security_enabled':
> True, 'hadoop_bin_dir': '/usr/hdp/current/hadoop-client/bin', 'keytab':
> '/etc/security/keytabs/hdfs.headless.keytab', 'source':
> '/usr/hdp/2.6.0.0-xxx/tez/lib/tez.tar.gz', 'dfs_type': '', 'default_fs':
> 'hdfs://host:8020', 'replace_existing_files': False,
> 'hdfs_resource_ignore_file':
> '/var/lib/ambari-agent/data/.hdfs_resource_ignore', 'hdfs_site': ...,
> 'kinit_path_local': '/usr/bin/kinit', 'principal_name': 'h...@example.com',
> 'user': 'hdfs', 'owner': 'hdfs', 'group': 'hadoop', 'hadoop_conf_dir':
> '/usr/hdp/current/hadoop-client/conf', 'type': 'file', 'action':
> ['create_on_execute'], 'immutable_paths': [u'/apps/hive/warehouse',
> u'/mr-history/done', u'/app-logs', u'/tmp'], 'mode': 0444}
> 2017-02-08 03:55:55,017 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/hdfs.headless.keytab h...@example.com'] {'user': 'hdfs'}
> 2017-02-08 03:55:55,096 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c
> 'curl -sS -L -w '"'"'%{http_code}'"'"' -X GET --negotiate -u : -k
> '"'"'https://host:50470/webhdfs/v1/hdp/apps/2.6.0.0-xxx/tez/tez.tar.gz?op=GETFILESTATUS&user.name=hdfs'"'"'
> 1>/tmp/tmpoIadeN 2>/tmp/tmp6nFiLj''] {'logoutput': None, 'quiet': False}
> 2017-02-08 03:55:55,292 - call returned (0, '')
> 2017-02-08 03:55:55,293 - DFS file /hdp/apps/2.6.0.0-xxx/tez/tez.tar.gz is
> identical to /usr/hdp/2.6.0.0-xxx/tez/lib/tez.tar.gz, skipping the copying
> 2017-02-08 03:55:55,293 - Will attempt to copy tez tarball from
> /usr/hdp/2.6.0.0-xxx/tez/lib/tez.tar.gz to DFS at
> /hdp/apps/2.6.0.0-xxx/tez/tez.tar.gz.
> 2017-02-08 03:55:55,293 - HdfsResource[None] {'security_enabled': True,
> 'hadoop_bin_dir': '/usr/hdp/current/hadoop-client/bin', 'keytab':
> '/etc/security/keytabs/hdfs.headless.keytab', 'dfs_type': '', 'default_fs':
> 'hdfs://host:8020', 'hdfs_resource_ignore_file':
> '/var/lib/ambari-agent/data/.hdfs_resource_ignore', 'hdfs_site': ...,
> 'kinit_path_local': '/usr/bin/kinit', 'principal_name': 'h...@example.com',
> 'user': 'hdfs', 'action': ['execute'], 'hadoop_conf_dir':
> '/usr/hdp/current/hadoop-client/conf', 'immutable_paths':
> [u'/apps/hive/warehouse', u'/mr-history/done', u'/app-logs', u'/tmp']}
> 2017-02-08 03:55:55,294 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com;']
> {'user': 'ambari-qa'}
> 2017-02-08 03:55:55,389 - ExecuteHadoop['jar
> /usr/hdp/current/tez-client/tez-examples*.jar orderedwordcount
> /tmp/tezsmokeinput/sample-tez-test /tmp/tezsmokeoutput/'] {'try_sleep': 5,
> 'tries': 3, 'bin_dir': '/usr/hdp/current/hadoop-client/bin', 'user':
> 'ambari-qa', 'conf_dir': '/usr/hdp/current/hadoop-client/conf'}
> 2017-02-08 03:55:55,390 - Execute['hadoop --config
> /usr/hdp/current/hadoop-client/conf jar
> /usr/hdp/current/tez-client/tez-examples*.jar orderedwordcount
> /tmp/tezsmokeinput/sample-tez-test /tmp/tezsmokeoutput/'] {'logoutput': None,
> 'try_sleep': 5, 'environment': {}, 'tries': 3, 'user': 'ambari-qa', 'path':
> ['/usr/hdp/current/hadoop-client/bin']}{code}
> {code}
> Requests: {
> aborted_tas
[jira] [Resolved] (AMBARI-19930) The service check status was set to TIMEOUT even if service check was failed
[
https://issues.apache.org/jira/browse/AMBARI-19930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty resolved AMBARI-19930.
Resolution: Fixed
Committed to branch-2.5
> The service check status was set to TIMEOUT even if service check was failed
>
>
> Key: AMBARI-19930
> URL: https://issues.apache.org/jira/browse/AMBARI-19930
> Project: Ambari
> Issue Type: Bug
>Reporter: Yesha Vora
>Assignee: Myroslav Papirkovskyi
>
> Steps to reproduce:
> * Install a cluster with Hadoop, Tez, Hbase , Hive, Spark
> * Enable Wire encryption
> * Run Tez service check
> Here, agent.service.check.task.timeout is set to 600 sec. Tez application was
> started in background. The service check then tries to find out SUCCESS file
> for couple of minutes only. In this particular instance, the application took
> 5 minutes to run. Thus, the check for SUCCESS file on HDFS failed.
> In this scenario, the status for service check should be failed instead
> Timeout.
> {code}
> stderr: /var/lib/ambari-agent/data/errors-370.txt
> stdout: /var/lib/ambari-agent/data/output-370.txt
> 2017-02-08 03:55:55,017 -
> HdfsResource['/hdp/apps/2.6.0.0-xxx/tez/tez.tar.gz'] {'security_enabled':
> True, 'hadoop_bin_dir': '/usr/hdp/current/hadoop-client/bin', 'keytab':
> '/etc/security/keytabs/hdfs.headless.keytab', 'source':
> '/usr/hdp/2.6.0.0-xxx/tez/lib/tez.tar.gz', 'dfs_type': '', 'default_fs':
> 'hdfs://host:8020', 'replace_existing_files': False,
> 'hdfs_resource_ignore_file':
> '/var/lib/ambari-agent/data/.hdfs_resource_ignore', 'hdfs_site': ...,
> 'kinit_path_local': '/usr/bin/kinit', 'principal_name': 'h...@example.com',
> 'user': 'hdfs', 'owner': 'hdfs', 'group': 'hadoop', 'hadoop_conf_dir':
> '/usr/hdp/current/hadoop-client/conf', 'type': 'file', 'action':
> ['create_on_execute'], 'immutable_paths': [u'/apps/hive/warehouse',
> u'/mr-history/done', u'/app-logs', u'/tmp'], 'mode': 0444}
> 2017-02-08 03:55:55,017 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/hdfs.headless.keytab h...@example.com'] {'user': 'hdfs'}
> 2017-02-08 03:55:55,096 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c
> 'curl -sS -L -w '"'"'%{http_code}'"'"' -X GET --negotiate -u : -k
> '"'"'https://host:50470/webhdfs/v1/hdp/apps/2.6.0.0-xxx/tez/tez.tar.gz?op=GETFILESTATUS&user.name=hdfs'"'"'
> 1>/tmp/tmpoIadeN 2>/tmp/tmp6nFiLj''] {'logoutput': None, 'quiet': False}
> 2017-02-08 03:55:55,292 - call returned (0, '')
> 2017-02-08 03:55:55,293 - DFS file /hdp/apps/2.6.0.0-xxx/tez/tez.tar.gz is
> identical to /usr/hdp/2.6.0.0-xxx/tez/lib/tez.tar.gz, skipping the copying
> 2017-02-08 03:55:55,293 - Will attempt to copy tez tarball from
> /usr/hdp/2.6.0.0-xxx/tez/lib/tez.tar.gz to DFS at
> /hdp/apps/2.6.0.0-xxx/tez/tez.tar.gz.
> 2017-02-08 03:55:55,293 - HdfsResource[None] {'security_enabled': True,
> 'hadoop_bin_dir': '/usr/hdp/current/hadoop-client/bin', 'keytab':
> '/etc/security/keytabs/hdfs.headless.keytab', 'dfs_type': '', 'default_fs':
> 'hdfs://host:8020', 'hdfs_resource_ignore_file':
> '/var/lib/ambari-agent/data/.hdfs_resource_ignore', 'hdfs_site': ...,
> 'kinit_path_local': '/usr/bin/kinit', 'principal_name': 'h...@example.com',
> 'user': 'hdfs', 'action': ['execute'], 'hadoop_conf_dir':
> '/usr/hdp/current/hadoop-client/conf', 'immutable_paths':
> [u'/apps/hive/warehouse', u'/mr-history/done', u'/app-logs', u'/tmp']}
> 2017-02-08 03:55:55,294 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com;']
> {'user': 'ambari-qa'}
> 2017-02-08 03:55:55,389 - ExecuteHadoop['jar
> /usr/hdp/current/tez-client/tez-examples*.jar orderedwordcount
> /tmp/tezsmokeinput/sample-tez-test /tmp/tezsmokeoutput/'] {'try_sleep': 5,
> 'tries': 3, 'bin_dir': '/usr/hdp/current/hadoop-client/bin', 'user':
> 'ambari-qa', 'conf_dir': '/usr/hdp/current/hadoop-client/conf'}
> 2017-02-08 03:55:55,390 - Execute['hadoop --config
> /usr/hdp/current/hadoop-client/conf jar
> /usr/hdp/current/tez-client/tez-examples*.jar orderedwordcount
> /tmp/tezsmokeinput/sample-tez-test /tmp/tezsmokeoutput/'] {'logoutput': None,
> 'try_sleep': 5, 'environment': {}, 'tries': 3, 'user': 'ambari-qa', 'path':
> ['/usr/hdp/current/hadoop-client/bin']}{code}
> {code}
> Requests: {
> aborted_task_count: 0,
> cluster_name: "cl1",
> completed_task_count: 1,
> create_time: 1486526151743,
> end_time: 1486526463038,
> exclusive: false,
> failed_task_count: 0,
> id: 29,
> inputs: "{}",
> operation_level: null,
> progress_percent: 100,
> queued_task_count: 0,
> request_context: "WE API TEZ Service Check",
> request_schedule: null,
> request_status: "TIMEDOUT",
> resource_filters: [
> {
> service_name: "TEZ"
> }
> ],
> start_time: 1486526151751,
> task_count: 1,
> timed_out_task_count: 1,
> type:
[jira] [Commented] (AMBARI-19992) Hive metrics are not collected if AMS HTTPS is enabled.
[
https://issues.apache.org/jira/browse/AMBARI-19992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864713#comment-15864713
]
Hadoop QA commented on AMBARI-19992:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852434/AMBARI-19992.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10554//console
This message is automatically generated.
> Hive metrics are not collected if AMS HTTPS is enabled.
> ---
>
> Key: AMBARI-19992
> URL: https://issues.apache.org/jira/browse/AMBARI-19992
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19992.patch
>
>
> In Hive logs
> {code}
> 2017-02-13 21:20:04,316 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to
> send metrics to. Metrics to be sent will be discarded.
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(476))
> - Unable to connect to collector to find live nodes.
> 2017-02-13 21:20:14,313 INFO [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:refreshCollectorsFromConfigured(419)) -
> Collector ctr-e127-1486658464320-4990-01-05.hwx.site is not longer live.
> Removing it from list of know live collector hosts : []
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(399)) - Couldn't
> find any live collectors. Returning null
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to
> send metrics to. Metrics to be sent will be discarded.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19994) Add PowerPC architecture support to contrib views
[
https://issues.apache.org/jira/browse/AMBARI-19994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864711#comment-15864711
]
Hadoop QA commented on AMBARI-19994:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852438/AMBARI-19994.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10553//console
This message is automatically generated.
> Add PowerPC architecture support to contrib views
> -
>
> Key: AMBARI-19994
> URL: https://issues.apache.org/jira/browse/AMBARI-19994
> Project: Ambari
> Issue Type: Bug
> Components: infra
>Affects Versions: 2.5.0
> Environment: Centos7 ppc64le
>Reporter: Vi On
> Labels: build
> Attachments: AMBARI-19994.patch
>
>
> Ambari builds currently fails on building hive, hive-jdbc, files, and hue
> views for powerpc. The build tries to download an x86 version of nodejs.
> The latest frontend-maven-plugin 1.3 supports powerpc architecture so we
> should update to version 1.3.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-19996) Perform kinit on Kafka Start
Bharat Viswanadham created AMBARI-19996: --- Summary: Perform kinit on Kafka Start Key: AMBARI-19996 URL: https://issues.apache.org/jira/browse/AMBARI-19996 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Bharat Viswanadham Assignee: Bharat Viswanadham Perform Kinit with kafka keytab on Kafka broker start. As Kafka Client uses the cached kerberos ticket, so when kafka console commands like producer, consumer are run with kafka user and cluster is kerberoized, kinit should happen automatically -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19981) Hive View 2.0: Enable Notifications
[ https://issues.apache.org/jira/browse/AMBARI-19981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864698#comment-15864698 ] Hudson commented on AMBARI-19981: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #979 (See [https://builds.apache.org/job/Ambari-branch-2.5/979/]) Revert "AMBARI-19981. Hive View 2.0: Enable Notifications. (dipayanb)" (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8fdc2b0ec32d3559887214043a918fce16124273]) * (edit) contrib/views/hive20/src/main/resources/ui/config/environment.js * (delete) contrib/views/hive20/src/main/resources/ui/app/controllers/messages.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/new-database.js * (delete) contrib/views/hive20/src/main/resources/ui/app/controllers/messages/message.js * (delete) contrib/views/hive20/src/main/resources/ui/app/templates/settings-loading.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/table/rename.js * (delete) contrib/views/hive20/src/main/resources/ui/app/templates/databases-loading.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/jobs.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/new.js * (delete) contrib/views/hive20/src/main/resources/ui/app/templates/databases/database/tables/table-loading.hbs * (delete) contrib/views/hive20/src/main/resources/ui/app/templates/udfs-loading.hbs * (delete) contrib/views/hive20/src/main/resources/ui/app/templates/savedqueries-loading.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/components/create-table.js * (delete) contrib/views/hive20/src/main/resources/ui/app/helpers/alert-message-context-class.js * (edit) contrib/views/hive20/src/main/resources/ui/app/configs/file-format.js * (delete) contrib/views/hive20/src/main/resources/ui/app/helpers/alert-message-icon-class.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/alert-messages.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/messages/message.hbs * (delete) contrib/views/hive20/src/main/resources/ui/app/helpers/shorten-text.js * (delete) contrib/views/hive20/src/main/resources/ui/app/templates/databases/database/tables-loading.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/table.js * (delete) contrib/views/hive20/src/main/resources/ui/app/mixins/ui-logger.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/settings.js * (delete) contrib/views/hive20/src/main/resources/ui/app/templates/jobs-loading.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/table/edit.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/messages.hbs > Hive View 2.0: Enable Notifications > --- > > Key: AMBARI-19981 > URL: https://issues.apache.org/jira/browse/AMBARI-19981 > 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-19981.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19981) Hive View 2.0: Enable Notifications
[ https://issues.apache.org/jira/browse/AMBARI-19981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864697#comment-15864697 ] Yusaku Sako commented on AMBARI-19981: -- Reverted from trunk and branch-2.5 due to rat check failure. > Hive View 2.0: Enable Notifications > --- > > Key: AMBARI-19981 > URL: https://issues.apache.org/jira/browse/AMBARI-19981 > 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-19981.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19995) HiveServerInteractive. Use "get_user_call_output()" instead of "shell.checked_call()" as it keeps the MOTD logging separated from STDOUT. Removed unnecessary log lines.
Swapan Shridhar created AMBARI-19995: Summary: HiveServerInteractive. Use "get_user_call_output()" instead of "shell.checked_call()" as it keeps the MOTD logging separated from STDOUT. Removed unnecessary log lines. Key: AMBARI-19995 URL: https://issues.apache.org/jira/browse/AMBARI-19995 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19994) Add PowerPC architecture support to contrib views
[ https://issues.apache.org/jira/browse/AMBARI-19994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vi On updated AMBARI-19994: --- Status: Patch Available (was: Open) > Add PowerPC architecture support to contrib views > - > > Key: AMBARI-19994 > URL: https://issues.apache.org/jira/browse/AMBARI-19994 > Project: Ambari > Issue Type: Bug > Components: infra >Affects Versions: 2.5.0 > Environment: Centos7 ppc64le >Reporter: Vi On > Labels: build > Attachments: AMBARI-19994.patch > > > Ambari builds currently fails on building hive, hive-jdbc, files, and hue > views for powerpc. The build tries to download an x86 version of nodejs. > The latest frontend-maven-plugin 1.3 supports powerpc architecture so we > should update to version 1.3. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19994) Add PowerPC architecture support to contrib views
[ https://issues.apache.org/jira/browse/AMBARI-19994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vi On updated AMBARI-19994: --- Attachment: AMBARI-19994.patch > Add PowerPC architecture support to contrib views > - > > Key: AMBARI-19994 > URL: https://issues.apache.org/jira/browse/AMBARI-19994 > Project: Ambari > Issue Type: Bug > Components: infra >Affects Versions: 2.5.0 > Environment: Centos7 ppc64le >Reporter: Vi On > Labels: build > Attachments: AMBARI-19994.patch > > > Ambari builds currently fails on building hive, hive-jdbc, files, and hue > views for powerpc. The build tries to download an x86 version of nodejs. > The latest frontend-maven-plugin 1.3 supports powerpc architecture so we > should update to version 1.3. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19972) Stop All services call failed to stop flume agent
[
https://issues.apache.org/jira/browse/AMBARI-19972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864650#comment-15864650
]
Hudson commented on AMBARI-19972:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6726 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6726/])
AMBARI-19972. Stop All services call failed to stop flume (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4deacdd7ba81ba4348d1929c09a66858dbd5ba6c])
* (edit) ambari-server/src/test/python/stacks/2.0.6/FLUME/test_flume.py
* (edit)
ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/scripts/flume.py
> Stop All services call failed to stop flume agent
> -
>
> Key: AMBARI-19972
> URL: https://issues.apache.org/jira/browse/AMBARI-19972
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.0
>
> Attachments: AMBARI-19972.patch, flume_stop_stack_trace.log
>
>
> Scenario:
> * Install a cluster with Hadoop, Hive, Flume, Hbase, Spark
> * Enable Wire encryption
> ** While enabling wire encryption, script makes a rest call to stop all
> services. In this instance the WE stop all service failed to stop flume agent
> on one of the hosts
> As per cluster state, Ambari failed to stop a2 agent on Host4. However stderr
> stack trace says it failed to stop a1 agent.
> {code:title=stderr}
> stderr: /var/lib/ambari-agent/data/errors-203.txt
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
> line 126, in
> FlumeHandler().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/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
> line 60, in stop
> flume(action='stop')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume.py",
> line 226, in flume
> raise Fail("Can't stop flume agent: {0}".format(agent))
> resource_management.core.exceptions.Fail: Can't stop flume agent: a1{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-19994) Add PowerPC architecture support to contrib views
Vi On created AMBARI-19994: -- Summary: Add PowerPC architecture support to contrib views Key: AMBARI-19994 URL: https://issues.apache.org/jira/browse/AMBARI-19994 Project: Ambari Issue Type: Bug Components: infra Affects Versions: 2.5.0 Environment: Centos7 ppc64le Reporter: Vi On Ambari builds currently fails on building hive, hive-jdbc, files, and hue views for powerpc. The build tries to download an x86 version of nodejs. The latest frontend-maven-plugin 1.3 supports powerpc architecture so we should update to version 1.3. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19972) Stop All services call failed to stop flume agent
[
https://issues.apache.org/jira/browse/AMBARI-19972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864646#comment-15864646
]
Hudson commented on AMBARI-19972:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #978 (See
[https://builds.apache.org/job/Ambari-branch-2.5/978/])
AMBARI-19972. Stop All services call failed to stop flume (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b0af5f74181e9704eb9bf7fe8e897859885866ca])
* (edit)
ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/scripts/flume.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/FLUME/test_flume.py
> Stop All services call failed to stop flume agent
> -
>
> Key: AMBARI-19972
> URL: https://issues.apache.org/jira/browse/AMBARI-19972
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.0
>
> Attachments: AMBARI-19972.patch, flume_stop_stack_trace.log
>
>
> Scenario:
> * Install a cluster with Hadoop, Hive, Flume, Hbase, Spark
> * Enable Wire encryption
> ** While enabling wire encryption, script makes a rest call to stop all
> services. In this instance the WE stop all service failed to stop flume agent
> on one of the hosts
> As per cluster state, Ambari failed to stop a2 agent on Host4. However stderr
> stack trace says it failed to stop a1 agent.
> {code:title=stderr}
> stderr: /var/lib/ambari-agent/data/errors-203.txt
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
> line 126, in
> FlumeHandler().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/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
> line 60, in stop
> flume(action='stop')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume.py",
> line 226, in flume
> raise Fail("Can't stop flume agent: {0}".format(agent))
> resource_management.core.exceptions.Fail: Can't stop flume agent: a1{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19972) Stop All services call failed to stop flume agent
[
https://issues.apache.org/jira/browse/AMBARI-19972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-19972:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> Stop All services call failed to stop flume agent
> -
>
> Key: AMBARI-19972
> URL: https://issues.apache.org/jira/browse/AMBARI-19972
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.0
>
> Attachments: AMBARI-19972.patch, flume_stop_stack_trace.log
>
>
> Scenario:
> * Install a cluster with Hadoop, Hive, Flume, Hbase, Spark
> * Enable Wire encryption
> ** While enabling wire encryption, script makes a rest call to stop all
> services. In this instance the WE stop all service failed to stop flume agent
> on one of the hosts
> As per cluster state, Ambari failed to stop a2 agent on Host4. However stderr
> stack trace says it failed to stop a1 agent.
> {code:title=stderr}
> stderr: /var/lib/ambari-agent/data/errors-203.txt
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
> line 126, in
> FlumeHandler().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/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
> line 60, in stop
> flume(action='stop')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume.py",
> line 226, in flume
> raise Fail("Can't stop flume agent: {0}".format(agent))
> resource_management.core.exceptions.Fail: Can't stop flume agent: a1{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19992) Hive metrics are not collected if AMS HTTPS is enabled.
[
https://issues.apache.org/jira/browse/AMBARI-19992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19992:
---
Status: Patch Available (was: Open)
> Hive metrics are not collected if AMS HTTPS is enabled.
> ---
>
> Key: AMBARI-19992
> URL: https://issues.apache.org/jira/browse/AMBARI-19992
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19992.patch
>
>
> In Hive logs
> {code}
> 2017-02-13 21:20:04,316 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to
> send metrics to. Metrics to be sent will be discarded.
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(476))
> - Unable to connect to collector to find live nodes.
> 2017-02-13 21:20:14,313 INFO [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:refreshCollectorsFromConfigured(419)) -
> Collector ctr-e127-1486658464320-4990-01-05.hwx.site is not longer live.
> Removing it from list of know live collector hosts : []
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(399)) - Couldn't
> find any live collectors. Returning null
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to
> send metrics to. Metrics to be sent will be discarded.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19992) Hive metrics are not collected if AMS HTTPS is enabled.
[
https://issues.apache.org/jira/browse/AMBARI-19992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19992:
---
Attachment: AMBARI-19992.patch
> Hive metrics are not collected if AMS HTTPS is enabled.
> ---
>
> Key: AMBARI-19992
> URL: https://issues.apache.org/jira/browse/AMBARI-19992
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19992.patch
>
>
> In Hive logs
> {code}
> 2017-02-13 21:20:04,316 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to
> send metrics to. Metrics to be sent will be discarded.
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(476))
> - Unable to connect to collector to find live nodes.
> 2017-02-13 21:20:14,313 INFO [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:refreshCollectorsFromConfigured(419)) -
> Collector ctr-e127-1486658464320-4990-01-05.hwx.site is not longer live.
> Removing it from list of know live collector hosts : []
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(399)) - Couldn't
> find any live collectors. Returning null
> 2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to
> send metrics to. Metrics to be sent will be discarded.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19993) Update atlas log-4j.xml configurations in ambari
[ https://issues.apache.org/jira/browse/AMBARI-19993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19993: Attachment: AMBARI-19993.patch > Update atlas log-4j.xml configurations in ambari > > > Key: AMBARI-19993 > URL: https://issues.apache.org/jira/browse/AMBARI-19993 > 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-19993.patch > > > Need to update atlas-log4j configurations in ambari to reflect latest in > atlas. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19993) Update atlas log-4j.xml configurations in ambari
Vishal Suvagia created AMBARI-19993: --- Summary: Update atlas log-4j.xml configurations in ambari Key: AMBARI-19993 URL: https://issues.apache.org/jira/browse/AMBARI-19993 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 Need to update atlas-log4j configurations in ambari to reflect latest in atlas. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19992) Hive metrics are not collected if AMS HTTPS is enabled.
Aravindan Vijayan created AMBARI-19992:
--
Summary: Hive metrics are not collected if AMS HTTPS is enabled.
Key: AMBARI-19992
URL: https://issues.apache.org/jira/browse/AMBARI-19992
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.5.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Critical
Fix For: 2.5.0
In Hive logs
{code}
2017-02-13 21:20:04,316 WARN [timeline]: timeline.HadoopTimelineMetricsSink
(AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to send
metrics to. Metrics to be sent will be discarded.
2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
(AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(476))
- Unable to connect to collector to find live nodes.
2017-02-13 21:20:14,313 INFO [timeline]: timeline.HadoopTimelineMetricsSink
(AbstractTimelineMetricsSink.java:refreshCollectorsFromConfigured(419)) -
Collector ctr-e127-1486658464320-4990-01-05.hwx.site is not longer live.
Removing it from list of know live collector hosts : []
2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
(AbstractTimelineMetricsSink.java:findPreferredCollectHost(399)) - Couldn't
find any live collectors. Returning null
2017-02-13 21:20:14,313 WARN [timeline]: timeline.HadoopTimelineMetricsSink
(AbstractTimelineMetricsSink.java:emitMetrics(227)) - No live collector to send
metrics to. Metrics to be sent will be discarded.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19915) Add Ranger KMS SSL properties in ambari stack
[
https://issues.apache.org/jira/browse/AMBARI-19915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864282#comment-15864282
]
Hadoop QA commented on AMBARI-19915:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852405/AMBARI-19915.1.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10552//console
This message is automatically generated.
> Add Ranger KMS SSL properties in ambari stack
> -
>
> Key: AMBARI-19915
> URL: https://issues.apache.org/jira/browse/AMBARI-19915
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19915.1.patch, AMBARI-19915.patch
>
>
> These are few properties, we observed in Ranger KMS: which needs to be added
> in Ambari for Ranger KMS in SSL environment.
> * ranger.service.https.attrib.keystore.file
> * ranger.service.https.attrib.client.auth
> * ranger.service.https.attrib.keystore.keyalias
> * ranger.service.https.attrib.keystore.pass
> * ranger.credential.provider.path
> * ranger.service.https.attrib.keystore.credential.alias
> Along with addition of these properties, we need to mask password properties
> so that plaintext passwords are not visible in config files.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19991) cluster deployment fails if cluster template has fewer host_groups than that in blueprint
[
https://issues.apache.org/jira/browse/AMBARI-19991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864279#comment-15864279
]
Hadoop QA commented on AMBARI-19991:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852407/AMBARI-19991.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10551//console
This message is automatically generated.
> cluster deployment fails if cluster template has fewer host_groups than that
> in blueprint
> -
>
> Key: AMBARI-19991
> URL: https://issues.apache.org/jira/browse/AMBARI-19991
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, blueprints
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-19991.patch
>
>
> cluster creation REST API request gets accepted when, cluster template does
> not list all the host_groups mentioned in the blueprint. But cluster
> deployment hangs showing error message in the logs
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:908)
> at
> org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:889)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19991) cluster deployment fails if cluster template has fewer host_groups than that in blueprint
[ https://issues.apache.org/jira/browse/AMBARI-19991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-19991: --- Status: Patch Available (was: In Progress) > cluster deployment fails if cluster template has fewer host_groups than that > in blueprint > - > > Key: AMBARI-19991 > URL: https://issues.apache.org/jira/browse/AMBARI-19991 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-19991.patch > > > cluster creation REST API request gets accepted when, cluster template does > not list all the host_groups mentioned in the blueprint. But cluster > deployment hangs showing error message in the logs > Caused by: java.lang.IllegalArgumentException: > TopologyManager.ConfigureClusterTask - prerequisites for config request > processing not yet satisfied > at > org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:908) > at > org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:889) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19991) cluster deployment fails if cluster template has fewer host_groups than that in blueprint
[ https://issues.apache.org/jira/browse/AMBARI-19991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-19991: --- Attachment: AMBARI-19991.patch > cluster deployment fails if cluster template has fewer host_groups than that > in blueprint > - > > Key: AMBARI-19991 > URL: https://issues.apache.org/jira/browse/AMBARI-19991 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-19991.patch > > > cluster creation REST API request gets accepted when, cluster template does > not list all the host_groups mentioned in the blueprint. But cluster > deployment hangs showing error message in the logs > Caused by: java.lang.IllegalArgumentException: > TopologyManager.ConfigureClusterTask - prerequisites for config request > processing not yet satisfied > at > org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:908) > at > org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:889) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19974) Test and fix new Notifications/Alerts styles on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864262#comment-15864262 ] Xi Wang commented on AMBARI-19974: -- Committed to side-navigation-feature-branch > Test and fix new Notifications/Alerts styles on Ambari > -- > > Key: AMBARI-19974 > URL: https://issues.apache.org/jira/browse/AMBARI-19974 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19974.patch, AMBARI-19974.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19974) Test and fix new Notifications/Alerts styles on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19974: - Resolution: Fixed Status: Resolved (was: Patch Available) > Test and fix new Notifications/Alerts styles on Ambari > -- > > Key: AMBARI-19974 > URL: https://issues.apache.org/jira/browse/AMBARI-19974 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19974.patch, AMBARI-19974.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19991) cluster deployment fails if cluster template has fewer host_groups than that in blueprint
Amruta Borkar created AMBARI-19991: -- Summary: cluster deployment fails if cluster template has fewer host_groups than that in blueprint Key: AMBARI-19991 URL: https://issues.apache.org/jira/browse/AMBARI-19991 Project: Ambari Issue Type: Bug Components: ambari-server, blueprints Reporter: Amruta Borkar Assignee: Amruta Borkar Fix For: trunk cluster creation REST API request gets accepted when, cluster template does not list all the host_groups mentioned in the blueprint. But cluster deployment hangs showing error message in the logs Caused by: java.lang.IllegalArgumentException: TopologyManager.ConfigureClusterTask - prerequisites for config request processing not yet satisfied at org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:908) at org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:889) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19974) Test and fix new Notifications/Alerts styles on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19974: - Status: Patch Available (was: Open) > Test and fix new Notifications/Alerts styles on Ambari > -- > > Key: AMBARI-19974 > URL: https://issues.apache.org/jira/browse/AMBARI-19974 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19974.patch, AMBARI-19974.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19974) Test and fix new Notifications/Alerts styles on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19974: - Attachment: AMBARI-19974.patch > Test and fix new Notifications/Alerts styles on Ambari > -- > > Key: AMBARI-19974 > URL: https://issues.apache.org/jira/browse/AMBARI-19974 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19974.patch, AMBARI-19974.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19974) Test and fix new Notifications/Alerts styles on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864232#comment-15864232 ] Xi Wang commented on AMBARI-19974: -- 20322 passing (26s) 153 pending > Test and fix new Notifications/Alerts styles on Ambari > -- > > Key: AMBARI-19974 > URL: https://issues.apache.org/jira/browse/AMBARI-19974 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19974.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19970) AMS graphs are not present on cluster with SSL
[
https://issues.apache.org/jira/browse/AMBARI-19970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864217#comment-15864217
]
Hudson commented on AMBARI-19970:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6725 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6725/])
AMBARI-19970 : AMS graphs are not present on cluster with SSL (Commit
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7cb9a6ad53a926f055c5bf78ac2a9a8bd1668d78])
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/templates/hadoop-metrics2-hbase.properties.j2
> AMS graphs are not present on cluster with SSL
> --
>
> Key: AMBARI-19970
> URL: https://issues.apache.org/jira/browse/AMBARI-19970
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19970.patch
>
>
> AMS graphs are not present on cluster with SSL
> https://172.27.30.84:8443/api/v1/clusters/cl1/services/AMBARI_METRICS/components/METRICS_COLLECTOR?fields=metrics/hbase/master/AverageLoad[1486750817,1486755417,15],metrics/hbase/regionserver/storefiles[1486750817,1486755417,15],metrics/hbase/regionserver/regions[1486750817,1486755417,15],metrics/hbase/regionserver/requests._rate[1486750817,1486755417,15],metrics/hbase/regionserver/blockCacheHitPercent[1486750817,1486755417,15],metrics/hbase/regionserver/compactionQueueSize[1486750817,1486755417,15]&_=1486755418562
> {code}
> {
> "href" :
> "https://172.27.30.84:8443/api/v1/clusters/cl1/services/AMBARI_METRICS/components/METRICS_COLLECTOR?fields=metrics/hbase/master/AverageLoad[1486750817,1486755417,15],metrics/hbase/regionserver/storefiles[1486750817,1486755417,15],metrics/hbase/regionserver/regions[1486750817,1486755417,15],metrics/hbase/regionserver/requests._rate[1486750817,1486755417,15],metrics/hbase/regionserver/blockCacheHitPercent[1486750817,1486755417,15],metrics/hbase/regionserver/compactionQueueSize[1486750817,1486755417,15]&_=1486755418562";,
> "ServiceComponentInfo" : {
> "cluster_name" : "cl1",
> "component_name" : "METRICS_COLLECTOR",
> "service_name" : "AMBARI_METRICS"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19915) Add Ranger KMS SSL properties in ambari stack
[ https://issues.apache.org/jira/browse/AMBARI-19915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-19915: - Attachment: AMBARI-19915.1.patch > Add Ranger KMS SSL properties in ambari stack > - > > Key: AMBARI-19915 > URL: https://issues.apache.org/jira/browse/AMBARI-19915 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19915.1.patch, AMBARI-19915.patch > > > These are few properties, we observed in Ranger KMS: which needs to be added > in Ambari for Ranger KMS in SSL environment. > * ranger.service.https.attrib.keystore.file > * ranger.service.https.attrib.client.auth > * ranger.service.https.attrib.keystore.keyalias > * ranger.service.https.attrib.keystore.pass > * ranger.credential.provider.path > * ranger.service.https.attrib.keystore.credential.alias > Along with addition of these properties, we need to mask password properties > so that plaintext passwords are not visible in config files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19989) Allow user to view Tez View after executing query
[ https://issues.apache.org/jira/browse/AMBARI-19989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-19989: Attachment: AMBARI-19989.branch-2.5.patch > Allow user to view Tez View after executing query > - > > Key: AMBARI-19989 > URL: https://issues.apache.org/jira/browse/AMBARI-19989 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Labels: hive-view > Fix For: 2.5.0 > > Attachments: AMBARI-19989.branch-2.5.patch > > > As per the parity with Hive View 1.5, allow user to traverse to tez view from > the query page after executing a query. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19974) Test and fix new Notifications/Alerts styles on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19974: - Attachment: AMBARI-19974.patch > Test and fix new Notifications/Alerts styles on Ambari > -- > > Key: AMBARI-19974 > URL: https://issues.apache.org/jira/browse/AMBARI-19974 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19974.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19911) When yarn-site.xml is changed, MapReduce related components should be required to restart
[
https://issues.apache.org/jira/browse/AMBARI-19911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864168#comment-15864168
]
Hadoop QA commented on AMBARI-19911:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12851537/AMBARI-19911.001.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10550//console
This message is automatically generated.
> When yarn-site.xml is changed, MapReduce related components should be
> required to restart
> -
>
> Key: AMBARI-19911
> URL: https://issues.apache.org/jira/browse/AMBARI-19911
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Yuanbo Liu
> Fix For: trunk
>
> Attachments: AMBARI-19911.001.patch
>
>
> Some properties in yarn-site.xml are used by MR components, such as
> "yarn.admin.acl", it's a good practice to have MR restart when yarn-site.xml
> is modified.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19972) Stop All services call failed to stop flume agent
[
https://issues.apache.org/jira/browse/AMBARI-19972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864165#comment-15864165
]
Hadoop QA commented on AMBARI-19972:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852375/AMBARI-19972.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10549//console
This message is automatically generated.
> Stop All services call failed to stop flume agent
> -
>
> Key: AMBARI-19972
> URL: https://issues.apache.org/jira/browse/AMBARI-19972
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.0
>
> Attachments: AMBARI-19972.patch, flume_stop_stack_trace.log
>
>
> Scenario:
> * Install a cluster with Hadoop, Hive, Flume, Hbase, Spark
> * Enable Wire encryption
> ** While enabling wire encryption, script makes a rest call to stop all
> services. In this instance the WE stop all service failed to stop flume agent
> on one of the hosts
> As per cluster state, Ambari failed to stop a2 agent on Host4. However stderr
> stack trace says it failed to stop a1 agent.
> {code:title=stderr}
> stderr: /var/lib/ambari-agent/data/errors-203.txt
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
> line 126, in
> FlumeHandler().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/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
> line 60, in stop
> flume(action='stop')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume.py",
> line 226, in flume
> raise Fail("Can't stop flume agent: {0}".format(agent))
> resource_management.core.exceptions.Fail: Can't stop flume agent: a1{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19988) Zeppelin UI to support proxy access via Knox in Ambari
[
https://issues.apache.org/jira/browse/AMBARI-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864161#comment-15864161
]
Hadoop QA commented on AMBARI-19988:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852377/AMBARI-19988_HDP-2.5_v1.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10548//console
This message is automatically generated.
> Zeppelin UI to support proxy access via Knox in Ambari
> --
>
> Key: AMBARI-19988
> URL: https://issues.apache.org/jira/browse/AMBARI-19988
> Project: Ambari
> Issue Type: Bug
>Reporter: Prabhjyot Singh
>Assignee: Prabhjyot Singh
> Attachments: AMBARI-19988_HDP-2.5_v1.patch
>
>
> Zeppelin UI to support proxy access via Knox should get configured with
> Ambari out-of-the-box.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19989) Allow user to view Tez View after executing query
[ https://issues.apache.org/jira/browse/AMBARI-19989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-19989: Summary: Allow user to view Tez View after executing query (was: User should not be allowed to Execute or visualize empty query, Allow user to view Tez View after executing query) > Allow user to view Tez View after executing query > - > > Key: AMBARI-19989 > URL: https://issues.apache.org/jira/browse/AMBARI-19989 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Labels: hive-view > Fix For: 2.5.0 > > > User should not be allowed to Execute or visualize empty query. As of now > when user performs these actions with empty query, UI keeps on loading in > that state without coming out of it. > Steps to reproduce : > 1) Navigate to Hive 2.0 query editor. > 2) Click on Execute/Visual Explain with empty query. > 3) UI keeps on loading. > And as per the parity with Hive View 1.5, allow user to traverse to tez view > from the query page after executing a query. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19989) Allow user to view Tez View after executing query
[ https://issues.apache.org/jira/browse/AMBARI-19989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-19989: Description: As per the parity with Hive View 1.5, allow user to traverse to tez view from the query page after executing a query. was: User should not be allowed to Execute or visualize empty query. As of now when user performs these actions with empty query, UI keeps on loading in that state without coming out of it. Steps to reproduce : 1) Navigate to Hive 2.0 query editor. 2) Click on Execute/Visual Explain with empty query. 3) UI keeps on loading. And as per the parity with Hive View 1.5, allow user to traverse to tez view from the query page after executing a query. > Allow user to view Tez View after executing query > - > > Key: AMBARI-19989 > URL: https://issues.apache.org/jira/browse/AMBARI-19989 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Labels: hive-view > Fix For: 2.5.0 > > > As per the parity with Hive View 1.5, allow user to traverse to tez view from > the query page after executing a query. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19990) Unable to delete config group.
[ https://issues.apache.org/jira/browse/AMBARI-19990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Pathak updated AMBARI-19990: -- Description: Currently deleting config group from Ambari does not work. Deleting and saving will show it is gone however on checking again it will show up with name Deleted. Following can be seen in ambari-server.log if trying to rename deleted config group: org.apache.ambari.server.AmbariException: Config group not found, clusterName = xyz, groupId = 2 Workaround is to delete all references of group id from ambari database manually. Backup ambari-server database and run below queries. delete from ambari."serviceconfighosts" where service_config_id in (select service_config_id from serviceconfig where group_id=2); delete from ambari."serviceconfigmapping" where service_config_id in (select service_config_id from serviceconfig where group_id=2); delete from ambari.serviceconfig where group_id=2; Here 2 is group id for which ambari is throwing error. Restart ambari-server. It will not display Deleted config group anymore. Rahul was: Currently deleting config group from Ambari does not work. Deleting and saving will show it is gone however on checking again it will show up with name Deleted. Following can be seen in ambari-server.log if trying to rename deleted config group: org.apache.ambari.server.AmbariException: Config group not found, clusterName = xyz, groupId = 2 Workaround is to delete all references of group id from ambari database manually. Backup ambari-server database and run below queries. delete from ambari."serviceconfighosts" where service_config_id in (select service_config_id from serviceconfig where group_id=2); delete from ambari."serviceconfigmapping" where service_config_id in (select service_config_id from serviceconfig where group_id=2); delete from ambari.serviceconfig where group_id=2; Here 2 is group id for which ambari is throwing error. Rahul > Unable to delete config group. > -- > > Key: AMBARI-19990 > URL: https://issues.apache.org/jira/browse/AMBARI-19990 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Rahul Pathak > > Currently deleting config group from Ambari does not work. > Deleting and saving will show it is gone however on checking again it will > show up with name Deleted. > Following can be seen in ambari-server.log if trying to rename deleted config > group: > org.apache.ambari.server.AmbariException: Config group not found, clusterName > = xyz, groupId = 2 > Workaround is to delete all references of group id from ambari database > manually. > Backup ambari-server database and run below queries. > delete from ambari."serviceconfighosts" where service_config_id in (select > service_config_id from serviceconfig where group_id=2); > delete from ambari."serviceconfigmapping" where service_config_id in (select > service_config_id from serviceconfig where group_id=2); > delete from ambari.serviceconfig where group_id=2; > Here 2 is group id for which ambari is throwing error. > Restart ambari-server. It will not display Deleted config group anymore. > Rahul -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19990) Unable to delete config group.
Rahul Pathak created AMBARI-19990: - Summary: Unable to delete config group. Key: AMBARI-19990 URL: https://issues.apache.org/jira/browse/AMBARI-19990 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Rahul Pathak Currently deleting config group from Ambari does not work. Deleting and saving will show it is gone however on checking again it will show up with name Deleted. Following can be seen in ambari-server.log if trying to rename deleted config group: org.apache.ambari.server.AmbariException: Config group not found, clusterName = xyz, groupId = 2 Workaround is to delete all references of group id from ambari database manually. Backup ambari-server database and run below queries. delete from ambari."serviceconfighosts" where service_config_id in (select service_config_id from serviceconfig where group_id=2); delete from ambari."serviceconfigmapping" where service_config_id in (select service_config_id from serviceconfig where group_id=2); delete from ambari.serviceconfig where group_id=2; Here 2 is group id for which ambari is throwing error. Rahul -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19989) User should not be allowed to Execute or visualize empty query, Allow user to view Tez View after executing query
[ https://issues.apache.org/jira/browse/AMBARI-19989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-19989: Labels: hive-view (was: ) > User should not be allowed to Execute or visualize empty query, Allow user to > view Tez View after executing query > - > > Key: AMBARI-19989 > URL: https://issues.apache.org/jira/browse/AMBARI-19989 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Labels: hive-view > Fix For: 2.5.0 > > > User should not be allowed to Execute or visualize empty query. As of now > when user performs these actions with empty query, UI keeps on loading in > that state without coming out of it. > Steps to reproduce : > 1) Navigate to Hive 2.0 query editor. > 2) Click on Execute/Visual Explain with empty query. > 3) UI keeps on loading. > And as per the parity with Hive View 1.5, allow user to traverse to tez view > from the query page after executing a query. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19989) User should not be allowed to Execute or visualize empty query, Allow user to view Tez View after executing query
venkat created AMBARI-19989: --- Summary: User should not be allowed to Execute or visualize empty query, Allow user to view Tez View after executing query Key: AMBARI-19989 URL: https://issues.apache.org/jira/browse/AMBARI-19989 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: venkat Assignee: venkat Fix For: 2.5.0 User should not be allowed to Execute or visualize empty query. As of now when user performs these actions with empty query, UI keeps on loading in that state without coming out of it. Steps to reproduce : 1) Navigate to Hive 2.0 query editor. 2) Click on Execute/Visual Explain with empty query. 3) UI keeps on loading. And as per the parity with Hive View 1.5, allow user to traverse to tez view from the query page after executing a query. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19987) Oozie start failed after enabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-19987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864070#comment-15864070
]
Hudson commented on AMBARI-19987:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6724 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6724/])
AMBARI-19987 Oozie start failed after enabling credential store (dsen) (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d252665ce94f532b08efb9bc5f31f7b8f6cde97a])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/api/query/render/ClusterBlueprintRenderer.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Service.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* (add) ambari-common/src/main/python/ambari_commons/credential_store_helper.py
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceDesiredStateEntity.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ServiceResourceProvider.java
* (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
> Oozie start failed after enabling credential store
> --
>
> Key: AMBARI-19987
> URL: https://issues.apache.org/jira/browse/AMBARI-19987
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19987_2.patch
>
>
> Oozie server start failed after enabling credential store.
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 222, in
> OozieServer().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/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 91, in start
> oozie_service(action='start', upgrade_type=upgrade_type)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
> line 109, in oozie_service
> user=params.oozie_user,
> 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
> '/base/tools/jdk1.8.0_112/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/oozie-server/libext/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://172.27.15.193/ooziedb'
[jira] [Commented] (AMBARI-19987) Oozie start failed after enabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-19987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864065#comment-15864065
]
Hudson commented on AMBARI-19987:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #977 (See
[https://builds.apache.org/job/Ambari-branch-2.5/977/])
AMBARI-19987 Oozie start failed after enabling credential store (dsen) (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ff4c849adce97c2a0c4f1adb1be07c2b740aa5e9])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/api/query/render/ClusterBlueprintRenderer.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py
* (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ServiceResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceDesiredStateEntity.java
* (add) ambari-common/src/main/python/ambari_commons/credential_store_helper.py
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Service.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
> Oozie start failed after enabling credential store
> --
>
> Key: AMBARI-19987
> URL: https://issues.apache.org/jira/browse/AMBARI-19987
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19987_2.patch
>
>
> Oozie server start failed after enabling credential store.
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 222, in
> OozieServer().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/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 91, in start
> oozie_service(action='start', upgrade_type=upgrade_type)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
> line 109, in oozie_service
> user=params.oozie_user,
> 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
> '/base/tools/jdk1.8.0_112/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/oozie-server/libext/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://172.27.15.193/ooziedb' oozieu
[jira] [Updated] (AMBARI-19987) Oozie start failed after enabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-19987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-19987:
Status: Patch Available (was: Open)
> Oozie start failed after enabling credential store
> --
>
> Key: AMBARI-19987
> URL: https://issues.apache.org/jira/browse/AMBARI-19987
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19987_2.patch
>
>
> Oozie server start failed after enabling credential store.
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 222, in
> OozieServer().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/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 91, in start
> oozie_service(action='start', upgrade_type=upgrade_type)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
> line 109, in oozie_service
> user=params.oozie_user,
> 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
> '/base/tools/jdk1.8.0_112/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/oozie-server/libext/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://172.27.15.193/ooziedb' oozieuser [PROTECTED]
> com.mysql.jdbc.Driver' returned 1. Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR: Unable to connect to the DB. Please check DB connection properties.
> java.sql.SQLException: Access denied for user
> 'oozieuser'@'ctr-e127-1486658464320-0864-01-04.hwx.site' (using password:
> NO)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19987) Oozie start failed after enabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-19987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864047#comment-15864047
]
Hadoop QA commented on AMBARI-19987:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852384/AMBARI-19987_2.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10546//console
This message is automatically generated.
> Oozie start failed after enabling credential store
> --
>
> Key: AMBARI-19987
> URL: https://issues.apache.org/jira/browse/AMBARI-19987
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19987_2.patch
>
>
> Oozie server start failed after enabling credential store.
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 222, in
> OozieServer().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/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 91, in start
> oozie_service(action='start', upgrade_type=upgrade_type)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
> line 109, in oozie_service
> user=params.oozie_user,
> 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
> '/base/tools/jdk1.8.0_112/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/oozie-server/libext/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://172.27.15.193/ooziedb' oozieuser [PROTECTED]
> com.mysql.jdbc.Driver' returned 1. Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR: Unable to connect to the DB. Please check DB connection properties.
> java.sql.SQLException: Access denied for user
> 'oozieuser'@'ctr-e127-1486658464320-0864-01-04.hwx.site' (using password:
> NO)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19987) Oozie start failed after enabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-19987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-19987:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> Oozie start failed after enabling credential store
> --
>
> Key: AMBARI-19987
> URL: https://issues.apache.org/jira/browse/AMBARI-19987
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19987_2.patch
>
>
> Oozie server start failed after enabling credential store.
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 222, in
> OozieServer().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/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 91, in start
> oozie_service(action='start', upgrade_type=upgrade_type)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
> line 109, in oozie_service
> user=params.oozie_user,
> 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
> '/base/tools/jdk1.8.0_112/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/oozie-server/libext/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://172.27.15.193/ooziedb' oozieuser [PROTECTED]
> com.mysql.jdbc.Driver' returned 1. Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR: Unable to connect to the DB. Please check DB connection properties.
> java.sql.SQLException: Access denied for user
> 'oozieuser'@'ctr-e127-1486658464320-0864-01-04.hwx.site' (using password:
> NO)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19987) Oozie start failed after enabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-19987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864050#comment-15864050
]
Hadoop QA commented on AMBARI-19987:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852384/AMBARI-19987_2.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10547//console
This message is automatically generated.
> Oozie start failed after enabling credential store
> --
>
> Key: AMBARI-19987
> URL: https://issues.apache.org/jira/browse/AMBARI-19987
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19987_2.patch
>
>
> Oozie server start failed after enabling credential store.
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 222, in
> OozieServer().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/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 91, in start
> oozie_service(action='start', upgrade_type=upgrade_type)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
> line 109, in oozie_service
> user=params.oozie_user,
> 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
> '/base/tools/jdk1.8.0_112/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/oozie-server/libext/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://172.27.15.193/ooziedb' oozieuser [PROTECTED]
> com.mysql.jdbc.Driver' returned 1. Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR: Unable to connect to the DB. Please check DB connection properties.
> java.sql.SQLException: Access denied for user
> 'oozieuser'@'ctr-e127-1486658464320-0864-01-04.hwx.site' (using password:
> NO)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19987) Oozie start failed after enabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-19987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-19987:
Attachment: AMBARI-19987_2.patch
> Oozie start failed after enabling credential store
> --
>
> Key: AMBARI-19987
> URL: https://issues.apache.org/jira/browse/AMBARI-19987
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19987_2.patch
>
>
> Oozie server start failed after enabling credential store.
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 222, in
> OozieServer().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/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 91, in start
> oozie_service(action='start', upgrade_type=upgrade_type)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
> line 109, in oozie_service
> user=params.oozie_user,
> 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
> '/base/tools/jdk1.8.0_112/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/oozie-server/libext/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://172.27.15.193/ooziedb' oozieuser [PROTECTED]
> com.mysql.jdbc.Driver' returned 1. Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR: Unable to connect to the DB. Please check DB connection properties.
> java.sql.SQLException: Access denied for user
> 'oozieuser'@'ctr-e127-1486658464320-0864-01-04.hwx.site' (using password:
> NO)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19987) Oozie start failed after enabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-19987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-19987:
Attachment: (was: AMBARI-19987.patch)
> Oozie start failed after enabling credential store
> --
>
> Key: AMBARI-19987
> URL: https://issues.apache.org/jira/browse/AMBARI-19987
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19987_2.patch
>
>
> Oozie server start failed after enabling credential store.
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 222, in
> OozieServer().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/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 91, in start
> oozie_service(action='start', upgrade_type=upgrade_type)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
> line 109, in oozie_service
> user=params.oozie_user,
> 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
> '/base/tools/jdk1.8.0_112/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/oozie-server/libext/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://172.27.15.193/ooziedb' oozieuser [PROTECTED]
> com.mysql.jdbc.Driver' returned 1. Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR: Unable to connect to the DB. Please check DB connection properties.
> java.sql.SQLException: Access denied for user
> 'oozieuser'@'ctr-e127-1486658464320-0864-01-04.hwx.site' (using password:
> NO)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19987) Oozie start failed after enabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-19987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-19987:
Status: Open (was: Patch Available)
> Oozie start failed after enabling credential store
> --
>
> Key: AMBARI-19987
> URL: https://issues.apache.org/jira/browse/AMBARI-19987
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19987.patch
>
>
> Oozie server start failed after enabling credential store.
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 222, in
> OozieServer().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/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 91, in start
> oozie_service(action='start', upgrade_type=upgrade_type)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
> line 109, in oozie_service
> user=params.oozie_user,
> 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
> '/base/tools/jdk1.8.0_112/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/oozie-server/libext/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://172.27.15.193/ooziedb' oozieuser [PROTECTED]
> com.mysql.jdbc.Driver' returned 1. Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR: Unable to connect to the DB. Please check DB connection properties.
> java.sql.SQLException: Access denied for user
> 'oozieuser'@'ctr-e127-1486658464320-0864-01-04.hwx.site' (using password:
> NO)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19987) Oozie start failed after enabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-19987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864037#comment-15864037
]
Hadoop QA commented on AMBARI-19987:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852370/AMBARI-19987.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10545//console
This message is automatically generated.
> Oozie start failed after enabling credential store
> --
>
> Key: AMBARI-19987
> URL: https://issues.apache.org/jira/browse/AMBARI-19987
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19987.patch
>
>
> Oozie server start failed after enabling credential store.
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 222, in
> OozieServer().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/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 91, in start
> oozie_service(action='start', upgrade_type=upgrade_type)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
> line 109, in oozie_service
> user=params.oozie_user,
> 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
> '/base/tools/jdk1.8.0_112/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/oozie-server/libext/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://172.27.15.193/ooziedb' oozieuser [PROTECTED]
> com.mysql.jdbc.Driver' returned 1. Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR: Unable to connect to the DB. Please check DB connection properties.
> java.sql.SQLException: Access denied for user
> 'oozieuser'@'ctr-e127-1486658464320-0864-01-04.hwx.site' (using password:
> NO)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19987) Oozie start failed after enabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-19987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-19987:
Status: Patch Available (was: In Progress)
> Oozie start failed after enabling credential store
> --
>
> Key: AMBARI-19987
> URL: https://issues.apache.org/jira/browse/AMBARI-19987
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19987.patch
>
>
> Oozie server start failed after enabling credential store.
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 222, in
> OozieServer().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/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 91, in start
> oozie_service(action='start', upgrade_type=upgrade_type)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
> line 109, in oozie_service
> user=params.oozie_user,
> 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
> '/base/tools/jdk1.8.0_112/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/oozie-server/libext/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://172.27.15.193/ooziedb' oozieuser [PROTECTED]
> com.mysql.jdbc.Driver' returned 1. Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR: Unable to connect to the DB. Please check DB connection properties.
> java.sql.SQLException: Access denied for user
> 'oozieuser'@'ctr-e127-1486658464320-0864-01-04.hwx.site' (using password:
> NO)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19988) Zeppelin UI to support proxy access via Knox in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-19988: - Attachment: AMBARI-19988_HDP-2.5_v1.patch > Zeppelin UI to support proxy access via Knox in Ambari > -- > > Key: AMBARI-19988 > URL: https://issues.apache.org/jira/browse/AMBARI-19988 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-19988_HDP-2.5_v1.patch > > > Zeppelin UI to support proxy access via Knox should get configured with > Ambari out-of-the-box. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19988) Zeppelin UI to support proxy access via Knox in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-19988: - Status: Patch Available (was: Open) > Zeppelin UI to support proxy access via Knox in Ambari > -- > > Key: AMBARI-19988 > URL: https://issues.apache.org/jira/browse/AMBARI-19988 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > > Zeppelin UI to support proxy access via Knox should get configured with > Ambari out-of-the-box. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
