[jira] [Updated] (AMBARI-16214) Ensure Blueprint deployment can start immediately - after Server start

[ https://issues.apache.org/jira/browse/AMBARI-16214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16214: -- Description: * Blueprint may be provided during cluster start up (no need for a REST

[jira] [Updated] (AMBARI-16214) Ensure Blueprint deployment can start immediately - after Server start

[ https://issues.apache.org/jira/browse/AMBARI-16214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16214: -- Assignee: Sandor Magyari > Ensure Blueprint deployment can start immediately - after

[jira] [Updated] (AMBARI-16220) No INSTALL commands

[ https://issues.apache.org/jira/browse/AMBARI-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16220: -- Assignee: Sandor Magyari > No INSTALL commands > --- > >

[jira] [Updated] (AMBARI-16220) No INSTALL commands

[ https://issues.apache.org/jira/browse/AMBARI-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16220: -- Fix Version/s: (was: 2.4.1) 2.5.0 > No INSTALL commands >

[jira] [Resolved] (AMBARI-17219) Removing and re-adding hosts makes database inconsitent

[ https://issues.apache.org/jira/browse/AMBARI-17219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader resolved AMBARI-17219. --- Resolution: Fixed Fix Version/s: (was: 2.5.0)

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Attachment: AMBARI-17248.trunk.patch > Reduce the idle time before first command from

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Status: Patch Available (was: In Progress) > Reduce the idle time before first

[jira] [Created] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

Sebastian Toader created AMBARI-17248: - Summary: Reduce the idle time before first command from next stage is executed on a host Key: AMBARI-17248 URL: https://issues.apache.org/jira/browse/AMBARI-17248

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Fix Version/s: (was: 2.5.0) (was: 2.2-next)

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Attachment: AMBARI-17248.trunk.v2.patch > Reduce the idle time before first command

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Attachment: (was: AMBARI-17248.trunk.patch) > Reduce the idle time before first

[jira] [Resolved] (AMBARI-16216) Agent to respond immediately after command execution

[ https://issues.apache.org/jira/browse/AMBARI-16216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader resolved AMBARI-16216. --- Resolution: Not A Problem > Agent to respond immediately after command execution >

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Attachment: AMBARI-17248.trunk.v7.patch > Reduce the idle time before first command

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Attachment: AMBARI-17248.trunk.v6.patch > Reduce the idle time before first command

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Attachment: (was: AMBARI-17248.trunk.v5.patch) > Reduce the idle time before

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Attachment: (was: AMBARI-17248.trunk.v6.patch) > Reduce the idle time before

[jira] [Commented] (AMBARI-17053) Add explicit ambari-server log line indicating cluster creation complete

[ https://issues.apache.org/jira/browse/AMBARI-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335546#comment-15335546 ] Sebastian Toader commented on AMBARI-17053: --- Committed to trunk: {code} commit

[jira] [Updated] (AMBARI-17053) Add explicit ambari-server log line indicating cluster creation complete

[ https://issues.apache.org/jira/browse/AMBARI-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17053: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Add explicit

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Attachment: AMBARI-17248.trunk.v5.patch > Reduce the idle time before first command

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Attachment: (was: AMBARI-17248.trunk.v4.patch) > Reduce the idle time before

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Reduce the idle

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Attachment: (was: AMBARI-17248.trunk.v3.patch) > Reduce the idle time before

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Attachment: AMBARI-17248.trunk.v4.patch > Reduce the idle time before first command

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Attachment: (was: AMBARI-17248.trunk.v2.patch) > Reduce the idle time before

[jira] [Updated] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host

[ https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17248: -- Attachment: AMBARI-17248.trunk.v3.patch > Reduce the idle time before first command

[jira] [Updated] (AMBARI-17419) Disabling the auto-start for ambari-server and ambari-agent doesn't work on systemd

[ https://issues.apache.org/jira/browse/AMBARI-17419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17419: -- Attachment: AMBARI-17419.trunk.v1.patch > Disabling the auto-start for ambari-server

[jira] [Updated] (AMBARI-17419) Disabling the auto-start for ambari-server and ambari-agent doesn't work on systemd

[ https://issues.apache.org/jira/browse/AMBARI-17419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17419: -- Attachment: (was: AMBARI-17419.v1.patch) > Disabling the auto-start for

[jira] [Created] (AMBARI-17419) Disabling the auto-start for ambari-server and ambari-agent doesn't work on systemd

Sebastian Toader created AMBARI-17419: - Summary: Disabling the auto-start for ambari-server and ambari-agent doesn't work on systemd Key: AMBARI-17419 URL: https://issues.apache.org/jira/browse/AMBARI-17419

[jira] [Updated] (AMBARI-17419) Disabling the auto-start for ambari-server and ambari-agent doesn't work on systemd

[ https://issues.apache.org/jira/browse/AMBARI-17419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17419: -- Attachment: AMBARI-17419.v1.patch > Disabling the auto-start for ambari-server and

[jira] [Updated] (AMBARI-17419) Disabling the auto-start for ambari-server and ambari-agent doesn't work on systemd

[ https://issues.apache.org/jira/browse/AMBARI-17419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17419: -- Status: Patch Available (was: In Progress) > Disabling the auto-start for

[jira] [Commented] (AMBARI-15296) Missing property: hive.server2.authentication.kerberos.keytab

[ https://issues.apache.org/jira/browse/AMBARI-15296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188906#comment-15188906 ] Sebastian Toader commented on AMBARI-15296: --- Committed to branch-2.2: {code} commit

[jira] [Updated] (AMBARI-15336) Blueprints: NullPointerException when unncessary config types found with %HOSTGROUP% tags

[ https://issues.apache.org/jira/browse/AMBARI-15336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15336: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Blueprints:

[jira] [Commented] (AMBARI-15457) Topology host info is not cleared when a host is removed

[ https://issues.apache.org/jira/browse/AMBARI-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202639#comment-15202639 ] Sebastian Toader commented on AMBARI-15457: --- Committed to branch-2.2 {noformat} commit

[jira] [Commented] (AMBARI-15241) Basic Operational Audit Logging

[ https://issues.apache.org/jira/browse/AMBARI-15241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15218707#comment-15218707 ] Sebastian Toader commented on AMBARI-15241: --- Committed to trunk: {code} commit

[jira] [Updated] (AMBARI-15241) Basic Operational Audit Logging

[ https://issues.apache.org/jira/browse/AMBARI-15241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15241: -- Attachment: AMBARI-15241.v2.patch > Basic Operational Audit Logging >

[jira] [Created] (AMBARI-15643) During cluster creation using Blueprints the cluster creation request has incorrect COMPLETED state instead of PENDING.

Sebastian Toader created AMBARI-15643: - Summary: During cluster creation using Blueprints the cluster creation request has incorrect COMPLETED state instead of PENDING. Key: AMBARI-15643 URL:

[jira] [Created] (AMBARI-15744) Webhcat Server failed to stop while stopping all the services

Sebastian Toader created AMBARI-15744: - Summary: Webhcat Server failed to stop while stopping all the services Key: AMBARI-15744 URL: https://issues.apache.org/jira/browse/AMBARI-15744 Project:

[jira] [Updated] (AMBARI-15744) Webhcat Server failed to stop while stopping all the services

[ https://issues.apache.org/jira/browse/AMBARI-15744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15744: -- Attachment: AMBARI-15744.trunk.v2.patch

[jira] [Commented] (AMBARI-15744) Webhcat Server failed to stop while stopping all the services

[ https://issues.apache.org/jira/browse/AMBARI-15744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230212#comment-15230212 ] Sebastian Toader commented on AMBARI-15744: --- Part2 committed to trunk: {code} commit

[jira] [Commented] (AMBARI-15646) Audit Log Code Cleanup & Safety

[ https://issues.apache.org/jira/browse/AMBARI-15646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230846#comment-15230846 ] Sebastian Toader commented on AMBARI-15646: --- Committed to trunk: {code} commit

[jira] [Updated] (AMBARI-15744) Webhcat Server failed to stop while stopping all the services

[ https://issues.apache.org/jira/browse/AMBARI-15744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15744: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Webhcat Server

[jira] [Updated] (AMBARI-15744) Webhcat Server failed to stop while stopping all the services

[ https://issues.apache.org/jira/browse/AMBARI-15744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15744: -- Attachment: AMBARI-15744.trunk.v1.patch

[jira] [Updated] (AMBARI-15744) Webhcat Server failed to stop while stopping all the services

[ https://issues.apache.org/jira/browse/AMBARI-15744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15744: -- Status: Patch Available (was: In Progress) > Webhcat Server failed to stop while

[jira] [Created] (AMBARI-15803) Restarting ambari-server after successful blueprint deploy of large cluster makes it unresponsive

Sebastian Toader created AMBARI-15803: - Summary: Restarting ambari-server after successful blueprint deploy of large cluster makes it unresponsive Key: AMBARI-15803 URL:

[jira] [Updated] (AMBARI-15803) Restarting ambari-server after successful blueprint deploy of large cluster makes it unresponsive

[ https://issues.apache.org/jira/browse/AMBARI-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15803: -- Attachment: AMBARI-15803.trunk.v1.patch

[jira] [Updated] (AMBARI-15803) Restarting ambari-server after successful blueprint deploy of large cluster makes it unresponsive

[ https://issues.apache.org/jira/browse/AMBARI-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15803: -- Attachment: (was: AMBARI-15803.branch-2.2.v1.patch) > Restarting ambari-server

[jira] [Updated] (AMBARI-15803) Restarting ambari-server after successful blueprint deploy of large cluster makes it unresponsive

[ https://issues.apache.org/jira/browse/AMBARI-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15803: -- Attachment: AMBARI-15803.trunk.v2.patch

[jira] [Updated] (AMBARI-15803) Restarting ambari-server after successful blueprint deploy of large cluster makes it unresponsive

[ https://issues.apache.org/jira/browse/AMBARI-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15803: -- Attachment: (was: AMBARI-15803.trunk.v1.patch) > Restarting ambari-server after

[jira] [Commented] (AMBARI-15804) Audit logging cleanup and tests

[ https://issues.apache.org/jira/browse/AMBARI-15804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238695#comment-15238695 ] Sebastian Toader commented on AMBARI-15804: --- Committed to trunk: {code} commit

[jira] [Updated] (AMBARI-15804) Audit logging cleanup and tests

[ https://issues.apache.org/jira/browse/AMBARI-15804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15804: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Audit logging

[jira] [Updated] (AMBARI-15646) Audit Log Code Cleanup & Safety

[ https://issues.apache.org/jira/browse/AMBARI-15646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15646: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Audit Log Code

[jira] [Updated] (AMBARI-15803) Restarting ambari-server after successful blueprint deploy of large cluster makes it unresponsive

[ https://issues.apache.org/jira/browse/AMBARI-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15803: -- Status: Patch Available (was: In Progress) > Restarting ambari-server after

[jira] [Commented] (AMBARI-15786) Add some logs to help co-related task ids from server and agent

[ https://issues.apache.org/jira/browse/AMBARI-15786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15234953#comment-15234953 ] Sebastian Toader commented on AMBARI-15786: --- +1 > Add some logs to help co-related task ids

[jira] [Updated] (AMBARI-15803) Restarting ambari-server after successful blueprint deploy of large cluster makes it unresponsive

[ https://issues.apache.org/jira/browse/AMBARI-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15803: -- Attachment: AMBARI-15803.trunk.v3.patch

[jira] [Updated] (AMBARI-15803) Restarting ambari-server after successful blueprint deploy of large cluster makes it unresponsive

[ https://issues.apache.org/jira/browse/AMBARI-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15803: -- Attachment: (was: AMBARI-15803.branch-2.2.v2.patch) > Restarting ambari-server

[jira] [Commented] (AMBARI-15803) Restarting ambari-server after successful blueprint deploy of large cluster makes it unresponsive

[ https://issues.apache.org/jira/browse/AMBARI-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237039#comment-15237039 ] Sebastian Toader commented on AMBARI-15803: --- Committed to trunk: {code} commit

[jira] [Updated] (AMBARI-15803) Restarting ambari-server after successful blueprint deploy of large cluster makes it unresponsive

[ https://issues.apache.org/jira/browse/AMBARI-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15803: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Restarting

[jira] [Commented] (AMBARI-15744) Webhcat Server failed to stop while stopping all the services

[ https://issues.apache.org/jira/browse/AMBARI-15744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230023#comment-15230023 ] Sebastian Toader commented on AMBARI-15744: --- Committed to trunk: {code} commit

[jira] [Commented] (AMBARI-15489) Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating Kerberized cluster with Blueprints

[ https://issues.apache.org/jira/browse/AMBARI-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15205284#comment-15205284 ] Sebastian Toader commented on AMBARI-15489: --- Committed to trunk: {code} commit

[jira] [Updated] (AMBARI-15489) Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating Kerberized cluster with Blueprints

[ https://issues.apache.org/jira/browse/AMBARI-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15489: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Configuration

[jira] [Updated] (AMBARI-15554) Ambari LDAP integration cannot handle LDAP directories with multiple entries for the same user

[ https://issues.apache.org/jira/browse/AMBARI-15554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15554: -- Attachment: AMBARI-15554.v1.patch > Ambari LDAP integration cannot handle LDAP

[jira] [Updated] (AMBARI-15531) Hiveserver2 goes down on HA cluster deployed via blueprint

[ https://issues.apache.org/jira/browse/AMBARI-15531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15531: -- Fix Version/s: 2.4.0 > Hiveserver2 goes down on HA cluster deployed via blueprint >

[jira] [Updated] (AMBARI-15489) Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating Kerberized cluster with Blueprints

[ https://issues.apache.org/jira/browse/AMBARI-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15489: -- Fix Version/s: (was: 2.4.0) > Configuration with tag 'TOPOLOGY_RESOLVED' exists

[jira] [Updated] (AMBARI-15489) Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating Kerberized cluster with Blueprints

[ https://issues.apache.org/jira/browse/AMBARI-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15489: -- Fix Version/s: (was: 2.4.0) > Configuration with tag 'TOPOLOGY_RESOLVED' exists

[jira] [Updated] (AMBARI-15489) Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating Kerberized cluster with Blueprints

[ https://issues.apache.org/jira/browse/AMBARI-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15489: -- Attachment: AMBARI-15489.v1.patch > Configuration with tag 'TOPOLOGY_RESOLVED' exists

[jira] [Updated] (AMBARI-15489) Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating Kerberized cluster with Blueprints

[ https://issues.apache.org/jira/browse/AMBARI-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15489: -- Fix Version/s: 2.2.2 2.4.0 > Configuration with tag

[jira] [Created] (AMBARI-15489) Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating Kerberized cluster with Blueprints

Sebastian Toader created AMBARI-15489: - Summary: Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating Kerberized cluster with Blueprints Key: AMBARI-15489 URL:

[jira] [Updated] (AMBARI-15489) Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating Kerberized cluster with Blueprints

[ https://issues.apache.org/jira/browse/AMBARI-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15489: -- Status: Patch Available (was: In Progress) > Configuration with tag

[jira] [Updated] (AMBARI-15489) Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating Kerberized cluster with Blueprints

[ https://issues.apache.org/jira/browse/AMBARI-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15489: -- Attachment: AMBARI-15489.v2.patch > Configuration with tag 'TOPOLOGY_RESOLVED' exists

[jira] [Updated] (AMBARI-15489) Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating Kerberized cluster with Blueprints

[ https://issues.apache.org/jira/browse/AMBARI-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15489: -- Attachment: (was: AMBARI-15489.v1.patch) > Configuration with tag

[jira] [Updated] (AMBARI-15489) Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating Kerberized cluster with Blueprints

[ https://issues.apache.org/jira/browse/AMBARI-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15489: -- Attachment: AMBARI-15489-trunk.v2.patch > Configuration with tag 'TOPOLOGY_RESOLVED'

[jira] [Updated] (AMBARI-15554) Ambari LDAP integration cannot handle LDAP directories with multiple entries for the same user

[ https://issues.apache.org/jira/browse/AMBARI-15554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15554: -- Attachment: AMBARI-15554.v2.patch > Ambari LDAP integration cannot handle LDAP

[jira] [Updated] (AMBARI-15554) Ambari LDAP integration cannot handle LDAP directories with multiple entries for the same user

[ https://issues.apache.org/jira/browse/AMBARI-15554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15554: -- Attachment: (was: AMBARI-15554.v1.patch) > Ambari LDAP integration cannot handle

[jira] [Commented] (AMBARI-15665) Unable to Create Cluster Fails Due To Audit Logger

[ https://issues.apache.org/jira/browse/AMBARI-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223162#comment-15223162 ] Sebastian Toader commented on AMBARI-15665: --- Committed to trunk: {code} commit

[jira] [Updated] (AMBARI-15665) Unable to Create Cluster Fails Due To Audit Logger

[ https://issues.apache.org/jira/browse/AMBARI-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15665: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Unable to Create

[jira] [Updated] (AMBARI-15643) During cluster creation using Blueprints the cluster creation request has incorrect COMPLETED state instead of PENDING.

[ https://issues.apache.org/jira/browse/AMBARI-15643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15643: -- Attachment: AMBARI-15643.v1.patch > During cluster creation using Blueprints the

[jira] [Commented] (AMBARI-15643) During cluster creation using Blueprints the cluster creation request has incorrect COMPLETED state instead of PENDING.

[ https://issues.apache.org/jira/browse/AMBARI-15643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220167#comment-15220167 ] Sebastian Toader commented on AMBARI-15643: --- Committed to trunk: {code} commit

[jira] [Updated] (AMBARI-15643) During cluster creation using Blueprints the cluster creation request has incorrect COMPLETED state instead of PENDING.

[ https://issues.apache.org/jira/browse/AMBARI-15643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15643: -- Status: Patch Available (was: In Progress) > During cluster creation using

[jira] [Updated] (AMBARI-15554) Ambari LDAP integration cannot handle LDAP directories with multiple entries for the same user

[ https://issues.apache.org/jira/browse/AMBARI-15554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15554: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari LDAP

[jira] [Updated] (AMBARI-15645) Upgrading Kerberized JournalNode requires HDFS principal to perform 'role edits' task

[ https://issues.apache.org/jira/browse/AMBARI-15645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15645: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrading

[jira] [Commented] (AMBARI-15554) Ambari LDAP integration cannot handle LDAP directories with multiple entries for the same user

[ https://issues.apache.org/jira/browse/AMBARI-15554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15214632#comment-15214632 ] Sebastian Toader commented on AMBARI-15554: --- Committed to trunk: {code} commit

[jira] [Commented] (AMBARI-15489) Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating Kerberized cluster with Blueprints

[ https://issues.apache.org/jira/browse/AMBARI-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15205073#comment-15205073 ] Sebastian Toader commented on AMBARI-15489: --- Committed to branch-2.2: {code} commit

[jira] [Commented] (AMBARI-16013) Host_status stuck in UNKNOWN status after blueprint deploy with host in heartbeat-lost

[ https://issues.apache.org/jira/browse/AMBARI-16013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252589#comment-15252589 ] Sebastian Toader commented on AMBARI-16013: --- {code:title=branch-2.2.2} commit

[jira] [Commented] (AMBARI-16180) Backport AMBARI-15457 to 2.2-next

[ https://issues.apache.org/jira/browse/AMBARI-16180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263860#comment-15263860 ] Sebastian Toader commented on AMBARI-16180: --- +1 > Backport AMBARI-15457 to 2.2-next >

[jira] [Updated] (AMBARI-16119) User imported from AD is unable to login to Ambari.

[ https://issues.apache.org/jira/browse/AMBARI-16119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16119: -- Resolution: Fixed Status: Resolved (was: Patch Available) > User imported

[jira] [Commented] (AMBARI-16119) User imported from AD is unable to login to Ambari.

[ https://issues.apache.org/jira/browse/AMBARI-16119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259626#comment-15259626 ] Sebastian Toader commented on AMBARI-16119: --- Committed to trunk: {code} commit

[jira] [Created] (AMBARI-16119) User imported from AD is unable to login to Ambari.

Sebastian Toader created AMBARI-16119: - Summary: User imported from AD is unable to login to Ambari. Key: AMBARI-16119 URL: https://issues.apache.org/jira/browse/AMBARI-16119 Project: Ambari

[jira] [Updated] (AMBARI-16119) User imported from AD is unable to login to Ambari.

[ https://issues.apache.org/jira/browse/AMBARI-16119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16119: -- Description: Steps to reproduce: # Install ambari 2.4.0 # Setup ambari with AD server

[jira] [Updated] (AMBARI-16119) User imported from AD is unable to login to Ambari.

[ https://issues.apache.org/jira/browse/AMBARI-16119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16119: -- Attachment: AMBARI-16119.trunk.v1.patch > User imported from AD is unable to login to

[jira] [Updated] (AMBARI-16119) User imported from AD is unable to login to Ambari.

[ https://issues.apache.org/jira/browse/AMBARI-16119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16119: -- Status: Patch Available (was: Open) > User imported from AD is unable to login to

[jira] [Updated] (AMBARI-16119) User imported from AD is unable to login to Ambari.

[ https://issues.apache.org/jira/browse/AMBARI-16119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16119: -- Attachment: (was: AMBARI-16119.trunk.v2.patch) > User imported from AD is unable

[jira] [Updated] (AMBARI-16119) User imported from AD is unable to login to Ambari.

[ https://issues.apache.org/jira/browse/AMBARI-16119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16119: -- Attachment: AMBARI-16119.trunk.v3.patch > User imported from AD is unable to login to

[jira] [Updated] (AMBARI-16119) User imported from AD is unable to login to Ambari.

[ https://issues.apache.org/jira/browse/AMBARI-16119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16119: -- Attachment: (was: AMBARI-16119.trunk.v1.patch) > User imported from AD is unable

[jira] [Updated] (AMBARI-16119) User imported from AD is unable to login to Ambari.

[ https://issues.apache.org/jira/browse/AMBARI-16119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16119: -- Attachment: AMBARI-16119.trunk.v2.patch > User imported from AD is unable to login to

[jira] [Commented] (AMBARI-16820) Blueprint Export does not replace hive.llap.zk.sm.connectionString

[ https://issues.apache.org/jira/browse/AMBARI-16820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15298087#comment-15298087 ] Sebastian Toader commented on AMBARI-16820: --- Committed to trunk: {code} commit

[jira] [Comment Edited] (AMBARI-16820) Blueprint Export does not replace hive.llap.zk.sm.connectionString

[ https://issues.apache.org/jira/browse/AMBARI-16820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15298087#comment-15298087 ] Sebastian Toader edited comment on AMBARI-16820 at 5/24/16 12:24 PM: -

[jira] [Updated] (AMBARI-16820) Blueprint Export does not replace hive.llap.zk.sm.connectionString

[ https://issues.apache.org/jira/browse/AMBARI-16820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16820: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Blueprint Export

[jira] [Updated] (AMBARI-16630) Extend logging for ActionQueue's retry logic

[ https://issues.apache.org/jira/browse/AMBARI-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16630: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to

[jira] [Created] (AMBARI-16214) Ensure Blueprint deployment can start immediately - after Server start

Sebastian Toader created AMBARI-16214: - Summary: Ensure Blueprint deployment can start immediately - after Server start Key: AMBARI-16214 URL: https://issues.apache.org/jira/browse/AMBARI-16214

[jira] [Created] (AMBARI-16221) AMS/LogSearch service should be outside the cluster and shared across clusters

Sebastian Toader created AMBARI-16221: - Summary: AMS/LogSearch service should be outside the cluster and shared across clusters Key: AMBARI-16221 URL: https://issues.apache.org/jira/browse/AMBARI-16221

  1   2   3   4   >