[jira] [Updated] (AMBARI-24066) Metrics Collector issues modify HTable descriptor calls every time it restarts.

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-24066:

Labels: pull-request-available  (was: )

> Metrics Collector issues modify HTable descriptor calls every time it 
> restarts.
> ---
>
> Key: AMBARI-24066
> URL: https://issues.apache.org/jira/browse/AMBARI-24066
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.7.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>
> * Fix issues in AMS HBase tables policies initialization.
> * Cleanup downsampling code and config.
> * Add ability to blacklist metrics through a file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24059) Ambari Views auto create instance should support matching to all known stacks

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-24059:

Labels: pull-request-available  (was: )

> Ambari Views auto create instance should support matching to all known stacks
> -
>
> Key: AMBARI-24059
> URL: https://issues.apache.org/jira/browse/AMBARI-24059
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Nettleton
>Assignee: Robert Nettleton
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> The Ambari Views framework currently defines a set of configuration tags that 
> can be used to configure the auto-instance deployment of a view.  Currently, 
> this configuration allows for a matching stack to be explicitly configured, 
> or a wildcard ('*") can be used to allow more flexible matching against a set 
> of stack version numbers. 
> The current configuration already supports this type of matching: 
>  
> {code:java}
> 
> AUTO_INSTANCE
> View Name
> HDP-*
> :
> {code}
> This configuration needs to be more flexible in order to allow a given View 
> implementation to specify that it can match to any stack, including those 
> defined outside of the "HDP" stack name. 
> The Ambari Views Registry should be updated to allow for specifying a wilcard 
> character in order to instruct the Views framework to match against any 
> stack, regardless of whether the stack begins with the "HDP" stack name. 
> {code:java}
> 
> AUTO_INSTANCE
> View Name
> *
> :
> {code}
> This change should allow for greater flexibility for service and view 
> developers, in cases where a given service's view can be used by more than 
> one stack.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-24066) Metrics Collector issues modify HTable descriptor calls every time it restarts.

[Aravindan Vijayan (JIRA)]

Aravindan Vijayan created AMBARI-24066:
--

 Summary: Metrics Collector issues modify HTable descriptor calls 
every time it restarts.
 Key: AMBARI-24066
 URL: https://issues.apache.org/jira/browse/AMBARI-24066
 Project: Ambari
  Issue Type: Bug
  Components: ambari-metrics
Affects Versions: 2.7.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
 Fix For: 2.7.0


* Fix issues in AMS HBase tables policies initialization.
* Cleanup downsampling code and config.
* Add ability to blacklist metrics through a file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AMBARI-24040) Infra Solr start/stop should be idempotent

[JIRA]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivér Szabó resolved AMBARI-24040.
---
Resolution: Fixed

> Infra Solr start/stop should be idempotent
> --
>
> Key: AMBARI-24040
> URL: https://issues.apache.org/jira/browse/AMBARI-24040
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-infra, ambari-server
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24060) Sys-prepped Hosts do not Install and Finalize correctly

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-24060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506513#comment-16506513
 ] 

Hudson commented on AMBARI-24060:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9427 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9427/])
[AMBARI-24060] Sys-prepped Hosts do not Install and Finalize correctly (github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=19b8f1c27abe55aeaa007a240121deca49e37a48])
* (edit) 
ambari-server/src/test/python/custom_actions/test_stack_select_set_all.py
* (edit) 
ambari-server/src/main/resources/custom_actions/scripts/stack_select_set_all.py
* (edit) 
ambari-common/src/main/python/ambari_commons/repo_manager/apt_manager.py


> Sys-prepped Hosts do not Install and Finalize correctly
> ---
>
> Key: AMBARI-24060
> URL: https://issues.apache.org/jira/browse/AMBARI-24060
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> * Installation of packages using a host that is sys-prepped is choosing 
> package names in a non-deterministic way on ubuntu14/16
> * Finalization is failing when there are no packages installed on-system.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24065) Ranger Kms service smart config tab - KMS HSM not shown after upgraded to Ambari-2.7.0.0

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-24065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506512#comment-16506512
 ] 

Hudson commented on AMBARI-24065:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9427 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9427/])
[AMBARI-24065] Ranger Kms service smart config tab - KMS HSM not shown 
(ishanbhatt.1989: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c314c5b674e44a5a9b883c12f71edeb09f4f8085])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER_KMS/themes/theme_version_2.json


> Ranger Kms service smart config tab - KMS HSM not shown after upgraded to 
> Ambari-2.7.0.0
> 
>
> Key: AMBARI-24065
> URL: https://issues.apache.org/jira/browse/AMBARI-24065
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
>  Labels: pull-request-available
> Fix For: trunk
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23945) Infra Solr migration: use less params for migration steps (make it easier to use)

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-23945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506479#comment-16506479
 ] 

