[jira] [Updated] (AMBARI-19123) Update zeppelin configuration for ambari 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-19123: - Attachment: AMBARI-19123_branch-2.5-v6.patch replace tab with 4 spaces > Update zeppelin configuration for ambari 2.5 > > > Key: AMBARI-19123 > URL: https://issues.apache.org/jira/browse/AMBARI-19123 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-19123_branch-2.5-v1.patch, > AMBARI-19123_branch-2.5-v2.patch, AMBARI-19123_branch-2.5-v3.patch, > AMBARI-19123_branch-2.5-v4.patch, AMBARI-19123_branch-2.5-v5.patch, > AMBARI-19123_branch-2.5-v6.patch > > > Update zeppelin configuration for ambari 2.5, and add more configuration > template for shiro.ini -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19123) Update zeppelin configuration for ambari 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-19123: - Attachment: AMBARI-19123_branch-2.5-v5.patch > Update zeppelin configuration for ambari 2.5 > > > Key: AMBARI-19123 > URL: https://issues.apache.org/jira/browse/AMBARI-19123 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-19123_branch-2.5-v1.patch, > AMBARI-19123_branch-2.5-v2.patch, AMBARI-19123_branch-2.5-v3.patch, > AMBARI-19123_branch-2.5-v4.patch, AMBARI-19123_branch-2.5-v5.patch > > > Update zeppelin configuration for ambari 2.5, and add more configuration > template for shiro.ini -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19184) Remove HSI host name from UI
[ https://issues.apache.org/jira/browse/AMBARI-19184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15747196#comment-15747196 ] Jaimin Jetly commented on AMBARI-19184: --- +1 for the patch. BE changes look good to me and in accordance with FE changes being made at https://issues.apache.org/jira/browse/AMBARI-19190 > Remove HSI host name from UI > > > Key: AMBARI-19184 > URL: https://issues.apache.org/jira/browse/AMBARI-19184 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.5.0 > > Attachments: AMBARI-19184.patch, Screen Shot 2016-12-12 at 6.12.42 > PM.png > > > Given that we are supporting HSI HA, we need to remove "HiveServer2 > Interactive Host" from UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18868) Stage and Request status should be persisted in the database
[ https://issues.apache.org/jira/browse/AMBARI-18868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-18868: -- Attachment: AMBARI-18868.3.patch > Stage and Request status should be persisted in the database > > > Key: AMBARI-18868 > URL: https://issues.apache.org/jira/browse/AMBARI-18868 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-18868.2.patch, AMBARI-18868.3.patch, > AMBARI-18868.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19195) Add permission for Service Auto Start
[ https://issues.apache.org/jira/browse/AMBARI-19195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-19195: -- Description: Add permission to give a role the ability to set services to auto-start. This permission should be allowed at the cluster-level to toggle the feature for the cluster (Manage Service Auto Start Configuration) and at the service-level to toggle the feature for specific services (Manage Service Auto Start). However the service-level feature may not be available via all interfaces. The following roles should be able to toggle auto-start at the cluster level: * Ambari Administrator * Cluster Administrator * Cluster Operator The following roles should be able to toggle auto-start at the service level: * Ambari Administrator * Cluster Administrator * Cluster Operator * Service Administrator was: Add permission to give a role the ability to set services to auto-start. This permission should be allowed at the cluster-level to toggle the feature for the cluster (Manage Service Auto Start Configuration) and at the service-level to toggle the feature for specific services (Manage Service Auto Start). However the service-level feature may not be available via all interfaces. The following roles should be able to toggle auto-start at the cluster level: * Ambari Administrator * Cluster Administrator * Cluster Operator The following roles should be able to toggle auto-start at the service level: * Ambari Administrator * Cluster Administrator * Cluster Operator * Service Administrator * Service Operator > Add permission for Service Auto Start > - > > Key: AMBARI-19195 > URL: https://issues.apache.org/jira/browse/AMBARI-19195 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Robert Levas >Assignee: Robert Levas > Labels: rbac > Fix For: 2.5.0 > > > Add permission to give a role the ability to set services to auto-start. This > permission should be allowed at the cluster-level to toggle the feature for > the cluster (Manage Service Auto Start Configuration) and at the > service-level to toggle the feature for specific services (Manage Service > Auto Start). However the service-level feature may not be available via all > interfaces. > The following roles should be able to toggle auto-start at the cluster level: > * Ambari Administrator > * Cluster Administrator > * Cluster Operator > The following roles should be able to toggle auto-start at the service level: > * Ambari Administrator > * Cluster Administrator > * Cluster Operator > * Service Administrator -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19195) Add permission for Service Auto Start
[ https://issues.apache.org/jira/browse/AMBARI-19195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-19195: -- Description: Add permission to give a role the ability to set services to auto-start. This permission should be allowed at the cluster-level to toggle the feature for the cluster (Manage Service Auto Start Configuration) and at the service-level to toggle the feature for specific services (Manage Service Auto Start). However the service-level feature may not be available via all interfaces. The following roles should be able to toggle auto-start at the cluster level: * Ambari Administrator * Cluster Administrator * Cluster Operator The following roles should be able to toggle auto-start at the service level: * Ambari Administrator * Cluster Administrator * Cluster Operator * Service Administrator * Service Operator was: Add permission to give a role the ability to set services to auto-start. This permission should be allowed at the cluster-level to toggle the feature for the cluster and at the service-level to toggle the feature for specific services. However the service-level feature may not be available via all interfaces. The following roles should be able to toggle auto-start at the cluster level: * Ambari Administrator * Cluster Administrator * Cluster Operator The following roles should be able to toggle auto-start at the service level: * Ambari Administrator * Cluster Administrator * Cluster Operator * Service Administrator * Service Operator > Add permission for Service Auto Start > - > > Key: AMBARI-19195 > URL: https://issues.apache.org/jira/browse/AMBARI-19195 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Robert Levas >Assignee: Robert Levas > Labels: rbac > Fix For: 2.5.0 > > > Add permission to give a role the ability to set services to auto-start. This > permission should be allowed at the cluster-level to toggle the feature for > the cluster (Manage Service Auto Start Configuration) and at the > service-level to toggle the feature for specific services (Manage Service > Auto Start). However the service-level feature may not be available via all > interfaces. > The following roles should be able to toggle auto-start at the cluster level: > * Ambari Administrator > * Cluster Administrator > * Cluster Operator > The following roles should be able to toggle auto-start at the service level: > * Ambari Administrator > * Cluster Administrator > * Cluster Operator > * Service Administrator > * Service Operator -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19195) Add permission for Service Auto Start
Robert Levas created AMBARI-19195: - Summary: Add permission for Service Auto Start Key: AMBARI-19195 URL: https://issues.apache.org/jira/browse/AMBARI-19195 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.5.0 Reporter: Robert Levas Assignee: Robert Levas Fix For: 2.5.0 Add permission to give a role the ability to set services to auto-start. This permission should be allowed at the cluster-level to toggle the feature for the cluster and at the service-level to toggle the feature for specific services. However the service-level feature may not be available via all interfaces. The following roles should be able to toggle auto-start at the cluster level: * Ambari Administrator * Cluster Administrator * Cluster Operator The following roles should be able to toggle auto-start at the service level: * Ambari Administrator * Cluster Administrator * Cluster Operator * Service Administrator * Service Operator -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19170) NPE during Ambari server schema upgrade
[
https://issues.apache.org/jira/browse/AMBARI-19170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746523#comment-15746523
]
Doroszlai, Attila commented on AMBARI-19170:
Thanks!
> NPE during Ambari server schema upgrade
> ---
>
> Key: AMBARI-19170
> URL: https://issues.apache.org/jira/browse/AMBARI-19170
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19170_branch-2.5.patch, AMBARI-19170_trunk.patch
>
>
> Ambari server upgrade path: 2.2.2.0 to 2.5.0.0-453
> Error seen while running 'ambari-server upgrade' command"
> {code}
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> WARNING: Original file krb5JAASLogin.conf kept
> INFO: File krb5JAASLogin.conf updated.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for Oracle. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/jdk64/jdk1.7.0_67/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/ojdbc6.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:209)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> Caused by: java.lang.NullPointerException
> at
> com.google.inject.persist.jpa.JpaPersistService.begin(JpaPersistService.java:70)
> at
> com.google.inject.persist.jpa.AmbariJpaPersistService.begin(AmbariJpaPersistService.java:29)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:106)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:206)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19193) Add common log rotation settings to YARN Configs
[ https://issues.apache.org/jira/browse/AMBARI-19193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-19193: --- Attachment: AMBARI-19193.patch > Add common log rotation settings to YARN Configs > > > Key: AMBARI-19193 > URL: https://issues.apache.org/jira/browse/AMBARI-19193 > Project: Ambari > Issue Type: Task >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19193.patch > > > Add common log rotation settings to YARN. > log4j.appender.RMSUMMARY.MaxFileSize > log4j.appender.RMSUMMARY.MaxBackupIndex -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19193) Add common log rotation settings to YARN Configs
[ https://issues.apache.org/jira/browse/AMBARI-19193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-19193: --- Status: Patch Available (was: Open) > Add common log rotation settings to YARN Configs > > > Key: AMBARI-19193 > URL: https://issues.apache.org/jira/browse/AMBARI-19193 > Project: Ambari > Issue Type: Task >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19193.patch > > > Add common log rotation settings to YARN. > log4j.appender.RMSUMMARY.MaxFileSize > log4j.appender.RMSUMMARY.MaxBackupIndex -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
[ https://issues.apache.org/jira/browse/AMBARI-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19156: --- Status: Patch Available (was: In Progress) > Install Packages fails with the old stack has services removed in the new > stack > --- > > Key: AMBARI-19156 > URL: https://issues.apache.org/jira/browse/AMBARI-19156 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19156-v2.patch, AMBARI-19156-v3.patch, > AMBARI-19156.patch > > > Install packages step (before RU/EU) fails with err "Cannot enumerate > services" if the current stack has services that have been removed in the new > stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2, > where Spark's metainfo.xml in mystack-2.0 has the true > section. > Workaround is to remove Spark before attempting the install packages. > The error is below: > 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27] > BaseManagementHandler:61 - Caught a system exception while attempting to > create a resource: Cannot enumerate services > org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate > services > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606) > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508) > at > org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298) > at > org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97) > at > org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37) > at > org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
[ https://issues.apache.org/jira/browse/AMBARI-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19156: --- Attachment: AMBARI-19156-v3.patch > Install Packages fails with the old stack has services removed in the new > stack > --- > > Key: AMBARI-19156 > URL: https://issues.apache.org/jira/browse/AMBARI-19156 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19156-v2.patch, AMBARI-19156-v3.patch, > AMBARI-19156.patch > > > Install packages step (before RU/EU) fails with err "Cannot enumerate > services" if the current stack has services that have been removed in the new > stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2, > where Spark's metainfo.xml in mystack-2.0 has the true > section. > Workaround is to remove Spark before attempting the install packages. > The error is below: > 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27] > BaseManagementHandler:61 - Caught a system exception while attempting to > create a resource: Cannot enumerate services > org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate > services > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606) > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508) > at > org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298) > at > org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97) > at > org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37) > at > org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
[ https://issues.apache.org/jira/browse/AMBARI-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19156: --- Status: In Progress (was: Patch Available) > Install Packages fails with the old stack has services removed in the new > stack > --- > > Key: AMBARI-19156 > URL: https://issues.apache.org/jira/browse/AMBARI-19156 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19156-v2.patch, AMBARI-19156.patch > > > Install packages step (before RU/EU) fails with err "Cannot enumerate > services" if the current stack has services that have been removed in the new > stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2, > where Spark's metainfo.xml in mystack-2.0 has the true > section. > Workaround is to remove Spark before attempting the install packages. > The error is below: > 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27] > BaseManagementHandler:61 - Caught a system exception while attempting to > create a resource: Cannot enumerate services > org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate > services > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606) > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508) > at > org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298) > at > org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97) > at > org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37) > at > org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17999) Typo in property name "yarn.nodemanager.log.retain-second", should be "seconds"
[ https://issues.apache.org/jira/browse/AMBARI-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746465#comment-15746465 ] Hudson commented on AMBARI-17999: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #522 (See [https://builds.apache.org/job/Ambari-branch-2.5/522/]) AMBARI-17999 Typo in property name yarn.nodemanager.log.retain-second, (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fb86ef73906f33ffc1d488b97eff127409c256c3]) * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/default_oozie_mysql.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/ha_bootstrap_standby_node_initial_start.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/ha_bootstrap_standby_node_initial_start_dfs_nameservices.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/default_client.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/ha_secured.json * (edit) ambari-server/src/test/resources/deploy_HDP2.sh * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/default_hive_non_hdfs.json * (edit) ambari-server/src/test/python/stacks/2.1/configs/default.json * (edit) ambari-server/src/test/python/stacks/2.2/configs/pig-service-check-secure.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/default_update_exclude_file_only.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/secured_client.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6.GlusterFS/services/YARN/configuration/yarn-site.xml * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/ha_default.json * (edit) ambari-server/src/test/python/stacks/2.1/configs/client-upgrade.json * (edit) ambari-server/src/test/python/stacks/2.3/configs/default.hbasedecom.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/hbase-2.2.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/hbase-check-2.2.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/secured.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/rebalancehdfs_secured.json * (edit) ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-site.xml * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/default_ams_embedded.json * (edit) ambari-server/src/test/python/stacks/2.2/configs/journalnode-upgrade.json * (edit) ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/yarn-site.xml * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/secured_no_jce_name.json * (edit) ambari-server/src/test/python/stacks/2.2/configs/journalnode-upgrade-hdfs-secure.json * (edit) ambari-server/src/test/python/stacks/2.2/configs/ranger-admin-upgrade.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/default.non_gmetad_host.json * (edit) ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/configuration/yarn-site.xml * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/flume_target.json * (edit) ambari-server/src/test/python/stacks/2.1/configs/secured.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/ha_bootstrap_standby_node.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/oozie_existing_sqla.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/ha_bootstrap_active_node.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/YARN/configuration/yarn-site.xml * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/altfs_plus_hdfs.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/client-upgrade.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/default.hbasedecom.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/hbase-rs-2.2-phoenix.json * (edit) ambari-server/src/test/python/stacks/2.3/common/services-sparkts-hive.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/default_with_bucket.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/hbase-rs-2.2.json * (edit) ambari-server/src/test/python/stacks/2.2/configs/ranger-usersync-upgrade.json * (edit) ambari-server/src/test/python/stacks/2.5/configs/hsi_default.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/rebalancehdfs_default.json * (edit) ambari-server/src/test/python/stacks/2.3/configs/ats_1_5.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/default.json * (edit) ambari-server/src/test/resources/stacks/HDP/2.0.5/services/YARN/configuration/yarn-site.xml * (edit) ambari-server/src/test/python/stacks/2.3/common/services-sparkts.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/flume_22.json * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/default_no_install.json * (edit) ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_1.3_to_2.2.json > Typo in property name "yarn.nodemanager.log.r
[jira] [Commented] (AMBARI-19178) HostCleanup can't list process details on RHEL7
[ https://issues.apache.org/jira/browse/AMBARI-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746418#comment-15746418 ] Hudson commented on AMBARI-19178: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6224 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6224/]) AMBARI-19178 HostCleanup can't list process details on RHEL7 (dili) (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2fee4286b69153b6f7727bc96bfe13764bebaadc]) * (edit) ambari-agent/src/main/python/ambari_agent/HostCleanup.py > HostCleanup can't list process details on RHEL7 > --- > > Key: AMBARI-19178 > URL: https://issues.apache.org/jira/browse/AMBARI-19178 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19178.patch > > > need to use ps auxww instead of just ps aux -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19194) Deployed Views Throw Exceptions On Ambari Server Startup
Jonathan Hurley created AMBARI-19194:
Summary: Deployed Views Throw Exceptions On Ambari Server Startup
Key: AMBARI-19194
URL: https://issues.apache.org/jira/browse/AMBARI-19194
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.5.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.5.0
- Install an HDP 2.5 cluster with HDFS, YARN, MapR, and ZK
-- Relevant views, like Capacity Scheduler, should be instantiated at this point
- Restart Ambari Server
{noformat}
12 Dec 2016 02:37:47,067 INFO [main] ViewRegistry:1796 - setting up logging
for view CAPACITY-SCHEDULER{1.0.0} as per property file view.log4j.properties
12 Dec 2016 02:37:47,112 INFO [main] ViewRegistry:1860 - Auto creating
instance of view CAPACITY-SCHEDULER for cluster cl1.
12 Dec 2016 02:37:47,165 ERROR [main] AmbariJpaLocalTxnInterceptor:180 -
[DETAILED ERROR] Rollback reason:
12 Dec 2016 02:37:47,166 ERROR [main] AmbariJpaLocalTxnInterceptor:188 -
[DETAILED ERROR] Internal exception (1) :
12 Dec 2016 02:37:47,167 ERROR [main] ViewRegistry:1867 - Can't auto create
instance of view CAPACITY-SCHEDULER for cluster cl1. Caught exception
:Exception [EclipseLink-4002] (Eclipse Persistence Services -
2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
12 Dec 2016 02:37:47,168 INFO [main] ViewRegistry:1738 - View deployed:
CAPACITY-SCHEDULER{1.0.0}.
12 Dec 2016 02:37:47,176 INFO [main] ViewRegistry:1705 - Reading view archive
/var/lib/ambari-server/resources/views/files-2.5.0.0.453.jar.
12 Dec 2016 02:37:47,227 INFO [main] ViewRegistry:1796 - setting up logging
for view FILES{1.0.0} as per property file view.log4j.properties
12 Dec 2016 02:37:47,277 INFO [main] ViewRegistry:1860 - Auto creating
instance of view FILES for cluster cl1.
12 Dec 2016 02:37:47,285 ERROR [main] AmbariJpaLocalTxnInterceptor:180 -
[DETAILED ERROR] Rollback reason:
12 Dec 2016 02:37:47,286 ERROR [main] AmbariJpaLocalTxnInterceptor:188 -
[DETAILED ERROR] Internal exception (1) :
12 Dec 2016 02:37:47,287 ERROR [main] ViewRegistry:1867 - Can't auto create
instance of view FILES for cluster cl1. Caught exception :Exception
[EclipseLink-4002] (Eclipse Persistence Services - 2.6.2.v20151217-774c696):
org.eclipse.persistence.exceptions.DatabaseException
{noformat}
and
{noformat}
12 Dec 2016 17:49:57,423 ERROR [main] AmbariJpaLocalTxnInterceptor:180 -
[DETAILED ERROR] Rollback reason:
Local Exception Stack:
Exception [EclipseLink-4002] (Eclipse Persistence Services -
2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception:
com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
Column 'resource_id' cannot be null
Error Code: 1048
{noformat}
This seems to be due to how view syncing works with in-memory (not persisted)
entities. Because the {{ViewInstanceEntity}} is constructed in memory (and not
retrieve from the DB), it's incomplete and cannot be used for things like
retrieving associated entities from.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19193) Add common log rotation settings to YARN Configs
[ https://issues.apache.org/jira/browse/AMBARI-19193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19193: --- Fix Version/s: 2.5.0 > Add common log rotation settings to YARN Configs > > > Key: AMBARI-19193 > URL: https://issues.apache.org/jira/browse/AMBARI-19193 > Project: Ambari > Issue Type: Bug >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > > Add common log rotation settings to YARN. > log4j.appender.RMSUMMARY.MaxFileSize > log4j.appender.RMSUMMARY.MaxBackupIndex -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19193) Add common log rotation settings to YARN Configs
[ https://issues.apache.org/jira/browse/AMBARI-19193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19193: --- Issue Type: Task (was: Bug) > Add common log rotation settings to YARN Configs > > > Key: AMBARI-19193 > URL: https://issues.apache.org/jira/browse/AMBARI-19193 > Project: Ambari > Issue Type: Task >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > > Add common log rotation settings to YARN. > log4j.appender.RMSUMMARY.MaxFileSize > log4j.appender.RMSUMMARY.MaxBackupIndex -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-19193) Add common log rotation settings to YARN Configs
[ https://issues.apache.org/jira/browse/AMBARI-19193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan reassigned AMBARI-19193: -- Assignee: Madhuvanthi Radhakrishnan > Add common log rotation settings to YARN Configs > > > Key: AMBARI-19193 > URL: https://issues.apache.org/jira/browse/AMBARI-19193 > Project: Ambari > Issue Type: Bug >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > > Add common log rotation settings to YARN. > log4j.appender.RMSUMMARY.MaxFileSize > log4j.appender.RMSUMMARY.MaxBackupIndex -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[
https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746411#comment-15746411
]
Hadoop QA commented on AMBARI-19190:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843057/AMBARI-19190.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9652//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9652//console
This message is automatically generated.
> Remove UI logic to set or expect hive_server_interactive_host
> -
>
> Key: AMBARI-19190
> URL: https://issues.apache.org/jira/browse/AMBARI-19190
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch
>
>
> With the support for HSI HA, the property no longer seems appropriate. Lets
> remove the dependency on this property and no longer expect or use it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Moved] (AMBARI-19193) Add common log rotation settings to YARN Configs
[ https://issues.apache.org/jira/browse/AMBARI-19193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj Das moved HDFS-11241 to AMBARI-19193: - Key: AMBARI-19193 (was: HDFS-11241) Project: Ambari (was: Hadoop HDFS) > Add common log rotation settings to YARN Configs > > > Key: AMBARI-19193 > URL: https://issues.apache.org/jira/browse/AMBARI-19193 > Project: Ambari > Issue Type: Bug >Reporter: Madhuvanthi Radhakrishnan > > Add common log rotation settings to YARN. > log4j.appender.RMSUMMARY.MaxFileSize > log4j.appender.RMSUMMARY.MaxBackupIndex -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19191) Metrics Collector Move Wizard should no longer Restart All Services
[ https://issues.apache.org/jira/browse/AMBARI-19191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746376#comment-15746376 ] Hudson commented on AMBARI-19191: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #521 (See [https://builds.apache.org/job/Ambari-branch-2.5/521/]) AMBARI-19191. Metrics Collector Move Wizard should no longer Restart All (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=78ffc3f7486f7d510d6cf101abb09eed2cd21889]) * (edit) ambari-web/app/controllers/main/service/reassign/step4_controller.js > Metrics Collector Move Wizard should no longer Restart All Services > --- > > Key: AMBARI-19191 > URL: https://issues.apache.org/jira/browse/AMBARI-19191 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19191.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19170) NPE during Ambari server schema upgrade
[
https://issues.apache.org/jira/browse/AMBARI-19170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746378#comment-15746378
]
Hudson commented on AMBARI-19170:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #521 (See
[https://builds.apache.org/job/Ambari-branch-2.5/521/])
AMBARI-19170 - NPE during Ambari server schema upgrade (Attila Doroszlai
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=928c978ee0eac4ed479cd3594b6c68306c79045f])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
> NPE during Ambari server schema upgrade
> ---
>
> Key: AMBARI-19170
> URL: https://issues.apache.org/jira/browse/AMBARI-19170
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19170_branch-2.5.patch, AMBARI-19170_trunk.patch
>
>
> Ambari server upgrade path: 2.2.2.0 to 2.5.0.0-453
> Error seen while running 'ambari-server upgrade' command"
> {code}
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> WARNING: Original file krb5JAASLogin.conf kept
> INFO: File krb5JAASLogin.conf updated.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for Oracle. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/jdk64/jdk1.7.0_67/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/ojdbc6.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:209)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> Caused by: java.lang.NullPointerException
> at
> com.google.inject.persist.jpa.JpaPersistService.begin(JpaPersistService.java:70)
> at
> com.google.inject.persist.jpa.AmbariJpaPersistService.begin(AmbariJpaPersistService.java:29)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:106)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:206)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19147) LogSearch - generate default jks file on startup
[
https://issues.apache.org/jira/browse/AMBARI-19147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746372#comment-15746372
]
Hudson commented on AMBARI-19147:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #521 (See
[https://builds.apache.org/job/Ambari-branch-2.5/521/])
AMBARI-19147. LogSearch - generate default jks file on startup (oleewere:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=66b1f381478ecf8936ac3019497499194a6a5321])
* (edit)
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/util/SSLUtil.java
* (edit) ambari-logsearch/ambari-logsearch-portal/src/main/resources/log4j.xml
* (edit)
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-env.xml
* (edit)
ambari-logsearch/ambari-logsearch-portal/src/main/resources/default.properties
* (edit)
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/LogSearch.java
* (edit) ambari-logsearch/ambari-logsearch-portal/pom.xml
* (edit)
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/common/PropertiesHelper.java
> LogSearch - generate default jks file on startup
>
>
> Key: AMBARI-19147
> URL: https://issues.apache.org/jira/browse/AMBARI-19147
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19147.patch
>
>
> Generate JKS file on startup if keystore/truststore is not configured.
> Also add 2 new properties (with defaults):
> {{logsearch.cert.folder.location=/etc/ambari-logsearch-portal/conf/keys}}
> {{logsearch.cert.algorithm=sha256WithRSAEncryption}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
[
https://issues.apache.org/jira/browse/AMBARI-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746343#comment-15746343
]
Hadoop QA commented on AMBARI-19156:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843075/AMBARI-19156-v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 7 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.AmbariManagementControllerTest
org.apache.ambari.server.stack.StackManagerExtensionTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9651//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9651//console
This message is automatically generated.
> Install Packages fails with the old stack has services removed in the new
> stack
> ---
>
> Key: AMBARI-19156
> URL: https://issues.apache.org/jira/browse/AMBARI-19156
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-19156-v2.patch, AMBARI-19156.patch
>
>
> Install packages step (before RU/EU) fails with err "Cannot enumerate
> services" if the current stack has services that have been removed in the new
> stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2,
> where Spark's metainfo.xml in mystack-2.0 has the true
> section.
> Workaround is to remove Spark before attempting the install packages.
> The error is below:
> 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27]
> BaseManagementHandler:61 - Caught a system exception while attempting to
> create a resource: Cannot enumerate services
> org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate
> services
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.
[jira] [Updated] (AMBARI-19178) HostCleanup can't list process details on RHEL7
[ https://issues.apache.org/jira/browse/AMBARI-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19178: --- Resolution: Fixed Status: Resolved (was: Patch Available) > HostCleanup can't list process details on RHEL7 > --- > > Key: AMBARI-19178 > URL: https://issues.apache.org/jira/browse/AMBARI-19178 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19178.patch > > > need to use ps auxww instead of just ps aux -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19178) HostCleanup can't list process details on RHEL7
[ https://issues.apache.org/jira/browse/AMBARI-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19178: --- Affects Version/s: (was: 2.5.0) > HostCleanup can't list process details on RHEL7 > --- > > Key: AMBARI-19178 > URL: https://issues.apache.org/jira/browse/AMBARI-19178 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19178.patch > > > need to use ps auxww instead of just ps aux -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19178) HostCleanup can't list process details on RHEL7
[ https://issues.apache.org/jira/browse/AMBARI-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746329#comment-15746329 ] Di Li commented on AMBARI-19178: AMBARI-19178 Pushed to Trunk as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=2fee4286b69153b6f7727bc96bfe13764bebaadc > HostCleanup can't list process details on RHEL7 > --- > > Key: AMBARI-19178 > URL: https://issues.apache.org/jira/browse/AMBARI-19178 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19178.patch > > > need to use ps auxww instead of just ps aux -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19140) Ambari Server symbolic links has double // when root dir is just /
[ https://issues.apache.org/jira/browse/AMBARI-19140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746300#comment-15746300 ] Hudson commented on AMBARI-19140: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #520 (See [https://builds.apache.org/job/Ambari-branch-2.5/520/]) AMBARI-19140 Ambari Server symbolic links has double // when root dir is (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bb920043077e67a7840fd264d2df306c6213f1e4]) * (edit) ambari-server/src/main/package/rpm/posttrans_server.sh * (edit) ambari-server/conf/unix/install-helper.sh * (edit) ambari-server/src/main/package/rpm/preinstall.sh > Ambari Server symbolic links has double // when root dir is just / > -- > > Key: AMBARI-19140 > URL: https://issues.apache.org/jira/browse/AMBARI-19140 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19140.patch > > > Notice the "//" in the symbolic link , where it could have been trimmed to be > just one leading "/" > [root]# ll /usr/sbin/ambari-server > lrwxrwxrwx 1 root root 26 Dec 5 11:27 /usr/sbin/ambari-server -> > //etc/init.d/ambari-server > [root]# clear > [root]# ll > total 20 > drwxrwxr-x 4 root root 8192 Dec 5 11:32 ambari_agent > lrwxrwxrwx 1 root root 42 Dec 5 11:27 ambari_commons -> > //usr/lib/ambari-server/lib/ambari_commons > lrwxrwxrwx 1 root root 41 Dec 5 11:27 ambari_jinja2 -> > //usr/lib/ambari-server/lib/ambari_jinja2 > drwxrwxr-x 2 root root 4096 Dec 5 11:28 ambari_server > lrwxrwxrwx 1 root root 45 Dec 5 11:27 ambari_simplejson -> > //usr/lib/ambari-server/lib/ambari_simplejson > lrwxrwxrwx 1 root root 47 Dec 5 11:27 resource_management -> > //usr/lib/ambari-server/lib/resource_management > drwxr-xr-x 5 ams hadoop 83 Dec 6 09:26 resource_monitoring -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19166) Handle Druid requirement for mysql in standard fashion as it is handled in services
[
https://issues.apache.org/jira/browse/AMBARI-19166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746255#comment-15746255
]
Hadoop QA commented on AMBARI-19166:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843078/ambari-19166.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9650//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9650//console
This message is automatically generated.
> Handle Druid requirement for mysql in standard fashion as it is handled in
> services
> ---
>
> Key: AMBARI-19166
> URL: https://issues.apache.org/jira/browse/AMBARI-19166
> Project: Ambari
> Issue Type: Task
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: 2.5.0
>
> Attachments: ambari-19166.patch
>
>
> Druid's requirement of mysql connector is not implemented in the standard
> fashion. Refer how oozie handles this requirement and implement it that way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19166) Handle Druid requirement for mysql in standard fashion as it is handled in services
[ https://issues.apache.org/jira/browse/AMBARI-19166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-19166: -- Status: Patch Available (was: Open) > Handle Druid requirement for mysql in standard fashion as it is handled in > services > --- > > Key: AMBARI-19166 > URL: https://issues.apache.org/jira/browse/AMBARI-19166 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: 2.5.0 > > Attachments: ambari-19166.patch > > > Druid's requirement of mysql connector is not implemented in the standard > fashion. Refer how oozie handles this requirement and implement it that way. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19166) Handle Druid requirement for mysql in standard fashion as it is handled in services
[ https://issues.apache.org/jira/browse/AMBARI-19166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-19166: -- Attachment: ambari-19166.patch > Handle Druid requirement for mysql in standard fashion as it is handled in > services > --- > > Key: AMBARI-19166 > URL: https://issues.apache.org/jira/browse/AMBARI-19166 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: 2.5.0 > > Attachments: ambari-19166.patch > > > Druid's requirement of mysql connector is not implemented in the standard > fashion. Refer how oozie handles this requirement and implement it that way. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19147) LogSearch - generate default jks file on startup
[
https://issues.apache.org/jira/browse/AMBARI-19147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746160#comment-15746160
]
Hudson commented on AMBARI-19147:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6223 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6223/])
AMBARI-19147. LogSearch - generate default jks file on startup (oleewere:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=176a1c6ba4187c24d7203a69c5ab257e778956a4])
* (edit) ambari-logsearch/ambari-logsearch-portal/pom.xml
* (edit) ambari-logsearch/ambari-logsearch-portal/src/main/resources/log4j.xml
* (edit)
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-env.xml
* (edit)
ambari-logsearch/ambari-logsearch-portal/src/main/resources/default.properties
* (edit)
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/LogSearch.java
* (edit)
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/util/SSLUtil.java
* (edit)
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/common/PropertiesHelper.java
> LogSearch - generate default jks file on startup
>
>
> Key: AMBARI-19147
> URL: https://issues.apache.org/jira/browse/AMBARI-19147
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19147.patch
>
>
> Generate JKS file on startup if keystore/truststore is not configured.
> Also add 2 new properties (with defaults):
> {{logsearch.cert.folder.location=/etc/ambari-logsearch-portal/conf/keys}}
> {{logsearch.cert.algorithm=sha256WithRSAEncryption}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
[ https://issues.apache.org/jira/browse/AMBARI-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19156: --- Status: Patch Available (was: In Progress) > Install Packages fails with the old stack has services removed in the new > stack > --- > > Key: AMBARI-19156 > URL: https://issues.apache.org/jira/browse/AMBARI-19156 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19156-v2.patch, AMBARI-19156.patch > > > Install packages step (before RU/EU) fails with err "Cannot enumerate > services" if the current stack has services that have been removed in the new > stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2, > where Spark's metainfo.xml in mystack-2.0 has the true > section. > Workaround is to remove Spark before attempting the install packages. > The error is below: > 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27] > BaseManagementHandler:61 - Caught a system exception while attempting to > create a resource: Cannot enumerate services > org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate > services > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606) > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508) > at > org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298) > at > org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97) > at > org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37) > at > org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
[ https://issues.apache.org/jira/browse/AMBARI-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19156: --- Status: In Progress (was: Patch Available) > Install Packages fails with the old stack has services removed in the new > stack > --- > > Key: AMBARI-19156 > URL: https://issues.apache.org/jira/browse/AMBARI-19156 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19156-v2.patch, AMBARI-19156.patch > > > Install packages step (before RU/EU) fails with err "Cannot enumerate > services" if the current stack has services that have been removed in the new > stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2, > where Spark's metainfo.xml in mystack-2.0 has the true > section. > Workaround is to remove Spark before attempting the install packages. > The error is below: > 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27] > BaseManagementHandler:61 - Caught a system exception while attempting to > create a resource: Cannot enumerate services > org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate > services > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606) > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508) > at > org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298) > at > org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97) > at > org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37) > at > org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
[ https://issues.apache.org/jira/browse/AMBARI-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19156: --- Attachment: AMBARI-19156-v2.patch > Install Packages fails with the old stack has services removed in the new > stack > --- > > Key: AMBARI-19156 > URL: https://issues.apache.org/jira/browse/AMBARI-19156 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19156-v2.patch, AMBARI-19156.patch > > > Install packages step (before RU/EU) fails with err "Cannot enumerate > services" if the current stack has services that have been removed in the new > stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2, > where Spark's metainfo.xml in mystack-2.0 has the true > section. > Workaround is to remove Spark before attempting the install packages. > The error is below: > 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27] > BaseManagementHandler:61 - Caught a system exception while attempting to > create a resource: Cannot enumerate services > org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate > services > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606) > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508) > at > org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298) > at > org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97) > at > org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37) > at > org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19147) LogSearch - generate default jks file on startup
[
https://issues.apache.org/jira/browse/AMBARI-19147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-19147:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk:
{code:java}
commit 176a1c6ba4187c24d7203a69c5ab257e778956a4
Author: oleewere
Date: Tue Dec 13 19:49:47 2016 +0100
AMBARI-19147. LogSearch - generate default jks file on startup (oleewere)
Change-Id: Ifeb0d1cf6e0a131be969f59c1c6817bb97e67a5a
{code}
committed to branch-2.5:
{code:java}
commit 66b1f381478ecf8936ac3019497499194a6a5321
Author: oleewere
Date: Tue Dec 13 19:49:47 2016 +0100
AMBARI-19147. LogSearch - generate default jks file on startup (oleewere)
Change-Id: Ifeb0d1cf6e0a131be969f59c1c6817bb97e67a5a
{code}
> LogSearch - generate default jks file on startup
>
>
> Key: AMBARI-19147
> URL: https://issues.apache.org/jira/browse/AMBARI-19147
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19147.patch
>
>
> Generate JKS file on startup if keystore/truststore is not configured.
> Also add 2 new properties (with defaults):
> {{logsearch.cert.folder.location=/etc/ambari-logsearch-portal/conf/keys}}
> {{logsearch.cert.algorithm=sha256WithRSAEncryption}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19147) LogSearch - generate default jks file on startup
[
https://issues.apache.org/jira/browse/AMBARI-19147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-19147:
--
Attachment: AMBARI-19147.patch
> LogSearch - generate default jks file on startup
>
>
> Key: AMBARI-19147
> URL: https://issues.apache.org/jira/browse/AMBARI-19147
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19147.patch
>
>
> Generate JKS file on startup if keystore/truststore is not configured.
> Also add 2 new properties (with defaults):
> {{logsearch.cert.folder.location=/etc/ambari-logsearch-portal/conf/keys}}
> {{logsearch.cert.algorithm=sha256WithRSAEncryption}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19147) LogSearch - generate default jks file on startup
[
https://issues.apache.org/jira/browse/AMBARI-19147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-19147:
--
Attachment: (was: AMBARI-19147.patch)
> LogSearch - generate default jks file on startup
>
>
> Key: AMBARI-19147
> URL: https://issues.apache.org/jira/browse/AMBARI-19147
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19147.patch
>
>
> Generate JKS file on startup if keystore/truststore is not configured.
> Also add 2 new properties (with defaults):
> {{logsearch.cert.folder.location=/etc/ambari-logsearch-portal/conf/keys}}
> {{logsearch.cert.algorithm=sha256WithRSAEncryption}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19147) LogSearch - generate default jks file on startup
[
https://issues.apache.org/jira/browse/AMBARI-19147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-19147:
--
Description:
Generate JKS file on startup if keystore/truststore is not configured.
Also add 2 new properties (with defaults):
{{logsearch.cert.folder.location=/etc/ambari-logsearch-portal/conf/keys}}
{{logsearch.cert.algorithm=sha256WithRSAEncryption}}
> LogSearch - generate default jks file on startup
>
>
> Key: AMBARI-19147
> URL: https://issues.apache.org/jira/browse/AMBARI-19147
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19147.patch
>
>
> Generate JKS file on startup if keystore/truststore is not configured.
> Also add 2 new properties (with defaults):
> {{logsearch.cert.folder.location=/etc/ambari-logsearch-portal/conf/keys}}
> {{logsearch.cert.algorithm=sha256WithRSAEncryption}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[
https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745993#comment-15745993
]
Hadoop QA commented on AMBARI-19190:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843057/AMBARI-19190.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9649//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9649//console
This message is automatically generated.
> Remove UI logic to set or expect hive_server_interactive_host
> -
>
> Key: AMBARI-19190
> URL: https://issues.apache.org/jira/browse/AMBARI-19190
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch
>
>
> With the support for HSI HA, the property no longer seems appropriate. Lets
> remove the dependency on this property and no longer expect or use it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19147) LogSearch - generate default jks file on startup
[ https://issues.apache.org/jira/browse/AMBARI-19147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19147: -- Attachment: (was: AMBARI-19147.patch) > LogSearch - generate default jks file on startup > > > Key: AMBARI-19147 > URL: https://issues.apache.org/jira/browse/AMBARI-19147 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19147.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19147) LogSearch - generate default jks file on startup
[ https://issues.apache.org/jira/browse/AMBARI-19147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19147: -- Attachment: AMBARI-19147.patch > LogSearch - generate default jks file on startup > > > Key: AMBARI-19147 > URL: https://issues.apache.org/jira/browse/AMBARI-19147 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19147.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Attachment: AMBARI-19190.patch > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19170) NPE during Ambari server schema upgrade
[
https://issues.apache.org/jira/browse/AMBARI-19170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745935#comment-15745935
]
Hudson commented on AMBARI-19170:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6222 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6222/])
AMBARI-19170 - NPE during Ambari server schema upgrade (Attila Doroszlai
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bd308247344ea067bcf2f120c28e5bc0eb312c58])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
> NPE during Ambari server schema upgrade
> ---
>
> Key: AMBARI-19170
> URL: https://issues.apache.org/jira/browse/AMBARI-19170
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19170_branch-2.5.patch, AMBARI-19170_trunk.patch
>
>
> Ambari server upgrade path: 2.2.2.0 to 2.5.0.0-453
> Error seen while running 'ambari-server upgrade' command"
> {code}
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> WARNING: Original file krb5JAASLogin.conf kept
> INFO: File krb5JAASLogin.conf updated.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for Oracle. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/jdk64/jdk1.7.0_67/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/ojdbc6.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:209)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> Caused by: java.lang.NullPointerException
> at
> com.google.inject.persist.jpa.JpaPersistService.begin(JpaPersistService.java:70)
> at
> com.google.inject.persist.jpa.AmbariJpaPersistService.begin(AmbariJpaPersistService.java:29)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:106)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:206)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Status: Patch Available (was: Open) > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745923#comment-15745923 ] Andrii Tkach commented on AMBARI-19190: --- 19726 passing (27s) 153 pending > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19190_branch-2.5.patch > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Attachment: AMBARI-19190_branch-2.5.patch > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19190_branch-2.5.patch > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19191) Metrics Collector Move Wizard should no longer Restart All Services
[
https://issues.apache.org/jira/browse/AMBARI-19191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745842#comment-15745842
]
Hadoop QA commented on AMBARI-19191:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843022/AMBARI-19191.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9648//console
This message is automatically generated.
> Metrics Collector Move Wizard should no longer Restart All Services
> ---
>
> Key: AMBARI-19191
> URL: https://issues.apache.org/jira/browse/AMBARI-19191
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19191.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19192) Use released Helix 0.6.6 instead of 0.7.1 beta as AMS dependency
[
https://issues.apache.org/jira/browse/AMBARI-19192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745840#comment-15745840
]
Hadoop QA commented on AMBARI-19192:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843030/AMBARI-19192.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:red}-1 javac{color}. The applied patch generated 112 javac
compiler warnings (more than the trunk's current 110 warnings).
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-metrics/ambari-metrics-timelineservice.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9647//testReport/
Javac warnings:
https://builds.apache.org/job/Ambari-trunk-test-patch/9647//artifact/trunk/patchprocess/diffJavacWarnings.txt
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9647//console
This message is automatically generated.
> Use released Helix 0.6.6 instead of 0.7.1 beta as AMS dependency
>
>
> Key: AMBARI-19192
> URL: https://issues.apache.org/jira/browse/AMBARI-19192
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19192.patch
>
>
> Use released Helix 0.6.6 instead of 0.7.1 beta as AMS dependency
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Status: Open (was: Patch Available) > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Attachment: (was: AMBARI-19190_branch-2.5.patch) > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Attachment: (was: AMBARI-19190.patch) > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19191) Metrics Collector Move Wizard should no longer Restart All Services
[ https://issues.apache.org/jira/browse/AMBARI-19191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745815#comment-15745815 ] Hudson commented on AMBARI-19191: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6221 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6221/]) AMBARI-19191. Metrics Collector Move Wizard should no longer Restart All (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e70985490ce387fdaea18f80cabead47d34a5e8c]) * (edit) ambari-web/app/controllers/main/service/reassign/step4_controller.js > Metrics Collector Move Wizard should no longer Restart All Services > --- > > Key: AMBARI-19191 > URL: https://issues.apache.org/jira/browse/AMBARI-19191 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19191.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19170) NPE during Ambari server schema upgrade
[
https://issues.apache.org/jira/browse/AMBARI-19170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19170:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to {{trunk}} and {{branch-2.5}}
> NPE during Ambari server schema upgrade
> ---
>
> Key: AMBARI-19170
> URL: https://issues.apache.org/jira/browse/AMBARI-19170
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19170_branch-2.5.patch, AMBARI-19170_trunk.patch
>
>
> Ambari server upgrade path: 2.2.2.0 to 2.5.0.0-453
> Error seen while running 'ambari-server upgrade' command"
> {code}
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> WARNING: Original file krb5JAASLogin.conf kept
> INFO: File krb5JAASLogin.conf updated.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for Oracle. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/jdk64/jdk1.7.0_67/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/ojdbc6.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:209)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> Caused by: java.lang.NullPointerException
> at
> com.google.inject.persist.jpa.JpaPersistService.begin(JpaPersistService.java:70)
> at
> com.google.inject.persist.jpa.AmbariJpaPersistService.begin(AmbariJpaPersistService.java:29)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:106)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:206)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[
https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745772#comment-15745772
]
Hadoop QA commented on AMBARI-19190:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843027/AMBARI-19190.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9646//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9646//console
This message is automatically generated.
> Remove UI logic to set or expect hive_server_interactive_host
> -
>
> Key: AMBARI-19190
> URL: https://issues.apache.org/jira/browse/AMBARI-19190
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch
>
>
> With the support for HSI HA, the property no longer seems appropriate. Lets
> remove the dependency on this property and no longer expect or use it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19140) Ambari Server symbolic links has double // when root dir is just /
[ https://issues.apache.org/jira/browse/AMBARI-19140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745724#comment-15745724 ] Hudson commented on AMBARI-19140: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6220 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6220/]) AMBARI-19140 Ambari Server symbolic links has double // when root dir is (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=70303d0c6526c92f53f95fa283f88de08b103559]) * (edit) ambari-server/conf/unix/install-helper.sh * (edit) ambari-server/src/main/package/rpm/posttrans_server.sh * (edit) ambari-server/src/main/package/rpm/preinstall.sh > Ambari Server symbolic links has double // when root dir is just / > -- > > Key: AMBARI-19140 > URL: https://issues.apache.org/jira/browse/AMBARI-19140 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19140.patch > > > Notice the "//" in the symbolic link , where it could have been trimmed to be > just one leading "/" > [root]# ll /usr/sbin/ambari-server > lrwxrwxrwx 1 root root 26 Dec 5 11:27 /usr/sbin/ambari-server -> > //etc/init.d/ambari-server > [root]# clear > [root]# ll > total 20 > drwxrwxr-x 4 root root 8192 Dec 5 11:32 ambari_agent > lrwxrwxrwx 1 root root 42 Dec 5 11:27 ambari_commons -> > //usr/lib/ambari-server/lib/ambari_commons > lrwxrwxrwx 1 root root 41 Dec 5 11:27 ambari_jinja2 -> > //usr/lib/ambari-server/lib/ambari_jinja2 > drwxrwxr-x 2 root root 4096 Dec 5 11:28 ambari_server > lrwxrwxrwx 1 root root 45 Dec 5 11:27 ambari_simplejson -> > //usr/lib/ambari-server/lib/ambari_simplejson > lrwxrwxrwx 1 root root 47 Dec 5 11:27 resource_management -> > //usr/lib/ambari-server/lib/resource_management > drwxr-xr-x 5 ams hadoop 83 Dec 6 09:26 resource_monitoring -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19140) Ambari Server symbolic links has double // when root dir is just /
[ https://issues.apache.org/jira/browse/AMBARI-19140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19140: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari Server symbolic links has double // when root dir is just / > -- > > Key: AMBARI-19140 > URL: https://issues.apache.org/jira/browse/AMBARI-19140 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19140.patch > > > Notice the "//" in the symbolic link , where it could have been trimmed to be > just one leading "/" > [root]# ll /usr/sbin/ambari-server > lrwxrwxrwx 1 root root 26 Dec 5 11:27 /usr/sbin/ambari-server -> > //etc/init.d/ambari-server > [root]# clear > [root]# ll > total 20 > drwxrwxr-x 4 root root 8192 Dec 5 11:32 ambari_agent > lrwxrwxrwx 1 root root 42 Dec 5 11:27 ambari_commons -> > //usr/lib/ambari-server/lib/ambari_commons > lrwxrwxrwx 1 root root 41 Dec 5 11:27 ambari_jinja2 -> > //usr/lib/ambari-server/lib/ambari_jinja2 > drwxrwxr-x 2 root root 4096 Dec 5 11:28 ambari_server > lrwxrwxrwx 1 root root 45 Dec 5 11:27 ambari_simplejson -> > //usr/lib/ambari-server/lib/ambari_simplejson > lrwxrwxrwx 1 root root 47 Dec 5 11:27 resource_management -> > //usr/lib/ambari-server/lib/resource_management > drwxr-xr-x 5 ams hadoop 83 Dec 6 09:26 resource_monitoring -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19140) Ambari Server symbolic links has double // when root dir is just /
[ https://issues.apache.org/jira/browse/AMBARI-19140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745630#comment-15745630 ] Di Li commented on AMBARI-19140: AMBARI-19140 Pushed to Trunk as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=70303d0c6526c92f53f95fa283f88de08b103559 Pushed to Branch-2.5 as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=bb920043077e67a7840fd264d2df306c6213f1e4 > Ambari Server symbolic links has double // when root dir is just / > -- > > Key: AMBARI-19140 > URL: https://issues.apache.org/jira/browse/AMBARI-19140 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19140.patch > > > Notice the "//" in the symbolic link , where it could have been trimmed to be > just one leading "/" > [root]# ll /usr/sbin/ambari-server > lrwxrwxrwx 1 root root 26 Dec 5 11:27 /usr/sbin/ambari-server -> > //etc/init.d/ambari-server > [root]# clear > [root]# ll > total 20 > drwxrwxr-x 4 root root 8192 Dec 5 11:32 ambari_agent > lrwxrwxrwx 1 root root 42 Dec 5 11:27 ambari_commons -> > //usr/lib/ambari-server/lib/ambari_commons > lrwxrwxrwx 1 root root 41 Dec 5 11:27 ambari_jinja2 -> > //usr/lib/ambari-server/lib/ambari_jinja2 > drwxrwxr-x 2 root root 4096 Dec 5 11:28 ambari_server > lrwxrwxrwx 1 root root 45 Dec 5 11:27 ambari_simplejson -> > //usr/lib/ambari-server/lib/ambari_simplejson > lrwxrwxrwx 1 root root 47 Dec 5 11:27 resource_management -> > //usr/lib/ambari-server/lib/resource_management > drwxr-xr-x 5 ams hadoop 83 Dec 6 09:26 resource_monitoring -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[
https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745611#comment-15745611
]
Hadoop QA commented on AMBARI-19190:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843027/AMBARI-19190.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9645//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9645//console
This message is automatically generated.
> Remove UI logic to set or expect hive_server_interactive_host
> -
>
> Key: AMBARI-19190
> URL: https://issues.apache.org/jira/browse/AMBARI-19190
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch
>
>
> With the support for HSI HA, the property no longer seems appropriate. Lets
> remove the dependency on this property and no longer expect or use it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19192) Use released Helix 0.6.6 instead of 0.7.1 beta as AMS dependency
[ https://issues.apache.org/jira/browse/AMBARI-19192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19192: Attachment: AMBARI-19192.patch > Use released Helix 0.6.6 instead of 0.7.1 beta as AMS dependency > > > Key: AMBARI-19192 > URL: https://issues.apache.org/jira/browse/AMBARI-19192 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19192.patch > > > Use released Helix 0.6.6 instead of 0.7.1 beta as AMS dependency -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19192) Use released Helix 0.6.6 instead of 0.7.1 beta as AMS dependency
[ https://issues.apache.org/jira/browse/AMBARI-19192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19192: Status: Patch Available (was: Open) > Use released Helix 0.6.6 instead of 0.7.1 beta as AMS dependency > > > Key: AMBARI-19192 > URL: https://issues.apache.org/jira/browse/AMBARI-19192 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19192.patch > > > Use released Helix 0.6.6 instead of 0.7.1 beta as AMS dependency -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19192) Use released Helix 0.6.6 instead of 0.7.1 beta as AMS dependency
Dmytro Sen created AMBARI-19192: --- Summary: Use released Helix 0.6.6 instead of 0.7.1 beta as AMS dependency Key: AMBARI-19192 URL: https://issues.apache.org/jira/browse/AMBARI-19192 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.5.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.5.0 Use released Helix 0.6.6 instead of 0.7.1 beta as AMS dependency -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19151) New REST API in Log Search Portal that returns the log files of the host components
[ https://issues.apache.org/jira/browse/AMBARI-19151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745576#comment-15745576 ] Hudson commented on AMBARI-19151: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #519 (See [https://builds.apache.org/job/Ambari-branch-2.5/519/]) AMBARI-19151 New Log Search REST API that returns the log files of the (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=56271c8aa1e87ac5b690381f28ed2f20d16e0bc9]) * (add) ambari-logsearch/ambari-logsearch-portal/src/test/java/org/apache/ambari/logsearch/converter/HostLogFilesRequestQueryConverterTest.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/test/java/org/apache/ambari/logsearch/converter/ServiceLogTreeRequestFacetQueryConverterTest.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/manager/ServiceLogsManager.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/manager/AuditLogsManager.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/model/response/NodeData.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/rest/ServiceLogsResource.java * (edit) ambari-logsearch/ambari-logsearch-portal/pom.xml * (add) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/converter/HostLogFilesRequestQueryConverter.java * (add) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/model/request/HostComponentParamDefinition.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/model/request/impl/ServiceAnyGraphRequest.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/common/ExternalServerClient.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/model/request/impl/BaseServiceLogRequest.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/converter/ServiceLogAnyGraphRequestQueryConverter.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/doc/DocConstants.java * (add) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/model/request/impl/HostLogFilesRequest.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/model/request/ServiceLogParamDefinition.java * (delete) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/graph/GraphDataGenerator.java * (add) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/solr/ResponseDataGenerator.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/test/java/org/apache/ambari/logsearch/converter/UserConfigRequestQueryConverterTest.java * (add) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/model/response/HostLogFilesResponse.java > New REST API in Log Search Portal that returns the log files of the host > components > --- > > Key: AMBARI-19151 > URL: https://issues.apache.org/jira/browse/AMBARI-19151 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > > Ambari Server fetches the log file names of the host components by fetching > the log entries, and get the log file field of the first entry it founds. > This new API replaces this logic, it explicitly returns the log files of a > host component, and thus giving the control to the Log Search server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19191) Metrics Collector Move Wizard should no longer Restart All Services
[
https://issues.apache.org/jira/browse/AMBARI-19191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745564#comment-15745564
]
Hadoop QA commented on AMBARI-19191:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843022/AMBARI-19191.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9644//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9644//console
This message is automatically generated.
> Metrics Collector Move Wizard should no longer Restart All Services
> ---
>
> Key: AMBARI-19191
> URL: https://issues.apache.org/jira/browse/AMBARI-19191
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19191.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Attachment: AMBARI-19190.patch > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Attachment: (was: AMBARI-19190.patch) > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19190_branch-2.5.patch > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19191) Metrics Collector Move Wizard should no longer Restart All Services
[ https://issues.apache.org/jira/browse/AMBARI-19191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-19191: - Status: Patch Available (was: Open) > Metrics Collector Move Wizard should no longer Restart All Services > --- > > Key: AMBARI-19191 > URL: https://issues.apache.org/jira/browse/AMBARI-19191 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19191.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19191) Metrics Collector Move Wizard should no longer Restart All Services
[ https://issues.apache.org/jira/browse/AMBARI-19191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-19191: - Attachment: AMBARI-19191.patch > Metrics Collector Move Wizard should no longer Restart All Services > --- > > Key: AMBARI-19191 > URL: https://issues.apache.org/jira/browse/AMBARI-19191 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19191.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19151) New REST API in Log Search Portal that returns the log files of the host components
[ https://issues.apache.org/jira/browse/AMBARI-19151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745504#comment-15745504 ] Hudson commented on AMBARI-19151: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6219 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6219/]) AMBARI-19151 New Log Search REST API that returns the log files of the (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2f038b2709068c0237b80f0b176d39abb434f9b2]) * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/model/request/impl/ServiceAnyGraphRequest.java * (add) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/model/request/HostComponentParamDefinition.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/model/request/impl/BaseServiceLogRequest.java * (add) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/model/request/impl/HostLogFilesRequest.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/rest/ServiceLogsResource.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/manager/ServiceLogsManager.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/common/ExternalServerClient.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/converter/ServiceLogAnyGraphRequestQueryConverter.java * (add) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/solr/ResponseDataGenerator.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/manager/AuditLogsManager.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/model/request/ServiceLogParamDefinition.java * (add) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/converter/HostLogFilesRequestQueryConverter.java * (delete) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/graph/GraphDataGenerator.java * (add) ambari-logsearch/ambari-logsearch-portal/src/test/java/org/apache/ambari/logsearch/converter/HostLogFilesRequestQueryConverterTest.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/test/java/org/apache/ambari/logsearch/converter/UserConfigRequestQueryConverterTest.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/doc/DocConstants.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/model/response/NodeData.java * (edit) ambari-logsearch/ambari-logsearch-portal/pom.xml * (add) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/model/response/HostLogFilesResponse.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/test/java/org/apache/ambari/logsearch/converter/ServiceLogTreeRequestFacetQueryConverterTest.java > New REST API in Log Search Portal that returns the log files of the host > components > --- > > Key: AMBARI-19151 > URL: https://issues.apache.org/jira/browse/AMBARI-19151 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > > Ambari Server fetches the log file names of the host components by fetching > the log entries, and get the log file field of the first entry it founds. > This new API replaces this logic, it explicitly returns the log files of a > host component, and thus giving the control to the Log Search server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19191) Metrics Collector Move Wizard should no longer Restart All Services
Aleksandr Kovalenko created AMBARI-19191: Summary: Metrics Collector Move Wizard should no longer Restart All Services Key: AMBARI-19191 URL: https://issues.apache.org/jira/browse/AMBARI-19191 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.5.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19188) Provide Atlas Hook support for Hive2
[
https://issues.apache.org/jira/browse/AMBARI-19188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745492#comment-15745492
]
Hadoop QA commented on AMBARI-19188:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843006/AMBARI-19188.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9643//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9643//console
This message is automatically generated.
> Provide Atlas Hook support for Hive2
>
>
> Key: AMBARI-19188
> URL: https://issues.apache.org/jira/browse/AMBARI-19188
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19188.patch
>
>
> Need to provide Atlas hook configuration support for HiveServer-Interactive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[
https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745424#comment-15745424
]
Hadoop QA commented on AMBARI-19190:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843014/AMBARI-19190.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9642//console
This message is automatically generated.
> Remove UI logic to set or expect hive_server_interactive_host
> -
>
> Key: AMBARI-19190
> URL: https://issues.apache.org/jira/browse/AMBARI-19190
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch
>
>
> With the support for HSI HA, the property no longer seems appropriate. Lets
> remove the dependency on this property and no longer expect or use it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[
https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745399#comment-15745399
]
Hadoop QA commented on AMBARI-19190:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843014/AMBARI-19190.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9641//console
This message is automatically generated.
> Remove UI logic to set or expect hive_server_interactive_host
> -
>
> Key: AMBARI-19190
> URL: https://issues.apache.org/jira/browse/AMBARI-19190
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch
>
>
> With the support for HSI HA, the property no longer seems appropriate. Lets
> remove the dependency on this property and no longer expect or use it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-19151) New REST API in Log Search Portal that returns the log files of the host components
[
https://issues.apache.org/jira/browse/AMBARI-19151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745386#comment-15745386
]
Miklos Gergely edited comment on AMBARI-19151 at 12/13/16 3:22 PM:
---
committed to trunk:
{code:java}
commit 2f038b2709068c0237b80f0b176d39abb434f9b2
Author: Miklos Gergely
Date: Tue Dec 13 16:14:23 2016 +0100
AMBARI-19151 New Log Search REST API that returns the log files of the host
components
Change-Id: Ie789a0c8c98b6b6b7dd02f32a3acb89039f56de4
{code}
committed to branch-2.5:
{code:java}
commit 56271c8aa1e87ac5b690381f28ed2f20d16e0bc9
Author: Miklos Gergely
Date: Tue Dec 13 16:21:35 2016 +0100
AMBARI-19151 New Log Search REST API that returns the log files of the host
components
Change-Id: I752fca2e12e2c8f528cca2d6ec00629a9527051f
{code}
was (Author: mgergely):
committed to trunk:
{code:java}
commit 2f038b2709068c0237b80f0b176d39abb434f9b2
Author: Miklos Gergely
Date: Tue Dec 13 16:14:23 2016 +0100
AMBARI-19151 New Log Search REST API that returns the log files of the host
components
Change-Id: Ie789a0c8c98b6b6b7dd02f32a3acb89039f56de4
{code}
committed to branch-2.5:
{code:java}
commit cbb81c44722362dc13f327c1fe690756998d8a7b
Author: Miklos Gergely
Date: Tue Dec 13 16:06:17 2016 +0100
New Log Search REST API that returns the log files of the host components
Change-Id: I8777e57fd17fa5704fbc5454b64f72ddf4c6ab5d
{code}
> New REST API in Log Search Portal that returns the log files of the host
> components
> ---
>
> Key: AMBARI-19151
> URL: https://issues.apache.org/jira/browse/AMBARI-19151
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
>
> Ambari Server fetches the log file names of the host components by fetching
> the log entries, and get the log file field of the first entry it founds.
> This new API replaces this logic, it explicitly returns the log files of a
> host component, and thus giving the control to the Log Search server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Attachment: AMBARI-19190.patch > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Attachment: (was: AMBARI-19190.patch) > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19190_branch-2.5.patch > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19151) New REST API in Log Search Portal that returns the log files of the host components
[
https://issues.apache.org/jira/browse/AMBARI-19151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745386#comment-15745386
]
Miklos Gergely commented on AMBARI-19151:
-
committed to trunk:
{code:java}
commit 2f038b2709068c0237b80f0b176d39abb434f9b2
Author: Miklos Gergely
Date: Tue Dec 13 16:14:23 2016 +0100
AMBARI-19151 New Log Search REST API that returns the log files of the host
components
Change-Id: Ie789a0c8c98b6b6b7dd02f32a3acb89039f56de4
{code}
committed to branch-2.5:
{code:java}
commit cbb81c44722362dc13f327c1fe690756998d8a7b
Author: Miklos Gergely
Date: Tue Dec 13 16:06:17 2016 +0100
New Log Search REST API that returns the log files of the host components
Change-Id: I8777e57fd17fa5704fbc5454b64f72ddf4c6ab5d
{code}
> New REST API in Log Search Portal that returns the log files of the host
> components
> ---
>
> Key: AMBARI-19151
> URL: https://issues.apache.org/jira/browse/AMBARI-19151
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
>
> Ambari Server fetches the log file names of the host components by fetching
> the log entries, and get the log file field of the first entry it founds.
> This new API replaces this logic, it explicitly returns the log files of a
> host component, and thus giving the control to the Log Search server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[
https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745358#comment-15745358
]
Hadoop QA commented on AMBARI-19190:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843005/AMBARI-19190.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9640//console
This message is automatically generated.
> Remove UI logic to set or expect hive_server_interactive_host
> -
>
> Key: AMBARI-19190
> URL: https://issues.apache.org/jira/browse/AMBARI-19190
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch
>
>
> With the support for HSI HA, the property no longer seems appropriate. Lets
> remove the dependency on this property and no longer expect or use it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18945) Allowing user to edit service name while enabling ranger plugin
[
https://issues.apache.org/jira/browse/AMBARI-18945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745355#comment-15745355
]
Hadoop QA commented on AMBARI-18945:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842982/AMBARI-18945.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9639//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9639//console
This message is automatically generated.
> Allowing user to edit service name while enabling ranger plugin
> ---
>
> Key: AMBARI-18945
> URL: https://issues.apache.org/jira/browse/AMBARI-18945
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
> Attachments: AMBARI-18945.1.patch, AMBARI-18945.2.patch,
> AMBARI-18945.patch
>
>
> Need to add a provision for creating default repository with static name or
> user provided name.
> This will help user to provided service name under Ranger supported plugins
> config tab and can take dump of latest snapshot of all policies and use it
> while recreating another/multiple clusters with same service name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19188) Provide Atlas Hook support for Hive2
[ https://issues.apache.org/jira/browse/AMBARI-19188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19188: Status: Patch Available (was: Open) Added fix for providing Atlas Hook for HiveServer2-Interactive > Provide Atlas Hook support for Hive2 > > > Key: AMBARI-19188 > URL: https://issues.apache.org/jira/browse/AMBARI-19188 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19188.patch > > > Need to provide Atlas hook configuration support for HiveServer-Interactive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19188) Provide Atlas Hook support for Hive2
[ https://issues.apache.org/jira/browse/AMBARI-19188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19188: Attachment: AMBARI-19188.patch > Provide Atlas Hook support for Hive2 > > > Key: AMBARI-19188 > URL: https://issues.apache.org/jira/browse/AMBARI-19188 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19188.patch > > > Need to provide Atlas hook configuration support for HiveServer-Interactive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Attachment: AMBARI-19190.patch > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Attachment: (was: AMBARI-19190.patch) > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[
https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745303#comment-15745303
]
Hadoop QA commented on AMBARI-19190:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842996/AMBARI-19190.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9638//console
This message is automatically generated.
> Remove UI logic to set or expect hive_server_interactive_host
> -
>
> Key: AMBARI-19190
> URL: https://issues.apache.org/jira/browse/AMBARI-19190
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch
>
>
> With the support for HSI HA, the property no longer seems appropriate. Lets
> remove the dependency on this property and no longer expect or use it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19189) Add host component should show configs being changed in recommendation popup modal
[
https://issues.apache.org/jira/browse/AMBARI-19189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745301#comment-15745301
]
Hadoop QA commented on AMBARI-19189:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842991/AMBARI-19189.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9637//console
This message is automatically generated.
> Add host component should show configs being changed in recommendation popup
> modal
> --
>
> Key: AMBARI-19189
> URL: https://issues.apache.org/jira/browse/AMBARI-19189
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19189.patch
>
>
> *STR:*
> # Navigate to Hosts details page and click on Add button
> # While adding components like ZooKeeper Server and some other host
> components, ambari-web also changes some configurations
> *Actual Result:* Before changing configurations, ambari-web warns user that a
> list of configurations will be changed in a modal popup. But UI does not show
> current and the new value that will be changed to the end-user in the popup,
> neither does it allow user to add component without changing configurations
> if user wants to do that
> *Expected Result:* Similar popup with the ux as the one shown for the stack
> advisor recommendation response should be shown which shows current value and
> new value of the config with checkboxes which user can choose to uncheck.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19189) Add host component should show configs being changed in recommendation popup modal
[ https://issues.apache.org/jira/browse/AMBARI-19189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745282#comment-15745282 ] Hudson commented on AMBARI-19189: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6218 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6218/]) AMBARI-19189 Add host component should show configs being changed in (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e148cb5a2ab5f1a64b0ba5c8c8ad01d396bd57ac]) * (add) ambari-web/app/templates/main/host/details/addComponentWithConfigsChanges.hbs * (edit) ambari-web/app/templates/common/modal_popups/dependent_configs_list.hbs * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/views/common/modal_popups/dependent_configs_list_popup.js * (edit) ambari-web/app/controllers/main/host/details.js * (edit) ambari-web/test/controllers/main/host/details_test.js > Add host component should show configs being changed in recommendation popup > modal > -- > > Key: AMBARI-19189 > URL: https://issues.apache.org/jira/browse/AMBARI-19189 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19189.patch > > > *STR:* > # Navigate to Hosts details page and click on Add button > # While adding components like ZooKeeper Server and some other host > components, ambari-web also changes some configurations > *Actual Result:* Before changing configurations, ambari-web warns user that a > list of configurations will be changed in a modal popup. But UI does not show > current and the new value that will be changed to the end-user in the popup, > neither does it allow user to add component without changing configurations > if user wants to do that > *Expected Result:* Similar popup with the ux as the one shown for the stack > advisor recommendation response should be shown which shows current value and > new value of the config with checkboxes which user can choose to uncheck. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19185) NameNode JVM has many parameters repeated 3 or more times
[ https://issues.apache.org/jira/browse/AMBARI-19185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745246#comment-15745246 ] Yuanbo Liu commented on AMBARI-19185: - [~Tim Thorpe] Thanks for your response. Sure, I will check my review board. > NameNode JVM has many parameters repeated 3 or more times > - > > Key: AMBARI-19185 > URL: https://issues.apache.org/jira/browse/AMBARI-19185 > Project: Ambari > Issue Type: Bug >Reporter: Yuanbo Liu > Attachments: AMBARI-19185.001.patch > > > When using Ambari to start NameNode, then looking at namenode process running > in Linux, we find that there are many repeated jvm options in the start > command. It will be good if we can get rid of the redundant options. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19187) Disable security hook
[ https://issues.apache.org/jira/browse/AMBARI-19187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-19187: --- Fix Version/s: 2.5.0 Status: Patch Available (was: Open) > Disable security hook > - > > Key: AMBARI-19187 > URL: https://issues.apache.org/jira/browse/AMBARI-19187 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server >Affects Versions: 2.5.0 >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 2.5.0 > > > Hadoop components need to establish a secure connection with ZooKeeper when > Kerberos is enabled. This involves the setup of the correct authentication > (JAAS config file) and authorization (per-component Kerberos-backed ACLs on > the znodes) between the service and ZooKeeper. Most services are able to set > these ACLs based on their config when the user enable kerberos. > When we disable kerberos again, the sasl ACL should be removed otherwise the > services won't be able to access their znodes. > This issue is about introducing a new command (DISABLE_SECURITY) that will be > sent by the ambari server to the services upon the dekerberiztion process. > When a service receives this command it will be able to do the zookeeper > secure to unsecure migration process (e.g. removing sasl ACLs). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19176) Perf: enable security fails
[
https://issues.apache.org/jira/browse/AMBARI-19176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745187#comment-15745187
]
Hudson commented on AMBARI-19176:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6217 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6217/])
AMBARI-19176 Perf: enable security fails (dsen) (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=69825b9ff20dd8c394e14f5acf1faa4f58246843])
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/metainfo.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/kerberos_client.py
* (edit) contrib/utils/perf/deploy-gce-perf-cluster.py
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/kerberos_common.py
> Perf: enable security fails
> ---
>
> Key: AMBARI-19176
> URL: https://issues.apache.org/jira/browse/AMBARI-19176
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-19176.patch
>
>
> STR:
> 1) Go to "Enable security" wizard.
> 2) Choose MIT security.
> 3) Populate all fields and click "Next" button. "Next" button doesn't work.
> Failed request
> {code}
> Request URL:http://as:8080/api/v1/clusters/fff/services/KERBEROS
> Request Method:DELETE
> Status Code:404 Not Found
> Remote Address:104.196.95.5:8080
> message
> :
> "org.apache.ambari.server.controller.spi.NoSuchResourceException: The
> specified resource doesn't exist: Service not found, clusterName=fff,
> serviceName=KERBEROS"
> status
> :
> 404
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19189) Add host component should show configs being changed in recommendation popup modal
[ https://issues.apache.org/jira/browse/AMBARI-19189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745188#comment-15745188 ] Andrii Babiichuk commented on AMBARI-19189: --- Committed to trunk > Add host component should show configs being changed in recommendation popup > modal > -- > > Key: AMBARI-19189 > URL: https://issues.apache.org/jira/browse/AMBARI-19189 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19189.patch > > > *STR:* > # Navigate to Hosts details page and click on Add button > # While adding components like ZooKeeper Server and some other host > components, ambari-web also changes some configurations > *Actual Result:* Before changing configurations, ambari-web warns user that a > list of configurations will be changed in a modal popup. But UI does not show > current and the new value that will be changed to the end-user in the popup, > neither does it allow user to add component without changing configurations > if user wants to do that > *Expected Result:* Similar popup with the ux as the one shown for the stack > advisor recommendation response should be shown which shows current value and > new value of the config with checkboxes which user can choose to uncheck. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[
https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745182#comment-15745182
]
Hadoop QA commented on AMBARI-19190:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842996/AMBARI-19190.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9636//console
This message is automatically generated.
> Remove UI logic to set or expect hive_server_interactive_host
> -
>
> Key: AMBARI-19190
> URL: https://issues.apache.org/jira/browse/AMBARI-19190
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch
>
>
> With the support for HSI HA, the property no longer seems appropriate. Lets
> remove the dependency on this property and no longer expect or use it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19189) Add host component should show configs being changed in recommendation popup modal
[
https://issues.apache.org/jira/browse/AMBARI-19189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745178#comment-15745178
]
Hadoop QA commented on AMBARI-19189:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842991/AMBARI-19189.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9635//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9635//console
This message is automatically generated.
> Add host component should show configs being changed in recommendation popup
> modal
> --
>
> Key: AMBARI-19189
> URL: https://issues.apache.org/jira/browse/AMBARI-19189
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19189.patch
>
>
> *STR:*
> # Navigate to Hosts details page and click on Add button
> # While adding components like ZooKeeper Server and some other host
> components, ambari-web also changes some configurations
> *Actual Result:* Before changing configurations, ambari-web warns user that a
> list of configurations will be changed in a modal popup. But UI does not show
> current and the new value that will be changed to the end-user in the popup,
> neither does it allow user to add component without changing configurations
> if user wants to do that
> *Expected Result:* Similar popup with the ux as the one shown for the stack
> advisor recommendation response should be shown which shows current value and
> new value of the config with checkboxes which user can choose to uncheck.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Status: Patch Available (was: Open) > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Attachment: AMBARI-19190.patch > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19190: -- Attachment: AMBARI-19190_branch-2.5.patch > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19190.patch, AMBARI-19190_branch-2.5.patch > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19176) Perf: enable security fails
[
https://issues.apache.org/jira/browse/AMBARI-19176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745164#comment-15745164
]
Hudson commented on AMBARI-19176:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #517 (See
[https://builds.apache.org/job/Ambari-branch-2.5/517/])
AMBARI-19176 Perf: enable security fails (dsen) (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ceec30a9f4530d6f0a079000aa3bb7f7d216be1c])
* (edit) contrib/utils/perf/deploy-gce-perf-cluster.py
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/kerberos_common.py
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/metainfo.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/kerberos_client.py
> Perf: enable security fails
> ---
>
> Key: AMBARI-19176
> URL: https://issues.apache.org/jira/browse/AMBARI-19176
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-19176.patch
>
>
> STR:
> 1) Go to "Enable security" wizard.
> 2) Choose MIT security.
> 3) Populate all fields and click "Next" button. "Next" button doesn't work.
> Failed request
> {code}
> Request URL:http://as:8080/api/v1/clusters/fff/services/KERBEROS
> Request Method:DELETE
> Status Code:404 Not Found
> Remote Address:104.196.95.5:8080
> message
> :
> "org.apache.ambari.server.controller.spi.NoSuchResourceException: The
> specified resource doesn't exist: Service not found, clusterName=fff,
> serviceName=KERBEROS"
> status
> :
> 404
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19190) Remove UI logic to set or expect hive_server_interactive_host
[ https://issues.apache.org/jira/browse/AMBARI-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745159#comment-15745159 ] Andrii Tkach commented on AMBARI-19190: --- 19701 passing (32s) 153 pending > Remove UI logic to set or expect hive_server_interactive_host > - > > Key: AMBARI-19190 > URL: https://issues.apache.org/jira/browse/AMBARI-19190 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > > With the support for HSI HA, the property no longer seems appropriate. Lets > remove the dependency on this property and no longer expect or use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19031) AMBARI-19031: UI Enhancements, import/export assets and smart version configuration
[ https://issues.apache.org/jira/browse/AMBARI-19031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-19031: --- Fix Version/s: 2.5.0 > AMBARI-19031: UI Enhancements, import/export assets and smart version > configuration > --- > > Key: AMBARI-19031 > URL: https://issues.apache.org/jira/browse/AMBARI-19031 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Padma Priya Nagaraj > Fix For: 2.5.0 > > Attachments: AMBARI-19031.01.patch > > > UX Enhancemenets > - Dashboard as a tab > - Coordinator UI changes > - Bundle smart name autofil > Features > - Version setting picked up from Oozie > - Ability to import/export assets(actions) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19189) Add host component should show configs being changed in recommendation popup modal
[ https://issues.apache.org/jira/browse/AMBARI-19189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-19189: -- Status: Patch Available (was: Open) > Add host component should show configs being changed in recommendation popup > modal > -- > > Key: AMBARI-19189 > URL: https://issues.apache.org/jira/browse/AMBARI-19189 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19189.patch > > > *STR:* > # Navigate to Hosts details page and click on Add button > # While adding components like ZooKeeper Server and some other host > components, ambari-web also changes some configurations > *Actual Result:* Before changing configurations, ambari-web warns user that a > list of configurations will be changed in a modal popup. But UI does not show > current and the new value that will be changed to the end-user in the popup, > neither does it allow user to add component without changing configurations > if user wants to do that > *Expected Result:* Similar popup with the ux as the one shown for the stack > advisor recommendation response should be shown which shows current value and > new value of the config with checkboxes which user can choose to uncheck. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
