[jira] [Commented] (AMBARI-19397) Infra Solr Upgrade support 2.4 -> 2.5
[
https://issues.apache.org/jira/browse/AMBARI-19397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803911#comment-15803911
]
Hadoop QA commented on AMBARI-19397:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845943/AMBARI-19397.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/9933//console
This message is automatically generated.
> Infra Solr Upgrade support 2.4 -> 2.5
> -
>
> Key: AMBARI-19397
> URL: https://issues.apache.org/jira/browse/AMBARI-19397
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-19397.patch
>
>
> Upgrade Infra solr related properties for ambari 2.5.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19398) Namenode not resolved while submitting workflow in certain environments
[
https://issues.apache.org/jira/browse/AMBARI-19398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803908#comment-15803908
]
Hadoop QA commented on AMBARI-19398:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845957/AMBARI-19398_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/wfmanager
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9932//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9932//console
This message is automatically generated.
> Namenode not resolved while submitting workflow in certain environments
> ---
>
> Key: AMBARI-19398
> URL: https://issues.apache.org/jira/browse/AMBARI-19398
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Padma Priya Nagaraj
>Assignee: Padma Priya Nagaraj
> Labels: WFD
> Fix For: 2.5.0
>
> Attachments: AMBARI-19398_trunk.patch
>
>
> Namenode is not resovled while creating configuration in job.properties while
> submitting workflow in certain environments.
> Step.
> if the hdfs-site does not have dfs.namenode.rpc-address property workflow
> submission fails.
> Expected.
> certain environments may not have dfs.namenode.rpc-address set, and in those
> environments workflow should be submitted without error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19399) Workflow imported into Local FS cannot be imported into WFD
venkat created AMBARI-19399: --- Summary: Workflow imported into Local FS cannot be imported into WFD Key: AMBARI-19399 URL: https://issues.apache.org/jira/browse/AMBARI-19399 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: venkat Priority: Blocker Fix For: 2.5.0 Step1:Create a workflow with an action. Step2:Fill all the action properties. Step3:Export the workflow into local FS. Step4:Import the same workflow into WFD -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19366) Hive-saved query and Pig script Migration is not working Hue-Ambari migration view
[
https://issues.apache.org/jira/browse/AMBARI-19366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-19366:
--
Resolution: Fixed
Assignee: Gaurav Nagar
Status: Resolved (was: Patch Available)
Committed to branch-2.5 and trunk
> Hive-saved query and Pig script Migration is not working Hue-Ambari migration
> view
> --
>
> Key: AMBARI-19366
> URL: https://issues.apache.org/jira/browse/AMBARI-19366
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Pradarttana
>Assignee: Gaurav Nagar
> Attachments: AMBARI-19366.1.patch, AMBARI-19366.patch,
> AMBARI-19366_trunk.1.patch, AMBARI-19366_trunk.patch
>
>
> Hive-saved query and Pig script Migration is not working Hue-Ambari migration
> view
> Saying error
> {code}
> 04 Jan 2017 17:25:14,992 ERROR [Thread-56]
> HiveSavedQueryMigrationImplementation:618 - Webhdfs:
> java.lang.IllegalArgumentException: Can't get Kerberos realm
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:65)
> at
> org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:247)
> at
> org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:283)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryMigrationImplementation.createDirHive(HiveSavedQueryMigrationImplementation.java:603)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryMigrationUtility.hiveSavedQueryMigration(HiveSavedQueryMigrationUtility.java:214)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryStartJob.run(HiveSavedQueryStartJob.java:66)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor308.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.security.authentication.util.KerberosUtil.getDefaultRealm(KerberosUtil.java:75)
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:63)
> ... 5 more
> Caused by: KrbException: Cannot locate default realm
> at sun.security.krb5.Config.getDefaultRealm(Config.java:1181)
> ... 10 more
> 04 Jan 2017 17:25:15,008 ERROR [Thread-56]
> HiveSavedQueryMigrationImplementation:706 - Webhdfs exception
> java.lang.IllegalArgumentException: Can't get Kerberos realm
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:65)
> at
> org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:247)
> at
> org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:283)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryMigrationImplementation.putFileinHdfs(HiveSavedQueryMigrationImplementation.java:670)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryMigrationUtility.hiveSavedQueryMigration(HiveSavedQueryMigrationUtility.java:215)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryStartJob.run(HiveSavedQueryStartJob.java:66)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor308.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.security.authentication.util.KerberosUtil.getDefaultRealm(KerberosUtil.java:75)
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:63)
> ... 5 more
> Caused by: KrbException: Cannot locate default realm
> at sun.security.krb5.Config.getDefaultRealm(Config.java:1181)
> ... 10 more
> 04 Jan 2017 17:25:15,022 ERROR [Thread-56]
> HiveSavedQueryMigrationImplementation:706 - Webhdfs exception
> java.lang.IllegalArgumentException: Can't get Kerberos realm
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:65)
> at
> org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:247)
> at
> org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:283)
> at
>
[jira] [Assigned] (AMBARI-19366) Hive-saved query and Pig script Migration is not working Hue-Ambari migration view
[
https://issues.apache.org/jira/browse/AMBARI-19366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar reassigned AMBARI-19366:
-
Assignee: Gaurav Nagar
> Hive-saved query and Pig script Migration is not working Hue-Ambari migration
> view
> --
>
> Key: AMBARI-19366
> URL: https://issues.apache.org/jira/browse/AMBARI-19366
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Pradarttana
>Assignee: Gaurav Nagar
> Attachments: AMBARI-19366.1.patch, AMBARI-19366.patch,
> AMBARI-19366_trunk.1.patch, AMBARI-19366_trunk.patch
>
>
> Hive-saved query and Pig script Migration is not working Hue-Ambari migration
> view
> Saying error
> {code}
> 04 Jan 2017 17:25:14,992 ERROR [Thread-56]
> HiveSavedQueryMigrationImplementation:618 - Webhdfs:
> java.lang.IllegalArgumentException: Can't get Kerberos realm
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:65)
> at
> org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:247)
> at
> org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:283)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryMigrationImplementation.createDirHive(HiveSavedQueryMigrationImplementation.java:603)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryMigrationUtility.hiveSavedQueryMigration(HiveSavedQueryMigrationUtility.java:214)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryStartJob.run(HiveSavedQueryStartJob.java:66)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor308.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.security.authentication.util.KerberosUtil.getDefaultRealm(KerberosUtil.java:75)
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:63)
> ... 5 more
> Caused by: KrbException: Cannot locate default realm
> at sun.security.krb5.Config.getDefaultRealm(Config.java:1181)
> ... 10 more
> 04 Jan 2017 17:25:15,008 ERROR [Thread-56]
> HiveSavedQueryMigrationImplementation:706 - Webhdfs exception
> java.lang.IllegalArgumentException: Can't get Kerberos realm
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:65)
> at
> org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:247)
> at
> org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:283)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryMigrationImplementation.putFileinHdfs(HiveSavedQueryMigrationImplementation.java:670)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryMigrationUtility.hiveSavedQueryMigration(HiveSavedQueryMigrationUtility.java:215)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryStartJob.run(HiveSavedQueryStartJob.java:66)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor308.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.security.authentication.util.KerberosUtil.getDefaultRealm(KerberosUtil.java:75)
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:63)
> ... 5 more
> Caused by: KrbException: Cannot locate default realm
> at sun.security.krb5.Config.getDefaultRealm(Config.java:1181)
> ... 10 more
> 04 Jan 2017 17:25:15,022 ERROR [Thread-56]
> HiveSavedQueryMigrationImplementation:706 - Webhdfs exception
> java.lang.IllegalArgumentException: Can't get Kerberos realm
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:65)
> at
> org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:247)
> at
> org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:283)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryMigrationImplementation.putFileinHdfs(HiveSavedQueryMigrationImplementation.java:670)
> at
>
[jira] [Updated] (AMBARI-19366) Hive-saved query and Pig script Migration is not working Hue-Ambari migration view
[
https://issues.apache.org/jira/browse/AMBARI-19366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-19366:
--
Assignee: (was: Gaurav Nagar)
> Hive-saved query and Pig script Migration is not working Hue-Ambari migration
> view
> --
>
> Key: AMBARI-19366
> URL: https://issues.apache.org/jira/browse/AMBARI-19366
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Pradarttana
> Attachments: AMBARI-19366.1.patch, AMBARI-19366.patch,
> AMBARI-19366_trunk.1.patch, AMBARI-19366_trunk.patch
>
>
> Hive-saved query and Pig script Migration is not working Hue-Ambari migration
> view
> Saying error
> {code}
> 04 Jan 2017 17:25:14,992 ERROR [Thread-56]
> HiveSavedQueryMigrationImplementation:618 - Webhdfs:
> java.lang.IllegalArgumentException: Can't get Kerberos realm
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:65)
> at
> org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:247)
> at
> org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:283)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryMigrationImplementation.createDirHive(HiveSavedQueryMigrationImplementation.java:603)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryMigrationUtility.hiveSavedQueryMigration(HiveSavedQueryMigrationUtility.java:214)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryStartJob.run(HiveSavedQueryStartJob.java:66)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor308.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.security.authentication.util.KerberosUtil.getDefaultRealm(KerberosUtil.java:75)
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:63)
> ... 5 more
> Caused by: KrbException: Cannot locate default realm
> at sun.security.krb5.Config.getDefaultRealm(Config.java:1181)
> ... 10 more
> 04 Jan 2017 17:25:15,008 ERROR [Thread-56]
> HiveSavedQueryMigrationImplementation:706 - Webhdfs exception
> java.lang.IllegalArgumentException: Can't get Kerberos realm
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:65)
> at
> org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:247)
> at
> org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:283)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryMigrationImplementation.putFileinHdfs(HiveSavedQueryMigrationImplementation.java:670)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryMigrationUtility.hiveSavedQueryMigration(HiveSavedQueryMigrationUtility.java:215)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryStartJob.run(HiveSavedQueryStartJob.java:66)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor308.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.security.authentication.util.KerberosUtil.getDefaultRealm(KerberosUtil.java:75)
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:63)
> ... 5 more
> Caused by: KrbException: Cannot locate default realm
> at sun.security.krb5.Config.getDefaultRealm(Config.java:1181)
> ... 10 more
> 04 Jan 2017 17:25:15,022 ERROR [Thread-56]
> HiveSavedQueryMigrationImplementation:706 - Webhdfs exception
> java.lang.IllegalArgumentException: Can't get Kerberos realm
> at
> org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:65)
> at
> org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:247)
> at
> org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:283)
> at
> org.apache.ambari.view.huetoambarimigration.migration.hive.savedquery.HiveSavedQueryMigrationImplementation.putFileinHdfs(HiveSavedQueryMigrationImplementation.java:670)
> at
>
[jira] [Updated] (AMBARI-19382) ATS service check failed on navigating to Hive View
[
https://issues.apache.org/jira/browse/AMBARI-19382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-19382:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.5 and trunk
> ATS service check failed on navigating to Hive View
> ---
>
> Key: AMBARI-19382
> URL: https://issues.apache.org/jira/browse/AMBARI-19382
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Anusha Bilgi
>Assignee: Gaurav Nagar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19382_branch-2.5.patch
>
>
> Logs:
> {code:java}
> 12 Dec 2016 15:39:56,099 INFO [ambari-client-thread-1258]
> ConfigurationBuilder:105 - HA HDFS cluster found.
> 12 Dec 2016 15:39:56,100 INFO [ambari-client-thread-1258]
> ConfigurationBuilder:120 - HdfsApi configured to connect to
> defaultFS='swebhdfs://nameservice'
> 12 Dec 2016 15:39:56,158 INFO [ambari-client-thread-1258] HdfsUtil:128 -
> HdfsApi connected OK
> 12 Dec 2016 15:39:56,286 INFO [ambari-client-thread-16522]
> ConfigurationBuilder:105 - HA HDFS cluster found.
> 12 Dec 2016 15:39:56,287 INFO [ambari-client-thread-16522]
> ConfigurationBuilder:120 - HdfsApi configured to connect to
> defaultFS='swebhdfs://nameservice'
> 12 Dec 2016 15:39:56,311 INFO [ambari-client-thread-16522] HdfsUtil:128 -
> HdfsApi connected OK
> 12 Dec 2016 15:40:43,945 ERROR [ambari-client-thread-36]
> LoggingSearchPropertyProvider:59 - Error occurred while making request to
> LogSearch service, unable to populate logging properties on this resource
> 12 Dec 2016 15:40:50,859 ERROR [ambari-client-thread-36]
> ContainerResponse:537 - Mapped exception to response: 500 (Internal Server
> Error)
> javax.ws.rs.WebApplicationException: java.net.ConnectException: Connection
> refused
> at
> org.apache.ambari.view.hive2.HelpService.atsStatus(HelpService.java:107)
> at sun.reflect.GeneratedMethodAccessor1163.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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.RightHandPathRule.accept(RightHandPathRule.java:147)
> 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)
> 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)
> 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)
> 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)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
>
[jira] [Updated] (AMBARI-19391) Password Should Not be in Clear Text while creating Hue-Ambari Migration View
[ https://issues.apache.org/jira/browse/AMBARI-19391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-19391: -- Status: Patch Available (was: Open) Committed to branch-2.5 and trunk > Password Should Not be in Clear Text while creating Hue-Ambari Migration View > - > > Key: AMBARI-19391 > URL: https://issues.apache.org/jira/browse/AMBARI-19391 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-19391.patch > > > While creating Hue-Ambari Migration View. We have to enter the Jdbc Passowrd > of Hue-database and Ambari-Database. > But those Password field are in clear text, which is not correct from a > security point of view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19385) Resolve variables in workflow if workflow path in coordinator contains variables.
[ https://issues.apache.org/jira/browse/AMBARI-19385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-19385: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk > Resolve variables in workflow if workflow path in coordinator contains > variables. > - > > Key: AMBARI-19385 > URL: https://issues.apache.org/jira/browse/AMBARI-19385 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19385_trunk.patch > > > Resolve variables in workflow ,if workflow path in coordinator contains > variables.. > Steps: > while creating coordinator use variables while configuring the workflow path. > User is not prompted for the variables in workflow. > Expected. > the variables in workflow should be prompted for user to submit. > Also need to add custom properties that the user can configure while > submitting workflow/coordinator/bundle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19391) Password Should Not be in Clear Text while creating Hue-Ambari Migration View
[ https://issues.apache.org/jira/browse/AMBARI-19391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-19391: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Password Should Not be in Clear Text while creating Hue-Ambari Migration View > - > > Key: AMBARI-19391 > URL: https://issues.apache.org/jira/browse/AMBARI-19391 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-19391.patch > > > While creating Hue-Ambari Migration View. We have to enter the Jdbc Passowrd > of Hue-database and Ambari-Database. > But those Password field are in clear text, which is not correct from a > security point of view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19391) Password Should Not be in Clear Text while creating Hue-Ambari Migration View
[ https://issues.apache.org/jira/browse/AMBARI-19391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-19391: -- Fix Version/s: (was: trunk) 2.5.0 > Password Should Not be in Clear Text while creating Hue-Ambari Migration View > - > > Key: AMBARI-19391 > URL: https://issues.apache.org/jira/browse/AMBARI-19391 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.5.0 > > Attachments: AMBARI-19391.patch > > > While creating Hue-Ambari Migration View. We have to enter the Jdbc Passowrd > of Hue-database and Ambari-Database. > But those Password field are in clear text, which is not correct from a > security point of view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19398) Namenode not resolved while submitting workflow in certain environments
[ https://issues.apache.org/jira/browse/AMBARI-19398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-19398: - Status: Patch Available (was: Open) > Namenode not resolved while submitting workflow in certain environments > --- > > Key: AMBARI-19398 > URL: https://issues.apache.org/jira/browse/AMBARI-19398 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19398_trunk.patch > > > Namenode is not resovled while creating configuration in job.properties while > submitting workflow in certain environments. > Step. > if the hdfs-site does not have dfs.namenode.rpc-address property workflow > submission fails. > Expected. > certain environments may not have dfs.namenode.rpc-address set, and in those > environments workflow should be submitted without error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19398) Namenode not resolved while submitting workflow in certain environments
[ https://issues.apache.org/jira/browse/AMBARI-19398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-19398: - Attachment: AMBARI-19398_trunk.patch > Namenode not resolved while submitting workflow in certain environments > --- > > Key: AMBARI-19398 > URL: https://issues.apache.org/jira/browse/AMBARI-19398 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19398_trunk.patch > > > Namenode is not resovled while creating configuration in job.properties while > submitting workflow in certain environments. > Step. > if the hdfs-site does not have dfs.namenode.rpc-address property workflow > submission fails. > Expected. > certain environments may not have dfs.namenode.rpc-address set, and in those > environments workflow should be submitted without error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19398) Namenode not resolved while submitting workflow in certain environments
Padma Priya Nagaraj created AMBARI-19398: Summary: Namenode not resolved while submitting workflow in certain environments Key: AMBARI-19398 URL: https://issues.apache.org/jira/browse/AMBARI-19398 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Fix For: 2.5.0 Namenode is not resovled while creating configuration in job.properties while submitting workflow in certain environments. Step. if the hdfs-site does not have dfs.namenode.rpc-address property workflow submission fails. Expected. certain environments may not have dfs.namenode.rpc-address set, and in those environments workflow should be submitted without error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19397) Infra Solr Upgrade support 2.4 -> 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-19397: Status: Patch Available (was: In Progress) > Infra Solr Upgrade support 2.4 -> 2.5 > - > > Key: AMBARI-19397 > URL: https://issues.apache.org/jira/browse/AMBARI-19397 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19397.patch > > > Upgrade Infra solr related properties for ambari 2.5.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19397) Infra Solr Upgrade support 2.4 -> 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-19397: Attachment: AMBARI-19397.patch > Infra Solr Upgrade support 2.4 -> 2.5 > - > > Key: AMBARI-19397 > URL: https://issues.apache.org/jira/browse/AMBARI-19397 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19397.patch > > > Upgrade Infra solr related properties for ambari 2.5.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19397) Infra Solr Upgrade support 2.4 -> 2.5
Miklos Gergely created AMBARI-19397: --- Summary: Infra Solr Upgrade support 2.4 -> 2.5 Key: AMBARI-19397 URL: https://issues.apache.org/jira/browse/AMBARI-19397 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.4.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 2.5.0 Upgrade Infra solr related properties for ambari 2.5.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19394) ambari-web action to download all client configs of a service
[ https://issues.apache.org/jira/browse/AMBARI-19394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803523#comment-15803523 ] Hudson commented on AMBARI-19394: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #651 (See [https://builds.apache.org/job/Ambari-branch-2.5/651/]) AMBARI-19394. ambari-web action to download all client configs of a (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f1cedfd89ebfd274f3d3e14769a9ea0db620e047]) * (edit) ambari-web/app/messages.js * (edit) ambari-web/test/controllers/main/service/item_test.js * (edit) ambari-web/app/controllers/main/service/item.js > ambari-web action to download all client configs of a service > - > > Key: AMBARI-19394 > URL: https://issues.apache.org/jira/browse/AMBARI-19394 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19394.trunk.v1.patch > > > Add a new ambari-web action to download all client configs of a service. This > action should be added in the submenu for "Download Client Conifgs" labelled > item in the service action -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19330) LogSearch upgrade support 2.4 -> 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803464#comment-15803464 ] Hudson commented on AMBARI-19330: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #650 (See [https://builds.apache.org/job/Ambari-branch-2.5/650/]) AMBARI-19330 LogSearch upgrade support 2.4 -> 2.5 (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=50e36c7f80b12b03106ab8277956d7999eb9b8da]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-web/app/data/HDP2/site_properties.js * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-system_log-env.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-log4j.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-output-config.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-properties.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-log4j.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-ambari-config.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-custom-logsearch-conf.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-env.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/logsearch-log4j.xml.j2 * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-audit_logs-solrconfig.xml > LogSearch upgrade support 2.4 -> 2.5 > > > Key: AMBARI-19330 > URL: https://issues.apache.org/jira/browse/AMBARI-19330 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19330.patch > > > Check configuration differences between logsearch in ambari version 2.4 and > 2.5. > Manually do a yum upgrade with new packages, then during ambari upgrade: > - check the new configurations are added properly > - implement renames/deletions in UpgradeCatalogXX.java > additional taks here (not really related with upgrade): > - config cleanup (check configuration dependencies, display names, typos etc.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19313) Improve and Fix "Hosts page" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803423#comment-15803423 ] Hudson commented on AMBARI-19313: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6373 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6373/]) AMBARI-19313. Improve and Fix 'Hosts page' after new guidelines.(xiwang) (xiwang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d243fea753edb39155f003058ee2e87828aa1955]) * (edit) ambari-web/app/styles/application.less > Improve and Fix "Hosts page" after new guidelines > - > > Key: AMBARI-19313 > URL: https://issues.apache.org/jira/browse/AMBARI-19313 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19313.patch > > > Hosts filter: > 1. Not aligned with Actions button. > 2. Filter dropdown menu, all host filter texts should be same font family as > other texts > 3. Remove icon has shadow, should not > Hosts table: > 4. Text in every table row was not centered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19395) Relax checkstyle rules since causing unit test failures
[
https://issues.apache.org/jira/browse/AMBARI-19395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803384#comment-15803384
]
Hadoop QA commented on AMBARI-19395:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845908/AMBARI-19395.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-admin ambari-server ambari-views utility.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9931//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9931//console
This message is automatically generated.
> Relax checkstyle rules since causing unit test failures
> ---
>
> Key: AMBARI-19395
> URL: https://issues.apache.org/jira/browse/AMBARI-19395
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: trunk
>
> Attachments: AMBARI-19395.patch
>
>
> Unit tests on Apache are failing because the checkstyle rules are too strict,
> especially when it comes to imports.
> Right now, it requires this, which I want to remove because it means that
> everyone has to use an IDE and setup the same rules for something that is
> trivial at compile-time and actually causes more headaches for developers.
> {code}
>
>
>
>
>
>
>
> {code}
> {noformat}
> [INFO] --- maven-checkstyle-plugin:2.17:check (checkstyle) @ ambari-server ---
> [INFO] Starting audit...
> [ERROR]
> /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/KerberosChecker.java:34:8:
> Unused import - com.sun.security.auth.callback.TextCallbackHandler.
> [UnusedImports]
> [ERROR]
> /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AmbariBasicAuthenticationFilterTest.java:41:
> Wrong order for 'org.easymock.EasyMockSupport' import. [ImportOrder]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19396) add services
[ https://issues.apache.org/jira/browse/AMBARI-19396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xlsong updated AMBARI-19396: Attachment: services.patch common-services.patch add services of AZKABAN DOCKER and ZEPPELIN > add services > > > Key: AMBARI-19396 > URL: https://issues.apache.org/jira/browse/AMBARI-19396 > Project: Ambari > Issue Type: Task > Components: ambari-server, stacks >Affects Versions: 2.2.1 >Reporter: xlsong > Labels: add, services > Fix For: 2.2.1 > > Attachments: common-services.patch, services.patch > > > add services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19396) add services
xlsong created AMBARI-19396: --- Summary: add services Key: AMBARI-19396 URL: https://issues.apache.org/jira/browse/AMBARI-19396 Project: Ambari Issue Type: Task Components: ambari-server, stacks Affects Versions: 2.2.1 Reporter: xlsong Fix For: 2.2.1 add services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19394) ambari-web action to download all client configs of a service
[ https://issues.apache.org/jira/browse/AMBARI-19394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803335#comment-15803335 ] Hudson commented on AMBARI-19394: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6372 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6372/]) AMBARI-19394. ambari-web action to download all client configs of a (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cae80946c98cb4ad9a44f99f66132ed149add50f]) * (edit) ambari-web/app/controllers/main/service/item.js * (edit) ambari-web/test/controllers/main/service/item_test.js * (edit) ambari-web/app/messages.js > ambari-web action to download all client configs of a service > - > > Key: AMBARI-19394 > URL: https://issues.apache.org/jira/browse/AMBARI-19394 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19394.trunk.v1.patch > > > Add a new ambari-web action to download all client configs of a service. This > action should be added in the submenu for "Download Client Conifgs" labelled > item in the service action -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19313) Improve and Fix "Hosts page" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19313: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Improve and Fix "Hosts page" after new guidelines > - > > Key: AMBARI-19313 > URL: https://issues.apache.org/jira/browse/AMBARI-19313 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19313.patch > > > Hosts filter: > 1. Not aligned with Actions button. > 2. Filter dropdown menu, all host filter texts should be same font family as > other texts > 3. Remove icon has shadow, should not > Hosts table: > 4. Text in every table row was not centered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19394) ambari-web action to download all client configs of a service
[ https://issues.apache.org/jira/browse/AMBARI-19394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19394: -- Resolution: Fixed Status: Resolved (was: Patch Available) Received +1 on reviewboard. Patch committed to trunk and branch-2.5 > ambari-web action to download all client configs of a service > - > > Key: AMBARI-19394 > URL: https://issues.apache.org/jira/browse/AMBARI-19394 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19394.trunk.v1.patch > > > Add a new ambari-web action to download all client configs of a service. This > action should be added in the submenu for "Download Client Conifgs" labelled > item in the service action -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19392) Status command executor may use obsolete settings
[
https://issues.apache.org/jira/browse/AMBARI-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803215#comment-15803215
]
Hadoop QA commented on AMBARI-19392:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845853/AMBARI-19392.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-agent.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9930//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9930//console
This message is automatically generated.
> Status command executor may use obsolete settings
> -
>
> Key: AMBARI-19392
> URL: https://issues.apache.org/jira/browse/AMBARI-19392
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19392.patch
>
>
> Ambari agent launches status command executor in a subprocess (since
> AMBARI-18505), passing an instance of {{config}}. Afterwards the agent may
> receive settings from the server in the response to registration. These new
> config values are not visible in the subprocess.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19395) Relax checkstyle rules since causing unit test failures
[
https://issues.apache.org/jira/browse/AMBARI-19395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-19395:
-
Description:
Unit tests on Apache are failing because the checkstyle rules are too strict,
especially when it comes to imports.
Right now, it requires this, which I want to remove because it means that
everyone has to use an IDE and setup the same rules for something that is
trivial at compile-time and actually causes more headaches for developers.
{code}
{code}
{noformat}
[INFO] --- maven-checkstyle-plugin:2.17:check (checkstyle) @ ambari-server ---
[INFO] Starting audit...
[ERROR]
/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/KerberosChecker.java:34:8:
Unused import - com.sun.security.auth.callback.TextCallbackHandler.
[UnusedImports]
[ERROR]
/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AmbariBasicAuthenticationFilterTest.java:41:
Wrong order for 'org.easymock.EasyMockSupport' import. [ImportOrder]
{noformat}
was:
Unit tests on Apache are failing because the checkstyle rules are too strict,
especially when it comes to imports.
Right now, it requires this, which I want to remove because it means that
everyone has to use an IDE and setup the same rules for something that is
trivial at compile-time and actually causes more headaches for developers.
{code}
{code}
> Relax checkstyle rules since causing unit test failures
> ---
>
> Key: AMBARI-19395
> URL: https://issues.apache.org/jira/browse/AMBARI-19395
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: trunk
>
> Attachments: AMBARI-19395.patch
>
>
> Unit tests on Apache are failing because the checkstyle rules are too strict,
> especially when it comes to imports.
> Right now, it requires this, which I want to remove because it means that
> everyone has to use an IDE and setup the same rules for something that is
> trivial at compile-time and actually causes more headaches for developers.
> {code}
>
>
>
>
>
>
>
> {code}
> {noformat}
> [INFO] --- maven-checkstyle-plugin:2.17:check (checkstyle) @ ambari-server ---
> [INFO] Starting audit...
> [ERROR]
> /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/KerberosChecker.java:34:8:
> Unused import - com.sun.security.auth.callback.TextCallbackHandler.
> [UnusedImports]
> [ERROR]
> /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AmbariBasicAuthenticationFilterTest.java:41:
> Wrong order for 'org.easymock.EasyMockSupport' import. [ImportOrder]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19394) ambari-web action to download all client configs of a service
[ https://issues.apache.org/jira/browse/AMBARI-19394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19394: -- Description: Add a new ambari-web action to download all client configs of a service. This action should be added in the submenu for "Download Client Conifgs" labelled item in the service action > ambari-web action to download all client configs of a service > - > > Key: AMBARI-19394 > URL: https://issues.apache.org/jira/browse/AMBARI-19394 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19394.trunk.v1.patch > > > Add a new ambari-web action to download all client configs of a service. This > action should be added in the submenu for "Download Client Conifgs" labelled > item in the service action -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19394) ambari-web action to download all client configs of a service
[ https://issues.apache.org/jira/browse/AMBARI-19394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19394: -- Status: Patch Available (was: Open) verified that patch works as expected on a cluster. verified that all ambari-web unit tests passes with the patch: 20121 passing (16s) 153 pending > ambari-web action to download all client configs of a service > - > > Key: AMBARI-19394 > URL: https://issues.apache.org/jira/browse/AMBARI-19394 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19394.trunk.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19394) ambari-web action to download all client configs of a service
[ https://issues.apache.org/jira/browse/AMBARI-19394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19394: -- Attachment: AMBARI-19394.trunk.v1.patch > ambari-web action to download all client configs of a service > - > > Key: AMBARI-19394 > URL: https://issues.apache.org/jira/browse/AMBARI-19394 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19394.trunk.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19395) Relax checkstyle rules since causing unit test failures
[
https://issues.apache.org/jira/browse/AMBARI-19395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-19395:
-
Status: Patch Available (was: Open)
> Relax checkstyle rules since causing unit test failures
> ---
>
> Key: AMBARI-19395
> URL: https://issues.apache.org/jira/browse/AMBARI-19395
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: trunk
>
> Attachments: AMBARI-19395.patch
>
>
> Unit tests on Apache are failing because the checkstyle rules are too strict,
> especially when it comes to imports.
> Right now, it requires this, which I want to remove because it means that
> everyone has to use an IDE and setup the same rules for something that is
> trivial at compile-time and actually causes more headaches for developers.
> {code}
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19395) Relax checkstyle rules since causing unit test failures
[
https://issues.apache.org/jira/browse/AMBARI-19395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-19395:
-
Attachment: AMBARI-19395.patch
> Relax checkstyle rules since causing unit test failures
> ---
>
> Key: AMBARI-19395
> URL: https://issues.apache.org/jira/browse/AMBARI-19395
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: trunk
>
> Attachments: AMBARI-19395.patch
>
>
> Unit tests on Apache are failing because the checkstyle rules are too strict,
> especially when it comes to imports.
> Right now, it requires this, which I want to remove because it means that
> everyone has to use an IDE and setup the same rules for something that is
> trivial at compile-time and actually causes more headaches for developers.
> {code}
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19395) Relax checkstyle rules since causing unit test failures
[
https://issues.apache.org/jira/browse/AMBARI-19395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-19395:
-
Summary: Relax checkstyle rules since causing unit test failures (was:
rules)
> Relax checkstyle rules since causing unit test failures
> ---
>
> Key: AMBARI-19395
> URL: https://issues.apache.org/jira/browse/AMBARI-19395
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: trunk
>
>
> Unit tests on Apache are failing because the checkstyle rules are too strict,
> especially when it comes to imports.
> Right now, it requires this, which I want to remove because it means that
> everyone has to use an IDE and setup the same rules for something that is
> trivial at compile-time and actually causes more headaches for developers.
> {code}
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19395) rules
Alejandro Fernandez created AMBARI-19395:
Summary: rules
Key: AMBARI-19395
URL: https://issues.apache.org/jira/browse/AMBARI-19395
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Fix For: trunk
Unit tests on Apache are failing because the checkstyle rules are too strict,
especially when it comes to imports.
Right now, it requires this, which I want to remove because it means that
everyone has to use an IDE and setup the same rules for something that is
trivial at compile-time and actually causes more headaches for developers.
{code}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19344) HOU Fails To Restart NameNode in non-HA Cluster
[
https://issues.apache.org/jira/browse/AMBARI-19344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803098#comment-15803098
]
Hadoop QA commented on AMBARI-19344:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845860/AMBARI-19344.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-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9928//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9928//console
This message is automatically generated.
> HOU Fails To Restart NameNode in non-HA Cluster
> ---
>
> Key: AMBARI-19344
> URL: https://issues.apache.org/jira/browse/AMBARI-19344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: host_ordered_upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19344.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 with Ambari-2.5.0.0-547 build (non-HA cluster)
> # Start Host Ordered Upgrade to HDP-2.5.3
>
> *Result:* Error at pre Upgrade HDFS step
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 156, in
> ExecuteUpgradeTasks().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 153, in actionexecute
> shell.checked_call(task.command, logoutput=True, quiet=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'source
> /var/lib/ambari-agent/ambari-env.sh ; /usr/bin/ambari-python-wrap
> /var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
> prepare_rolling_upgrade /var/lib/ambari-agent/data/command-111.json
> /var/lib/ambari-agent/cache/custom_actions
> /var/lib/ambari-agent/data/structured-out-111.json INFO
> /var/lib/ambari-agent/tmp' returned 1. 2017-01-03 17:07:47,095 - In the
> middle of a stack upgrade/downgrade for Stack HDP and destination version
> 2.5.3.0-37, determining which hadoop conf dir to use.
> 2017-01-03 17:07:47,096 - Hadoop conf dir: /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-01-03 17:07:47,096 - The hadoop conf dir /usr/hdp/2.5.3.0-37/hadoop/conf
> exists, will call conf-select on it for version 2.5.3.0-37
> 2017-01-03 17:07:47,096 - Checking if need to create versioned conf dir
> /etc/hadoop/2.5.3.0-37/0
> 2017-01-03 17:07:47,097 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'create-conf-dir', '--package', 'hadoop', '--stack-version', '2.5.3.0-37',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-01-03 17:07:47,141 - call returned (1, '/etc/hadoop/2.5.3.0-37/0 exist
> already', '')
> 2017-01-03 17:07:47,141 - checked_call[('ambari-python-wrap',
> '/usr/bin/conf-select', 'set-conf-dir', '--package', 'hadoop',
> '--stack-version', '2.5.3.0-37', '--conf-version', '0')] {'logoutput': False,
> 'sudo': True, 'quiet': False}
> 2017-01-03 17:07:47,179 - checked_call returned (0, '')
> 2017-01-03 17:07:47,180 - Ensuring that hadoop has the correct symlink
> structure
> 2017-01-03 17:07:47,180 - Using hadoop conf dir:
> /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-01-03 17:07:47,182 - Stack Feature Version Info: stack_version=2.5,
> version=2.5.3.0-37, current_cluster_version=2.5.0.0-1245,
> upgrade_direction=upgrade -> 2.5.3.0-37
>
[jira] [Updated] (AMBARI-19394) ambari-web action to download all client configs of a service
[ https://issues.apache.org/jira/browse/AMBARI-19394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19394: -- Issue Type: Task (was: Bug) > ambari-web action to download all client configs of a service > - > > Key: AMBARI-19394 > URL: https://issues.apache.org/jira/browse/AMBARI-19394 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19394) ambari-web action to download all client configs of a service
Jaimin Jetly created AMBARI-19394: - Summary: ambari-web action to download all client configs of a service Key: AMBARI-19394 URL: https://issues.apache.org/jira/browse/AMBARI-19394 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Jaimin Jetly Assignee: Jaimin Jetly Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19330) LogSearch upgrade support 2.4 -> 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803069#comment-15803069 ] Hudson commented on AMBARI-19330: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6371 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6371/]) AMBARI-19330 LogSearch upgrade support 2.4 -> 2.5 (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b46a2f627e2137f2f361239f944869cf0e0dfd1d]) * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-audit_logs-solrconfig.xml * (edit) ambari-web/app/data/configs/services/logsearch_properties.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/logsearch-log4j.xml.j2 * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-ambari-config.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-log4j.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-output-config.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-log4j.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-properties.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-custom-logsearch-conf.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-env.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-system_log-env.xml > LogSearch upgrade support 2.4 -> 2.5 > > > Key: AMBARI-19330 > URL: https://issues.apache.org/jira/browse/AMBARI-19330 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19330.patch > > > Check configuration differences between logsearch in ambari version 2.4 and > 2.5. > Manually do a yum upgrade with new packages, then during ambari upgrade: > - check the new configurations are added properly > - implement renames/deletions in UpgradeCatalogXX.java > additional taks here (not really related with upgrade): > - config cleanup (check configuration dependencies, display names, typos etc.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19313) Improve and Fix "Hosts page" after new guidelines
[
https://issues.apache.org/jira/browse/AMBARI-19313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803044#comment-15803044
]
Hadoop QA commented on AMBARI-19313:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845861/AMBARI-19313.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/9927//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9927//console
This message is automatically generated.
> Improve and Fix "Hosts page" after new guidelines
> -
>
> Key: AMBARI-19313
> URL: https://issues.apache.org/jira/browse/AMBARI-19313
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19313.patch
>
>
> Hosts filter:
> 1. Not aligned with Actions button.
> 2. Filter dropdown menu, all host filter texts should be same font family as
> other texts
> 3. Remove icon has shadow, should not
> Hosts table:
> 4. Text in every table row was not centered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-19330) LogSearch upgrade support 2.4 -> 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely resolved AMBARI-19330. - Resolution: Fixed > LogSearch upgrade support 2.4 -> 2.5 > > > Key: AMBARI-19330 > URL: https://issues.apache.org/jira/browse/AMBARI-19330 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19330.patch > > > Check configuration differences between logsearch in ambari version 2.4 and > 2.5. > Manually do a yum upgrade with new packages, then during ambari upgrade: > - check the new configurations are added properly > - implement renames/deletions in UpgradeCatalogXX.java > additional taks here (not really related with upgrade): > - config cleanup (check configuration dependencies, display names, typos etc.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19373) Grafana datasource changes to accommodate new visualizations for TopN
[
https://issues.apache.org/jira/browse/AMBARI-19373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802973#comment-15802973
]
Hadoop QA commented on AMBARI-19373:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845895/AMBARI-19373.v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9926//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9926//console
This message is automatically generated.
> Grafana datasource changes to accommodate new visualizations for TopN
> -
>
> Key: AMBARI-19373
> URL: https://issues.apache.org/jira/browse/AMBARI-19373
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19373.v1.patch, AMBARI-19373.v2.patch
>
>
> We need a visualization of a scatter plot for NNTop metrics for HDFS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19330) LogSearch upgrade support 2.4 -> 2.5
[
https://issues.apache.org/jira/browse/AMBARI-19330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802968#comment-15802968
]
Miklos Gergely commented on AMBARI-19330:
-
committed to trunk:
{code:java}
commit b46a2f627e2137f2f361239f944869cf0e0dfd1d
Author: Miklos Gergely
Date: Fri Jan 6 01:10:46 2017 +0100
AMBARI-19330 LogSearch upgrade support 2.4 -> 2.5
Change-Id: I1fd3ac23499eba6a96e1c3297f6895cc5b36a956
{code}
committed to branch-2.5:
{code:java}
commit 50e36c7f80b12b03106ab8277956d7999eb9b8da
Author: Miklos Gergely
Date: Fri Jan 6 00:39:08 2017 +0100
AMBARI-19330 LogSearch upgrade support 2.4 -> 2.5
Change-Id: If6d7a7f94c2e858cbd7d73ad0c9440aeec89c0ab
{code}
> LogSearch upgrade support 2.4 -> 2.5
>
>
> Key: AMBARI-19330
> URL: https://issues.apache.org/jira/browse/AMBARI-19330
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19330.patch
>
>
> Check configuration differences between logsearch in ambari version 2.4 and
> 2.5.
> Manually do a yum upgrade with new packages, then during ambari upgrade:
> - check the new configurations are added properly
> - implement renames/deletions in UpgradeCatalogXX.java
> additional taks here (not really related with upgrade):
> - config cleanup (check configuration dependencies, display names, typos etc.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19393) Cluster User role is able to view auto start page
[ https://issues.apache.org/jira/browse/AMBARI-19393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802937#comment-15802937 ] Hudson commented on AMBARI-19393: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #649 (See [https://builds.apache.org/job/Ambari-branch-2.5/649/]) AMBARI-19393 - Cluster User role is able to view auto start page (rzang) (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8ca19525a59d9ee512df12d2110f6e8f1453f87a]) * (edit) ambari-web/app/routes/main.js > Cluster User role is able to view auto start page > - > > Key: AMBARI-19393 > URL: https://issues.apache.org/jira/browse/AMBARI-19393 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19393.patch > > > When logged in with Cluster User role, if auto start page url is pasted it > should directly navigate to dashboard page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19373) Grafana datasource changes to accommodate new visualizations for TopN
[ https://issues.apache.org/jira/browse/AMBARI-19373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19373: Attachment: AMBARI-19373.v2.patch > Grafana datasource changes to accommodate new visualizations for TopN > - > > Key: AMBARI-19373 > URL: https://issues.apache.org/jira/browse/AMBARI-19373 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19373.v1.patch, AMBARI-19373.v2.patch > > > We need a visualization of a scatter plot for NNTop metrics for HDFS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19365) Executing ambari-server unit tests with JDK 1.8 results in unit test failures
[
https://issues.apache.org/jira/browse/AMBARI-19365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802813#comment-15802813
]
Hudson commented on AMBARI-19365:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6369 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6369/])
Revert "AMBARI-19365. Executing ambari-server unit tests with JDK 1.8 (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9109d1c3b9c20c98310472c05b1572d744c58363])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/KerberosChecker.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/utilities/KerberosCheckerTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/JvmMetricsSourceTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AmbariBasicAuthenticationFilterTest.java
* (delete)
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/LoginContextHelper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/view/persistence/DataStoreImplTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog222Test.java
AMBARI-19365. Executing ambari-server unit tests with JDK 1.8 results in
(rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bd1b744403bfa9c6e6aaf02e7c56062e7fdb21cd])
* (add)
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/LoginContextHelper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog222Test.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/JvmMetricsSourceTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/utilities/KerberosCheckerTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/view/persistence/DataStoreImplTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AmbariBasicAuthenticationFilterTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/KerberosChecker.java
> Executing ambari-server unit tests with JDK 1.8 results in unit test failures
> -
>
> Key: AMBARI-19365
> URL: https://issues.apache.org/jira/browse/AMBARI-19365
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: jdk1_8, unit-test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19365_branch-2.5_01.patch,
> AMBARI-19365_trunk_01.patch
>
>
> Following unit tests fails when executed with JDK 1.8
> {code}
> mvn test -Dtest=DataStoreImplTest
> mvn clean test -Dtest=UpgradeCatalog222Test
> mvn test -Dtest=KerberosCheckerTest,AmbariBasicAuthenticationFilterTest
> {code}
> Same unit tests passes if the environment is switched to use JDK 1.7
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19393) Cluster User role is able to view auto start page
[ https://issues.apache.org/jira/browse/AMBARI-19393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19393: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 33239523dcc0e226171fa7a699194e9bdb33ab4b > Cluster User role is able to view auto start page > - > > Key: AMBARI-19393 > URL: https://issues.apache.org/jira/browse/AMBARI-19393 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19393.patch > > > When logged in with Cluster User role, if auto start page url is pasted it > should directly navigate to dashboard page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19393) Cluster User role is able to view auto start page
[ https://issues.apache.org/jira/browse/AMBARI-19393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19393: -- Status: Patch Available (was: Open) > Cluster User role is able to view auto start page > - > > Key: AMBARI-19393 > URL: https://issues.apache.org/jira/browse/AMBARI-19393 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19393.patch > > > When logged in with Cluster User role, if auto start page url is pasted it > should directly navigate to dashboard page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19393) Cluster User role is able to view auto start page
[ https://issues.apache.org/jira/browse/AMBARI-19393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19393: -- Attachment: AMBARI-19393.patch > Cluster User role is able to view auto start page > - > > Key: AMBARI-19393 > URL: https://issues.apache.org/jira/browse/AMBARI-19393 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19393.patch > > > When logged in with Cluster User role, if auto start page url is pasted it > should directly navigate to dashboard page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-19365) Executing ambari-server unit tests with JDK 1.8 results in unit test failures
[
https://issues.apache.org/jira/browse/AMBARI-19365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas resolved AMBARI-19365.
---
Resolution: Fixed
Fixed checkstyle issues in trunk
{noformat}
commit bd1b744403bfa9c6e6aaf02e7c56062e7fdb21cd
Author: Robert Levas
Date: Thu Jan 5 17:33:03 2017 -0500
{noformat}
> Executing ambari-server unit tests with JDK 1.8 results in unit test failures
> -
>
> Key: AMBARI-19365
> URL: https://issues.apache.org/jira/browse/AMBARI-19365
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: jdk1_8, unit-test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19365_branch-2.5_01.patch,
> AMBARI-19365_trunk_01.patch
>
>
> Following unit tests fails when executed with JDK 1.8
> {code}
> mvn test -Dtest=DataStoreImplTest
> mvn clean test -Dtest=UpgradeCatalog222Test
> mvn test -Dtest=KerberosCheckerTest,AmbariBasicAuthenticationFilterTest
> {code}
> Same unit tests passes if the environment is switched to use JDK 1.7
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (AMBARI-19365) Executing ambari-server unit tests with JDK 1.8 results in unit test failures
[
https://issues.apache.org/jira/browse/AMBARI-19365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas reopened AMBARI-19365:
---
Reverting commit 5e72ee6f2c6ebcda105e521d819f95ffde1b245e on trunk to fix
checkstyle issues.
{noformat}
commit 9109d1c3b9c20c98310472c05b1572d744c58363
Author: Robert Levas
Date: Thu Jan 5 16:49:15 2017 -0500
{noformat}
> Executing ambari-server unit tests with JDK 1.8 results in unit test failures
> -
>
> Key: AMBARI-19365
> URL: https://issues.apache.org/jira/browse/AMBARI-19365
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: jdk1_8, unit-test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19365_branch-2.5_01.patch,
> AMBARI-19365_trunk_01.patch
>
>
> Following unit tests fails when executed with JDK 1.8
> {code}
> mvn test -Dtest=DataStoreImplTest
> mvn clean test -Dtest=UpgradeCatalog222Test
> mvn test -Dtest=KerberosCheckerTest,AmbariBasicAuthenticationFilterTest
> {code}
> Same unit tests passes if the environment is switched to use JDK 1.7
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19393) Cluster User role is able to view auto start page
Richard Zang created AMBARI-19393: - Summary: Cluster User role is able to view auto start page Key: AMBARI-19393 URL: https://issues.apache.org/jira/browse/AMBARI-19393 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.5.0 When logged in with Cluster User role, if auto start page url is pasted it should directly navigate to dashboard page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19373) Grafana datasource changes to accommodate new visualizations for TopN
[ https://issues.apache.org/jira/browse/AMBARI-19373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19373: Attachment: AMBARI-19373.v1.patch > Grafana datasource changes to accommodate new visualizations for TopN > - > > Key: AMBARI-19373 > URL: https://issues.apache.org/jira/browse/AMBARI-19373 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19373.v1.patch > > > We need a visualization of a scatter plot for NNTop metrics for HDFS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19373) Grafana datasource changes to accommodate new visualizations for TopN
[ https://issues.apache.org/jira/browse/AMBARI-19373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19373: Status: Patch Available (was: In Progress) > Grafana datasource changes to accommodate new visualizations for TopN > - > > Key: AMBARI-19373 > URL: https://issues.apache.org/jira/browse/AMBARI-19373 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19373.v1.patch > > > We need a visualization of a scatter plot for NNTop metrics for HDFS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19313) Improve and Fix "Hosts page" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19313: - Status: Patch Available (was: Open) > Improve and Fix "Hosts page" after new guidelines > - > > Key: AMBARI-19313 > URL: https://issues.apache.org/jira/browse/AMBARI-19313 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19313.patch > > > Hosts filter: > 1. Not aligned with Actions button. > 2. Filter dropdown menu, all host filter texts should be same font family as > other texts > 3. Remove icon has shadow, should not > Hosts table: > 4. Text in every table row was not centered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19313) Improve and Fix "Hosts page" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19313: - Attachment: AMBARI-19313.patch > Improve and Fix "Hosts page" after new guidelines > - > > Key: AMBARI-19313 > URL: https://issues.apache.org/jira/browse/AMBARI-19313 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19313.patch > > > Hosts filter: > 1. Not aligned with Actions button. > 2. Filter dropdown menu, all host filter texts should be same font family as > other texts > 3. Remove icon has shadow, should not > Hosts table: > 4. Text in every table row was not centered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19313) Improve and Fix "Hosts page" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802666#comment-15802666 ] Xi Wang commented on AMBARI-19313: -- 19976 passing (20s) 153 pending > Improve and Fix "Hosts page" after new guidelines > - > > Key: AMBARI-19313 > URL: https://issues.apache.org/jira/browse/AMBARI-19313 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > > Hosts filter: > 1. Not aligned with Actions button. > 2. Filter dropdown menu, all host filter texts should be same font family as > other texts > 3. Remove icon has shadow, should not > Hosts table: > 4. Text in every table row was not centered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19344) HOU Fails To Restart NameNode in non-HA Cluster
[
https://issues.apache.org/jira/browse/AMBARI-19344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19344:
-
Status: Patch Available (was: Open)
> HOU Fails To Restart NameNode in non-HA Cluster
> ---
>
> Key: AMBARI-19344
> URL: https://issues.apache.org/jira/browse/AMBARI-19344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: host_ordered_upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19344.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 with Ambari-2.5.0.0-547 build (non-HA cluster)
> # Start Host Ordered Upgrade to HDP-2.5.3
>
> *Result:* Error at pre Upgrade HDFS step
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 156, in
> ExecuteUpgradeTasks().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 153, in actionexecute
> shell.checked_call(task.command, logoutput=True, quiet=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'source
> /var/lib/ambari-agent/ambari-env.sh ; /usr/bin/ambari-python-wrap
> /var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
> prepare_rolling_upgrade /var/lib/ambari-agent/data/command-111.json
> /var/lib/ambari-agent/cache/custom_actions
> /var/lib/ambari-agent/data/structured-out-111.json INFO
> /var/lib/ambari-agent/tmp' returned 1. 2017-01-03 17:07:47,095 - In the
> middle of a stack upgrade/downgrade for Stack HDP and destination version
> 2.5.3.0-37, determining which hadoop conf dir to use.
> 2017-01-03 17:07:47,096 - Hadoop conf dir: /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-01-03 17:07:47,096 - The hadoop conf dir /usr/hdp/2.5.3.0-37/hadoop/conf
> exists, will call conf-select on it for version 2.5.3.0-37
> 2017-01-03 17:07:47,096 - Checking if need to create versioned conf dir
> /etc/hadoop/2.5.3.0-37/0
> 2017-01-03 17:07:47,097 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'create-conf-dir', '--package', 'hadoop', '--stack-version', '2.5.3.0-37',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-01-03 17:07:47,141 - call returned (1, '/etc/hadoop/2.5.3.0-37/0 exist
> already', '')
> 2017-01-03 17:07:47,141 - checked_call[('ambari-python-wrap',
> '/usr/bin/conf-select', 'set-conf-dir', '--package', 'hadoop',
> '--stack-version', '2.5.3.0-37', '--conf-version', '0')] {'logoutput': False,
> 'sudo': True, 'quiet': False}
> 2017-01-03 17:07:47,179 - checked_call returned (0, '')
> 2017-01-03 17:07:47,180 - Ensuring that hadoop has the correct symlink
> structure
> 2017-01-03 17:07:47,180 - Using hadoop conf dir:
> /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-01-03 17:07:47,182 - Stack Feature Version Info: stack_version=2.5,
> version=2.5.3.0-37, current_cluster_version=2.5.0.0-1245,
> upgrade_direction=upgrade -> 2.5.3.0-37
> 2017-01-03 17:07:47,185 - In the middle of a stack upgrade/downgrade for
> Stack HDP and destination version 2.5.3.0-37, determining which hadoop conf
> dir to use.
> 2017-01-03 17:07:47,185 - Hadoop conf dir: /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-01-03 17:07:47,186 - The hadoop conf dir /usr/hdp/2.5.3.0-37/hadoop/conf
> exists, will call conf-select on it for version 2.5.3.0-37
> 2017-01-03 17:07:47,186 - Checking if need to create versioned conf dir
> /etc/hadoop/2.5.3.0-37/0
> 2017-01-03 17:07:47,187 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'create-conf-dir', '--package', 'hadoop', '--stack-version', '2.5.3.0-37',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-01-03 17:07:47,224 - call returned (1, '/etc/hadoop/2.5.3.0-37/0 exist
> already', '')
> 2017-01-03 17:07:47,225 - checked_call[('ambari-python-wrap',
>
[jira] [Updated] (AMBARI-19344) HOU Fails To Restart NameNode in non-HA Cluster
[
https://issues.apache.org/jira/browse/AMBARI-19344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19344:
-
Attachment: AMBARI-19344.patch
> HOU Fails To Restart NameNode in non-HA Cluster
> ---
>
> Key: AMBARI-19344
> URL: https://issues.apache.org/jira/browse/AMBARI-19344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: host_ordered_upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19344.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 with Ambari-2.5.0.0-547 build (non-HA cluster)
> # Start Host Ordered Upgrade to HDP-2.5.3
>
> *Result:* Error at pre Upgrade HDFS step
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 156, in
> ExecuteUpgradeTasks().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 153, in actionexecute
> shell.checked_call(task.command, logoutput=True, quiet=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'source
> /var/lib/ambari-agent/ambari-env.sh ; /usr/bin/ambari-python-wrap
> /var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
> prepare_rolling_upgrade /var/lib/ambari-agent/data/command-111.json
> /var/lib/ambari-agent/cache/custom_actions
> /var/lib/ambari-agent/data/structured-out-111.json INFO
> /var/lib/ambari-agent/tmp' returned 1. 2017-01-03 17:07:47,095 - In the
> middle of a stack upgrade/downgrade for Stack HDP and destination version
> 2.5.3.0-37, determining which hadoop conf dir to use.
> 2017-01-03 17:07:47,096 - Hadoop conf dir: /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-01-03 17:07:47,096 - The hadoop conf dir /usr/hdp/2.5.3.0-37/hadoop/conf
> exists, will call conf-select on it for version 2.5.3.0-37
> 2017-01-03 17:07:47,096 - Checking if need to create versioned conf dir
> /etc/hadoop/2.5.3.0-37/0
> 2017-01-03 17:07:47,097 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'create-conf-dir', '--package', 'hadoop', '--stack-version', '2.5.3.0-37',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-01-03 17:07:47,141 - call returned (1, '/etc/hadoop/2.5.3.0-37/0 exist
> already', '')
> 2017-01-03 17:07:47,141 - checked_call[('ambari-python-wrap',
> '/usr/bin/conf-select', 'set-conf-dir', '--package', 'hadoop',
> '--stack-version', '2.5.3.0-37', '--conf-version', '0')] {'logoutput': False,
> 'sudo': True, 'quiet': False}
> 2017-01-03 17:07:47,179 - checked_call returned (0, '')
> 2017-01-03 17:07:47,180 - Ensuring that hadoop has the correct symlink
> structure
> 2017-01-03 17:07:47,180 - Using hadoop conf dir:
> /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-01-03 17:07:47,182 - Stack Feature Version Info: stack_version=2.5,
> version=2.5.3.0-37, current_cluster_version=2.5.0.0-1245,
> upgrade_direction=upgrade -> 2.5.3.0-37
> 2017-01-03 17:07:47,185 - In the middle of a stack upgrade/downgrade for
> Stack HDP and destination version 2.5.3.0-37, determining which hadoop conf
> dir to use.
> 2017-01-03 17:07:47,185 - Hadoop conf dir: /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-01-03 17:07:47,186 - The hadoop conf dir /usr/hdp/2.5.3.0-37/hadoop/conf
> exists, will call conf-select on it for version 2.5.3.0-37
> 2017-01-03 17:07:47,186 - Checking if need to create versioned conf dir
> /etc/hadoop/2.5.3.0-37/0
> 2017-01-03 17:07:47,187 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'create-conf-dir', '--package', 'hadoop', '--stack-version', '2.5.3.0-37',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-01-03 17:07:47,224 - call returned (1, '/etc/hadoop/2.5.3.0-37/0 exist
> already', '')
> 2017-01-03 17:07:47,225 - checked_call[('ambari-python-wrap',
>
[jira] [Commented] (AMBARI-19316) Zeppelin stop failed during EU while deleting pid file with customized service user
[
https://issues.apache.org/jira/browse/AMBARI-19316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802618#comment-15802618
]
Yusaku Sako commented on AMBARI-19316:
--
After revert, the Zeppelin-related unit test failures are gone. The failure
reported is related to Hive LLAP.
> Zeppelin stop failed during EU while deleting pid file with customized
> service user
> ---
>
> Key: AMBARI-19316
> URL: https://issues.apache.org/jira/browse/AMBARI-19316
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Renjith Kamath
>Priority: Critical
> Labels: express_upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19316-branch-2.5-v1.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 cluster with Ambari-2.5.0.0 (customized service users
> enabled for all services including Zeppelin)
> # Start Express Upgrade to 2.6.0.0-267
> *Result:*
> Observed error while stopping Zeppelin notebook
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 361, in
> Master().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 159, in stop
> user=params.zeppelin_user)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh stop >>
> /grid/0/log/zeppelin/zeppelin-setup.log' returned 1. Hortonworks
> #
> This is MOTD message, added for testing in qe infra
> rm: cannot remove
> ‘/var/run/zeppelin/zeppelin-cstm-zeppelin-ctr-e85-1482808692054-0723-01-03.hwx.site.pid’:
> Permission denied
> rm: cannot remove
> ‘/var/run/zeppelin/zeppelin-cstm-zeppelin-ctr-e85-1482808692054-0723-01-03.hwx.site.pid’:
> Permission denied
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19389) Authentication negotiation HTTP response should be sent when Kerberos authentication is enabled
[
https://issues.apache.org/jira/browse/AMBARI-19389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19389:
--
Status: Patch Available (was: In Progress)
> Authentication negotiation HTTP response should be sent when Kerberos
> authentication is enabled
> ---
>
> Key: AMBARI-19389
> URL: https://issues.apache.org/jira/browse/AMBARI-19389
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: authentication, kerberos, security
> Fix For: 2.5.0
>
> Attachments: AMBARI-19389_branch-2.5_01.patch,
> AMBARI-19389_trunk_01.patch
>
>
> Authentication negotiation HTTP response should be automatically sent when
> needed when Kerberos authentication is enabled.
> The expected HTTP response during authentication failure when Kerberos
> authentication into Ambari is enabled is as follows:
> {noformat}
> HTTP/1.1 401 Authentication requested
> WWW-Authenticate: Negotiate
> {noformat}
> When Kerberos authentication into Ambari is not enabled the expected HTTP
> response for an authentication failure is:
> {noformat}
> HTTP/1.1 403 Missing authentication token
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19389) Authentication negotiation HTTP response should be sent when Kerberos authentication is enabled
[
https://issues.apache.org/jira/browse/AMBARI-19389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19389:
--
Attachment: AMBARI-19389_trunk_01.patch
AMBARI-19389_branch-2.5_01.patch
> Authentication negotiation HTTP response should be sent when Kerberos
> authentication is enabled
> ---
>
> Key: AMBARI-19389
> URL: https://issues.apache.org/jira/browse/AMBARI-19389
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: authentication, kerberos, security
> Fix For: 2.5.0
>
> Attachments: AMBARI-19389_branch-2.5_01.patch,
> AMBARI-19389_trunk_01.patch
>
>
> Authentication negotiation HTTP response should be automatically sent when
> needed when Kerberos authentication is enabled.
> The expected HTTP response during authentication failure when Kerberos
> authentication into Ambari is enabled is as follows:
> {noformat}
> HTTP/1.1 401 Authentication requested
> WWW-Authenticate: Negotiate
> {noformat}
> When Kerberos authentication into Ambari is not enabled the expected HTTP
> response for an authentication failure is:
> {noformat}
> HTTP/1.1 403 Missing authentication token
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19344) HOU Fails To Restart NameNode in non-HA Cluster
[
https://issues.apache.org/jira/browse/AMBARI-19344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19344:
-
Summary: HOU Fails To Restart NameNode in non-HA Cluster (was: HOU failed
at pre Upgrade HDFS step on non-HA cluster)
> HOU Fails To Restart NameNode in non-HA Cluster
> ---
>
> Key: AMBARI-19344
> URL: https://issues.apache.org/jira/browse/AMBARI-19344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Priority: Critical
> Labels: host_ordered_upgrade
> Fix For: 2.5.0
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 with Ambari-2.5.0.0-547 build (non-HA cluster)
> # Start Host Ordered Upgrade to HDP-2.5.3
>
> *Result:* Error at pre Upgrade HDFS step
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 156, in
> ExecuteUpgradeTasks().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 153, in actionexecute
> shell.checked_call(task.command, logoutput=True, quiet=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'source
> /var/lib/ambari-agent/ambari-env.sh ; /usr/bin/ambari-python-wrap
> /var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
> prepare_rolling_upgrade /var/lib/ambari-agent/data/command-111.json
> /var/lib/ambari-agent/cache/custom_actions
> /var/lib/ambari-agent/data/structured-out-111.json INFO
> /var/lib/ambari-agent/tmp' returned 1. 2017-01-03 17:07:47,095 - In the
> middle of a stack upgrade/downgrade for Stack HDP and destination version
> 2.5.3.0-37, determining which hadoop conf dir to use.
> 2017-01-03 17:07:47,096 - Hadoop conf dir: /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-01-03 17:07:47,096 - The hadoop conf dir /usr/hdp/2.5.3.0-37/hadoop/conf
> exists, will call conf-select on it for version 2.5.3.0-37
> 2017-01-03 17:07:47,096 - Checking if need to create versioned conf dir
> /etc/hadoop/2.5.3.0-37/0
> 2017-01-03 17:07:47,097 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'create-conf-dir', '--package', 'hadoop', '--stack-version', '2.5.3.0-37',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-01-03 17:07:47,141 - call returned (1, '/etc/hadoop/2.5.3.0-37/0 exist
> already', '')
> 2017-01-03 17:07:47,141 - checked_call[('ambari-python-wrap',
> '/usr/bin/conf-select', 'set-conf-dir', '--package', 'hadoop',
> '--stack-version', '2.5.3.0-37', '--conf-version', '0')] {'logoutput': False,
> 'sudo': True, 'quiet': False}
> 2017-01-03 17:07:47,179 - checked_call returned (0, '')
> 2017-01-03 17:07:47,180 - Ensuring that hadoop has the correct symlink
> structure
> 2017-01-03 17:07:47,180 - Using hadoop conf dir:
> /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-01-03 17:07:47,182 - Stack Feature Version Info: stack_version=2.5,
> version=2.5.3.0-37, current_cluster_version=2.5.0.0-1245,
> upgrade_direction=upgrade -> 2.5.3.0-37
> 2017-01-03 17:07:47,185 - In the middle of a stack upgrade/downgrade for
> Stack HDP and destination version 2.5.3.0-37, determining which hadoop conf
> dir to use.
> 2017-01-03 17:07:47,185 - Hadoop conf dir: /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-01-03 17:07:47,186 - The hadoop conf dir /usr/hdp/2.5.3.0-37/hadoop/conf
> exists, will call conf-select on it for version 2.5.3.0-37
> 2017-01-03 17:07:47,186 - Checking if need to create versioned conf dir
> /etc/hadoop/2.5.3.0-37/0
> 2017-01-03 17:07:47,187 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'create-conf-dir', '--package', 'hadoop', '--stack-version', '2.5.3.0-37',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-01-03 17:07:47,224 - call returned (1, '/etc/hadoop/2.5.3.0-37/0 exist
> already', '')
> 2017-01-03 17:07:47,225 - checked_call[('ambari-python-wrap',
>
[jira] [Assigned] (AMBARI-19344) HOU Fails To Restart NameNode in non-HA Cluster
[
https://issues.apache.org/jira/browse/AMBARI-19344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley reassigned AMBARI-19344:
Assignee: Jonathan Hurley
> HOU Fails To Restart NameNode in non-HA Cluster
> ---
>
> Key: AMBARI-19344
> URL: https://issues.apache.org/jira/browse/AMBARI-19344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: host_ordered_upgrade
> Fix For: 2.5.0
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 with Ambari-2.5.0.0-547 build (non-HA cluster)
> # Start Host Ordered Upgrade to HDP-2.5.3
>
> *Result:* Error at pre Upgrade HDFS step
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 156, in
> ExecuteUpgradeTasks().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 153, in actionexecute
> shell.checked_call(task.command, logoutput=True, quiet=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'source
> /var/lib/ambari-agent/ambari-env.sh ; /usr/bin/ambari-python-wrap
> /var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
> prepare_rolling_upgrade /var/lib/ambari-agent/data/command-111.json
> /var/lib/ambari-agent/cache/custom_actions
> /var/lib/ambari-agent/data/structured-out-111.json INFO
> /var/lib/ambari-agent/tmp' returned 1. 2017-01-03 17:07:47,095 - In the
> middle of a stack upgrade/downgrade for Stack HDP and destination version
> 2.5.3.0-37, determining which hadoop conf dir to use.
> 2017-01-03 17:07:47,096 - Hadoop conf dir: /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-01-03 17:07:47,096 - The hadoop conf dir /usr/hdp/2.5.3.0-37/hadoop/conf
> exists, will call conf-select on it for version 2.5.3.0-37
> 2017-01-03 17:07:47,096 - Checking if need to create versioned conf dir
> /etc/hadoop/2.5.3.0-37/0
> 2017-01-03 17:07:47,097 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'create-conf-dir', '--package', 'hadoop', '--stack-version', '2.5.3.0-37',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-01-03 17:07:47,141 - call returned (1, '/etc/hadoop/2.5.3.0-37/0 exist
> already', '')
> 2017-01-03 17:07:47,141 - checked_call[('ambari-python-wrap',
> '/usr/bin/conf-select', 'set-conf-dir', '--package', 'hadoop',
> '--stack-version', '2.5.3.0-37', '--conf-version', '0')] {'logoutput': False,
> 'sudo': True, 'quiet': False}
> 2017-01-03 17:07:47,179 - checked_call returned (0, '')
> 2017-01-03 17:07:47,180 - Ensuring that hadoop has the correct symlink
> structure
> 2017-01-03 17:07:47,180 - Using hadoop conf dir:
> /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-01-03 17:07:47,182 - Stack Feature Version Info: stack_version=2.5,
> version=2.5.3.0-37, current_cluster_version=2.5.0.0-1245,
> upgrade_direction=upgrade -> 2.5.3.0-37
> 2017-01-03 17:07:47,185 - In the middle of a stack upgrade/downgrade for
> Stack HDP and destination version 2.5.3.0-37, determining which hadoop conf
> dir to use.
> 2017-01-03 17:07:47,185 - Hadoop conf dir: /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-01-03 17:07:47,186 - The hadoop conf dir /usr/hdp/2.5.3.0-37/hadoop/conf
> exists, will call conf-select on it for version 2.5.3.0-37
> 2017-01-03 17:07:47,186 - Checking if need to create versioned conf dir
> /etc/hadoop/2.5.3.0-37/0
> 2017-01-03 17:07:47,187 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'create-conf-dir', '--package', 'hadoop', '--stack-version', '2.5.3.0-37',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-01-03 17:07:47,224 - call returned (1, '/etc/hadoop/2.5.3.0-37/0 exist
> already', '')
> 2017-01-03 17:07:47,225 - checked_call[('ambari-python-wrap',
> '/usr/bin/conf-select', 'set-conf-dir', '--package', 'hadoop',
[jira] [Resolved] (AMBARI-19155) Ambari Blueprint doesn't configure the SmartSense ActiveAnalysis Admin password
[ https://issues.apache.org/jira/browse/AMBARI-19155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez resolved AMBARI-19155. -- Resolution: Not A Bug > Ambari Blueprint doesn't configure the SmartSense ActiveAnalysis Admin > password > --- > > Key: AMBARI-19155 > URL: https://issues.apache.org/jira/browse/AMBARI-19155 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez > Attachments: 9374-screen-shot-2016-11-11-at-202221.png > > > When using a blueprint to install HDP 2.5.0 including SmartSense, the > ActivityAnalysis admin password is not configured by the "default_password" > in blueprint. The component fails to start, and the user has to set the > password manually. > See attached screenshot. > This issue was created based on > https://community.hortonworks.com/questions/66107/ambari-blueprint-doesnt-configure-the-smartsense-a.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19155) Ambari Blueprint doesn't configure the SmartSense ActiveAnalysis Admin password
[
https://issues.apache.org/jira/browse/AMBARI-19155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802557#comment-15802557
]
Alejandro Fernandez commented on AMBARI-19155:
--
This field doesn't have default value, you had to explicitly set it, either
installing SmartSense via UI or Blueprint.
In case of Blueprint install you need to add the below property to
configuration list:
{code}
"activity-zeppelin-shiro": {
"properties": {
"users.admin": "ADMIN_PASSWORD"
}
}
{code}
> Ambari Blueprint doesn't configure the SmartSense ActiveAnalysis Admin
> password
> ---
>
> Key: AMBARI-19155
> URL: https://issues.apache.org/jira/browse/AMBARI-19155
> Project: Ambari
> Issue Type: Bug
> Components: blueprints
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
> Attachments: 9374-screen-shot-2016-11-11-at-202221.png
>
>
> When using a blueprint to install HDP 2.5.0 including SmartSense, the
> ActivityAnalysis admin password is not configured by the "default_password"
> in blueprint. The component fails to start, and the user has to set the
> password manually.
> See attached screenshot.
> This issue was created based on
> https://community.hortonworks.com/questions/66107/ambari-blueprint-doesnt-configure-the-smartsense-a.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19392) Status command executor may use obsolete settings
[
https://issues.apache.org/jira/browse/AMBARI-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19392:
---
Status: Patch Available (was: Open)
> Status command executor may use obsolete settings
> -
>
> Key: AMBARI-19392
> URL: https://issues.apache.org/jira/browse/AMBARI-19392
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19392.patch
>
>
> Ambari agent launches status command executor in a subprocess (since
> AMBARI-18505), passing an instance of {{config}}. Afterwards the agent may
> receive settings from the server in the response to registration. These new
> config values are not visible in the subprocess.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19392) Status command executor may use obsolete settings
[
https://issues.apache.org/jira/browse/AMBARI-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19392:
---
Attachment: AMBARI-19392.patch
> Status command executor may use obsolete settings
> -
>
> Key: AMBARI-19392
> URL: https://issues.apache.org/jira/browse/AMBARI-19392
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19392.patch
>
>
> Ambari agent launches status command executor in a subprocess (since
> AMBARI-18505), passing an instance of {{config}}. Afterwards the agent may
> receive settings from the server in the response to registration. These new
> config values are not visible in the subprocess.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19392) Status command executor may use obsolete settings
Doroszlai, Attila created AMBARI-19392:
--
Summary: Status command executor may use obsolete settings
Key: AMBARI-19392
URL: https://issues.apache.org/jira/browse/AMBARI-19392
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 3.0.0
Reporter: Doroszlai, Attila
Assignee: Sebastian Toader
Priority: Critical
Fix For: 3.0.0
Ambari agent launches status command executor in a subprocess (since
AMBARI-18505), passing an instance of {{config}}. Afterwards the agent may
receive settings from the server in the response to registration. These new
config values are not visible in the subprocess.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19316) Zeppelin stop failed during EU while deleting pid file with customized service user
[
https://issues.apache.org/jira/browse/AMBARI-19316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802369#comment-15802369
]
Hudson commented on AMBARI-19316:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6368 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6368/])
Revert "AMBARI-19316 Zeppelin stop failed during EU while deleting pid
(yusaku:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3ce361049520098d9df9ec6aef8748aa1120cad3])
* (edit)
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py
> Zeppelin stop failed during EU while deleting pid file with customized
> service user
> ---
>
> Key: AMBARI-19316
> URL: https://issues.apache.org/jira/browse/AMBARI-19316
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Renjith Kamath
>Priority: Critical
> Labels: express_upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19316-branch-2.5-v1.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 cluster with Ambari-2.5.0.0 (customized service users
> enabled for all services including Zeppelin)
> # Start Express Upgrade to 2.6.0.0-267
> *Result:*
> Observed error while stopping Zeppelin notebook
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 361, in
> Master().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 159, in stop
> user=params.zeppelin_user)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh stop >>
> /grid/0/log/zeppelin/zeppelin-setup.log' returned 1. Hortonworks
> #
> This is MOTD message, added for testing in qe infra
> rm: cannot remove
> ‘/var/run/zeppelin/zeppelin-cstm-zeppelin-ctr-e85-1482808692054-0723-01-03.hwx.site.pid’:
> Permission denied
> rm: cannot remove
> ‘/var/run/zeppelin/zeppelin-cstm-zeppelin-ctr-e85-1482808692054-0723-01-03.hwx.site.pid’:
> Permission denied
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19391) Password Should Not be in Clear Text while creating Hue-Ambari Migration View
[ https://issues.apache.org/jira/browse/AMBARI-19391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-19391: - Attachment: AMBARI-19391.patch > Password Should Not be in Clear Text while creating Hue-Ambari Migration View > - > > Key: AMBARI-19391 > URL: https://issues.apache.org/jira/browse/AMBARI-19391 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-19391.patch > > > While creating Hue-Ambari Migration View. We have to enter the Jdbc Passowrd > of Hue-database and Ambari-Database. > But those Password field are in clear text, which is not correct from a > security point of view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19365) Executing ambari-server unit tests with JDK 1.8 results in unit test failures
[
https://issues.apache.org/jira/browse/AMBARI-19365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802335#comment-15802335
]
Hudson commented on AMBARI-19365:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #648 (See
[https://builds.apache.org/job/Ambari-branch-2.5/648/])
AMBARI-19365. Executing ambari-server unit tests with JDK 1.8 results in
(rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8e070f4bd5fde2ceedf67738c74f2f5f5a6d1d51])
* (add)
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/LoginContextHelper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/utilities/KerberosCheckerTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/view/persistence/DataStoreImplTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/KerberosChecker.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AmbariBasicAuthenticationFilterTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog222Test.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/JvmMetricsSourceTest.java
> Executing ambari-server unit tests with JDK 1.8 results in unit test failures
> -
>
> Key: AMBARI-19365
> URL: https://issues.apache.org/jira/browse/AMBARI-19365
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: jdk1_8, unit-test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19365_branch-2.5_01.patch,
> AMBARI-19365_trunk_01.patch
>
>
> Following unit tests fails when executed with JDK 1.8
> {code}
> mvn test -Dtest=DataStoreImplTest
> mvn clean test -Dtest=UpgradeCatalog222Test
> mvn test -Dtest=KerberosCheckerTest,AmbariBasicAuthenticationFilterTest
> {code}
> Same unit tests passes if the environment is switched to use JDK 1.7
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19391) Password Should Not be in Clear Text while creating Hue-Ambari Migration View
Ishan Bhatt created AMBARI-19391: Summary: Password Should Not be in Clear Text while creating Hue-Ambari Migration View Key: AMBARI-19391 URL: https://issues.apache.org/jira/browse/AMBARI-19391 Project: Ambari Issue Type: Bug Components: ambari-views Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk While creating Hue-Ambari Migration View. We have to enter the Jdbc Passowrd of Hue-database and Ambari-Database. But those Password field are in clear text, which is not correct from a security point of view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
Vivek Rathod created AMBARI-19390: - Summary: AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY Key: AMBARI-19390 URL: https://issues.apache.org/jira/browse/AMBARI-19390 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-19316) Zeppelin stop failed during EU while deleting pid file with customized service user
[ https://issues.apache.org/jira/browse/AMBARI-19316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reopened AMBARI-19316: -- Reopened due to introduction of unit test failures on trunk. The patch has been reverted from trunk. https://builds.apache.org/job/Ambari-trunk-commit/6360/ ### Running tests for stack:2.5 service:ZEPPELIN test_configure_default (test_zeppelin_master.TestZeppelinMaster) ... 2017-01-05 09:40:02,925 - Skipping get_stack_version since " + stack_selector_tool + " is not yet available 2017-01-05 09:40:02,935 - Using hadoop conf dir: /usr/hdp/current/hadoop-client/conf FAIL test_configure_secured (test_zeppelin_master.TestZeppelinMaster) ... 2017-01-05 09:40:02,951 - Skipping get_stack_version since " + stack_selector_tool + " is not yet available 2017-01-05 09:40:02,961 - Using hadoop conf dir: /usr/hdp/current/hadoop-client/conf FAIL test_start_default (test_zeppelin_master.TestZeppelinMaster) ... 2017-01-05 09:40:02,974 - Skipping get_stack_version since " + stack_selector_tool + " is not yet available 2017-01-05 09:40:02,984 - Using hadoop conf dir: /usr/hdp/current/hadoop-client/conf 2017-01-05 09:40:02,992 - Pid file is: /tmp FAIL test_start_secured (test_zeppelin_master.TestZeppelinMaster) ... 2017-01-05 09:40:02,997 - Skipping get_stack_version since " + stack_selector_tool + " is not yet available 2017-01-05 09:40:03,007 - Using hadoop conf dir: /usr/hdp/current/hadoop-client/conf 2017-01-05 09:40:03,015 - Pid file is: /tmp FAIL test_stop_default (test_zeppelin_master.TestZeppelinMaster) ... 2017-01-05 09:40:03,020 - Skipping get_stack_version since " + stack_selector_tool + " is not yet available 2017-01-05 09:40:03,031 - Using hadoop conf dir: /usr/hdp/current/hadoop-client/conf FAIL test_stop_secured (test_zeppelin_master.TestZeppelinMaster) ... 2017-01-05 09:40:03,038 - Skipping get_stack_version since " + stack_selector_tool + " is not yet available 2017-01-05 09:40:03,049 - Using hadoop conf dir: /usr/hdp/current/hadoop-client/conf FAIL == FAIL: test_configure_default (test_zeppelin_master.TestZeppelinMaster) -- Traceback (most recent call last): File "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py", line 1199, in patched return func(*args, **keywargs) File "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/2.5/ZEPPELIN/test_zeppelin_master.py", line 140, in test_configure_default self.assert_configure_default() File "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/2.5/ZEPPELIN/test_zeppelin_master.py", line 47, in assert_configure_default cd_access = 'a', File "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/utils/RMFTestCase.py", line 280, in assertResourceCalled self.assertEquals(resource_type, resource.__class__.__name__) AssertionError: 'Directory' != 'Execute' == FAIL: test_configure_secured (test_zeppelin_master.TestZeppelinMaster) -- Traceback (most recent call last): File "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py", line 1199, in patched return func(*args, **keywargs) File "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/2.5/ZEPPELIN/test_zeppelin_master.py", line 151, in test_configure_secured self.assert_configure_secured() File "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/2.5/ZEPPELIN/test_zeppelin_master.py", line 96, in assert_configure_secured cd_access = 'a', File "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/utils/RMFTestCase.py", line 280, in assertResourceCalled self.assertEquals(resource_type, resource.__class__.__name__) AssertionError: 'Directory' != 'Execute' == FAIL: test_start_default (test_zeppelin_master.TestZeppelinMaster) -- Traceback (most recent call last): File "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py", line 1199, in patched return func(*args, **keywargs) File "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/2.5/ZEPPELIN/test_zeppelin_master.py", line 311, in test_start_default self.assert_configure_default() File
[jira] [Updated] (AMBARI-19365) Executing ambari-server unit tests with JDK 1.8 results in unit test failures
[
https://issues.apache.org/jira/browse/AMBARI-19365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19365:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 5e72ee6f2c6ebcda105e521d819f95ffde1b245e
Author: Robert Levas
Date: Thu Jan 5 12:53:53 2017 -0500
{noformat}
Committed to branch-2.5
{noformat}
commit 8e070f4bd5fde2ceedf67738c74f2f5f5a6d1d51
Author: Robert Levas
Date: Thu Jan 5 13:52:04 2017 -0500
{noformat}
> Executing ambari-server unit tests with JDK 1.8 results in unit test failures
> -
>
> Key: AMBARI-19365
> URL: https://issues.apache.org/jira/browse/AMBARI-19365
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: jdk1_8, unit-test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19365_branch-2.5_01.patch,
> AMBARI-19365_trunk_01.patch
>
>
> Following unit tests fails when executed with JDK 1.8
> {code}
> mvn test -Dtest=DataStoreImplTest
> mvn clean test -Dtest=UpgradeCatalog222Test
> mvn test -Dtest=KerberosCheckerTest,AmbariBasicAuthenticationFilterTest
> {code}
> Same unit tests passes if the environment is switched to use JDK 1.7
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19365) Executing ambari-server unit tests with JDK 1.8 results in unit test failures
[
https://issues.apache.org/jira/browse/AMBARI-19365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802158#comment-15802158
]
Hudson commented on AMBARI-19365:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6367 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6367/])
AMBARI-19365. Executing ambari-server unit tests with JDK 1.8 results in
(rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5e72ee6f2c6ebcda105e521d819f95ffde1b245e])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog222Test.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/KerberosChecker.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/LoginContextHelper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/JvmMetricsSourceTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AmbariBasicAuthenticationFilterTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/view/persistence/DataStoreImplTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/utilities/KerberosCheckerTest.java
> Executing ambari-server unit tests with JDK 1.8 results in unit test failures
> -
>
> Key: AMBARI-19365
> URL: https://issues.apache.org/jira/browse/AMBARI-19365
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: jdk1_8, unit-test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19365_branch-2.5_01.patch,
> AMBARI-19365_trunk_01.patch
>
>
> Following unit tests fails when executed with JDK 1.8
> {code}
> mvn test -Dtest=DataStoreImplTest
> mvn clean test -Dtest=UpgradeCatalog222Test
> mvn test -Dtest=KerberosCheckerTest,AmbariBasicAuthenticationFilterTest
> {code}
> Same unit tests passes if the environment is switched to use JDK 1.7
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18896) Suse11 deployment failures due to package issues
[
https://issues.apache.org/jira/browse/AMBARI-18896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802153#comment-15802153
]
Qin Liu commented on AMBARI-18896:
--
@dsen, Hi Dmytro,
Could you please tell when you are going to ship this JIRA? Thanks!
> Suse11 deployment failures due to package issues
>
>
> Key: AMBARI-18896
> URL: https://issues.apache.org/jira/browse/AMBARI-18896
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
> Environment: Suse
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18896.patch, AMBARI-18896_2.patch
>
>
> Suse 11 deployment failed due to
> {code}
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/zypper --quiet install --auto-agree-with-licenses --no-confirm
> ambari-metrics-monitor' returned 4. Problem: nothing provides python-kerberos
> needed by ambari-metrics-monitor-2.5.0.0-283.x86_64
> Solution 1: do not install ambari-metrics-monitor-2.5.0.0-283.x86_64
> Solution 2: break ambari-metrics-monitor-2.5.0.0-283.x86_64 by ignoring some
> of its dependencies
> Choose from above solutions by number or cancel [1/2/c] (c): c
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19368) Add common log rotation settings to ranger, ranger-kms, falcon
[ https://issues.apache.org/jira/browse/AMBARI-19368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802062#comment-15802062 ] Hudson commented on AMBARI-19368: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #647 (See [https://builds.apache.org/job/Ambari-branch-2.5/647/]) AMBARI-19368. Add common log rotation settings to ranger, ranger-kms and (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1482ffdbf59d597bf731e48b93c063fdf4377168]) * (edit) ambari-server/src/test/python/stacks/2.1/FALCON/test_falcon_client.py * (edit) ambari-server/src/test/python/stacks/2.5/RANGER/test_ranger_admin.py * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py * (edit) ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/configuration/kms-log4j.xml * (edit) ambari-server/src/test/python/stacks/2.5/RANGER/test_ranger_tagsync.py * (edit) ambari-server/src/test/python/stacks/2.6/RANGER/test_ranger_tagsync.py * (edit) ambari-server/src/main/resources/common-services/RANGER/0.6.0/configuration/usersync-log4j.xml * (edit) ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/params.py * (edit) ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/configuration/falcon-log4j.xml * (edit) ambari-server/src/test/python/stacks/2.1/configs/default.json * (edit) ambari-server/src/test/python/stacks/2.2/configs/falcon-upgrade.json * (edit) ambari-server/src/test/python/stacks/2.1/FALCON/test_falcon_server.py * (edit) ambari-server/src/test/python/stacks/2.6/RANGER/test_ranger_admin.py * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py * (edit) ambari-server/src/test/python/stacks/2.5/RANGER/test_ranger_usersync.py * (edit) ambari-server/src/main/resources/common-services/RANGER/0.6.0/configuration/tagsync-log4j.xml * (edit) ambari-server/src/main/resources/common-services/RANGER/0.6.0/configuration/admin-log4j.xml * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms.py > Add common log rotation settings to ranger, ranger-kms, falcon > -- > > Key: AMBARI-19368 > URL: https://issues.apache.org/jira/browse/AMBARI-19368 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19368.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19368) Add common log rotation settings to ranger, ranger-kms, falcon
[ https://issues.apache.org/jira/browse/AMBARI-19368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802038#comment-15802038 ] Hudson commented on AMBARI-19368: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6366 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6366/]) AMBARI-19368. Add common log rotation settings to ranger, ranger-kms and (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=381b474d6ec2a77894329f8d16c74a793fdccec2]) * (edit) ambari-server/src/test/python/stacks/2.1/FALCON/test_falcon_client.py * (edit) ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms.py * (edit) ambari-server/src/test/python/stacks/2.1/configs/default.json * (edit) ambari-server/src/main/resources/common-services/RANGER/0.6.0/configuration/tagsync-log4j.xml * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py * (edit) ambari-server/src/main/resources/common-services/RANGER/0.6.0/configuration/usersync-log4j.xml * (edit) ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/configuration/kms-log4j.xml * (edit) ambari-server/src/test/python/stacks/2.1/FALCON/test_falcon_server.py * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/params_linux.py * (edit) ambari-server/src/test/python/stacks/2.5/RANGER/test_ranger_admin.py * (edit) ambari-server/src/main/resources/common-services/RANGER/0.6.0/configuration/admin-log4j.xml * (edit) ambari-server/src/test/python/stacks/2.6/RANGER/test_ranger_admin.py * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/configuration/falcon-log4j.xml * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py * (edit) ambari-server/src/test/python/stacks/2.2/configs/falcon-upgrade.json * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py * (edit) ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py * (edit) ambari-server/src/test/python/stacks/2.5/RANGER/test_ranger_tagsync.py * (edit) ambari-server/src/test/python/stacks/2.6/RANGER/test_ranger_tagsync.py * (edit) ambari-server/src/test/python/stacks/2.5/RANGER/test_ranger_usersync.py > Add common log rotation settings to ranger, ranger-kms, falcon > -- > > Key: AMBARI-19368 > URL: https://issues.apache.org/jira/browse/AMBARI-19368 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19368.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19375) Update the execution mode for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801958#comment-15801958 ] Hudson commented on AMBARI-19375: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #646 (See [https://builds.apache.org/job/Ambari-branch-2.5/646/]) AMBARI-19375. Update the execution mode for hive interactive in HDP 2.6 (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4ea61b72a2682ab6822fa435b8aac933d23b305d]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-site.xml > Update the execution mode for hive interactive in HDP 2.6 stack > --- > > Key: AMBARI-19375 > URL: https://issues.apache.org/jira/browse/AMBARI-19375 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19375.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19387) When deleting services UI shows a lot of configs to be changing but none changes
[
https://issues.apache.org/jira/browse/AMBARI-19387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801936#comment-15801936
]
Hadoop QA commented on AMBARI-19387:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845808/AMBARI-19387.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/9923//console
This message is automatically generated.
> When deleting services UI shows a lot of configs to be changing but none
> changes
>
>
> Key: AMBARI-19387
> URL: https://issues.apache.org/jira/browse/AMBARI-19387
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19387.patch, _delete_smartsense.png
>
>
> It appears that UI feedback shows the sum total of configs recommended by
> stack advisor even if only a subset of the configs are actually applied.
> [See attached|^_delete_smartsense.png] what is shown while SmartSense is
> deleted. The actual configs changed is none which is expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19368) Add common log rotation settings to ranger, ranger-kms, falcon
[ https://issues.apache.org/jira/browse/AMBARI-19368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19368: --- Issue Type: Task (was: Bug) > Add common log rotation settings to ranger, ranger-kms, falcon > -- > > Key: AMBARI-19368 > URL: https://issues.apache.org/jira/browse/AMBARI-19368 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19368.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19368) Add common log rotation settings to ranger, ranger-kms, falcon
[ https://issues.apache.org/jira/browse/AMBARI-19368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19368: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Add common log rotation settings to ranger, ranger-kms, falcon > -- > > Key: AMBARI-19368 > URL: https://issues.apache.org/jira/browse/AMBARI-19368 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19368.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19387) When deleting services UI shows a lot of configs to be changing but none changes
[ https://issues.apache.org/jira/browse/AMBARI-19387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801902#comment-15801902 ] Hudson commented on AMBARI-19387: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6365 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6365/]) AMBARI-19387 When deleting services UI shows a lot of configs to be (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c76d6a1ec9306064e900687ec32ab926c89cd88a]) * (edit) ambari-web/app/controllers/main/service/info/configs.js * (edit) ambari-web/app/controllers/main/service/item.js * (edit) ambari-web/test/mixins/common/configs/enhanced_configs_test.js * (edit) ambari-web/test/controllers/main/service/info/config_test.js * (edit) ambari-web/app/mixins/common/configs/enhanced_configs.js > When deleting services UI shows a lot of configs to be changing but none > changes > > > Key: AMBARI-19387 > URL: https://issues.apache.org/jira/browse/AMBARI-19387 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19387.patch, _delete_smartsense.png > > > It appears that UI feedback shows the sum total of configs recommended by > stack advisor even if only a subset of the configs are actually applied. > [See attached|^_delete_smartsense.png] what is shown while SmartSense is > deleted. The actual configs changed is none which is expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19388) PERF: disabling security fails
[ https://issues.apache.org/jira/browse/AMBARI-19388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801822#comment-15801822 ] Dmytro Sen commented on AMBARI-19388: - Failed tests aren't related to the patch > PERF: disabling security fails > -- > > Key: AMBARI-19388 > URL: https://issues.apache.org/jira/browse/AMBARI-19388 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19388.patch > > > When you are trying to disable security om perf cluster it fails. > 1) For cluster with 1200 agents it works fine but for cluster with 1850 > agents it fails. > 2) According to what i found, root cause is PUT request to > http://:8080/api/v1/clusters/ with data > like "security_type" : "NONE". So, this request trying to change security > type from KERBEROS to NONE and fails by timeout of three minutes. > 3) Interesting thing, request to change security type fails and UI showing > Error on disable security window. But in the same time in BG operations > process which destroying keytabs proceed work. > 4) One more thing. After failed disabling kerberos, if you will click restart > the same request(update security type) will finish work in a few seconds. > So, what we need to do is to connect profiler and find out what exactly take > so much time for request to change security type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19389) Authentication negotiation HTTP response should be sent when Kerberos authentication is enabled
[
https://issues.apache.org/jira/browse/AMBARI-19389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19389:
--
Labels: authentication kerberos security (was: kerberos)
> Authentication negotiation HTTP response should be sent when Kerberos
> authentication is enabled
> ---
>
> Key: AMBARI-19389
> URL: https://issues.apache.org/jira/browse/AMBARI-19389
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: authentication, kerberos, security
> Fix For: 2.5.0
>
>
> Authentication negotiation HTTP response should be automatically sent when
> needed when Kerberos authentication is enabled.
> The expected HTTP response during authentication failure when Kerberos
> authentication into Ambari is enabled is as follows:
> {noformat}
> HTTP/1.1 401 Authentication requested
> WWW-Authenticate: Negotiate
> {noformat}
> When Kerberos authentication into Ambari is not enabled the expected HTTP
> response for an authentication failure is:
> {noformat}
> HTTP/1.1 403 Missing authentication token
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19389) Authentication negotiation HTTP response should be sent when Kerberos authentication is enabled
Robert Levas created AMBARI-19389:
-
Summary: Authentication negotiation HTTP response should be sent
when Kerberos authentication is enabled
Key: AMBARI-19389
URL: https://issues.apache.org/jira/browse/AMBARI-19389
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Robert Levas
Assignee: Robert Levas
Fix For: 2.5.0
Authentication negotiation HTTP response should be automatically sent when
needed when Kerberos authentication is enabled.
The expected HTTP response during authentication failure when Kerberos
authentication into Ambari is enabled is as follows:
{noformat}
HTTP/1.1 401 Authentication requested
WWW-Authenticate: Negotiate
{noformat}
When Kerberos authentication into Ambari is not enabled the expected HTTP
response for an authentication failure is:
{noformat}
HTTP/1.1 403 Missing authentication token
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19388) PERF: disabling security fails
[
https://issues.apache.org/jira/browse/AMBARI-19388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801765#comment-15801765
]
Hadoop QA commented on AMBARI-19388:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845815/AMBARI-19388.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9922//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9922//console
This message is automatically generated.
> PERF: disabling security fails
> --
>
> Key: AMBARI-19388
> URL: https://issues.apache.org/jira/browse/AMBARI-19388
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19388.patch
>
>
> When you are trying to disable security om perf cluster it fails.
> 1) For cluster with 1200 agents it works fine but for cluster with 1850
> agents it fails.
> 2) According to what i found, root cause is PUT request to
> http://:8080/api/v1/clusters/ with data
> like "security_type" : "NONE". So, this request trying to change security
> type from KERBEROS to NONE and fails by timeout of three minutes.
> 3) Interesting thing, request to change security type fails and UI showing
> Error on disable security window. But in the same time in BG operations
> process which destroying keytabs proceed work.
> 4) One more thing. After failed disabling kerberos, if you will click restart
> the same request(update security type) will finish work in a few seconds.
> So, what we need to do is to connect profiler and find out what exactly take
> so much time for request to change security type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19368) Add common log rotation settings to ranger, ranger-kms, falcon
[ https://issues.apache.org/jira/browse/AMBARI-19368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19368: --- Status: Patch Available (was: Open) > Add common log rotation settings to ranger, ranger-kms, falcon > -- > > Key: AMBARI-19368 > URL: https://issues.apache.org/jira/browse/AMBARI-19368 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19368.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19375) Update the execution mode for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801705#comment-15801705 ] Sumit Mohanty commented on AMBARI-19375: Committed to trunk and branch-2.5 > Update the execution mode for hive interactive in HDP 2.6 stack > --- > > Key: AMBARI-19375 > URL: https://issues.apache.org/jira/browse/AMBARI-19375 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19375.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19375) Update the execution mode for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801700#comment-15801700 ] Sumit Mohanty commented on AMBARI-19375: LGTM, +1 > Update the execution mode for hive interactive in HDP 2.6 stack > --- > > Key: AMBARI-19375 > URL: https://issues.apache.org/jira/browse/AMBARI-19375 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19375.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19387) When deleting services UI shows a lot of configs to be changing but none changes
[ https://issues.apache.org/jira/browse/AMBARI-19387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801663#comment-15801663 ] Andrii Babiichuk commented on AMBARI-19387: --- Committed to trunk > When deleting services UI shows a lot of configs to be changing but none > changes > > > Key: AMBARI-19387 > URL: https://issues.apache.org/jira/browse/AMBARI-19387 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19387.patch, _delete_smartsense.png > > > It appears that UI feedback shows the sum total of configs recommended by > stack advisor even if only a subset of the configs are actually applied. > [See attached|^_delete_smartsense.png] what is shown while SmartSense is > deleted. The actual configs changed is none which is expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19387) When deleting services UI shows a lot of configs to be changing but none changes
[
https://issues.apache.org/jira/browse/AMBARI-19387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801642#comment-15801642
]
Hadoop QA commented on AMBARI-19387:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845808/AMBARI-19387.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/9921//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9921//console
This message is automatically generated.
> When deleting services UI shows a lot of configs to be changing but none
> changes
>
>
> Key: AMBARI-19387
> URL: https://issues.apache.org/jira/browse/AMBARI-19387
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19387.patch, _delete_smartsense.png
>
>
> It appears that UI feedback shows the sum total of configs recommended by
> stack advisor even if only a subset of the configs are actually applied.
> [See attached|^_delete_smartsense.png] what is shown while SmartSense is
> deleted. The actual configs changed is none which is expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19388) PERF: disabling security fails
[ https://issues.apache.org/jira/browse/AMBARI-19388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19388: Status: Patch Available (was: Open) > PERF: disabling security fails > -- > > Key: AMBARI-19388 > URL: https://issues.apache.org/jira/browse/AMBARI-19388 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19388.patch > > > When you are trying to disable security om perf cluster it fails. > 1) For cluster with 1200 agents it works fine but for cluster with 1850 > agents it fails. > 2) According to what i found, root cause is PUT request to > http://:8080/api/v1/clusters/ with data > like "security_type" : "NONE". So, this request trying to change security > type from KERBEROS to NONE and fails by timeout of three minutes. > 3) Interesting thing, request to change security type fails and UI showing > Error on disable security window. But in the same time in BG operations > process which destroying keytabs proceed work. > 4) One more thing. After failed disabling kerberos, if you will click restart > the same request(update security type) will finish work in a few seconds. > So, what we need to do is to connect profiler and find out what exactly take > so much time for request to change security type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19388) PERF: disabling security fails
[ https://issues.apache.org/jira/browse/AMBARI-19388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19388: Attachment: AMBARI-19388.patch > PERF: disabling security fails > -- > > Key: AMBARI-19388 > URL: https://issues.apache.org/jira/browse/AMBARI-19388 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19388.patch > > > When you are trying to disable security om perf cluster it fails. > 1) For cluster with 1200 agents it works fine but for cluster with 1850 > agents it fails. > 2) According to what i found, root cause is PUT request to > http://:8080/api/v1/clusters/ with data > like "security_type" : "NONE". So, this request trying to change security > type from KERBEROS to NONE and fails by timeout of three minutes. > 3) Interesting thing, request to change security type fails and UI showing > Error on disable security window. But in the same time in BG operations > process which destroying keytabs proceed work. > 4) One more thing. After failed disabling kerberos, if you will click restart > the same request(update security type) will finish work in a few seconds. > So, what we need to do is to connect profiler and find out what exactly take > so much time for request to change security type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19388) PERF: disabling security fails
Dmytro Sen created AMBARI-19388: --- Summary: PERF: disabling security fails Key: AMBARI-19388 URL: https://issues.apache.org/jira/browse/AMBARI-19388 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.5.0 When you are trying to disable security om perf cluster it fails. 1) For cluster with 1200 agents it works fine but for cluster with 1850 agents it fails. 2) According to what i found, root cause is PUT request to http://:8080/api/v1/clusters/ with data like "security_type" : "NONE". So, this request trying to change security type from KERBEROS to NONE and fails by timeout of three minutes. 3) Interesting thing, request to change security type fails and UI showing Error on disable security window. But in the same time in BG operations process which destroying keytabs proceed work. 4) One more thing. After failed disabling kerberos, if you will click restart the same request(update security type) will finish work in a few seconds. So, what we need to do is to connect profiler and find out what exactly take so much time for request to change security type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19182) Config Groups: Save button not enabled while trying to overwrite configs
[ https://issues.apache.org/jira/browse/AMBARI-19182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801616#comment-15801616 ] Hudson commented on AMBARI-19182: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6364 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6364/]) AMBARI-19182. Config Groups: Save button not enabled while trying to (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bca0346b9f3eb01cd90e00cfce366305fca7a38b]) * (edit) ambari-web/test/utils/config_test.js * (edit) ambari-web/test/controllers/main/admin/highAvailability/journalNode/step4_controller_test.js * (edit) ambari-web/test/controllers/main/admin/highAvailability/resourceManager/step3_controller_test.js * (edit) ambari-web/app/models/configs/objects/service_config.js > Config Groups: Save button not enabled while trying to overwrite configs > > > Key: AMBARI-19182 > URL: https://issues.apache.org/jira/browse/AMBARI-19182 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Oleg Nechiporenko > Fix For: 2.5.0 > > Attachments: AMBARI-19182.patch, AMBARI-19182_branch-2.5.patch > > > STR: > -> For a service, create a config group > -> Go to configs page, select the config group. Now try to overwrite a > config, Save button is not enabled here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19182) Config Groups: Save button not enabled while trying to overwrite configs
[ https://issues.apache.org/jira/browse/AMBARI-19182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801599#comment-15801599 ] Hudson commented on AMBARI-19182: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #645 (See [https://builds.apache.org/job/Ambari-branch-2.5/645/]) AMBARI-19182. Config Groups: Save button not enabled while trying to (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=11c8067e00e0c5abc3e3e269b87dcee0b1944a0f]) * (edit) ambari-web/app/models/configs/objects/service_config.js > Config Groups: Save button not enabled while trying to overwrite configs > > > Key: AMBARI-19182 > URL: https://issues.apache.org/jira/browse/AMBARI-19182 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Oleg Nechiporenko > Fix For: 2.5.0 > > Attachments: AMBARI-19182.patch, AMBARI-19182_branch-2.5.patch > > > STR: > -> For a service, create a config group > -> Go to configs page, select the config group. Now try to overwrite a > config, Save button is not enabled here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19382) ATS service check failed on navigating to Hive View
[
https://issues.apache.org/jira/browse/AMBARI-19382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801574#comment-15801574
]
Hadoop QA commented on AMBARI-19382:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845795/AMBARI-19382_branch-2.5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/hive-next contrib/views/hive20
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9920//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9920//console
This message is automatically generated.
> ATS service check failed on navigating to Hive View
> ---
>
> Key: AMBARI-19382
> URL: https://issues.apache.org/jira/browse/AMBARI-19382
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Anusha Bilgi
>Assignee: Gaurav Nagar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19382_branch-2.5.patch
>
>
> Logs:
> {code:java}
> 12 Dec 2016 15:39:56,099 INFO [ambari-client-thread-1258]
> ConfigurationBuilder:105 - HA HDFS cluster found.
> 12 Dec 2016 15:39:56,100 INFO [ambari-client-thread-1258]
> ConfigurationBuilder:120 - HdfsApi configured to connect to
> defaultFS='swebhdfs://nameservice'
> 12 Dec 2016 15:39:56,158 INFO [ambari-client-thread-1258] HdfsUtil:128 -
> HdfsApi connected OK
> 12 Dec 2016 15:39:56,286 INFO [ambari-client-thread-16522]
> ConfigurationBuilder:105 - HA HDFS cluster found.
> 12 Dec 2016 15:39:56,287 INFO [ambari-client-thread-16522]
> ConfigurationBuilder:120 - HdfsApi configured to connect to
> defaultFS='swebhdfs://nameservice'
> 12 Dec 2016 15:39:56,311 INFO [ambari-client-thread-16522] HdfsUtil:128 -
> HdfsApi connected OK
> 12 Dec 2016 15:40:43,945 ERROR [ambari-client-thread-36]
> LoggingSearchPropertyProvider:59 - Error occurred while making request to
> LogSearch service, unable to populate logging properties on this resource
> 12 Dec 2016 15:40:50,859 ERROR [ambari-client-thread-36]
> ContainerResponse:537 - Mapped exception to response: 500 (Internal Server
> Error)
> javax.ws.rs.WebApplicationException: java.net.ConnectException: Connection
> refused
> at
> org.apache.ambari.view.hive2.HelpService.atsStatus(HelpService.java:107)
> at sun.reflect.GeneratedMethodAccessor1163.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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.RightHandPathRule.accept(RightHandPathRule.java:147)
> 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)
> 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)
> 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)
> 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)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
>