Hudson commented on AMBARI-23945:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9426 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9426/])
AMBARI-23945. Infra Solr migration - restored data can be deleted on (oleewere: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=5529b29b0ba8e20bac7a69ef541539cc9085e709])
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/collection.py
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/command_commons.py
* (edit) 
ambari-infra/ambari-infra-solr-client/src/main/python/migrationHelper.py
* (edit) ambari-infra/ambari-infra-solr-client/build.xml
* (edit) 
ambari-common/src/main/python/resource_management/libraries/functions/solr_cloud_util.py
* (add) ambari-infra/ambari-infra-solr-client/src/main/resources/data/.keep


> Infra Solr migration: use less params for migration steps (make it easier to 
> use)
> -
>
> Key: AMBARI-23945
> URL: https://issues.apache.org/jira/browse/AMBARI-23945
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-infra
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24065) Ranger Kms service smart config tab - KMS HSM not shown after upgraded to Ambari-2.7.0.0

[Ishan Bhatt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ishan Bhatt updated AMBARI-24065:
-
Component/s: (was: ambari-web)
 ambari-server

> Ranger Kms service smart config tab - KMS HSM not shown after upgraded to 
> Ambari-2.7.0.0
> 
>
> Key: AMBARI-24065
> URL: https://issues.apache.org/jira/browse/AMBARI-24065
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
>  Labels: pull-request-available
> Fix For: trunk
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AMBARI-24065) Ranger Kms service smart config tab - KMS HSM not shown after upgraded to Ambari-2.7.0.0

[Ishan Bhatt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ishan Bhatt resolved AMBARI-24065.
--
Resolution: Fixed

> Ranger Kms service smart config tab - KMS HSM not shown after upgraded to 
> Ambari-2.7.0.0
> 
>
> Key: AMBARI-24065
> URL: https://issues.apache.org/jira/browse/AMBARI-24065
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
>  Labels: pull-request-available
> Fix For: trunk
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24063) ZooKeeper Server Start fail during cluster deployment via api

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-24063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506434#comment-16506434
 ] 

Hudson commented on AMBARI-24063:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9425 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9425/])
AMBARI-24063. ZooKeeper Server Start fail during cluster deployment via 
(github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=58a676001e582201d0fa4648dd3d29106c80a879])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java


> ZooKeeper Server Start fail during cluster deployment via api
> -
>
> Key: AMBARI-24063
> URL: https://issues.apache.org/jira/browse/AMBARI-24063
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24065) Ranger Kms service smart config tab - KMS HSM not shown after upgraded to Ambari-2.7.0.0

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-24065:

Labels: pull-request-available  (was: )

> Ranger Kms service smart config tab - KMS HSM not shown after upgraded to 
> Ambari-2.7.0.0
> 
>
> Key: AMBARI-24065
> URL: https://issues.apache.org/jira/browse/AMBARI-24065
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
>  Labels: pull-request-available
> Fix For: trunk
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24064) Missing LdapFacade in HostUpdateHelper

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-24064:

Labels: pull-request-available  (was: )

> Missing LdapFacade in HostUpdateHelper
> --
>
> Key: AMBARI-24064
> URL: https://issues.apache.org/jira/browse/AMBARI-24064
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>
> The following error is encountered when executing executing
> {noformat}
> ambari-server update-host-names host_names_changes.json
> {noformat}
> {noformat}
> 2018-06-07 18:04:12,933 ERROR [main] HostUpdateHelper:573 - Unexpected error, 
> host names update failed
> com.google.inject.CreationException: Unable to create injector, see the 
> following errors:
> 1) No implementation for org.apache.ambari.server.ldap.service.LdapFacade was 
> bound.
>   while locating org.apache.ambari.server.ldap.service.LdapFacade
> for the 1st parameter of 
> org.apache.ambari.server.controller.internal.AmbariServerLDAPConfigurationHandler.(AmbariServerLDAPConfigurationHandler.java:53)
>   while locating 
> org.apache.ambari.server.controller.internal.AmbariServerLDAPConfigurationHandler
> for field at 
> org.apache.ambari.server.controller.internal.RootServiceComponentConfigurationHandlerFactory.ldapConfigurationHandler(RootServiceComponentConfigurationHandlerFactory.java:33)
>   while locating 
> org.apache.ambari.server.controller.internal.RootServiceComponentConfigurationHandlerFactory
> for field at 
> org.apache.ambari.server.controller.internal.RootServiceComponentConfigurationResourceProvider.rootServiceComponentConfigurationHandlerFactory(RootServiceComponentConfigurationResourceProvider.java:48)
>   at 
> org.apache.ambari.server.controller.ResourceProviderFactory.getRootServiceHostComponentConfigurationResourceProvider(ResourceProviderFactory.java:1)
>   at 
> com.google.inject.assistedinject.FactoryProvider2.initialize(FactoryProvider2.java:666)
>   at 
> com.google.inject.assistedinject.FactoryModuleBuilder$1.configure(FactoryModuleBuilder.java:335)
>  (via modules: 
> org.apache.ambari.server.update.HostUpdateHelper$UpdateHelperModule -> 
> com.google.inject.assistedinject.FactoryModuleBuilder$1)
> 1 error
> at 
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:470)
> at 
> com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:176)
> at 
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:110)
> at com.google.inject.Guice.createInjector(Guice.java:99)
> at com.google.inject.Guice.createInjector(Guice.java:73)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at 
> org.apache.ambari.server.update.HostUpdateHelper.main(HostUpdateHelper.java:544)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24065) Ranger Kms service smart config tab - KMS HSM not shown after upgraded to Ambari-2.7.0.0

