[jira] [Updated] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging
[ https://issues.apache.org/jira/browse/AMBARI-18637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18637: --- Attachment: AMBARI-18637.patch > Management pack purge option should warn user and ask for confirmation before > purging > - > > Key: AMBARI-18637 > URL: https://issues.apache.org/jira/browse/AMBARI-18637 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.2 > > Attachments: AMBARI-18637.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging
[ https://issues.apache.org/jira/browse/AMBARI-18637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18637: --- Attachment: (was: AMBARI-18637.patch) > Management pack purge option should warn user and ask for confirmation before > purging > - > > Key: AMBARI-18637 > URL: https://issues.apache.org/jira/browse/AMBARI-18637 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.2 > > Attachments: AMBARI-18637.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging
[ https://issues.apache.org/jira/browse/AMBARI-18637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15597219#comment-15597219 ] Jayush Luniya commented on AMBARI-18637: Above test failures are not related to this patch. > Management pack purge option should warn user and ask for confirmation before > purging > - > > Key: AMBARI-18637 > URL: https://issues.apache.org/jira/browse/AMBARI-18637 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.2 > > Attachments: AMBARI-18637.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-17981: -- Status: Patch Available (was: Reopened) > Integrate Druid With Ambari > --- > > Key: AMBARI-17981 > URL: https://issues.apache.org/jira/browse/AMBARI-17981 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nishant Bangarwa >Assignee: Swapan Shridhar > Labels: features > Fix For: 2.5.0 > > Attachments: AMABARI-17981.patch > > > This task includes adding support for druid cluster provisioning via Ambari. > Details about Druid cluster design and different node types are present here > - > http://druid.io/docs/latest/design/design.html > In general, Druid can be defined as a service in HDP which has following > components - > 1) Coordinator > 2) Overlord > 3) Historical > 4) Broker > 5) Middlemanager > > Druid also has external dependencies on following > 1) Zookeeper - Ambari should be able to pass in zk configs to druid cluster > 2) Deep storage - A distributed FS, can be one of HDFS/S3 or any other NFS. > 3) Metadata Store - Mysql/Postgres. can be either provided by the user or a > mysql instance provisioned by ambari itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-17981: -- Attachment: AMABARI-17981.patch > Integrate Druid With Ambari > --- > > Key: AMBARI-17981 > URL: https://issues.apache.org/jira/browse/AMBARI-17981 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nishant Bangarwa >Assignee: Swapan Shridhar > Labels: features > Fix For: 2.5.0 > > Attachments: AMABARI-17981.patch > > > This task includes adding support for druid cluster provisioning via Ambari. > Details about Druid cluster design and different node types are present here > - > http://druid.io/docs/latest/design/design.html > In general, Druid can be defined as a service in HDP which has following > components - > 1) Coordinator > 2) Overlord > 3) Historical > 4) Broker > 5) Middlemanager > > Druid also has external dependencies on following > 1) Zookeeper - Ambari should be able to pass in zk configs to druid cluster > 2) Deep storage - A distributed FS, can be one of HDFS/S3 or any other NFS. > 3) Metadata Store - Mysql/Postgres. can be either provided by the user or a > mysql instance provisioned by ambari itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-17981: -- Attachment: (was: ambari-17981.patch) > Integrate Druid With Ambari > --- > > Key: AMBARI-17981 > URL: https://issues.apache.org/jira/browse/AMBARI-17981 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nishant Bangarwa >Assignee: Swapan Shridhar > Labels: features > Fix For: 2.5.0 > > Attachments: AMABARI-17981.patch > > > This task includes adding support for druid cluster provisioning via Ambari. > Details about Druid cluster design and different node types are present here > - > http://druid.io/docs/latest/design/design.html > In general, Druid can be defined as a service in HDP which has following > components - > 1) Coordinator > 2) Overlord > 3) Historical > 4) Broker > 5) Middlemanager > > Druid also has external dependencies on following > 1) Zookeeper - Ambari should be able to pass in zk configs to druid cluster > 2) Deep storage - A distributed FS, can be one of HDFS/S3 or any other NFS. > 3) Metadata Store - Mysql/Postgres. can be either provided by the user or a > mysql instance provisioned by ambari itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18669) Manage Journal Node Wizard Initial UI
[ https://issues.apache.org/jira/browse/AMBARI-18669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-18669: -- Attachment: AMBARI-18669.patch > Manage Journal Node Wizard Initial UI > - > > Key: AMBARI-18669 > URL: https://issues.apache.org/jira/browse/AMBARI-18669 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-18669.patch > > > Create a wizard to allow user to to add, remove, reassign JournalNodes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18669) Manage Journal Node Wizard Initial UI
Richard Zang created AMBARI-18669: - Summary: Manage Journal Node Wizard Initial UI Key: AMBARI-18669 URL: https://issues.apache.org/jira/browse/AMBARI-18669 Project: Ambari Issue Type: Task Components: ambari-admin Affects Versions: 2.5.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.5.0 Create a wizard to allow user to to add, remove, reassign JournalNodes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18668) Workflow Designer View: Tooltip for Edit button shows "Back"
[ https://issues.apache.org/jira/browse/AMBARI-18668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18668: Status: Patch Available (was: In Progress) > Workflow Designer View: Tooltip for Edit button shows "Back" > > > Key: AMBARI-18668 > URL: https://issues.apache.org/jira/browse/AMBARI-18668 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18668.patch > > > When you click on a workflow in the dashboard and hover over Edit Workflow > button, it shows the tooltip "Back" rather than Edit Workflow as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18668) Workflow Designer View: Tooltip for Edit button shows "Back"
[ https://issues.apache.org/jira/browse/AMBARI-18668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18668: Attachment: AMBARI-18668.patch > Workflow Designer View: Tooltip for Edit button shows "Back" > > > Key: AMBARI-18668 > URL: https://issues.apache.org/jira/browse/AMBARI-18668 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18668.patch > > > When you click on a workflow in the dashboard and hover over Edit Workflow > button, it shows the tooltip "Back" rather than Edit Workflow as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18664) While syncing with LDAP, username collisions should be handled based on configuration value
[
https://issues.apache.org/jira/browse/AMBARI-18664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596628#comment-15596628
]
Hadoop QA commented on AMBARI-18664:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834753/AMBARI-18664_branch-2.5_01.patch
against trunk revision .
{color:red}-1 patch{color}. Trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8977//console
This message is automatically generated.
> While syncing with LDAP, username collisions should be handled based on
> configuration value
> ---
>
> Key: AMBARI-18664
> URL: https://issues.apache.org/jira/browse/AMBARI-18664
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 2.4.2
>
> Attachments: AMBARI-18664_branch-2.4_01.patch,
> AMBARI-18664_branch-2.5_01.patch
>
>
> While syncing with LDAP, username collisions should be handled based on an
> LDAP sync configuration value.
> The configuration options should be to indicate the following behaviors
> * convert
> ** convert the existing (non-LDAP user) user to an LDAP user
> ** This is the existing behavior
> * skip
> ** skip or ignore the collision, leaving the existing user unchanged
> ** a new user record should not be created
> Note: Future behavior may be to cause the sync operation to fail, but that
> shouldn't be handed yet.
> This configuration value should be set when setting up LDAP sync properties
> via {{ambari-server setup-ldap}} and be enforced when processing the sync
> operation in methods like
> {{org.apache.ambari.server.controller.AmbariManagementControllerImpl#synchronizeLdapUsersAndGroups}}
> or {{org.apache.ambari.server.security.authorization.Users#processLdapSync}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18668) Workflow Designer View: Tooltip for Edit button shows "Back"
Sangeeta Ravindran created AMBARI-18668: --- Summary: Workflow Designer View: Tooltip for Edit button shows "Back" Key: AMBARI-18668 URL: https://issues.apache.org/jira/browse/AMBARI-18668 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran Priority: Minor Fix For: 2.5.0 When you click on a workflow in the dashboard and hover over Edit Workflow button, it shows the tooltip "Back" rather than Edit Workflow as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18665) Workflow Designer View: When you execute a workflow designer view instance, it does not load immediately unless you return to the dashboard.
[
https://issues.apache.org/jira/browse/AMBARI-18665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596607#comment-15596607
]
Hadoop QA commented on AMBARI-18665:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834764/AMBARI-18665.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/wfmanager
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8976//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8976//console
This message is automatically generated.
> Workflow Designer View: When you execute a workflow designer view instance,
> it does not load immediately unless you return to the dashboard.
>
>
> Key: AMBARI-18665
> URL: https://issues.apache.org/jira/browse/AMBARI-18665
> Project: Ambari
> Issue Type: Bug
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Attachments: AMBARI-18665.patch
>
>
> Workflow designer view doesn't execute on clicking the go to instance button
> after creating the view.
> Navigating to the Ambari dashboard and executing the view using the drop down
> menu works and loads the workflow designer view
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18667) Workflow Designer View: Folder hint does not get overwritten when you type folder name when creating folder in File Browser
[ https://issues.apache.org/jira/browse/AMBARI-18667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18667: Status: Patch Available (was: In Progress) > Workflow Designer View: Folder hint does not get overwritten when you type > folder name when creating folder in File Browser > --- > > Key: AMBARI-18667 > URL: https://issues.apache.org/jira/browse/AMBARI-18667 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18667.patch > > > 1.In the Workflow Designer View instance, click on Create Workflow and add a > FS action > 2. Try to create a new folder by clicking on "Create Folder". > 3. The folder hint "" does not get overwritten when you > type a folder name. > Expected results: > The hint should disappear when you start typing in the folder name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18667) Workflow Designer View: Folder hint does not get overwritten when you type folder name when creating folder in File Browser
[ https://issues.apache.org/jira/browse/AMBARI-18667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18667: Attachment: AMBARI-18667.patch > Workflow Designer View: Folder hint does not get overwritten when you type > folder name when creating folder in File Browser > --- > > Key: AMBARI-18667 > URL: https://issues.apache.org/jira/browse/AMBARI-18667 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18667.patch > > > 1.In the Workflow Designer View instance, click on Create Workflow and add a > FS action > 2. Try to create a new folder by clicking on "Create Folder". > 3. The folder hint "" does not get overwritten when you > type a folder name. > Expected results: > The hint should disappear when you start typing in the folder name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18667) Workflow Designer View: Folder hint does not get overwritten when you type folder name when creating folder in File Browser
Sangeeta Ravindran created AMBARI-18667: --- Summary: Workflow Designer View: Folder hint does not get overwritten when you type folder name when creating folder in File Browser Key: AMBARI-18667 URL: https://issues.apache.org/jira/browse/AMBARI-18667 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran Priority: Minor Fix For: 2.5.0 1.In the Workflow Designer View instance, click on Create Workflow and add a FS action 2. Try to create a new folder by clicking on "Create Folder". 3. The folder hint "" does not get overwritten when you type a folder name. Expected results: The hint should disappear when you start typing in the folder name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18666) Move HAWQ and PXF RCO from stacks to common-services
[ https://issues.apache.org/jira/browse/AMBARI-18666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-18666: -- Attachment: AMBARI-18666-trunk-orig.patch > Move HAWQ and PXF RCO from stacks to common-services > > > Key: AMBARI-18666 > URL: https://issues.apache.org/jira/browse/AMBARI-18666 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.5.0, 2.4.2 >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18666-trunk-orig.patch > > > Move HAWQ and PXF RCO from stacks to common-services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18666) Move HAWQ and PXF RCO from stacks to common-services
[ https://issues.apache.org/jira/browse/AMBARI-18666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-18666: -- Status: Patch Available (was: Open) > Move HAWQ and PXF RCO from stacks to common-services > > > Key: AMBARI-18666 > URL: https://issues.apache.org/jira/browse/AMBARI-18666 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.5.0, 2.4.2 >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18666-trunk-orig.patch > > > Move HAWQ and PXF RCO from stacks to common-services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18666) Move HAWQ and PXF RCO from stacks to common-services
Matt created AMBARI-18666: - Summary: Move HAWQ and PXF RCO from stacks to common-services Key: AMBARI-18666 URL: https://issues.apache.org/jira/browse/AMBARI-18666 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: trunk, 2.5.0, 2.4.2 Reporter: Matt Assignee: Matt Priority: Minor Fix For: trunk, 2.5.0, 2.4.2 Move HAWQ and PXF RCO from stacks to common-services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18635) Authorizations given to roles, should use generic role-based principals rather than hard-coded pseudo-role-based principals
[
https://issues.apache.org/jira/browse/AMBARI-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18635:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 176c691eaed6dbf639617f6208f7fb117597c1ce
Author: Robert Levas
Date: Fri Oct 21 16:01:44 2016 -0400
{noformat}
Committed to branch-2.5
{noformat}
commit 49f58e8402b543875c61f8d74a052bd6cd45a788
Author: Robert Levas
Date: Fri Oct 21 15:55:21 2016 -0400
{noformat}
Committed to branch-2.4
{noformat}
commit b632b33bc35afc5a01354e8916fdcdf698e49e19
Author: Robert Levas
Date: Fri Oct 21 18:38:04 2016 -0400
{noformat}
> Authorizations given to roles, should use generic role-based principals
> rather than hard-coded pseudo-role-based principals
> ---
>
> Key: AMBARI-18635
> URL: https://issues.apache.org/jira/browse/AMBARI-18635
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 2.4.2
>
> Attachments: AMBARI-18635_branch-2.4_01.patch,
> AMBARI-18635_branch-2.4_02.patch, AMBARI-18635_branch-2.5_01.patch,
> AMBARI-18635_branch-2.5_02.patch, AMBARI-18635_trunk_01.patch,
> AMBARI-18635_trunk_02.patch
>
>
> Authorizations given to roles, should use generic role-based principals
> rather than hard-coded resource types.
> Access to views can be assigned to all users with a given role. The
> implementation for this lead to the creation of hard-coded principals that
> represent the current set of roles. This is not dynamic enough for possibly
> future enhancements where new roles may be created by administrators.
> This needs to be changed such that rather that using the hard-coded
> pseudo-role-principals, the dynamically generated role-principals are to be
> used.
> The hard-coded pseudo-role-principals have the following
> {{adminprincipaltype}} values as opposed to "ROLE":
> * ALL.CLUSTER.ADMINISTRATOR
> * ALL.CLUSTER.OPERATOR
> * ALL.SERVICE.ADMINISTRATOR
> * ALL.SERVICE.OPERATOR
> * ALL.CLUSTER.USER
> These should be removed along with the associated {{adminprincipal}} records.
> Also, the FE should be updated to set permissions using the dynamic
> role-principals.
> Finally, code should be cleaned up to remove unneeded code in
> *
> org.apache.ambari.server.security.authorization.ClusterInheritedPermissionHelper
> *
> org.apache.ambari.server.controller.internal.GroupPrivilegeResourceProvider#getResources
> *
> org.apache.ambari.server.controller.internal.PrivilegeResourceProvider#toEntity
> *
> org.apache.ambari.server.controller.internal.UserPrivilegeResourceProvider#getResources
> *
> org.apache.ambari.server.security.authorization.AuthorizationHelper#isAuthorized
> * org.apache.ambari.server.view.ViewRegistry#addClusterInheritedPermissions
> * ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18648) There were no labels on fields on step "Configure Kerberos" after clicking back
[ https://issues.apache.org/jira/browse/AMBARI-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596574#comment-15596574 ] Hudson commented on AMBARI-18648: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5850 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5850/]) AMBARI-18648. There were no labels on fields on step "Configure (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=96ef52f4b688d26e0236fc80213f19bd714aab6a]) * (edit) ambari-web/app/controllers/main/admin/kerberos/step2_controller.js * (edit) ambari-web/test/controllers/main/admin/kerberos/step2_controller_test.js * (edit) ambari-web/app/utils/config.js > There were no labels on fields on step "Configure Kerberos" after clicking > back > --- > > Key: AMBARI-18648 > URL: https://issues.apache.org/jira/browse/AMBARI-18648 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.4.2 > > Attachments: AMBARI-18648.patch, AMBARI-18648_2.4.patch > > > STR: > #setup secure cluster > #start enabling Kerberos > #within "Install and test Kerberos client" step test got "Admin session > expiration error" window > #click cancel on "Admin session expiration error" window > #click back to step "Configure Kerberos" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18648) There were no labels on fields on step "Configure Kerberos" after clicking back
[ https://issues.apache.org/jira/browse/AMBARI-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596544#comment-15596544 ] Hudson commented on AMBARI-18648: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #189 (See [https://builds.apache.org/job/Ambari-branch-2.5/189/]) AMBARI-18648. There were no labels on fields on step "Configure (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a3923fdd16f5c0ca3d7fb14d416402cde4be9a75]) * (edit) ambari-web/app/controllers/main/admin/kerberos/step2_controller.js * (edit) ambari-web/app/utils/config.js * (edit) ambari-web/test/controllers/main/admin/kerberos/step2_controller_test.js > There were no labels on fields on step "Configure Kerberos" after clicking > back > --- > > Key: AMBARI-18648 > URL: https://issues.apache.org/jira/browse/AMBARI-18648 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.4.2 > > Attachments: AMBARI-18648.patch, AMBARI-18648_2.4.patch > > > STR: > #setup secure cluster > #start enabling Kerberos > #within "Install and test Kerberos client" step test got "Admin session > expiration error" window > #click cancel on "Admin session expiration error" window > #click back to step "Configure Kerberos" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18592) Ability to enable DEBUG logs without restarting ambari-server
[ https://issues.apache.org/jira/browse/AMBARI-18592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596535#comment-15596535 ] amarnathreddy commented on AMBARI-18592: Code review request - https://reviews.apache.org/r/52839/ have attached patch here > Ability to enable DEBUG logs without restarting ambari-server > - > > Key: AMBARI-18592 > URL: https://issues.apache.org/jira/browse/AMBARI-18592 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: amarnathreddy > Attachments: AMBARI-18543.patch > > > Currently there is no way to enable the DEBUG logs in Ambari-server without > actually restart. > Enabling the DEBUG logs without restart will be very useful in large clusters -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18592) Ability to enable DEBUG logs without restarting ambari-server
[ https://issues.apache.org/jira/browse/AMBARI-18592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnathreddy updated AMBARI-18592: --- Attachment: AMBARI-18543.patch > Ability to enable DEBUG logs without restarting ambari-server > - > > Key: AMBARI-18592 > URL: https://issues.apache.org/jira/browse/AMBARI-18592 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: amarnathreddy > Attachments: AMBARI-18543.patch > > > Currently there is no way to enable the DEBUG logs in Ambari-server without > actually restart. > Enabling the DEBUG logs without restart will be very useful in large clusters -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18631) Incorporate database consistency check into main Ambari process
[ https://issues.apache.org/jira/browse/AMBARI-18631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596515#comment-15596515 ] Hudson commented on AMBARI-18631: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5849 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5849/]) AMBARI-18631. Incorporate database consistency check into main Ambari (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dbe77dda8a21dffa7edc8228a9e65d8b72492034]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyChecker.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelperTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariServerTest.java * (edit) ambari-server/src/main/python/ambari_server/utils.py * (edit) ambari-server/src/test/python/TestUtils.py * (edit) ambari-server/src/main/python/ambari_server_main.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java > Incorporate database consistency check into main Ambari process > --- > > Key: AMBARI-18631 > URL: https://issues.apache.org/jira/browse/AMBARI-18631 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 2.5.0 > > Attachments: AMBARI-18631_branch_2.5.patch, AMBARI-18631_trunk.patch > > > Currently the database consistency check runs as a separate process prior > Ambari process. The database consistency checker load various modules needed > for performing the validations. (e.g. load stack definitions to be able to > compare service configs from stack with configs from db). > Once database consistency checker completed Ambari server is started. Ambari > server beside others loads the same modules as database consistency checker. > This double initialisation adds time to the ambari server startup time which > could be reduced if the database consistency check is moved into the ambari > server process. > Moreover the database consistency check may check at the beginning if the > database is empty and perform the checks only if there is data in the > database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18631) Incorporate database consistency check into main Ambari process
[ https://issues.apache.org/jira/browse/AMBARI-18631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596497#comment-15596497 ] Hudson commented on AMBARI-18631: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #188 (See [https://builds.apache.org/job/Ambari-branch-2.5/188/]) AMBARI-18631. Incorporate database consistency check into main Ambari (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1b907353991e8382ff47e30a5cb130412a6e3b08]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelperTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariServerTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyChecker.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java * (edit) ambari-server/src/main/python/ambari_server_main.py > Incorporate database consistency check into main Ambari process > --- > > Key: AMBARI-18631 > URL: https://issues.apache.org/jira/browse/AMBARI-18631 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 2.5.0 > > Attachments: AMBARI-18631_branch_2.5.patch, AMBARI-18631_trunk.patch > > > Currently the database consistency check runs as a separate process prior > Ambari process. The database consistency checker load various modules needed > for performing the validations. (e.g. load stack definitions to be able to > compare service configs from stack with configs from db). > Once database consistency checker completed Ambari server is started. Ambari > server beside others loads the same modules as database consistency checker. > This double initialisation adds time to the ambari server startup time which > could be reduced if the database consistency check is moved into the ambari > server process. > Moreover the database consistency check may check at the beginning if the > database is empty and perform the checks only if there is data in the > database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18665) Workflow Designer View: When you execute a workflow designer view instance, it does not load immediately unless you return to the dashboard.
[ https://issues.apache.org/jira/browse/AMBARI-18665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18665: -- Status: Patch Available (was: Open) > Workflow Designer View: When you execute a workflow designer view instance, > it does not load immediately unless you return to the dashboard. > > > Key: AMBARI-18665 > URL: https://issues.apache.org/jira/browse/AMBARI-18665 > Project: Ambari > Issue Type: Bug >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Attachments: AMBARI-18665.patch > > > Workflow designer view doesn't execute on clicking the go to instance button > after creating the view. > Navigating to the Ambari dashboard and executing the view using the drop down > menu works and loads the workflow designer view -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18665) Workflow Designer View: When you execute a workflow designer view instance, it does not load immediately unless you return to the dashboard.
[ https://issues.apache.org/jira/browse/AMBARI-18665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18665: -- Attachment: AMBARI-18665.patch > Workflow Designer View: When you execute a workflow designer view instance, > it does not load immediately unless you return to the dashboard. > > > Key: AMBARI-18665 > URL: https://issues.apache.org/jira/browse/AMBARI-18665 > Project: Ambari > Issue Type: Bug >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Attachments: AMBARI-18665.patch > > > Workflow designer view doesn't execute on clicking the go to instance button > after creating the view. > Navigating to the Ambari dashboard and executing the view using the drop down > menu works and loads the workflow designer view -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18648) There were no labels on fields on step "Configure Kerberos" after clicking back
[ https://issues.apache.org/jira/browse/AMBARI-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18648: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk, 2.4, 2.5 > There were no labels on fields on step "Configure Kerberos" after clicking > back > --- > > Key: AMBARI-18648 > URL: https://issues.apache.org/jira/browse/AMBARI-18648 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.4.2 > > Attachments: AMBARI-18648.patch, AMBARI-18648_2.4.patch > > > STR: > #setup secure cluster > #start enabling Kerberos > #within "Install and test Kerberos client" step test got "Admin session > expiration error" window > #click cancel on "Admin session expiration error" window > #click back to step "Configure Kerberos" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18662) Check that Stack Version and repo URLs match up when registering repo
[ https://issues.apache.org/jira/browse/AMBARI-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18662: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk > Check that Stack Version and repo URLs match up when registering repo > -- > > Key: AMBARI-18662 > URL: https://issues.apache.org/jira/browse/AMBARI-18662 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-18662.patch > > > Right now there's no validation when registering a repo to catch these type > of user errors, which caused a lot of problems down the road. We should have > very basic validation using JS so that if we detect a number like "2.5.0.0" > we ensure that the selected stack is also HDP 2.5. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18648) There were no labels on fields on step "Configure Kerberos" after clicking back
[ https://issues.apache.org/jira/browse/AMBARI-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596477#comment-15596477 ] Antonenko Alexander commented on AMBARI-18648: -- rat check passed 30366 tests complete (32 seconds) 151 tests pending > There were no labels on fields on step "Configure Kerberos" after clicking > back > --- > > Key: AMBARI-18648 > URL: https://issues.apache.org/jira/browse/AMBARI-18648 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.4.2 > > Attachments: AMBARI-18648.patch, AMBARI-18648_2.4.patch > > > STR: > #setup secure cluster > #start enabling Kerberos > #within "Install and test Kerberos client" step test got "Admin session > expiration error" window > #click cancel on "Admin session expiration error" window > #click back to step "Configure Kerberos" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18665) Workflow Designer View: When you execute a workflow designer view instance, it does not load immediately unless you return to the dashboard.
Anita Gnanamalar Jebaraj created AMBARI-18665: - Summary: Workflow Designer View: When you execute a workflow designer view instance, it does not load immediately unless you return to the dashboard. Key: AMBARI-18665 URL: https://issues.apache.org/jira/browse/AMBARI-18665 Project: Ambari Issue Type: Bug Reporter: Anita Gnanamalar Jebaraj Assignee: Anita Gnanamalar Jebaraj Workflow designer view doesn't execute on clicking the go to instance button after creating the view. Navigating to the Ambari dashboard and executing the view using the drop down menu works and loads the workflow designer view -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18631) Incorporate database consistency check into main Ambari process
[ https://issues.apache.org/jira/browse/AMBARI-18631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18631: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Incorporate database consistency check into main Ambari process > --- > > Key: AMBARI-18631 > URL: https://issues.apache.org/jira/browse/AMBARI-18631 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 2.5.0 > > Attachments: AMBARI-18631_branch_2.5.patch, AMBARI-18631_trunk.patch > > > Currently the database consistency check runs as a separate process prior > Ambari process. The database consistency checker load various modules needed > for performing the validations. (e.g. load stack definitions to be able to > compare service configs from stack with configs from db). > Once database consistency checker completed Ambari server is started. Ambari > server beside others loads the same modules as database consistency checker. > This double initialisation adds time to the ambari server startup time which > could be reduced if the database consistency check is moved into the ambari > server process. > Moreover the database consistency check may check at the beginning if the > database is empty and perform the checks only if there is data in the > database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17783) Add falcon to oozie admin user for HDP 2.5
[
https://issues.apache.org/jira/browse/AMBARI-17783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596422#comment-15596422
]
Venkat Ranganathan commented on AMBARI-17783:
-
[~Tim Thorpe]/[~afernandez]
If you look at patch 2 attached, you can see that there is this code block
{code}
+if not "FALCON_SERVER" in clusterData["components"] :
+ print "Falcon is not part of the installation"
+ return
{code}
It probably got missed during merge into the branch and needs to be applied -
Note sure checking for services will work as the stack_advisor code can have
partial list of services during invocation
> Add falcon to oozie admin user for HDP 2.5
> --
>
> Key: AMBARI-17783
> URL: https://issues.apache.org/jira/browse/AMBARI-17783
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Murali Ramasami
>Assignee: Venkat Ranganathan
> Fix For: 2.4.0
>
> Attachments: AMBARI-17783.patch, AMBARI-17783.patch.2
>
>
> we need to add falcon and falcon-admin in the oozie_admin_users of oozie
> advanced env section.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18617) Adding custom property to hive-site adds it to other 'Custom' panels on hive
[ https://issues.apache.org/jira/browse/AMBARI-18617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596426#comment-15596426 ] Hudson commented on AMBARI-18617: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #187 (See [https://builds.apache.org/job/Ambari-branch-2.5/187/]) AMBARI-18617. Adding custom property to hive-site adds it to other (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=edbc4865f2abbbe836b7c27076a2ac41c8ba5063]) * (edit) ambari-web/app/views/common/configs/service_configs_by_category_view.js * (edit) ambari-web/test/views/common/configs/custom_category_views/notification_configs_view_test.js * (edit) ambari-web/test/views/common/configs/service_configs_by_category_view_test.js > Adding custom property to hive-site adds it to other 'Custom' panels on hive > > > Key: AMBARI-18617 > URL: https://issues.apache.org/jira/browse/AMBARI-18617 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Dhanya Balasundaran >Assignee: Jaimin D Jetly > Fix For: 2.4.2 > > Attachments: AMBARI-18617.patch > > > - Navigate through Ambari Install Wizard to reach Customize Services page > - Choose Hive > - Add a custom property to Custom-hive-site > - Noticed that its getting added to Custom hivemetastore-site, > Custom hiveserver2-interactive-site, Custom hiveserver2-site, > Custom hivemetastore-site, Custom tez-interactive-site. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18652) Alert Targets Cannot Be Updated Due To Transaction / Cache Timing Issues
[
https://issues.apache.org/jira/browse/AMBARI-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596425#comment-15596425
]
Hudson commented on AMBARI-18652:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #187 (See
[https://builds.apache.org/job/Ambari-branch-2.5/187/])
AMBARI-18652 - Alert Targets Cannot Be Updated Due To Transaction / (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a132f9c00210836dfd576a06437db0c497ab3b23])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertGroupEntity.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/AlertDispatchDAO.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertNoticeEntity.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/services/AlertNoticeDispatchServiceTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertTargetEntity.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertStateChangedEventTest.java
> Alert Targets Cannot Be Updated Due To Transaction / Cache Timing Issues
>
>
> Key: AMBARI-18652
> URL: https://issues.apache.org/jira/browse/AMBARI-18652
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18652.patch
>
>
> There is a JPA timing issue WRT to updating alert targets where lazy loaded
> lists outside of a transaction cause the data set on the {{AlertTargetEnity}}
> to be refreshed from the database.
> While maintaining the bi-directional relationship between
> {{AlertTargetEntity}} and {{AlertGroupEntity}}, and {{IndirectSet}} from JPA
> causes JPA to detect a stale entity from another transaction.
> STR:
> It's more likely to happen when there are active alerts.
> - Create a new alert target for _just_ HDFS
> - Shut down HDFS
> - Try to edit the name of the alert target
> It will return a 200 return code, but the data will not have changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18365) Add Ambari configuration options to support Kerberos token authentication
[ https://issues.apache.org/jira/browse/AMBARI-18365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596424#comment-15596424 ] Hudson commented on AMBARI-18365: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #187 (See [https://builds.apache.org/job/Ambari-branch-2.5/187/]) AMBARI-18365. Authorizations given to roles, should use generic (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=49f58e8402b543875c61f8d74a052bd6cd45a788]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/GroupPrivilegeResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog242Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UserPrivilegeResourceProvider.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ViewPrivilegeResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/PermissionLoader.js * (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/event/request/ViewPrivilegeChangeRequestAuditEvent.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserPrivilegeResourceProviderTest.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/ambariViews/edit.html * (edit) ambari-admin/src/main/resources/ui/admin-web/test/unit/services/PermissionSaver_test.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/view/ViewRegistry.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterPrivilegeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/PrincipalTypeDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/event/request/ClusterPrivilegeChangeRequestAuditEvent.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/ViewPrivilegeEventCreator.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/PermissionEntity.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AuthorizationHelperTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AmbariPrivilegeResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/PrivilegeEventCreator.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/Users.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog242.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AuthorizationHelper.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/PermissionsSaver.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ViewPrivilegeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/PrincipalTypeEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AmbariPrivilegeResourceProvider.java * (add) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AbstractPrivilegeResourceProviderTest.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/ambariViews/ViewsEditCtrl.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/GroupPrivilegeResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/view/configuration/AutoInstanceConfigTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PrivilegeResourceProvider.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/ClusterInheritedPermissionHelper.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterPrivilegeResourceProviderTest.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/view/configuration/AutoInstanceConfig.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/View.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/PermissionDAO.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * (edit
[jira] [Commented] (AMBARI-18648) There were no labels on fields on step "Configure Kerberos" after clicking back
[
https://issues.apache.org/jira/browse/AMBARI-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596383#comment-15596383
]
Hadoop QA commented on AMBARI-18648:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834735/AMBARI-18648_2.4.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/8975//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8975//console
This message is automatically generated.
> There were no labels on fields on step "Configure Kerberos" after clicking
> back
> ---
>
> Key: AMBARI-18648
> URL: https://issues.apache.org/jira/browse/AMBARI-18648
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18648.patch, AMBARI-18648_2.4.patch
>
>
> STR:
> #setup secure cluster
> #start enabling Kerberos
> #within "Install and test Kerberos client" step test got "Admin session
> expiration error" window
> #click cancel on "Admin session expiration error" window
> #click back to step "Configure Kerberos"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18663) Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
[
https://issues.apache.org/jira/browse/AMBARI-18663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596361#comment-15596361
]
Hudson commented on AMBARI-18663:
-
ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #186 (See
[https://builds.apache.org/job/Ambari-branch-2.5/186/])
AMBARI-18663. Storm becomes stopped by itself after upgrade from 2.2.1.0
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7f26a6ae8922bd447fa55cccac4a00e24a9a7c83])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.4.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.4.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/STORM/configuration/storm-site.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.4.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ConfigureTask.java
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.4.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/common-services/STORM/0.9.1/configuration/storm-site.xml
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> -
>
> Key: AMBARI-18663
> URL: https://issues.apache.org/jira/browse/AMBARI-18663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.2
>
> Attachments: AMBARI-18663.patch
>
>
> STR:
> 1)Deploy old version cluster regarding environment (use public repo)
> 2)Enable AMS distr. mode
> 3)Make ambari only upgrade to 2.4.1.0
> Actual result:
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> {code}
> supervisor.log
> 2016-09-01 21:51:48.996 o.a.s.c.ConnectionState [ERROR] Connection timed out
> for connection string (host:2181,host:2181,host:2181/storm) and timeout
> (15000) / elapsed (18214)
> org.apache.storm.curator.CuratorConnectionLossException: KeeperErrorCode =
> ConnectionLoss
> at
> org.apache.storm.curator.ConnectionState.checkTimeouts(ConnectionState.java:195)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.ConnectionState.getZooKeeper(ConnectionState.java:87)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:115)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:821)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:807)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:63)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:267)
> [storm-core-0.10.0.2.4.2.0-258.jar
[jira] [Commented] (AMBARI-18654) Implement instrumented Lock for profiling/logging
[ https://issues.apache.org/jira/browse/AMBARI-18654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596360#comment-15596360 ] Hudson commented on AMBARI-18654: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #186 (See [https://builds.apache.org/job/Ambari-branch-2.5/186/]) AMBARI-18654. Implement instrumented Lock for profiling/logging. (Attila (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c2507d575599a44403107e375b583aa1222af65c]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java * (add) ambari-server/src/test/java/org/apache/ambari/server/logging/LockFactoryTest.java * (add) ambari-server/src/test/java/org/apache/ambari/server/logging/ProfiledReentrantReadWriteLockTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (add) ambari-server/src/main/java/org/apache/ambari/server/logging/ProfiledReentrantReadWriteLock.java * (add) ambari-server/src/main/java/org/apache/ambari/server/logging/LockFactory.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/configuration/ConfigurationTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/logging/ProfiledLock.java * (add) ambari-server/src/main/java/org/apache/ambari/server/logging/LockProfileDelegate.java * (add) ambari-server/src/main/java/org/apache/ambari/server/logging/ProfiledReentrantLock.java > Implement instrumented Lock for profiling/logging > - > > Key: AMBARI-18654 > URL: https://issues.apache.org/jira/browse/AMBARI-18654 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Minor > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-18654.patch > > > As part of the reduced reliance on Java locks, we should allow for the lock > implementation provided to business objects to be able to log information > about their acquisition and release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-1365) Make Hosts table update dynamically
[ https://issues.apache.org/jira/browse/AMBARI-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596334#comment-15596334 ] Hudson commented on AMBARI-1365: FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5848 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5848/]) Revert "AMBARI-1365. Authorizations given to roles, should use generic (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b90b286366e67b7b494b2f2cf886dc4eab4ff006]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AuthorizationHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/PrincipalTypeEntity.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ViewPrivilegeResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/view/configuration/AutoInstanceConfigTest.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/ambariViews/edit.html * (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/event/request/ViewPrivilegeChangeRequestAuditEvent.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AmbariPrivilegeResourceProviderTest.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/ambariViews/ViewsEditCtrl.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/event/request/ClusterPrivilegeChangeRequestAuditEvent.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/ViewPrivilegeEventCreator.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AmbariPrivilegeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/view/ViewRegistry.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/GroupPrivilegeResourceProviderTest.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/PermissionLoader.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/PermissionDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UserPrivilegeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ViewPrivilegeResourceProvider.java * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/Users.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AuthorizationHelperTest.java * (edit) ambari-admin/src/main/resources/ui/admin-web/test/unit/services/PermissionSaver_test.js * (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/PermissionEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterPrivilegeResourceProvider.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/View.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PrivilegeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog242.java * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/GroupPrivilegeResourceProvider.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/PermissionsSaver.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/view/configuration/AutoInstanceConfig.java * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/PrivilegeEventCreator.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/PrincipalDAO.java * (add) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/ClusterInheritedPermissionHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/PrincipalTypeDAO.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserPrivilegeResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterPrivilegeResourceProviderTest.java * (delete) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AbstractPrivilegeResourceProviderTest.java * (edi
[jira] [Commented] (AMBARI-18365) Add Ambari configuration options to support Kerberos token authentication
[ https://issues.apache.org/jira/browse/AMBARI-18365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596333#comment-15596333 ] Hudson commented on AMBARI-18365: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5848 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5848/]) AMBARI-18365. Authorizations given to roles, should use generic (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=176c691eaed6dbf639617f6208f7fb117597c1ce]) * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/ViewPrivilegeEventCreator.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AmbariPrivilegeResourceProvider.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * (edit) ambari-admin/src/main/resources/ui/admin-web/test/unit/services/PermissionSaver_test.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterPrivilegeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UserPrivilegeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/PrincipalDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AuthorizationHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/view/ViewRegistry.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/PrivilegeEventCreator.java * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ViewPrivilegeResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AuthorizationHelperTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ViewPrivilegeResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/GroupPrivilegeResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterPrivilegeResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog242Test.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/PrincipalTypeDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/PermissionEntity.java * (add) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AbstractPrivilegeResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/event/request/ViewPrivilegeChangeRequestAuditEvent.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserPrivilegeResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/view/configuration/AutoInstanceConfig.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AmbariPrivilegeResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/Users.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/ambariViews/ViewsEditCtrl.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PrivilegeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/PermissionDAO.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/PermissionsSaver.js * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog242.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/ambariViews/edit.html * (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * (edit) ambari-server/src/test/java/org/apache/ambari/server/view/configuration/AutoInstanceConfigTest.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/View.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/GroupPrivilegeResourceProvider.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/ClusterInheritedPermissionHelper.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/PermissionLoader.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/event/request/ClusterPrivilegeChangeRequestAuditEvent.java * (edit) amb
[jira] [Commented] (AMBARI-18617) Adding custom property to hive-site adds it to other 'Custom' panels on hive
[ https://issues.apache.org/jira/browse/AMBARI-18617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596335#comment-15596335 ] Hudson commented on AMBARI-18617: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5848 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5848/]) AMBARI-18617. Adding custom property to hive-site adds it to other (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0dd7770d9f3efd99e8bc9475d5f58422f4800fcd]) * (edit) ambari-web/test/views/common/configs/custom_category_views/notification_configs_view_test.js * (edit) ambari-web/app/views/common/configs/service_configs_by_category_view.js * (edit) ambari-web/test/views/common/configs/service_configs_by_category_view_test.js > Adding custom property to hive-site adds it to other 'Custom' panels on hive > > > Key: AMBARI-18617 > URL: https://issues.apache.org/jira/browse/AMBARI-18617 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Dhanya Balasundaran >Assignee: Jaimin D Jetly > Fix For: 2.4.2 > > Attachments: AMBARI-18617.patch > > > - Navigate through Ambari Install Wizard to reach Customize Services page > - Choose Hive > - Add a custom property to Custom-hive-site > - Noticed that its getting added to Custom hivemetastore-site, > Custom hiveserver2-interactive-site, Custom hiveserver2-site, > Custom hivemetastore-site, Custom tez-interactive-site. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18664) While syncing with LDAP, username collisions should be handled based on configuration value
[
https://issues.apache.org/jira/browse/AMBARI-18664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18664:
--
Attachment: AMBARI-18664_branch-2.5_01.patch
AMBARI-18664_branch-2.4_01.patch
> While syncing with LDAP, username collisions should be handled based on
> configuration value
> ---
>
> Key: AMBARI-18664
> URL: https://issues.apache.org/jira/browse/AMBARI-18664
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 2.4.2
>
> Attachments: AMBARI-18664_branch-2.4_01.patch,
> AMBARI-18664_branch-2.5_01.patch
>
>
> While syncing with LDAP, username collisions should be handled based on an
> LDAP sync configuration value.
> The configuration options should be to indicate the following behaviors
> * convert
> ** convert the existing (non-LDAP user) user to an LDAP user
> ** This is the existing behavior
> * skip
> ** skip or ignore the collision, leaving the existing user unchanged
> ** a new user record should not be created
> Note: Future behavior may be to cause the sync operation to fail, but that
> shouldn't be handed yet.
> This configuration value should be set when setting up LDAP sync properties
> via {{ambari-server setup-ldap}} and be enforced when processing the sync
> operation in methods like
> {{org.apache.ambari.server.controller.AmbariManagementControllerImpl#synchronizeLdapUsersAndGroups}}
> or {{org.apache.ambari.server.security.authorization.Users#processLdapSync}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18664) While syncing with LDAP, username collisions should be handled based on configuration value
[
https://issues.apache.org/jira/browse/AMBARI-18664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18664:
--
Status: Patch Available (was: Open)
> While syncing with LDAP, username collisions should be handled based on
> configuration value
> ---
>
> Key: AMBARI-18664
> URL: https://issues.apache.org/jira/browse/AMBARI-18664
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 2.4.2
>
> Attachments: AMBARI-18664_branch-2.4_01.patch,
> AMBARI-18664_branch-2.5_01.patch
>
>
> While syncing with LDAP, username collisions should be handled based on an
> LDAP sync configuration value.
> The configuration options should be to indicate the following behaviors
> * convert
> ** convert the existing (non-LDAP user) user to an LDAP user
> ** This is the existing behavior
> * skip
> ** skip or ignore the collision, leaving the existing user unchanged
> ** a new user record should not be created
> Note: Future behavior may be to cause the sync operation to fail, but that
> shouldn't be handed yet.
> This configuration value should be set when setting up LDAP sync properties
> via {{ambari-server setup-ldap}} and be enforced when processing the sync
> operation in methods like
> {{org.apache.ambari.server.controller.AmbariManagementControllerImpl#synchronizeLdapUsersAndGroups}}
> or {{org.apache.ambari.server.security.authorization.Users#processLdapSync}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18648) There were no labels on fields on step "Configure Kerberos" after clicking back
[
https://issues.apache.org/jira/browse/AMBARI-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596328#comment-15596328
]
Hadoop QA commented on AMBARI-18648:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834735/AMBARI-18648_2.4.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/8974//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8974//console
This message is automatically generated.
> There were no labels on fields on step "Configure Kerberos" after clicking
> back
> ---
>
> Key: AMBARI-18648
> URL: https://issues.apache.org/jira/browse/AMBARI-18648
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18648.patch, AMBARI-18648_2.4.patch
>
>
> STR:
> #setup secure cluster
> #start enabling Kerberos
> #within "Install and test Kerberos client" step test got "Admin session
> expiration error" window
> #click cancel on "Admin session expiration error" window
> #click back to step "Configure Kerberos"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-1365) Make Hosts table update dynamically
[ https://issues.apache.org/jira/browse/AMBARI-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596246#comment-15596246 ] Hudson commented on AMBARI-1365: FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5847 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5847/]) AMBARI-1365. Authorizations given to roles, should use generic (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b3dda4ffe9c8bc47725fd9292dc621568df45610]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AmbariPrivilegeResourceProvider.java * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/PermissionDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/view/configuration/AutoInstanceConfig.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/ViewPrivilegeEventCreator.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/event/request/ViewPrivilegeChangeRequestAuditEvent.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/ambariViews/edit.html * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserPrivilegeResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog242Test.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/PermissionsSaver.js * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js * (edit) ambari-admin/src/main/resources/ui/admin-web/test/unit/services/PermissionSaver_test.js * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ViewPrivilegeResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ViewPrivilegeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AuthorizationHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/GroupPrivilegeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/PermissionEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PrivilegeResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterPrivilegeResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/PrincipalDAO.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/GroupPrivilegeResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/PrincipalTypeDAO.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/PermissionLoader.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterPrivilegeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/event/request/ClusterPrivilegeChangeRequestAuditEvent.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/View.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/view/ViewRegistry.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AmbariPrivilegeResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AuthorizationHelperTest.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/ambariViews/ViewsEditCtrl.js * (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * (add) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AbstractPrivilegeResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/PrincipalTypeEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/Users.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/ClusterInheritedPermissionHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UserPrivilegeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/PrivilegeEventCreator.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * (edit) ambari-server/src/test/java/org/apache/ambari/server/view/configuration/AutoInstanceConfigTest.java * (edit)
[jira] [Commented] (AMBARI-15966) ambari-web 2.2.1 build error
[ https://issues.apache.org/jira/browse/AMBARI-15966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596169#comment-15596169 ] Vi On commented on AMBARI-15966: I had the same issue with: node version v5.7.0 brunch version: 2.8.0 As mentioned in https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development I switch to these versions and it worked. node v0.10.45 brunch 1.7.20 > ambari-web 2.2.1 build error > > > Key: AMBARI-15966 > URL: https://issues.apache.org/jira/browse/AMBARI-15966 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.1 >Reporter: skrho >Assignee: Jaimin D Jetly > Fix For: 2.5.0 > > > Hi Everyone~~ > Now I am building the ambari-web 2.2.1 version > My Environment is > npm : 3.8.7 > node : 4.4.3 > brunch : 2.5.3 > I have a problem when building .. > I just command > # $apache-ambari-2.2.1-src/ambari-web]#brunch build -d > There is error message > brunch:config Trying to load brunch-config +0ms > brunch:config Trying to load config +5ms > 19 Apr 08:26:28 - warn: config.files.stylesheets.defaultPaths was removed > 19 Apr 08:26:28 - warn: config.files.templates.defaultPaths was removed > 19 Apr 08:26:28 - error: Initialization error - You probably need to execute > `npm install` to install brunch plugins. SyntaxError: Setter must have > exactly one formal parameter. > at /usr/lib/node_modules/brunch/lib/plugins.js:101:17 > at Array.map (native) > at deps.filter.dependency.map > (/usr/lib/node_modules/brunch/lib/plugins.js:88:8) > at packages.filter.plugins.map.plugin.filter.deps.filter.allPlugins.filter > (/usr/lib/node_modules/brunch/lib/plugins.js:108:19) > at > Object.packages.filter.plugins.map.plugin.filter.deps.filter.exports.init.plugins.filter.map.preCompilers.push.teardownBrunch > [as init] (/usr/lib/node_modules/brunch/lib/plugins.js:131:20) > at /usr/lib/node_modules/brunch/lib/watch.js:101:19 > Please Help me~ > What can I do that? > In advanced Thank you everyone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18617) Adding custom property to hive-site adds it to other 'Custom' panels on hive
[ https://issues.apache.org/jira/browse/AMBARI-18617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18617: Resolution: Fixed Status: Resolved (was: Patch Available) Received +1 on ReviewBoard. Patch committed to trunk, branch-2.4 and branch-2.5 > Adding custom property to hive-site adds it to other 'Custom' panels on hive > > > Key: AMBARI-18617 > URL: https://issues.apache.org/jira/browse/AMBARI-18617 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Dhanya Balasundaran >Assignee: Jaimin D Jetly > Fix For: 2.4.2 > > Attachments: AMBARI-18617.patch > > > - Navigate through Ambari Install Wizard to reach Customize Services page > - Choose Hive > - Add a custom property to Custom-hive-site > - Noticed that its getting added to Custom hivemetastore-site, > Custom hiveserver2-interactive-site, Custom hiveserver2-site, > Custom hivemetastore-site, Custom tez-interactive-site. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18648) There were no labels on fields on step "Configure Kerberos" after clicking back
[ https://issues.apache.org/jira/browse/AMBARI-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596124#comment-15596124 ] Andrii Babiichuk commented on AMBARI-18648: --- +1 for the patch > There were no labels on fields on step "Configure Kerberos" after clicking > back > --- > > Key: AMBARI-18648 > URL: https://issues.apache.org/jira/browse/AMBARI-18648 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.4.2 > > Attachments: AMBARI-18648.patch, AMBARI-18648_2.4.patch > > > STR: > #setup secure cluster > #start enabling Kerberos > #within "Install and test Kerberos client" step test got "Admin session > expiration error" window > #click cancel on "Admin session expiration error" window > #click back to step "Configure Kerberos" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18648) There were no labels on fields on step "Configure Kerberos" after clicking back
[ https://issues.apache.org/jira/browse/AMBARI-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18648: - Attachment: AMBARI-18648_2.4.patch > There were no labels on fields on step "Configure Kerberos" after clicking > back > --- > > Key: AMBARI-18648 > URL: https://issues.apache.org/jira/browse/AMBARI-18648 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.4.2 > > Attachments: AMBARI-18648.patch, AMBARI-18648_2.4.patch > > > STR: > #setup secure cluster > #start enabling Kerberos > #within "Install and test Kerberos client" step test got "Admin session > expiration error" window > #click cancel on "Admin session expiration error" window > #click back to step "Configure Kerberos" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18662) Check that Stack Version and repo URLs match up when registering repo
[ https://issues.apache.org/jira/browse/AMBARI-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596114#comment-15596114 ] Hudson commented on AMBARI-18662: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5846 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5846/]) AMBARI-18662. Check that Stack Version and repo URLs match up when (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=00f1e71b62f4133e70d7d8f9f2cd6fa0624ec40d]) * (edit) ambari-web/app/controllers/installer.js * (edit) ambari-web/app/controllers/wizard/step1_controller.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/test/controllers/installer_test.js > Check that Stack Version and repo URLs match up when registering repo > -- > > Key: AMBARI-18662 > URL: https://issues.apache.org/jira/browse/AMBARI-18662 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-18662.patch > > > Right now there's no validation when registering a repo to catch these type > of user errors, which caused a lot of problems down the road. We should have > very basic validation using JS so that if we detect a number like "2.5.0.0" > we ensure that the selected stack is also HDP 2.5. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18627) Add service wizard hung at Choose services page as no ClusterStackVersion is available with state=CURRENT
[ https://issues.apache.org/jira/browse/AMBARI-18627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596116#comment-15596116 ] Hudson commented on AMBARI-18627: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5846 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5846/]) AMBARI-18627. Add service wizard hung at Choose services page as no (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=db8f3e3f8855fc3174fa6b41ed86c87b9263321a]) * (edit) ambari-web/test/controllers/global/cluster_controller_test.js * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js * (edit) ambari-web/app/controllers/global/cluster_controller.js * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/app/utils/ajax/ajax.js * (edit) ambari-web/app/controllers/wizard.js > Add service wizard hung at Choose services page as no ClusterStackVersion is > available with state=CURRENT > - > > Key: AMBARI-18627 > URL: https://issues.apache.org/jira/browse/AMBARI-18627 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-18627.patch, AMBARI-18627.patch > > > Add service wizard hung at Choose services page as no ClusterStackVersion is > available with state=CURRENT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-18664) While syncing with LDAP, username collisions should be handled based on configuration value
[
https://issues.apache.org/jira/browse/AMBARI-18664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas reassigned AMBARI-18664:
-
Assignee: Robert Levas (was: Eugene Chekanskiy)
> While syncing with LDAP, username collisions should be handled based on
> configuration value
> ---
>
> Key: AMBARI-18664
> URL: https://issues.apache.org/jira/browse/AMBARI-18664
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 2.4.2
>
>
> While syncing with LDAP, username collisions should be handled based on an
> LDAP sync configuration value.
> The configuration options should be to indicate the following behaviors
> * convert
> ** convert the existing (non-LDAP user) user to an LDAP user
> ** This is the existing behavior
> * skip
> ** skip or ignore the collision, leaving the existing user unchanged
> ** a new user record should not be created
> Note: Future behavior may be to cause the sync operation to fail, but that
> shouldn't be handed yet.
> This configuration value should be set when setting up LDAP sync properties
> via {{ambari-server setup-ldap}} and be enforced when processing the sync
> operation in methods like
> {{org.apache.ambari.server.controller.AmbariManagementControllerImpl#synchronizeLdapUsersAndGroups}}
> or {{org.apache.ambari.server.security.authorization.Users#processLdapSync}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18631) Incorporate database consistency check into main Ambari process
[ https://issues.apache.org/jira/browse/AMBARI-18631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18631: --- Attachment: (was: AMBARI-18631.patch) > Incorporate database consistency check into main Ambari process > --- > > Key: AMBARI-18631 > URL: https://issues.apache.org/jira/browse/AMBARI-18631 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 2.5.0 > > Attachments: AMBARI-18631_branch_2.5.patch, AMBARI-18631_trunk.patch > > > Currently the database consistency check runs as a separate process prior > Ambari process. The database consistency checker load various modules needed > for performing the validations. (e.g. load stack definitions to be able to > compare service configs from stack with configs from db). > Once database consistency checker completed Ambari server is started. Ambari > server beside others loads the same modules as database consistency checker. > This double initialisation adds time to the ambari server startup time which > could be reduced if the database consistency check is moved into the ambari > server process. > Moreover the database consistency check may check at the beginning if the > database is empty and perform the checks only if there is data in the > database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18631) Incorporate database consistency check into main Ambari process
[ https://issues.apache.org/jira/browse/AMBARI-18631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18631: --- Attachment: AMBARI-18631_trunk.patch AMBARI-18631_branch_2.5.patch > Incorporate database consistency check into main Ambari process > --- > > Key: AMBARI-18631 > URL: https://issues.apache.org/jira/browse/AMBARI-18631 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 2.5.0 > > Attachments: AMBARI-18631_branch_2.5.patch, AMBARI-18631_trunk.patch > > > Currently the database consistency check runs as a separate process prior > Ambari process. The database consistency checker load various modules needed > for performing the validations. (e.g. load stack definitions to be able to > compare service configs from stack with configs from db). > Once database consistency checker completed Ambari server is started. Ambari > server beside others loads the same modules as database consistency checker. > This double initialisation adds time to the ambari server startup time which > could be reduced if the database consistency check is moved into the ambari > server process. > Moreover the database consistency check may check at the beginning if the > database is empty and perform the checks only if there is data in the > database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[
https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596055#comment-15596055
]
Swapan Shridhar commented on AMBARI-17981:
--
Trunk failure :
https://builds.apache.org/job/Ambari-trunk-Commit/5836/testReport/
branch-2.5 failure: https://builds.apache.org/job/Ambari-branch-2.5/
Revert because of test failure:
Trunk:
{code}
commit f37b518b5d29e227e56a9b2eef57673b164be22b
Author: Swapan Shridhar
Date: Fri Oct 21 12:02:38 2016 -0700
Revert "Integrate Druid with Ambari (Nishant Bangarwa, Slim Bouguerra via
Swapan Shridhar)."
This reverts commit 685e926db0d442411ab5bee50c1e189cfb0a261e.
{code}
branch-2.5:
{code}
commit 4a8544c5d54e41c20f3a2109170e84fe050e419b
Author: Swapan Shridhar
Date: Fri Oct 21 12:09:25 2016 -0700
Revert "Integrate Druid with Ambari (Nishant Bangarwa, Slim Bouguerra via
Swapan Shridhar)."
This reverts commit fca146a5d4284a8156ff3bcf468af7388a8283fe.
{code}
CC [~adoroszlai]
[~bslim] [~nishantbangarwa] Please look into the failure and fix it.
> Integrate Druid With Ambari
> ---
>
> Key: AMBARI-17981
> URL: https://issues.apache.org/jira/browse/AMBARI-17981
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Nishant Bangarwa
>Assignee: Swapan Shridhar
> Labels: features
> Fix For: 2.5.0
>
> Attachments: ambari-17981.patch
>
>
> This task includes adding support for druid cluster provisioning via Ambari.
> Details about Druid cluster design and different node types are present here
> -
> http://druid.io/docs/latest/design/design.html
> In general, Druid can be defined as a service in HDP which has following
> components -
> 1) Coordinator
> 2) Overlord
> 3) Historical
> 4) Broker
> 5) Middlemanager
>
> Druid also has external dependencies on following
> 1) Zookeeper - Ambari should be able to pass in zk configs to druid cluster
> 2) Deep storage - A distributed FS, can be one of HDFS/S3 or any other NFS.
> 3) Metadata Store - Mysql/Postgres. can be either provided by the user or a
> mysql instance provisioned by ambari itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar reopened AMBARI-17981: -- > Integrate Druid With Ambari > --- > > Key: AMBARI-17981 > URL: https://issues.apache.org/jira/browse/AMBARI-17981 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nishant Bangarwa >Assignee: Swapan Shridhar > Labels: features > Fix For: 2.5.0 > > Attachments: ambari-17981.patch > > > This task includes adding support for druid cluster provisioning via Ambari. > Details about Druid cluster design and different node types are present here > - > http://druid.io/docs/latest/design/design.html > In general, Druid can be defined as a service in HDP which has following > components - > 1) Coordinator > 2) Overlord > 3) Historical > 4) Broker > 5) Middlemanager > > Druid also has external dependencies on following > 1) Zookeeper - Ambari should be able to pass in zk configs to druid cluster > 2) Deep storage - A distributed FS, can be one of HDFS/S3 or any other NFS. > 3) Metadata Store - Mysql/Postgres. can be either provided by the user or a > mysql instance provisioned by ambari itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18664) While syncing with LDAP, username collisions should be handled based on configuration value
Robert Levas created AMBARI-18664:
-
Summary: While syncing with LDAP, username collisions should be
handled based on configuration value
Key: AMBARI-18664
URL: https://issues.apache.org/jira/browse/AMBARI-18664
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.0.0
Reporter: Robert Levas
Assignee: Eugene Chekanskiy
Fix For: 2.4.2
While syncing with LDAP, username collisions should be handled based on an LDAP
sync configuration value.
The configuration options should be to indicate the following behaviors
* convert
** convert the existing (non-LDAP user) user to an LDAP user
** This is the existing behavior
* skip
** skip or ignore the collision, leaving the existing user unchanged
** a new user record should not be created
Note: Future behavior may be to cause the sync operation to fail, but that
shouldn't be handed yet.
This configuration value should be set when setting up LDAP sync properties via
{{ambari-server setup-ldap}} and be enforced when processing the sync operation
in methods like
{{org.apache.ambari.server.controller.AmbariManagementControllerImpl#synchronizeLdapUsersAndGroups}}
or {{org.apache.ambari.server.security.authorization.Users#processLdapSync}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18648) There were no labels on fields on step "Configure Kerberos" after clicking back
[ https://issues.apache.org/jira/browse/AMBARI-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18648: - Attachment: AMBARI-18648.patch > There were no labels on fields on step "Configure Kerberos" after clicking > back > --- > > Key: AMBARI-18648 > URL: https://issues.apache.org/jira/browse/AMBARI-18648 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.4.2 > > Attachments: AMBARI-18648.patch > > > STR: > #setup secure cluster > #start enabling Kerberos > #within "Install and test Kerberos client" step test got "Admin session > expiration error" window > #click cancel on "Admin session expiration error" window > #click back to step "Configure Kerberos" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18648) There were no labels on fields on step "Configure Kerberos" after clicking back
[ https://issues.apache.org/jira/browse/AMBARI-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18648: - Status: Patch Available (was: Open) > There were no labels on fields on step "Configure Kerberos" after clicking > back > --- > > Key: AMBARI-18648 > URL: https://issues.apache.org/jira/browse/AMBARI-18648 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.4.2 > > Attachments: AMBARI-18648.patch > > > STR: > #setup secure cluster > #start enabling Kerberos > #within "Install and test Kerberos client" step test got "Admin session > expiration error" window > #click cancel on "Admin session expiration error" window > #click back to step "Configure Kerberos" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18657) Slider always creates storm slider conf directory
[ https://issues.apache.org/jira/browse/AMBARI-18657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-18657: Status: Patch Available (was: Open) Added a test case to test broken links > Slider always creates storm slider conf directory > - > > Key: AMBARI-18657 > URL: https://issues.apache.org/jira/browse/AMBARI-18657 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18657.patch > > Original Estimate: 4h > Remaining Estimate: 4h > > The slider.py script in common-services should respect all possible ways of > installing slider. In a stack without storm there is no need to install the > storm slider client RPM. As a result the storm slider client directory will > be a broken link and attempting to create the storm slider client config > directory will result in an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18657) Slider always creates storm slider conf directory
[ https://issues.apache.org/jira/browse/AMBARI-18657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-18657: Attachment: AMBARI-18657.patch > Slider always creates storm slider conf directory > - > > Key: AMBARI-18657 > URL: https://issues.apache.org/jira/browse/AMBARI-18657 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18657.patch > > Original Estimate: 4h > Remaining Estimate: 4h > > The slider.py script in common-services should respect all possible ways of > installing slider. In a stack without storm there is no need to install the > storm slider client RPM. As a result the storm slider client directory will > be a broken link and attempting to create the storm slider client config > directory will result in an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18657) Slider always creates storm slider conf directory
[ https://issues.apache.org/jira/browse/AMBARI-18657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-18657: Attachment: (was: AMBARI-18657.patch) > Slider always creates storm slider conf directory > - > > Key: AMBARI-18657 > URL: https://issues.apache.org/jira/browse/AMBARI-18657 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18657.patch > > Original Estimate: 4h > Remaining Estimate: 4h > > The slider.py script in common-services should respect all possible ways of > installing slider. In a stack without storm there is no need to install the > storm slider client RPM. As a result the storm slider client directory will > be a broken link and attempting to create the storm slider client config > directory will result in an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18657) Slider always creates storm slider conf directory
[ https://issues.apache.org/jira/browse/AMBARI-18657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-18657: Status: Open (was: Patch Available) > Slider always creates storm slider conf directory > - > > Key: AMBARI-18657 > URL: https://issues.apache.org/jira/browse/AMBARI-18657 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18657.patch > > Original Estimate: 4h > Remaining Estimate: 4h > > The slider.py script in common-services should respect all possible ways of > installing slider. In a stack without storm there is no need to install the > storm slider client RPM. As a result the storm slider client directory will > be a broken link and attempting to create the storm slider client config > directory will result in an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18489) configs.sh spelling mistake fix
[
https://issues.apache.org/jira/browse/AMBARI-18489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595956#comment-15595956
]
Hudson commented on AMBARI-18489:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5845 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5845/])
AMBARI-18489: configs.sh has a spelling mistake inside the script (Jay (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5114bc9f7d4d8a246603e5d60dd528ab4cd312c7])
* (edit) ambari-server/src/main/resources/scripts/configs.sh
> configs.sh spelling mistake fix
> ---
>
> Key: AMBARI-18489
> URL: https://issues.apache.org/jira/browse/AMBARI-18489
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: All
>Reporter: JaySenSharma
>Assignee: JaySenSharma
> Labels: patch-available
> Attachments: AMBARI-18489.patch
>
>
> The "/var/lib/ambari-server/resources/scripts/configs.sh" shows incorrect
> spelling of "PUTting" instead of "putting"
> Example:
> {code}
> # /var/lib/ambari-server/resources/scripts/configs.sh set erie1.example.com
> ErieCluster cluster-env fetch_nonlocal_groups false
> ## Performing 'set' fetch_nonlocal_groups:false on (Site:cluster-env,
> Tag:TOPOLOGY_RESOLVED)
> ## Config found. Skipping origin value
> ## PUTting json into: doSet_version1475127716251871184.json
> ## NEW Site:cluster-env, Tag:version1475127716251871184
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18648) There were no labels on fields on step "Configure Kerberos" after clicking back
[ https://issues.apache.org/jira/browse/AMBARI-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-18648: - Fix Version/s: (was: 2.5.0) 2.4.2 > There were no labels on fields on step "Configure Kerberos" after clicking > back > --- > > Key: AMBARI-18648 > URL: https://issues.apache.org/jira/browse/AMBARI-18648 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.4.2 > > > STR: > #setup secure cluster > #start enabling Kerberos > #within "Install and test Kerberos client" step test got "Admin session > expiration error" window > #click cancel on "Admin session expiration error" window > #click back to step "Configure Kerberos" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18587) Post user creation hook
[
https://issues.apache.org/jira/browse/AMBARI-18587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595880#comment-15595880
]
Hadoop QA commented on AMBARI-18587:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834701/AMBARI-18587-trunk.v6.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.upgrade.UpgradeCatalog240Test
org.apache.ambari.server.security.authorization.AmbariLdapAuthenticationProviderTest
org.apache.ambari.server.agent.TestHeartbeatHandler
org.apache.ambari.server.state.cluster.ClusterEffectiveVersionTest
org.apache.ambari.server.controller.internal.StackUpgradeConfigurationMergeTest
org.apache.ambari.server.state.ServicePropertiesTest
org.apache.ambari.server.controller.internal.ActiveWidgetLayoutResourceProviderTest
org.apache.ambari.server.controller.internal.UserAuthorizationResourceProviderTest
org.apache.ambari.server.controller.AmbariManagementControllerImplTest
org.apache.ambari.server.security.authorization.AmbariLdapAuthenticationProviderForDNWithSpaceTest
org.apache.ambari.server.security.authorization.UsersTest
org.apache.ambari.server.controller.internal.UserResourceProviderTest
org.apache.ambari.server.security.authorization.AmbariAuthorizationFilterTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8969//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8969//console
This message is automatically generated.
> Post user creation hook
> ---
>
> Key: AMBARI-18587
> URL: https://issues.apache.org/jira/browse/AMBARI-18587
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Reporter: Laszlo Puskas
>Assignee: Laszlo Puskas
> Fix For: 2.5.0
>
> Attachments: AMBARI-18587-trunk.v6.patch
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> Ability to execute post user creation script
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18652) Alert Targets Cannot Be Updated Due To Transaction / Cache Timing Issues
[
https://issues.apache.org/jira/browse/AMBARI-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595874#comment-15595874
]
Hudson commented on AMBARI-18652:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5844 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5844/])
AMBARI-18652 - Alert Targets Cannot Be Updated Due To Transaction / (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=66259872fede7645be5c49391a3aa8bf13f4c8bf])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/AlertDispatchDAO.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertStateChangedEventTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/services/AlertNoticeDispatchServiceTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertGroupEntity.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertTargetEntity.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertNoticeEntity.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProviderTest.java
> Alert Targets Cannot Be Updated Due To Transaction / Cache Timing Issues
>
>
> Key: AMBARI-18652
> URL: https://issues.apache.org/jira/browse/AMBARI-18652
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18652.patch
>
>
> There is a JPA timing issue WRT to updating alert targets where lazy loaded
> lists outside of a transaction cause the data set on the {{AlertTargetEnity}}
> to be refreshed from the database.
> While maintaining the bi-directional relationship between
> {{AlertTargetEntity}} and {{AlertGroupEntity}}, and {{IndirectSet}} from JPA
> causes JPA to detect a stale entity from another transaction.
> STR:
> It's more likely to happen when there are active alerts.
> - Create a new alert target for _just_ HDFS
> - Shut down HDFS
> - Try to edit the name of the alert target
> It will return a 200 return code, but the data will not have changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18654) Implement instrumented Lock for profiling/logging
[ https://issues.apache.org/jira/browse/AMBARI-18654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595789#comment-15595789 ] Hudson commented on AMBARI-18654: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5843 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5843/]) AMBARI-18654. Implement instrumented Lock for profiling/logging. (Attila (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=462c8d9f61554f42704013d53b6376379dc408e0]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java * (add) ambari-server/src/test/java/org/apache/ambari/server/logging/ProfiledReentrantReadWriteLockTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/logging/ProfiledLock.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (add) ambari-server/src/main/java/org/apache/ambari/server/logging/LockProfileDelegate.java * (add) ambari-server/src/test/java/org/apache/ambari/server/logging/LockFactoryTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/logging/ProfiledReentrantLock.java * (add) ambari-server/src/main/java/org/apache/ambari/server/logging/ProfiledReentrantReadWriteLock.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/configuration/ConfigurationTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/logging/LockFactory.java > Implement instrumented Lock for profiling/logging > - > > Key: AMBARI-18654 > URL: https://issues.apache.org/jira/browse/AMBARI-18654 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Minor > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-18654.patch > > > As part of the reduced reliance on Java locks, we should allow for the lock > implementation provided to business objects to be able to log information > about their acquisition and release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18663) Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
[
https://issues.apache.org/jira/browse/AMBARI-18663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595791#comment-15595791
]
Hudson commented on AMBARI-18663:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5843 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5843/])
AMBARI-18663. Storm becomes stopped by itself after upgrade from 2.2.1.0
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3b159d27290a31df3c2269df1d0f6152d0dff780])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/common-services/STORM/0.9.1/configuration/storm-site.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.4.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.4.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.4.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ConfigureTask.java
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.4.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/STORM/configuration/storm-site.xml
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> -
>
> Key: AMBARI-18663
> URL: https://issues.apache.org/jira/browse/AMBARI-18663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.2
>
> Attachments: AMBARI-18663.patch
>
>
> STR:
> 1)Deploy old version cluster regarding environment (use public repo)
> 2)Enable AMS distr. mode
> 3)Make ambari only upgrade to 2.4.1.0
> Actual result:
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> {code}
> supervisor.log
> 2016-09-01 21:51:48.996 o.a.s.c.ConnectionState [ERROR] Connection timed out
> for connection string (host:2181,host:2181,host:2181/storm) and timeout
> (15000) / elapsed (18214)
> org.apache.storm.curator.CuratorConnectionLossException: KeeperErrorCode =
> ConnectionLoss
> at
> org.apache.storm.curator.ConnectionState.checkTimeouts(ConnectionState.java:195)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.ConnectionState.getZooKeeper(ConnectionState.java:87)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:115)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:821)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:807)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:63)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:267)
> [storm-core-0.10.0.2.4.2.0-2
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595787#comment-15595787 ] Doroszlai, Attila commented on AMBARI-17981: Hi [~swapanshridhar], could you please check the unit test that started giving error with this commit? https://builds.apache.org/job/Ambari-trunk-Commit/5836/testReport/ > Integrate Druid With Ambari > --- > > Key: AMBARI-17981 > URL: https://issues.apache.org/jira/browse/AMBARI-17981 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nishant Bangarwa >Assignee: Swapan Shridhar > Labels: features > Fix For: 2.5.0 > > Attachments: ambari-17981.patch > > > This task includes adding support for druid cluster provisioning via Ambari. > Details about Druid cluster design and different node types are present here > - > http://druid.io/docs/latest/design/design.html > In general, Druid can be defined as a service in HDP which has following > components - > 1) Coordinator > 2) Overlord > 3) Historical > 4) Broker > 5) Middlemanager > > Druid also has external dependencies on following > 1) Zookeeper - Ambari should be able to pass in zk configs to druid cluster > 2) Deep storage - A distributed FS, can be one of HDFS/S3 or any other NFS. > 3) Metadata Store - Mysql/Postgres. can be either provided by the user or a > mysql instance provisioned by ambari itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18657) Slider always creates storm slider conf directory
[
https://issues.apache.org/jira/browse/AMBARI-18657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595576#comment-15595576
]
Hadoop QA commented on AMBARI-18657:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834698/AMBARI-18657.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8966//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8966//console
This message is automatically generated.
> Slider always creates storm slider conf directory
> -
>
> Key: AMBARI-18657
> URL: https://issues.apache.org/jira/browse/AMBARI-18657
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
>Priority: Minor
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18657.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> The slider.py script in common-services should respect all possible ways of
> installing slider. In a stack without storm there is no need to install the
> storm slider client RPM. As a result the storm slider client directory will
> be a broken link and attempting to create the storm slider client config
> directory will result in an error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18652) Alert Targets Cannot Be Updated Due To Transaction / Cache Timing Issues
[
https://issues.apache.org/jira/browse/AMBARI-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18652:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Alert Targets Cannot Be Updated Due To Transaction / Cache Timing Issues
>
>
> Key: AMBARI-18652
> URL: https://issues.apache.org/jira/browse/AMBARI-18652
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18652.patch
>
>
> There is a JPA timing issue WRT to updating alert targets where lazy loaded
> lists outside of a transaction cause the data set on the {{AlertTargetEnity}}
> to be refreshed from the database.
> While maintaining the bi-directional relationship between
> {{AlertTargetEntity}} and {{AlertGroupEntity}}, and {{IndirectSet}} from JPA
> causes JPA to detect a stale entity from another transaction.
> STR:
> It's more likely to happen when there are active alerts.
> - Create a new alert target for _just_ HDFS
> - Shut down HDFS
> - Try to edit the name of the alert target
> It will return a 200 return code, but the data will not have changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18654) Implement instrumented Lock for profiling/logging
[ https://issues.apache.org/jira/browse/AMBARI-18654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-18654: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk: 462c8d9f61554f42704013d53b6376379dc408e0 branch-2.5: c2507d575599a44403107e375b583aa1222af65c > Implement instrumented Lock for profiling/logging > - > > Key: AMBARI-18654 > URL: https://issues.apache.org/jira/browse/AMBARI-18654 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Minor > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-18654.patch > > > As part of the reduced reliance on Java locks, we should allow for the lock > implementation provided to business objects to be able to log information > about their acquisition and release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18652) Alert Targets Cannot Be Updated Due To Transaction / Cache Timing Issues
[
https://issues.apache.org/jira/browse/AMBARI-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595720#comment-15595720
]
Hadoop QA commented on AMBARI-18652:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834436/AMBARI-18652.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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.agent.TestHeartbeatHandler
org.apache.ambari.server.state.ServicePropertiesTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8968//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8968//console
This message is automatically generated.
> Alert Targets Cannot Be Updated Due To Transaction / Cache Timing Issues
>
>
> Key: AMBARI-18652
> URL: https://issues.apache.org/jira/browse/AMBARI-18652
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18652.patch
>
>
> There is a JPA timing issue WRT to updating alert targets where lazy loaded
> lists outside of a transaction cause the data set on the {{AlertTargetEnity}}
> to be refreshed from the database.
> While maintaining the bi-directional relationship between
> {{AlertTargetEntity}} and {{AlertGroupEntity}}, and {{IndirectSet}} from JPA
> causes JPA to detect a stale entity from another transaction.
> STR:
> It's more likely to happen when there are active alerts.
> - Create a new alert target for _just_ HDFS
> - Shut down HDFS
> - Try to edit the name of the alert target
> It will return a 200 return code, but the data will not have changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18663) Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
[
https://issues.apache.org/jira/browse/AMBARI-18663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18663:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed
32565cd..a36a78f branch-2.4 -> branch-2.4
c2507d5..7f26a6a branch-2.5 -> branch-2.5
942b3db..3b159d2 trunk -> trunk
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> -
>
> Key: AMBARI-18663
> URL: https://issues.apache.org/jira/browse/AMBARI-18663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.2
>
> Attachments: AMBARI-18663.patch
>
>
> STR:
> 1)Deploy old version cluster regarding environment (use public repo)
> 2)Enable AMS distr. mode
> 3)Make ambari only upgrade to 2.4.1.0
> Actual result:
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> {code}
> supervisor.log
> 2016-09-01 21:51:48.996 o.a.s.c.ConnectionState [ERROR] Connection timed out
> for connection string (host:2181,host:2181,host:2181/storm) and timeout
> (15000) / elapsed (18214)
> org.apache.storm.curator.CuratorConnectionLossException: KeeperErrorCode =
> ConnectionLoss
> at
> org.apache.storm.curator.ConnectionState.checkTimeouts(ConnectionState.java:195)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.ConnectionState.getZooKeeper(ConnectionState.java:87)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:115)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:821)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:807)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:63)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:267)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [?:1.7.0_67]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [?:1.7.0_67]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [?:1.7.0_67]
> at java.lang.Thread.run(Thread.java:745) [?:1.7.0_67]
> 2016-09-01 21:51:49.000 b.s.d.supervisor [INFO]
> d0050058-970d-4faa-8170-b8d9b0515baf still hasn't started
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18587) Post user creation hook
[ https://issues.apache.org/jira/browse/AMBARI-18587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Puskas updated AMBARI-18587: --- Issue Type: New Feature (was: Bug) > Post user creation hook > --- > > Key: AMBARI-18587 > URL: https://issues.apache.org/jira/browse/AMBARI-18587 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Laszlo Puskas >Assignee: Laszlo Puskas > Fix For: 2.5.0 > > Attachments: AMBARI-18587-trunk.v6.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Ability to execute post user creation script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18587) Post user creation hook
[ https://issues.apache.org/jira/browse/AMBARI-18587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Puskas updated AMBARI-18587: --- Description: Ability to execute post user creation script (was: Implement ability to execute post user creation script) > Post user creation hook > --- > > Key: AMBARI-18587 > URL: https://issues.apache.org/jira/browse/AMBARI-18587 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Laszlo Puskas >Assignee: Laszlo Puskas > Fix For: 2.5.0 > > Attachments: AMBARI-18587-trunk.v6.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Ability to execute post user creation script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18108) [BLUEPRINT] hive.metastore.uris contains single entry when deployed with metastore HA enabled
[ https://issues.apache.org/jira/browse/AMBARI-18108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-18108: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk: 942b3dba72d946bbf82ea90d0f66b6d9c16c0eff branch-2.5: 90c531317b33f37c6c68e3cc1cf6039be92d8616 branch-2.4: 32565cd3c705dc48885064d454084deef4e44655 > [BLUEPRINT] hive.metastore.uris contains single entry when deployed with > metastore HA enabled > - > > Key: AMBARI-18108 > URL: https://issues.apache.org/jira/browse/AMBARI-18108 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.4.0 >Reporter: Michael Harp >Assignee: Doroszlai, Attila >Priority: Critical > Fix For: 3.0.0, 2.5.0, 2.4.2 > > Attachments: AMBARI-18108.patch > > > STR: > 1. Deploy using blueprint with Hive HA enabled > 2. Verify hive.metastore.uris contains single entry, should contain both > metastore URIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18108) [BLUEPRINT] hive.metastore.uris contains single entry when deployed with metastore HA enabled
[
https://issues.apache.org/jira/browse/AMBARI-18108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595532#comment-15595532
]
Doroszlai, Attila commented on AMBARI-18108:
Failed tests are unrelated and [were
failing|https://builds.apache.org/job/Ambari-trunk-Commit/5841/consoleText]
before the commit, too:
{noformat}
Failed tests:
TestHeartbeatHandler.testRegistrationRecoveryConfig:432
Tests in error:
ServicePropertiesTest.validatePropertySchemaOfServiceXMLs:48
{noformat}
> [BLUEPRINT] hive.metastore.uris contains single entry when deployed with
> metastore HA enabled
> -
>
> Key: AMBARI-18108
> URL: https://issues.apache.org/jira/browse/AMBARI-18108
> Project: Ambari
> Issue Type: Bug
> Components: blueprints
>Affects Versions: 2.4.0
>Reporter: Michael Harp
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 3.0.0, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18108.patch
>
>
> STR:
> 1. Deploy using blueprint with Hive HA enabled
> 2. Verify hive.metastore.uris contains single entry, should contain both
> metastore URIs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-18617) Adding custom property to hive-site adds it to other 'Custom' panels on hive
[ https://issues.apache.org/jira/browse/AMBARI-18617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly reassigned AMBARI-18617: --- Assignee: Jaimin D Jetly > Adding custom property to hive-site adds it to other 'Custom' panels on hive > > > Key: AMBARI-18617 > URL: https://issues.apache.org/jira/browse/AMBARI-18617 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Dhanya Balasundaran >Assignee: Jaimin D Jetly > Fix For: 2.4.2 > > Attachments: AMBARI-18617.patch > > > - Navigate through Ambari Install Wizard to reach Customize Services page > - Choose Hive > - Add a custom property to Custom-hive-site > - Noticed that its getting added to Custom hivemetastore-site, > Custom hiveserver2-interactive-site, Custom hiveserver2-site, > Custom hivemetastore-site, Custom tez-interactive-site. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18108) [BLUEPRINT] hive.metastore.uris contains single entry when deployed with metastore HA enabled
[ https://issues.apache.org/jira/browse/AMBARI-18108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595511#comment-15595511 ] Hudson commented on AMBARI-18108: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5842 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5842/]) AMBARI-18108. [BLUEPRINT] hive.metastore.uris contains single entry when (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=942b3dba72d946bbf82ea90d0f66b6d9c16c0eff]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java > [BLUEPRINT] hive.metastore.uris contains single entry when deployed with > metastore HA enabled > - > > Key: AMBARI-18108 > URL: https://issues.apache.org/jira/browse/AMBARI-18108 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.4.0 >Reporter: Michael Harp >Assignee: Doroszlai, Attila >Priority: Critical > Fix For: 3.0.0, 2.5.0, 2.4.2 > > Attachments: AMBARI-18108.patch > > > STR: > 1. Deploy using blueprint with Hive HA enabled > 2. Verify hive.metastore.uris contains single entry, should contain both > metastore URIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18658) Pig view does not load - Issue with codemirror versions
[
https://issues.apache.org/jira/browse/AMBARI-18658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595505#comment-15595505
]
Hadoop QA commented on AMBARI-18658:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834644/AMBARI-18658.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/pig
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8965//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8965//console
This message is automatically generated.
> Pig view does not load - Issue with codemirror versions
> ---
>
> Key: AMBARI-18658
> URL: https://issues.apache.org/jira/browse/AMBARI-18658
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Ashwin Rajeev
>Assignee: Ashwin Rajeev
> Fix For: 2.5.0
>
> Attachments: AMBARI-18658.trunk.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18587) Post user creation hook
[ https://issues.apache.org/jira/browse/AMBARI-18587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Puskas updated AMBARI-18587: --- Attachment: AMBARI-18587-trunk.v6.patch > Post user creation hook > --- > > Key: AMBARI-18587 > URL: https://issues.apache.org/jira/browse/AMBARI-18587 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Laszlo Puskas >Assignee: Laszlo Puskas > Fix For: 2.5.0 > > Attachments: AMBARI-18587-trunk.v6.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Implement ability to execute post user creation script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18108) [BLUEPRINT] hive.metastore.uris contains single entry when deployed with metastore HA enabled
[ https://issues.apache.org/jira/browse/AMBARI-18108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595490#comment-15595490 ] Hudson commented on AMBARI-18108: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #185 (See [https://builds.apache.org/job/Ambari-branch-2.5/185/]) AMBARI-18108. [BLUEPRINT] hive.metastore.uris contains single entry when (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=90c531317b33f37c6c68e3cc1cf6039be92d8616]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java > [BLUEPRINT] hive.metastore.uris contains single entry when deployed with > metastore HA enabled > - > > Key: AMBARI-18108 > URL: https://issues.apache.org/jira/browse/AMBARI-18108 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.4.0 >Reporter: Michael Harp >Assignee: Doroszlai, Attila >Priority: Critical > Fix For: 3.0.0, 2.5.0, 2.4.2 > > Attachments: AMBARI-18108.patch > > > STR: > 1. Deploy using blueprint with Hive HA enabled > 2. Verify hive.metastore.uris contains single entry, should contain both > metastore URIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18587) Post user creation hook
[ https://issues.apache.org/jira/browse/AMBARI-18587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Puskas updated AMBARI-18587: --- Status: Patch Available (was: Open) > Post user creation hook > --- > > Key: AMBARI-18587 > URL: https://issues.apache.org/jira/browse/AMBARI-18587 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Laszlo Puskas >Assignee: Laszlo Puskas > Fix For: 2.5.0 > > Original Estimate: 336h > Remaining Estimate: 336h > > Implement ability to execute post user creation script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18663) Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
[
https://issues.apache.org/jira/browse/AMBARI-18663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18663:
Fix Version/s: 2.4.2
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> -
>
> Key: AMBARI-18663
> URL: https://issues.apache.org/jira/browse/AMBARI-18663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.2
>
> Attachments: AMBARI-18663.patch
>
>
> STR:
> 1)Deploy old version cluster regarding environment (use public repo)
> 2)Enable AMS distr. mode
> 3)Make ambari only upgrade to 2.4.1.0
> Actual result:
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> {code}
> supervisor.log
> 2016-09-01 21:51:48.996 o.a.s.c.ConnectionState [ERROR] Connection timed out
> for connection string (host:2181,host:2181,host:2181/storm) and timeout
> (15000) / elapsed (18214)
> org.apache.storm.curator.CuratorConnectionLossException: KeeperErrorCode =
> ConnectionLoss
> at
> org.apache.storm.curator.ConnectionState.checkTimeouts(ConnectionState.java:195)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.ConnectionState.getZooKeeper(ConnectionState.java:87)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:115)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:821)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:807)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:63)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:267)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [?:1.7.0_67]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [?:1.7.0_67]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [?:1.7.0_67]
> at java.lang.Thread.run(Thread.java:745) [?:1.7.0_67]
> 2016-09-01 21:51:49.000 b.s.d.supervisor [INFO]
> d0050058-970d-4faa-8170-b8d9b0515baf still hasn't started
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18663) Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
[
https://issues.apache.org/jira/browse/AMBARI-18663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18663:
Status: Patch Available (was: Open)
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> -
>
> Key: AMBARI-18663
> URL: https://issues.apache.org/jira/browse/AMBARI-18663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18663.patch
>
>
> STR:
> 1)Deploy old version cluster regarding environment (use public repo)
> 2)Enable AMS distr. mode
> 3)Make ambari only upgrade to 2.4.1.0
> Actual result:
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> {code}
> supervisor.log
> 2016-09-01 21:51:48.996 o.a.s.c.ConnectionState [ERROR] Connection timed out
> for connection string (host:2181,host:2181,host:2181/storm) and timeout
> (15000) / elapsed (18214)
> org.apache.storm.curator.CuratorConnectionLossException: KeeperErrorCode =
> ConnectionLoss
> at
> org.apache.storm.curator.ConnectionState.checkTimeouts(ConnectionState.java:195)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.ConnectionState.getZooKeeper(ConnectionState.java:87)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:115)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:821)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:807)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:63)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:267)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [?:1.7.0_67]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [?:1.7.0_67]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [?:1.7.0_67]
> at java.lang.Thread.run(Thread.java:745) [?:1.7.0_67]
> 2016-09-01 21:51:49.000 b.s.d.supervisor [INFO]
> d0050058-970d-4faa-8170-b8d9b0515baf still hasn't started
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18663) Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
[
https://issues.apache.org/jira/browse/AMBARI-18663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18663:
Attachment: AMBARI-18663.patch
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> -
>
> Key: AMBARI-18663
> URL: https://issues.apache.org/jira/browse/AMBARI-18663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18663.patch
>
>
> STR:
> 1)Deploy old version cluster regarding environment (use public repo)
> 2)Enable AMS distr. mode
> 3)Make ambari only upgrade to 2.4.1.0
> Actual result:
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> {code}
> supervisor.log
> 2016-09-01 21:51:48.996 o.a.s.c.ConnectionState [ERROR] Connection timed out
> for connection string (host:2181,host:2181,host:2181/storm) and timeout
> (15000) / elapsed (18214)
> org.apache.storm.curator.CuratorConnectionLossException: KeeperErrorCode =
> ConnectionLoss
> at
> org.apache.storm.curator.ConnectionState.checkTimeouts(ConnectionState.java:195)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.ConnectionState.getZooKeeper(ConnectionState.java:87)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:115)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:821)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:807)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:63)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:267)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [?:1.7.0_67]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [?:1.7.0_67]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [?:1.7.0_67]
> at java.lang.Thread.run(Thread.java:745) [?:1.7.0_67]
> 2016-09-01 21:51:49.000 b.s.d.supervisor [INFO]
> d0050058-970d-4faa-8170-b8d9b0515baf still hasn't started
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18663) Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
[
https://issues.apache.org/jira/browse/AMBARI-18663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18663:
Component/s: ambari-server
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> -
>
> Key: AMBARI-18663
> URL: https://issues.apache.org/jira/browse/AMBARI-18663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18663.patch
>
>
> STR:
> 1)Deploy old version cluster regarding environment (use public repo)
> 2)Enable AMS distr. mode
> 3)Make ambari only upgrade to 2.4.1.0
> Actual result:
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> {code}
> supervisor.log
> 2016-09-01 21:51:48.996 o.a.s.c.ConnectionState [ERROR] Connection timed out
> for connection string (host:2181,host:2181,host:2181/storm) and timeout
> (15000) / elapsed (18214)
> org.apache.storm.curator.CuratorConnectionLossException: KeeperErrorCode =
> ConnectionLoss
> at
> org.apache.storm.curator.ConnectionState.checkTimeouts(ConnectionState.java:195)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.ConnectionState.getZooKeeper(ConnectionState.java:87)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:115)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:821)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:807)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:63)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at
> org.apache.storm.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:267)
> [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [?:1.7.0_67]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [?:1.7.0_67]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [?:1.7.0_67]
> at java.lang.Thread.run(Thread.java:745) [?:1.7.0_67]
> 2016-09-01 21:51:49.000 b.s.d.supervisor [INFO]
> d0050058-970d-4faa-8170-b8d9b0515baf still hasn't started
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18663) Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
Dmitry Lysnichenko created AMBARI-18663:
---
Summary: Storm becomes stopped by itself after upgrade from
2.2.1.0 to 2.4.1.0
Key: AMBARI-18663
URL: https://issues.apache.org/jira/browse/AMBARI-18663
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
STR:
1)Deploy old version cluster regarding environment (use public repo)
2)Enable AMS distr. mode
3)Make ambari only upgrade to 2.4.1.0
Actual result:
Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
{code}
supervisor.log
2016-09-01 21:51:48.996 o.a.s.c.ConnectionState [ERROR] Connection timed out
for connection string (host:2181,host:2181,host:2181/storm) and timeout (15000)
/ elapsed (18214)
org.apache.storm.curator.CuratorConnectionLossException: KeeperErrorCode =
ConnectionLoss
at
org.apache.storm.curator.ConnectionState.checkTimeouts(ConnectionState.java:195)
[storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
at
org.apache.storm.curator.ConnectionState.getZooKeeper(ConnectionState.java:87)
[storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
at
org.apache.storm.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:115)
[storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
at
org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:821)
[storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
at
org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:807)
[storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
at
org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:63)
[storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
at
org.apache.storm.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:267)
[storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [?:1.7.0_67]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[?:1.7.0_67]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[?:1.7.0_67]
at java.lang.Thread.run(Thread.java:745) [?:1.7.0_67]
2016-09-01 21:51:49.000 b.s.d.supervisor [INFO]
d0050058-970d-4faa-8170-b8d9b0515baf still hasn't started
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18657) Slider always creates storm slider conf directory
[
https://issues.apache.org/jira/browse/AMBARI-18657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595464#comment-15595464
]
Hadoop QA commented on AMBARI-18657:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834645/AMBARI-18657.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8964//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8964//console
This message is automatically generated.
> Slider always creates storm slider conf directory
> -
>
> Key: AMBARI-18657
> URL: https://issues.apache.org/jira/browse/AMBARI-18657
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
>Priority: Minor
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18657.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> The slider.py script in common-services should respect all possible ways of
> installing slider. In a stack without storm there is no need to install the
> storm slider client RPM. As a result the storm slider client directory will
> be a broken link and attempting to create the storm slider client config
> directory will result in an error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18657) Slider always creates storm slider conf directory
[ https://issues.apache.org/jira/browse/AMBARI-18657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-18657: Status: Patch Available (was: Open) > Slider always creates storm slider conf directory > - > > Key: AMBARI-18657 > URL: https://issues.apache.org/jira/browse/AMBARI-18657 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18657.patch > > Original Estimate: 4h > Remaining Estimate: 4h > > The slider.py script in common-services should respect all possible ways of > installing slider. In a stack without storm there is no need to install the > storm slider client RPM. As a result the storm slider client directory will > be a broken link and attempting to create the storm slider client config > directory will result in an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18657) Slider always creates storm slider conf directory
[ https://issues.apache.org/jira/browse/AMBARI-18657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-18657: Attachment: AMBARI-18657.patch > Slider always creates storm slider conf directory > - > > Key: AMBARI-18657 > URL: https://issues.apache.org/jira/browse/AMBARI-18657 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18657.patch > > Original Estimate: 4h > Remaining Estimate: 4h > > The slider.py script in common-services should respect all possible ways of > installing slider. In a stack without storm there is no need to install the > storm slider client RPM. As a result the storm slider client directory will > be a broken link and attempting to create the storm slider client config > directory will result in an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18657) Slider always creates storm slider conf directory
[ https://issues.apache.org/jira/browse/AMBARI-18657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-18657: Attachment: (was: AMBARI-18657.patch) > Slider always creates storm slider conf directory > - > > Key: AMBARI-18657 > URL: https://issues.apache.org/jira/browse/AMBARI-18657 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Original Estimate: 4h > Remaining Estimate: 4h > > The slider.py script in common-services should respect all possible ways of > installing slider. In a stack without storm there is no need to install the > storm slider client RPM. As a result the storm slider client directory will > be a broken link and attempting to create the storm slider client config > directory will result in an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18657) Slider always creates storm slider conf directory
[ https://issues.apache.org/jira/browse/AMBARI-18657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-18657: Status: Open (was: Patch Available) > Slider always creates storm slider conf directory > - > > Key: AMBARI-18657 > URL: https://issues.apache.org/jira/browse/AMBARI-18657 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Original Estimate: 4h > Remaining Estimate: 4h > > The slider.py script in common-services should respect all possible ways of > installing slider. In a stack without storm there is no need to install the > storm slider client RPM. As a result the storm slider client directory will > be a broken link and attempting to create the storm slider client config > directory will result in an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18662) Check that Stack Version and repo URLs match up when registering repo
[
https://issues.apache.org/jira/browse/AMBARI-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595393#comment-15595393
]
Hadoop QA commented on AMBARI-18662:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834686/AMBARI-18662.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/8959//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8959//console
This message is automatically generated.
> Check that Stack Version and repo URLs match up when registering repo
> --
>
> Key: AMBARI-18662
> URL: https://issues.apache.org/jira/browse/AMBARI-18662
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-18662.patch
>
>
> Right now there's no validation when registering a repo to catch these type
> of user errors, which caused a lot of problems down the road. We should have
> very basic validation using JS so that if we detect a number like "2.5.0.0"
> we ensure that the selected stack is also HDP 2.5.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18660) Log Search schema meta data loader fix
[
https://issues.apache.org/jira/browse/AMBARI-18660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595404#comment-15595404
]
Hadoop QA commented on AMBARI-18660:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834651/AMBARI-18660.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8963//console
This message is automatically generated.
> Log Search schema meta data loader fix
> --
>
> Key: AMBARI-18660
> URL: https://issues.apache.org/jira/browse/AMBARI-18660
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-18660.patch
>
>
> Log Search periodically queries the solr for the field meta data, which may
> not work on some clusters. Scheduling this task should be done by spring.
> Also the luke request sent for this purpose must be requested from each
> shard, and the results must be summarized. Unfortunately the solr client can
> not be used for this purpose because it sends it to random shard.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18606) Improve Audit Log processing by Logfeeder
[
https://issues.apache.org/jira/browse/AMBARI-18606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595402#comment-15595402
]
Hadoop QA commented on AMBARI-18606:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834658/AMBARI-18606.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8962//console
This message is automatically generated.
> Improve Audit Log processing by Logfeeder
> -
>
> Key: AMBARI-18606
> URL: https://issues.apache.org/jira/browse/AMBARI-18606
> Project: Ambari
> Issue Type: Bug
> Components: logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-18606.patch
>
>
> Logfeeder should be able to handle dynamic audit fields.
> Ambari Audit log has some information which should be indexed, searchable,
> and present in the log table on the UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