[Ishan Bhatt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ishan Bhatt updated AMBARI-24065:
-
Description: (was: Cluster with Ambari - 2.6.2.0 + HDP 2.6.5.0-292
Upgrade to Ambari - 2.7.0.0
Under Ranger KMS Service > Configs > KMS HSM (Smart config tab is missing))

> Ranger Kms service smart config tab - KMS HSM not shown after upgraded to 
> Ambari-2.7.0.0
> 
>
> Key: AMBARI-24065
> URL: https://issues.apache.org/jira/browse/AMBARI-24065
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
> Fix For: trunk
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-24065) Ranger Kms service smart config tab - KMS HSM not shown after upgraded to Ambari-2.7.0.0

[Ishan Bhatt (JIRA)]

Ishan Bhatt created AMBARI-24065:


 Summary: Ranger Kms service smart config tab - KMS HSM not shown 
after upgraded to Ambari-2.7.0.0
 Key: AMBARI-24065
 URL: https://issues.apache.org/jira/browse/AMBARI-24065
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Reporter: Ishan Bhatt
Assignee: Ishan Bhatt
 Fix For: trunk


Cluster with Ambari - 2.6.2.0 + HDP 2.6.5.0-292
Upgrade to Ambari - 2.7.0.0
Under Ranger KMS Service > Configs > KMS HSM (Smart config tab is missing)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-24064) Missing LdapFacade in HostUpdateHelper

[Dmitry Lysnichenko (JIRA)]

Dmitry Lysnichenko created AMBARI-24064:
---

 Summary: Missing LdapFacade in HostUpdateHelper
 Key: AMBARI-24064
 URL: https://issues.apache.org/jira/browse/AMBARI-24064
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.7.0
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
 Fix For: 2.7.0


The following error is encountered when executing executing
{noformat}
ambari-server update-host-names host_names_changes.json
{noformat}

{noformat}
2018-06-07 18:04:12,933 ERROR [main] HostUpdateHelper:573 - Unexpected error, 
host names update failed
com.google.inject.CreationException: Unable to create injector, see the 
following errors:

1) No implementation for org.apache.ambari.server.ldap.service.LdapFacade was 
bound.
  while locating org.apache.ambari.server.ldap.service.LdapFacade
for the 1st parameter of 
org.apache.ambari.server.controller.internal.AmbariServerLDAPConfigurationHandler.(AmbariServerLDAPConfigurationHandler.java:53)
  while locating 
org.apache.ambari.server.controller.internal.AmbariServerLDAPConfigurationHandler
for field at 
org.apache.ambari.server.controller.internal.RootServiceComponentConfigurationHandlerFactory.ldapConfigurationHandler(RootServiceComponentConfigurationHandlerFactory.java:33)
  while locating 
org.apache.ambari.server.controller.internal.RootServiceComponentConfigurationHandlerFactory
for field at 
org.apache.ambari.server.controller.internal.RootServiceComponentConfigurationResourceProvider.rootServiceComponentConfigurationHandlerFactory(RootServiceComponentConfigurationResourceProvider.java:48)
  at 
org.apache.ambari.server.controller.ResourceProviderFactory.getRootServiceHostComponentConfigurationResourceProvider(ResourceProviderFactory.java:1)
  at 
com.google.inject.assistedinject.FactoryProvider2.initialize(FactoryProvider2.java:666)
  at 
com.google.inject.assistedinject.FactoryModuleBuilder$1.configure(FactoryModuleBuilder.java:335)
 (via modules: 
org.apache.ambari.server.update.HostUpdateHelper$UpdateHelperModule -> 
com.google.inject.assistedinject.FactoryModuleBuilder$1)

1 error
at 
com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:470)
at 
com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:176)
at 
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:110)
at com.google.inject.Guice.createInjector(Guice.java:99)
at com.google.inject.Guice.createInjector(Guice.java:73)
at com.google.inject.Guice.createInjector(Guice.java:62)
at 
org.apache.ambari.server.update.HostUpdateHelper.main(HostUpdateHelper.java:544)
{noformat}




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24063) ZooKeeper Server Start fail during cluster deployment via api

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-24063:

Labels: pull-request-available  (was: )

> ZooKeeper Server Start fail during cluster deployment via api
> -
>
> Key: AMBARI-24063
> URL: https://issues.apache.org/jira/browse/AMBARI-24063
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-24063) ZooKeeper Server Start fail during cluster deployment via api

[Attila Magyar (JIRA)]

Attila Magyar created AMBARI-24063:
--

 Summary: ZooKeeper Server Start fail during cluster deployment via 
api
 Key: AMBARI-24063
 URL: https://issues.apache.org/jira/browse/AMBARI-24063
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.7.0
Reporter: Attila Magyar
Assignee: Attila Magyar
 Fix For: 2.7.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24061) Clicking on 'Details' button in Upgrade wizard shows no data

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-24061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506244#comment-16506244
 ] 

Hudson commented on AMBARI-24061:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9424 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9424/])
AMBARI-24061. Clicking on 'Details' button in Upgrade wizard shows no 
(aleksandrkovalenko: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=39f60f8cc564fb2ae836839af8fa3e417f47e8c6])
* (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_task_view.js


> Clicking on 'Details' button in Upgrade wizard shows no data
> 
>
> Key: AMBARI-24061
> URL: https://issues.apache.org/jira/browse/AMBARI-24061
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When clicked on 'show details' button while Upgrade is in progress, it shows 
> a spinning icon and no data underneath.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24062) Command retry on server when agent-server connection drops

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-24062:

Labels: pull-request-available  (was: )

> Command retry on server when agent-server connection drops
> --
>
> Key: AMBARI-24062
> URL: https://issues.apache.org/jira/browse/AMBARI-24062
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>
> Server should try to re-send execution command message when agent does not 
> confirmed successful receiving.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AMBARI-24061) Clicking on 'Details' button in Upgrade wizard shows no data

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko resolved AMBARI-24061.
--
Resolution: Fixed

> Clicking on 'Details' button in Upgrade wizard shows no data
> 
>
> Key: AMBARI-24061
> URL: https://issues.apache.org/jira/browse/AMBARI-24061
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When clicked on 'show details' button while Upgrade is in progress, it shows 
> a spinning icon and no data underneath.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-24062) Command retry on server when agent-server connection drops

[Myroslav Papirkovskyi (JIRA)]

Myroslav Papirkovskyi created AMBARI-24062:
--

 Summary: Command retry on server when agent-server connection drops
 Key: AMBARI-24062
 URL: https://issues.apache.org/jira/browse/AMBARI-24062
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.7.0
Reporter: Myroslav Papirkovskyi
Assignee: Myroslav Papirkovskyi
 Fix For: 2.7.0


Server should try to re-send execution command message when agent does not 
confirmed successful receiving.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AMBARI-24053) Do not move service-specific configs to Misc section

[Jason Golieb (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Golieb resolved AMBARI-24053.
---
Resolution: Fixed

> Do not move service-specific configs to Misc section
> 
>
> Key: AMBARI-24053
> URL: https://issues.apache.org/jira/browse/AMBARI-24053
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Jason Golieb
>Assignee: Jason Golieb
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.0.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Previously, we would consolidate certain service-specific configs, 
> specifically user settings, onto the Misc tab in the UI. This made send when 
> there was only one instance of each service and we wanted to have all user 
> settings in one place. However, in the future we will have multiple instances 
> of services and user settings will need to be specific to each instance. 
> Therefore, we need to keep these user settings with their respective service 
> (instances).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24061) Clicking on 'Details' button in Upgrade wizard shows no data

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-24061:

Labels: pull-request-available  (was: )

> Clicking on 'Details' button in Upgrade wizard shows no data
> 
>
> Key: AMBARI-24061
> URL: https://issues.apache.org/jira/browse/AMBARI-24061
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>
> When clicked on 'show details' button while Upgrade is in progress, it shows 
> a spinning icon and no data underneath.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-24061) Clicking on 'Details' button in Upgrade wizard shows no data

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-24061:


 Summary: Clicking on 'Details' button in Upgrade wizard shows no 
data
 Key: AMBARI-24061
 URL: https://issues.apache.org/jira/browse/AMBARI-24061
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.7.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
 Fix For: 2.7.0


When clicked on 'show details' button while Upgrade is in progress, it shows a 
spinning icon and no data underneath.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23752) Hide SmartSense master components in HDF stack

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-23752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506094#comment-16506094
 ] 

Hudson commented on AMBARI-23752:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9423 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9423/])
AMBARI-23752 Hide SmartSense master components in HDF stack (1963907+atkach: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=f996c0670b8d4eabbe8d5cfdbd2a8fb8fc923a81])
* (edit) ambari-web/app/models/stack_service_component.js
* (edit) ambari-web/app/controllers/wizard/step8_controller.js
* (edit) ambari-web/app/controllers/installer.js


> Hide SmartSense master components in HDF stack
> --
>
> Key: AMBARI-23752
> URL: https://issues.apache.org/jira/browse/AMBARI-23752
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Our assumption is that ambari should be able to allow zero node deployment of 
> this master component. But unfortunately, UI does not have any provision to 
> remove master components (which has cardinality 0-3). This causes dependency 
> issues in HDF environment where the dependent component does not exists.
> For the Activity Analyzer and Activity Explorer. We don’t want those to show 
> up in assign masters for the HDF stack.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24060) Sys-prepped Hosts do not Install and Finalize correctly

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-24060:

Labels: pull-request-available  (was: )

> Sys-prepped Hosts do not Install and Finalize correctly
> ---
>
> Key: AMBARI-24060
> URL: https://issues.apache.org/jira/browse/AMBARI-24060
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>
> * Installation of packages using a host that is sys-prepped is choosing 
> package names in a non-deterministic way on ubuntu14/16
> * Finalization is failing when there are no packages installed on-system.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-24060) Sys-prepped Hosts do not Install and Finalize correctly

[Nate Cole (JIRA)]

Nate Cole created AMBARI-24060:
--

 Summary: Sys-prepped Hosts do not Install and Finalize correctly
 Key: AMBARI-24060
 URL: https://issues.apache.org/jira/browse/AMBARI-24060
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
 Fix For: 2.7.0


* Installation of packages using a host that is sys-prepped is choosing package 
names in a non-deterministic way on ubuntu14/16
* Finalization is failing when there are no packages installed on-system.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AMBARI-23752) Hide SmartSense master components in HDF stack

[Andrii Tkach (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-23752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrii Tkach resolved AMBARI-23752.
---
Resolution: Fixed

> Hide SmartSense master components in HDF stack
> --
>
> Key: AMBARI-23752
> URL: https://issues.apache.org/jira/browse/AMBARI-23752
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Our assumption is that ambari should be able to allow zero node deployment of 
> this master component. But unfortunately, UI does not have any provision to 
> remove master components (which has cardinality 0-3). This causes dependency 
> issues in HDF environment where the dependent component does not exists.
> For the Activity Analyzer and Activity Explorer. We don’t want those to show 
> up in assign masters for the HDF stack.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23752) Hide SmartSense master components in HDF stack

[Andrii Tkach (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-23752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506053#comment-16506053
 ] 

Andrii Tkach commented on AMBARI-23752:
---

committed to trunk

> Hide SmartSense master components in HDF stack
> --
>
> Key: AMBARI-23752
> URL: https://issues.apache.org/jira/browse/AMBARI-23752
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Our assumption is that ambari should be able to allow zero node deployment of 
> this master component. But unfortunately, UI does not have any provision to 
> remove master components (which has cardinality 0-3). This causes dependency 
> issues in HDF environment where the dependent component does not exists.
> For the Activity Analyzer and Activity Explorer. We don’t want those to show 
> up in assign masters for the HDF stack.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24056) Autostart is not working for TIMELINE_READER.

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-24056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506049#comment-16506049
 ] 

Hudson commented on AMBARI-24056:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9422 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9422/])
AMBARI-24056. Autostart is not working for TIMELINE_READER.  (aonishuk) 
(aonishuk: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=b794b9400db4e79fe8ae3a8ebc5fe0041674f0dc])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/agent/stomp/TopologyHolder.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/agent/stomp/dto/TopologyComponent.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
AMBARI-24056. Autostart is not working for TIMELINE_READER.  (aonishuk) 
(aonishuk: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=43a777a368bbddb29e15aa7650cced077b5a7fb4])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java


> Autostart is not working for TIMELINE_READER. 
> --
>
> Key: AMBARI-24056
> URL: https://issues.apache.org/jira/browse/AMBARI-24056
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-24056.patch
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Steps to reproduce:-  
> 1\. Enable Autostart for all components.  
> 2.restart one host which contain TIMELINE_READER component.  
> 3\. wait for 5-10 minute for autostart to take an effect
> verify from the logs  
> tail -f /var/log/ambari-agent/ambari-agent.log |grep -i RecoveryManager.py
> 
> 
> 
> INFO 2018-06-07 08:32:32,487 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:34,488 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:36,489 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:38,490 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:40,491 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:42,496 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:44,501 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:46,505 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:48,518 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:50,519 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:52,521 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:54,533 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:56,534 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:58,535 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:33:00,537 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:33:02,538 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> 
> repro cluster:-  
> repro job:-  EC2-Run-HDP/965535/>



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-24059) Ambari Views auto create instance should support matching to all known stacks

[Robert Nettleton (JIRA)]

Robert Nettleton created AMBARI-24059:
-

 Summary: Ambari Views auto create instance should support matching 
to all known stacks
 Key: AMBARI-24059
 URL: https://issues.apache.org/jira/browse/AMBARI-24059
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.6.0
Reporter: Robert Nettleton
Assignee: Robert Nettleton
 Fix For: 2.7.0


The Ambari Views framework currently defines a set of configuration tags that 
can be used to configure the auto-instance deployment of a view.  Currently, 
this configuration allows for a matching stack to be explicitly configured, or 
a wildcard ('*") can be used to allow more flexible matching against a set of 
stack version numbers. 

The current configuration already supports this type of matching: 

 
{code:java}

AUTO_INSTANCE
View Name
HDP-*
:
{code}
This configuration needs to be more flexible in order to allow a given View 
implementation to specify that it can match to any stack, including those 
defined outside of the "HDP" stack name. 

The Ambari Views Registry should be updated to allow for specifying a wilcard 
character in order to instruct the Views framework to match against any stack, 
regardless of whether the stack begins with the "HDP" stack name. 
{code:java}

AUTO_INSTANCE
View Name
*
:
{code}
This change should allow for greater flexibility for service and view 
developers, in cases where a given service's view can be used by more than one 
stack.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24058) Infra Solr: Add GC options properties

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-24058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505999#comment-16505999
 ] 

Hudson commented on AMBARI-24058:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9421 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9421/])
AMBARI-24058 - Infra Solr: Add GC options properties (#1493) (oleewere: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c48a231302495cbe55a29a0cc44ad53d1debe38b])
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/properties/infra-solr-env.sh.j2
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/configuration/infra-solr-env.xml
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/params.py


> Infra Solr: Add GC options properties
> -
>
> Key: AMBARI-24058
> URL: https://issues.apache.org/jira/browse/AMBARI-24058
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-infra
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24055) INFRA_SOLR START failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-24055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505958#comment-16505958
 ] 

Hudson commented on AMBARI-24055:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9420 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9420/])
AMBARI-24055 - INFRA_SOLR START failed (#1491) (oleewere: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=0d2c63bae2aa9baa7440046a3090205f5585095f])
* (edit) 
ambari-infra/ambari-infra-solr-client/src/main/java/org/apache/ambari/infra/solr/AmbariSolrCloudCLI.java


> INFRA_SOLR START failed
> ---
>
> Key: AMBARI-24055
> URL: https://issues.apache.org/jira/browse/AMBARI-24055
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-infra
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (AMBARI-23752) Hide SmartSense master components in HDF stack

[Andrii Tkach (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-23752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrii Tkach reopened AMBARI-23752:
---

We still see the problem in "Add Service" operation for SmartSense. 

> Hide SmartSense master components in HDF stack
> --
>
> Key: AMBARI-23752
> URL: https://issues.apache.org/jira/browse/AMBARI-23752
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Our assumption is that ambari should be able to allow zero node deployment of 
> this master component. But unfortunately, UI does not have any provision to 
> remove master components (which has cardinality 0-3). This causes dependency 
> issues in HDF environment where the dependent component does not exists.
> For the Activity Analyzer and Activity Explorer. We don’t want those to show 
> up in assign masters for the HDF stack.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24052) Add Kerberos-related configuration recommendations to the stack advisor

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-24052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505933#comment-16505933
 ] 

Hudson commented on AMBARI-24052:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9419 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9419/])
[AMBARI-24052] Add Kerberos-related configuration recommendations to the 
(github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=d27b4454544e98227219e1b7fc0a6c91d905f005])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorHelperTest.java
* (delete) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/commands/SingleSignOnConfigurationRecommendationCommand.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/commands/ConfigurationRecommendationCommand.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py
* (edit) ambari-server/src/main/resources/stacks/service_advisor.py
* (edit) ambari-server/src/main/resources/scripts/stack_advisor.py
* (edit) 
ambari-serviceadvisor/src/main/java/org/apache/ambari/serviceadvisor/ServiceAdvisorCommandType.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/commands/StackAdvisorCommandType.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorHelper.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/api/services/stackadvisor/commands/ConfigurationRecommendationCommandTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorRequestTypeTest.java
* (edit) ambari-server/src/main/resources/stacks/stack_advisor.py
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorRequest.java


> Add Kerberos-related configuration recommendations to the stack advisor
> ---
>
> Key: AMBARI-24052
> URL: https://issues.apache.org/jira/browse/AMBARI-24052
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
>  Labels: pull-request-available, stackadvisor
> Fix For: 2.7.0
>
>  Time Spent: 3h
>  Remaining Estimate: 0h
>
> Add Kerberos-related configuration recommendations to the stack advisor.
> * Add a new action, {{recommend-configurations-for-kerberos}}, to query 
> services for only Kerberos-related configuration changes



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24058) Infra Solr: Add GC options properties

[Krisztian Kasa (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krisztian Kasa updated AMBARI-24058:

Status: Patch Available  (was: In Progress)

> Infra Solr: Add GC options properties
> -
>
> Key: AMBARI-24058
> URL: https://issues.apache.org/jira/browse/AMBARI-24058
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-infra
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24058) Infra Solr: Add GC options properties

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-24058:

Labels: pull-request-available  (was: )

> Infra Solr: Add GC options properties
> -
>
> Key: AMBARI-24058
> URL: https://issues.apache.org/jira/browse/AMBARI-24058
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-infra
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-24058) Infra Solr: Add GC options properties

[Krisztian Kasa (JIRA)]

Krisztian Kasa created AMBARI-24058:
---

 Summary: Infra Solr: Add GC options properties
 Key: AMBARI-24058
 URL: https://issues.apache.org/jira/browse/AMBARI-24058
 Project: Ambari
  Issue Type: Bug
  Components: ambari-infra
Affects Versions: 2.7.0
Reporter: Krisztian Kasa
Assignee: Krisztian Kasa
 Fix For: 2.7.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24052) Add Kerberos-related configuration recommendations to the stack advisor

[Robert Levas (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Levas updated AMBARI-24052:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Add Kerberos-related configuration recommendations to the stack advisor
> ---
>
> Key: AMBARI-24052
> URL: https://issues.apache.org/jira/browse/AMBARI-24052
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
>  Labels: pull-request-available, stackadvisor
> Fix For: 2.7.0
>
>  Time Spent: 3h
>  Remaining Estimate: 0h
>
> Add Kerberos-related configuration recommendations to the stack advisor.
> * Add a new action, {{recommend-configurations-for-kerberos}}, to query 
> services for only Kerberos-related configuration changes



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24056) Autostart is not working for TIMELINE_READER.

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-24056:

Labels: pull-request-available  (was: )

> Autostart is not working for TIMELINE_READER. 
> --
>
> Key: AMBARI-24056
> URL: https://issues.apache.org/jira/browse/AMBARI-24056
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-24056.patch
>
>
> Steps to reproduce:-  
> 1\. Enable Autostart for all components.  
> 2.restart one host which contain TIMELINE_READER component.  
> 3\. wait for 5-10 minute for autostart to take an effect
> verify from the logs  
> tail -f /var/log/ambari-agent/ambari-agent.log |grep -i RecoveryManager.py
> 
> 
> 
> INFO 2018-06-07 08:32:32,487 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:34,488 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:36,489 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:38,490 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:40,491 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:42,496 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:44,501 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:46,505 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:48,518 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:50,519 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:52,521 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:54,533 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:56,534 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:58,535 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:33:00,537 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:33:02,538 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> 
> repro cluster:-  
> repro job:-  EC2-Run-HDP/965535/>



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-24057) Deploy button doesn't show in Review Page of Move Master Wizard

[Srikanth Janardhan (JIRA)]

Srikanth Janardhan created AMBARI-24057:
---

 Summary: Deploy button doesn't show in Review Page of Move Master 
Wizard
 Key: AMBARI-24057
 URL: https://issues.apache.org/jira/browse/AMBARI-24057
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
 Fix For: 2.7.0
 Attachments: Screen Shot 2018-06-08 at 2.42.37 PM.png

With ambari-2.7.0.0-657, noticed in the Review Page of Move Master Wizard for 
Hive Metastore is stuck and doesn't enable the Deploy button to proceed further.

Steps:
# Add Hive Metastore to a host
# Select Move action in the Host Details page for Hive Metastore
# Navigate the wizard till the Review Page

Screenshot:   !Screen Shot 2018-06-08 at 2.42.37 PM.png! 

Javascript errors: 
{code}
app.js:31203 Uncaught TypeError: Cannot read property 'tag' of undefined
at app.js:31203
at Array.forEach ()
at Class.getConfigUrlParams (app.js:31202)
at Class.onLoadConfigsTags (app.js:31187)
at Class.opt.success (app.js:183168)
at fire (vendor.js:1141)
at Object.fireWith [as resolveWith] (vendor.js:1252)
at done (vendor.js:8178)
at XMLHttpRequest.callback (vendor.js:8702)
{code}




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24056) Autostart is not working for TIMELINE_READER.

[Andrew Onischuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Onischuk updated AMBARI-24056:
-
Status: Patch Available  (was: Open)

> Autostart is not working for TIMELINE_READER. 
> --
>
> Key: AMBARI-24056
> URL: https://issues.apache.org/jira/browse/AMBARI-24056
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-24056.patch
>
>
> Steps to reproduce:-  
> 1\. Enable Autostart for all components.  
> 2.restart one host which contain TIMELINE_READER component.  
> 3\. wait for 5-10 minute for autostart to take an effect
> verify from the logs  
> tail -f /var/log/ambari-agent/ambari-agent.log |grep -i RecoveryManager.py
> 
> 
> 
> INFO 2018-06-07 08:32:32,487 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:34,488 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:36,489 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:38,490 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:40,491 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:42,496 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:44,501 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:46,505 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:48,518 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:50,519 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:52,521 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:54,533 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:56,534 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:58,535 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:33:00,537 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:33:02,538 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> 
> repro cluster:-  
> repro job:-  EC2-Run-HDP/965535/>



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-24056) Autostart is not working for TIMELINE_READER.

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-24056:


 Summary: Autostart is not working for TIMELINE_READER. 
 Key: AMBARI-24056
 URL: https://issues.apache.org/jira/browse/AMBARI-24056
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.7.0
 Attachments: AMBARI-24056.patch

Steps to reproduce:-  
1\. Enable Autostart for all components.  
2.restart one host which contain TIMELINE_READER component.  
3\. wait for 5-10 minute for autostart to take an effect

verify from the logs  
tail -f /var/log/ambari-agent/ambari-agent.log |grep -i RecoveryManager.py




INFO 2018-06-07 08:32:32,487 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:32:34,488 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:32:36,489 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:32:38,490 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:32:40,491 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:32:42,496 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:32:44,501 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:32:46,505 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:32:48,518 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:32:50,519 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:32:52,521 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:32:54,533 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:32:56,534 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:32:58,535 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:33:00,537 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.
INFO 2018-06-07 08:33:02,538 RecoveryManager.py:213 - TIMELINE_READER needs 
recovery, desired = STARTED, and current = INSTALLED.


repro cluster:-  
repro job:- 





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24056) Autostart is not working for TIMELINE_READER.

[Andrew Onischuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Onischuk updated AMBARI-24056:
-
Attachment: AMBARI-24056.patch

> Autostart is not working for TIMELINE_READER. 
> --
>
> Key: AMBARI-24056
> URL: https://issues.apache.org/jira/browse/AMBARI-24056
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-24056.patch
>
>
> Steps to reproduce:-  
> 1\. Enable Autostart for all components.  
> 2.restart one host which contain TIMELINE_READER component.  
> 3\. wait for 5-10 minute for autostart to take an effect
> verify from the logs  
> tail -f /var/log/ambari-agent/ambari-agent.log |grep -i RecoveryManager.py
> 
> 
> 
> INFO 2018-06-07 08:32:32,487 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:34,488 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:36,489 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:38,490 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:40,491 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:42,496 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:44,501 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:46,505 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:48,518 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:50,519 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:52,521 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:54,533 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:56,534 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:32:58,535 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:33:00,537 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> INFO 2018-06-07 08:33:02,538 RecoveryManager.py:213 - TIMELINE_READER 
> needs recovery, desired = STARTED, and current = INSTALLED.
> 
> repro cluster:-  
> repro job:-  EC2-Run-HDP/965535/>



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24055) INFRA_SOLR START failed

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-24055:

Labels: pull-request-available  (was: )

> INFRA_SOLR START failed
> ---
>
> Key: AMBARI-24055
> URL: https://issues.apache.org/jira/browse/AMBARI-24055
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-infra
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24055) INFRA_SOLR START failed

[Krisztian Kasa (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krisztian Kasa updated AMBARI-24055:

Status: Patch Available  (was: In Progress)

> INFRA_SOLR START failed
> ---
>
> Key: AMBARI-24055
> URL: https://issues.apache.org/jira/browse/AMBARI-24055
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-infra
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AMBARI-24048) Installation of knox fails on HDF only cluster

[Krisztian Kasa (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-24048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krisztian Kasa resolved AMBARI-24048.
-
Resolution: Fixed

> Installation of knox fails on HDF only cluster
> --
>
> Key: AMBARI-24048
> URL: https://issues.apache.org/jira/browse/AMBARI-24048
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 2.7.0
>
>
> Installation of knox fails on AMBARI-2.7.0.0-363 with HDF--3.2 only cluster 
> (no HDP on it).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-24055) INFRA_SOLR START failed

[Krisztian Kasa (JIRA)]

Krisztian Kasa created AMBARI-24055:
---

 Summary: INFRA_SOLR START failed
 Key: AMBARI-24055
 URL: https://issues.apache.org/jira/browse/AMBARI-24055
 Project: Ambari
  Issue Type: Bug
  Components: ambari-infra
Affects Versions: 2.7.0
Reporter: Krisztian Kasa
Assignee: Krisztian Kasa
 Fix For: 2.7.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)