[jira] [Updated] (AMBARI-18192) Can't build RPM package due to lack of upgradeHelper.py
[
https://issues.apache.org/jira/browse/AMBARI-18192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-18192:
-
Attachment: AMBARI-18192.patch
> Can't build RPM package due to lack of upgradeHelper.py
> ---
>
> Key: AMBARI-18192
> URL: https://issues.apache.org/jira/browse/AMBARI-18192
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-18192.patch
>
>
> When I ran {{mvn clean install package rpm:rpm -DskipTests}}, I got an error
> {code}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6:14.285s
> [INFO] Finished at: Thu Aug 18 03:53:29 UTC 2016
> [INFO] Final Memory: 226M/1125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single
> (make-assembly) on project ambari-server: Failed to create assembly: Error
> adding file to archive:
> /tmp/ambari/ambari-server/src/main/python/upgradeHelper.py isn't a file. ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18192) Can't build RPM package due to lack of upgradeHelper.py
[
https://issues.apache.org/jira/browse/AMBARI-18192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-18192:
-
Status: Patch Available (was: Open)
> Can't build RPM package due to lack of upgradeHelper.py
> ---
>
> Key: AMBARI-18192
> URL: https://issues.apache.org/jira/browse/AMBARI-18192
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-18192.patch
>
>
> When I ran {{mvn clean install package rpm:rpm -DskipTests}}, I got an error
> {code}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6:14.285s
> [INFO] Finished at: Thu Aug 18 03:53:29 UTC 2016
> [INFO] Final Memory: 226M/1125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single
> (make-assembly) on project ambari-server: Failed to create assembly: Error
> adding file to archive:
> /tmp/ambari/ambari-server/src/main/python/upgradeHelper.py isn't a file. ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18192) Can't build RPM package due to lack of upgradeHelper.py
[
https://issues.apache.org/jira/browse/AMBARI-18192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426047#comment-15426047
]
Masahiro Tanaka commented on AMBARI-18192:
--
Attached a patch
> Can't build RPM package due to lack of upgradeHelper.py
> ---
>
> Key: AMBARI-18192
> URL: https://issues.apache.org/jira/browse/AMBARI-18192
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-18192.patch
>
>
> When I ran {{mvn clean install package rpm:rpm -DskipTests}}, I got an error
> {code}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6:14.285s
> [INFO] Finished at: Thu Aug 18 03:53:29 UTC 2016
> [INFO] Final Memory: 226M/1125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single
> (make-assembly) on project ambari-server: Failed to create assembly: Error
> adding file to archive:
> /tmp/ambari/ambari-server/src/main/python/upgradeHelper.py isn't a file. ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18193) Zeppelin logsearch configuration typo
Miklos Gergely created AMBARI-18193: --- Summary: Zeppelin logsearch configuration typo Key: AMBARI-18193 URL: https://issues.apache.org/jira/browse/AMBARI-18193 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.4.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18194) Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException: Connection reset by peer"
Andrew Onischuk created AMBARI-18194: Summary: Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException: Connection reset by peer" Key: AMBARI-18194 URL: https://issues.apache.org/jira/browse/AMBARI-18194 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.4.0 I'd reported this issue previously in not see this due to its intermitent nature. In yesterdays nightly, around 8 tests had failed with this issue and on rerun 48 failed. Hs2 logs are below: 2016-08-17T07:28:55,479 INFO [HiveServer2-Background-Pool: Thread-6508]: SessionState (SessionState.java:printInfo(1075)) - Status: Running (Executing on YARN cluster with App id application_1471417242320_0006) Map 1: 1/1 Reducer 2: 0(+1)/1 Reducer 3: 0/1 2016-08-17T07:28:55,480 INFO [HiveServer2-Background-Pool: Thread-6508]: SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 0(+1)/1 Reducer 3: 0/1 Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1 2016-08-17T07:28:55,681 INFO [HiveServer2-Background-Pool: Thread-6508]: SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1 Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6503]: SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1 Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6507]: SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1 Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1 2016-08-17T07:28:58,955 INFO [HiveServer2-Background-Pool: Thread-6508]: SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1 Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1 2016-08-17T07:29:00,566 INFO [HiveServer2-Background-Pool: Thread-6508]: SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1 Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-3)/1 2016-08-17T07:29:00,633 INFO [HiveServer2-Background-Pool: Thread-6503]: SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-3)/1 Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1 2016-08-17T07:29:00,635 INFO [HiveServer2-Background-Pool: Thread-6507]: SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1 Status: Failed 2016-08-17T07:29:00,708 ERROR [HiveServer2-Background-Pool: Thread-6503]: SessionState (SessionState.java:printError(1084)) - Status: Failed Vertex failed, vertexName=Reducer 3, vertexId=vertex_1471417242320_0005_293_02, diagnostics=[Task failed, taskId=task_1471417242320_0005_293_02_00, diagnostics=[TaskAttempt 0 failed, info=[Error: Error while running task ( failure ) : attempt_1471417242320_0005_293_02_00_0:java.lang.RuntimeException: java.lang.RuntimeException: Hive Runtime Error while closing operators: java.io.IOException: Connection reset by peer at org.apache.hadoop.hive.ql.exec.tez.TezProcessor.initializeAndRunProcessor(TezProcessor.java:211) at org.apache.hadoop.hive.ql.exec.tez.TezProcessor.run(TezProcessor.java:168) at org.apache.tez.runtime.LogicalIOProcessorRuntimeTask.run(LogicalIOProcessorRuntimeTask.java:370) at org.apache.tez.runtime.task.TaskRunner2Callable$1.run(TaskRunner2Callable.java:73) at org.apache.tez.runtime.task.TaskRunner2Callable$1.run(TaskRunner2Callable.java:61) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1724) at org.apache.tez.runtime.task.TaskRunner2Callable.callInternal(TaskRunner2Callable.java:61) at org.apache.tez.runtime.task.TaskRunner2Callable.callInternal(TaskRunner2Callable.java:37) at org.apache.tez.common.CallableWithNdc.call(CallableWithNdc.java:36) at org.apache.hadoop.hive.llap.daemon.impl.StatsRecordingThreadPool$WrappedCallable.call(StatsRecordingThreadPool.java:110) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: Hive Runtime Error while closing operators: java.i
[jira] [Updated] (AMBARI-18194) Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException: Connection reset by peer"
[ https://issues.apache.org/jira/browse/AMBARI-18194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18194: - Attachment: AMBARI-18194.patch > Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException: > Connection reset by peer" > - > > Key: AMBARI-18194 > URL: https://issues.apache.org/jira/browse/AMBARI-18194 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-18194.patch, AMBARI-18194.patch > > > I'd reported this issue previously in > not see this due to its intermitent nature. > In yesterdays nightly, around 8 tests had failed with this issue and on rerun > 48 failed. Hs2 logs are below: > > > > 2016-08-17T07:28:55,479 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Status: Running (Executing > on YARN cluster with App id application_1471417242320_0006) > > Map 1: 1/1 Reducer 2: 0(+1)/1 Reducer 3: 0/1 > 2016-08-17T07:28:55,480 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: > 0(+1)/1 Reducer 3: 0/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1 > 2016-08-17T07:28:55,681 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1 > 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-2)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1 > 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6507]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1 > 2016-08-17T07:28:58,955 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1 > 2016-08-17T07:29:00,566 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-3)/1 > 2016-08-17T07:29:00,633 INFO [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-3)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1 > 2016-08-17T07:29:00,635 INFO [HiveServer2-Background-Pool: Thread-6507]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-2)/1 > Status: Failed > 2016-08-17T07:29:00,708 ERROR [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printError(1084)) - Status: Failed > Vertex failed, vertexName=Reducer 3, > vertexId=vertex_1471417242320_0005_293_02, diagnostics=[Task failed, > taskId=task_1471417242320_0005_293_02_00, diagnostics=[TaskAttempt 0 > failed, info=[Error: Error while running task ( failure ) : > attempt_1471417242320_0005_293_02_00_0:java.lang.RuntimeException: > java.lang.RuntimeException: Hive Runtime Error while closing operators: > java.io.IOException: Connection reset by peer > at > org.apache.hadoop.hive.ql.exec.tez.TezProcessor.initializeAndRunProcessor(TezProcessor.java:211) > at > org.apache.hadoop.hive.ql.exec.tez.TezProcessor.run(TezProcessor.java:168) > at > org.apache.tez.runtime.LogicalIOProcessorRuntimeTask.run(LogicalIOProcessorRuntimeTask.java:370) > at > org.apache.tez.runtime.task.TaskRunner2Callable$1.run(TaskRunner2Callable.java:73) > at > org.apache.tez.runtime.task.TaskRunner2Callable$1.run(TaskRunner2Callable.java:61) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1724) > at > org.apache.tez.runtime.task.TaskRunner2Callable.callInternal(TaskRunner2Callable.java:61) > at > org.apache.tez.runtime.task.TaskRunner2Callable.callInternal(TaskRunner2Callable.java:37) > at > org.apache.tez.common.CallableWithNdc.call(CallableWithNdc.java:36) > at > org.apache.hadoop.hive.llap.daemon.impl.StatsRecordingThreadPool
[jira] [Updated] (AMBARI-18194) Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException: Connection reset by peer"
[ https://issues.apache.org/jira/browse/AMBARI-18194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18194: - Attachment: AMBARI-18194.patch > Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException: > Connection reset by peer" > - > > Key: AMBARI-18194 > URL: https://issues.apache.org/jira/browse/AMBARI-18194 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-18194.patch, AMBARI-18194.patch > > > I'd reported this issue previously in > not see this due to its intermitent nature. > In yesterdays nightly, around 8 tests had failed with this issue and on rerun > 48 failed. Hs2 logs are below: > > > > 2016-08-17T07:28:55,479 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Status: Running (Executing > on YARN cluster with App id application_1471417242320_0006) > > Map 1: 1/1 Reducer 2: 0(+1)/1 Reducer 3: 0/1 > 2016-08-17T07:28:55,480 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: > 0(+1)/1 Reducer 3: 0/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1 > 2016-08-17T07:28:55,681 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1 > 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-2)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1 > 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6507]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1 > 2016-08-17T07:28:58,955 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1 > 2016-08-17T07:29:00,566 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-3)/1 > 2016-08-17T07:29:00,633 INFO [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-3)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1 > 2016-08-17T07:29:00,635 INFO [HiveServer2-Background-Pool: Thread-6507]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-2)/1 > Status: Failed > 2016-08-17T07:29:00,708 ERROR [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printError(1084)) - Status: Failed > Vertex failed, vertexName=Reducer 3, > vertexId=vertex_1471417242320_0005_293_02, diagnostics=[Task failed, > taskId=task_1471417242320_0005_293_02_00, diagnostics=[TaskAttempt 0 > failed, info=[Error: Error while running task ( failure ) : > attempt_1471417242320_0005_293_02_00_0:java.lang.RuntimeException: > java.lang.RuntimeException: Hive Runtime Error while closing operators: > java.io.IOException: Connection reset by peer > at > org.apache.hadoop.hive.ql.exec.tez.TezProcessor.initializeAndRunProcessor(TezProcessor.java:211) > at > org.apache.hadoop.hive.ql.exec.tez.TezProcessor.run(TezProcessor.java:168) > at > org.apache.tez.runtime.LogicalIOProcessorRuntimeTask.run(LogicalIOProcessorRuntimeTask.java:370) > at > org.apache.tez.runtime.task.TaskRunner2Callable$1.run(TaskRunner2Callable.java:73) > at > org.apache.tez.runtime.task.TaskRunner2Callable$1.run(TaskRunner2Callable.java:61) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1724) > at > org.apache.tez.runtime.task.TaskRunner2Callable.callInternal(TaskRunner2Callable.java:61) > at > org.apache.tez.runtime.task.TaskRunner2Callable.callInternal(TaskRunner2Callable.java:37) > at > org.apache.tez.common.CallableWithNdc.call(CallableWithNdc.java:36) > at > org.apache.hadoop.hive.llap.daemon.impl.StatsRecordingThreadPool
[jira] [Updated] (AMBARI-18194) Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException: Connection reset by peer"
[ https://issues.apache.org/jira/browse/AMBARI-18194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18194: - Status: Patch Available (was: Open) > Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException: > Connection reset by peer" > - > > Key: AMBARI-18194 > URL: https://issues.apache.org/jira/browse/AMBARI-18194 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-18194.patch, AMBARI-18194.patch > > > I'd reported this issue previously in > not see this due to its intermitent nature. > In yesterdays nightly, around 8 tests had failed with this issue and on rerun > 48 failed. Hs2 logs are below: > > > > 2016-08-17T07:28:55,479 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Status: Running (Executing > on YARN cluster with App id application_1471417242320_0006) > > Map 1: 1/1 Reducer 2: 0(+1)/1 Reducer 3: 0/1 > 2016-08-17T07:28:55,480 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: > 0(+1)/1 Reducer 3: 0/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1 > 2016-08-17T07:28:55,681 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1 > 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-2)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1 > 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6507]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1 > 2016-08-17T07:28:58,955 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1 > 2016-08-17T07:29:00,566 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-3)/1 > 2016-08-17T07:29:00,633 INFO [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-3)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1 > 2016-08-17T07:29:00,635 INFO [HiveServer2-Background-Pool: Thread-6507]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-2)/1 > Status: Failed > 2016-08-17T07:29:00,708 ERROR [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printError(1084)) - Status: Failed > Vertex failed, vertexName=Reducer 3, > vertexId=vertex_1471417242320_0005_293_02, diagnostics=[Task failed, > taskId=task_1471417242320_0005_293_02_00, diagnostics=[TaskAttempt 0 > failed, info=[Error: Error while running task ( failure ) : > attempt_1471417242320_0005_293_02_00_0:java.lang.RuntimeException: > java.lang.RuntimeException: Hive Runtime Error while closing operators: > java.io.IOException: Connection reset by peer > at > org.apache.hadoop.hive.ql.exec.tez.TezProcessor.initializeAndRunProcessor(TezProcessor.java:211) > at > org.apache.hadoop.hive.ql.exec.tez.TezProcessor.run(TezProcessor.java:168) > at > org.apache.tez.runtime.LogicalIOProcessorRuntimeTask.run(LogicalIOProcessorRuntimeTask.java:370) > at > org.apache.tez.runtime.task.TaskRunner2Callable$1.run(TaskRunner2Callable.java:73) > at > org.apache.tez.runtime.task.TaskRunner2Callable$1.run(TaskRunner2Callable.java:61) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1724) > at > org.apache.tez.runtime.task.TaskRunner2Callable.callInternal(TaskRunner2Callable.java:61) > at > org.apache.tez.runtime.task.TaskRunner2Callable.callInternal(TaskRunner2Callable.java:37) > at > org.apache.tez.common.CallableWithNdc.call(CallableWithNdc.java:36) > at > org.apache.hadoop.hive.llap.daemon.impl.StatsRecordingThre
[jira] [Commented] (AMBARI-18194) Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException: Connection reset by peer"
[
https://issues.apache.org/jira/browse/AMBARI-18194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426151#comment-15426151
]
Andrew Onischuk commented on AMBARI-18194:
--
{noformat}
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 148 licence.
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Views .. SUCCESS [2.205s]
[INFO] Ambari Metrics Common . SUCCESS [1.214s]
[INFO] Ambari Server . SUCCESS [1:09.942s]
[INFO] Ambari Agent .. SUCCESS [12.907s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1:27.085s
[INFO] Finished at: Thu Aug 18 12:25:54 EEST 2016
[INFO] Final Memory: 86M/1131M
[INFO]
{noformat}
> Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException:
> Connection reset by peer"
> -
>
> Key: AMBARI-18194
> URL: https://issues.apache.org/jira/browse/AMBARI-18194
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-18194.patch, AMBARI-18194.patch
>
>
> I'd reported this issue previously in
> not see this due to its intermitent nature.
> In yesterdays nightly, around 8 tests had failed with this issue and on rerun
> 48 failed. Hs2 logs are below:
>
>
>
> 2016-08-17T07:28:55,479 INFO [HiveServer2-Background-Pool: Thread-6508]:
> SessionState (SessionState.java:printInfo(1075)) - Status: Running (Executing
> on YARN cluster with App id application_1471417242320_0006)
>
> Map 1: 1/1 Reducer 2: 0(+1)/1 Reducer 3: 0/1
> 2016-08-17T07:28:55,480 INFO [HiveServer2-Background-Pool: Thread-6508]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2:
> 0(+1)/1 Reducer 3: 0/1
> Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1
> 2016-08-17T07:28:55,681 INFO [HiveServer2-Background-Pool: Thread-6508]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1
> Reducer 3: 0(+1)/1
> Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1
> 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6503]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1
> Reducer 3: 0(+1,-2)/1
> Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1
> 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6507]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1
> Reducer 3: 0(+1,-1)/1
> Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1
> 2016-08-17T07:28:58,955 INFO [HiveServer2-Background-Pool: Thread-6508]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1
> Reducer 3: 0(+1)/1
> Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1
> 2016-08-17T07:29:00,566 INFO [HiveServer2-Background-Pool: Thread-6508]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1
> Reducer 3: 0(+1,-1)/1
> Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-3)/1
> 2016-08-17T07:29:00,633 INFO [HiveServer2-Background-Pool: Thread-6503]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1
> Reducer 3: 0(+1,-3)/1
> Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1
> 2016-08-17T07:29:00,635 INFO [HiveServer2-Background-Pool: Thread-6507]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1
> Reducer 3: 0(+1,-2)/1
> Status: Failed
> 2016-08-17T07:29:00,708 ERROR [HiveServer2-Background-Pool: Thread-6503]:
> SessionState (SessionState.java:printError(1084)) - Status: Failed
> Vertex failed, vertexName=Reducer 3,
> vertexId=vertex_1471417242320_0005_293_02, diagnostics=[Task failed,
> taskId=task_1471417242320_0005_293_02_00, diagnostics=[TaskAttempt 0
> failed, info=[Error: Error while running task ( failure ) :
> attempt_1471417242320_0005_293_02_00_0:java.lang.RuntimeException:
> java.lang.RuntimeException: Hive Runtime Error while closing operators:
> java.io.IOException: Connection reset by peer
> at
> org.apache.hadoop.hive.ql.exec.tez.TezProcessor.initializeAndRunProcessor(TezProcessor.java:211)
> at
> org.apache.hadoop.hive.ql.exec.tez.TezProcessor.run(TezProcessor.java:168)
> at
> org.apache
[jira] [Commented] (AMBARI-18194) Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException: Connection reset by peer"
[
https://issues.apache.org/jira/browse/AMBARI-18194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426152#comment-15426152
]
Hadoop QA commented on AMBARI-18194:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824316/AMBARI-18194.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8449//console
This message is automatically generated.
> Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException:
> Connection reset by peer"
> -
>
> Key: AMBARI-18194
> URL: https://issues.apache.org/jira/browse/AMBARI-18194
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-18194.patch, AMBARI-18194.patch
>
>
> I'd reported this issue previously in
> not see this due to its intermitent nature.
> In yesterdays nightly, around 8 tests had failed with this issue and on rerun
> 48 failed. Hs2 logs are below:
>
>
>
> 2016-08-17T07:28:55,479 INFO [HiveServer2-Background-Pool: Thread-6508]:
> SessionState (SessionState.java:printInfo(1075)) - Status: Running (Executing
> on YARN cluster with App id application_1471417242320_0006)
>
> Map 1: 1/1 Reducer 2: 0(+1)/1 Reducer 3: 0/1
> 2016-08-17T07:28:55,480 INFO [HiveServer2-Background-Pool: Thread-6508]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2:
> 0(+1)/1 Reducer 3: 0/1
> Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1
> 2016-08-17T07:28:55,681 INFO [HiveServer2-Background-Pool: Thread-6508]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1
> Reducer 3: 0(+1)/1
> Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1
> 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6503]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1
> Reducer 3: 0(+1,-2)/1
> Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1
> 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6507]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1
> Reducer 3: 0(+1,-1)/1
> Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1
> 2016-08-17T07:28:58,955 INFO [HiveServer2-Background-Pool: Thread-6508]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1
> Reducer 3: 0(+1)/1
> Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1
> 2016-08-17T07:29:00,566 INFO [HiveServer2-Background-Pool: Thread-6508]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1
> Reducer 3: 0(+1,-1)/1
> Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-3)/1
> 2016-08-17T07:29:00,633 INFO [HiveServer2-Background-Pool: Thread-6503]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1
> Reducer 3: 0(+1,-3)/1
> Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1
> 2016-08-17T07:29:00,635 INFO [HiveServer2-Background-Pool: Thread-6507]:
> SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1
> Reducer 3: 0(+1,-2)/1
> Status: Failed
> 2016-08-17T07:29:00,708 ERROR [HiveServer2-Background-Pool: Thread-6503]:
> SessionState (SessionState.java:printError(1084)) - Status: Failed
> Vertex failed, vertexName=Reducer 3,
> vertexId=vertex_1471417242320_0005_293_02, diagnostics=[Task failed,
> taskId=task_1471417242320_0005_293_02_00, diagnostics=[TaskAttempt 0
> failed, info=[Error: Error while running task ( failure ) :
> attempt_1471417242320_0005_293_02_00_0:java.lang.RuntimeException:
> java.lang.RuntimeException: Hive Runtime Error while closing operators:
> java.io.IOException: Connection reset by peer
> at
> org.apache.hadoop.hive.ql.exec.tez.TezProcessor.initializeAndRunProcessor(TezProcessor.java:211)
> at
> org.apache.hadoop.hive.ql.exec.tez.TezProcessor.run(TezProcessor.java:168)
> at
> org.apache.tez.runtime.LogicalIOProcessorRuntimeTask.run(LogicalIOProcessorRuntimeTask.java:370)
> at
> org.apache.tez.runtime.task.TaskRunner2Callable$1.run(TaskRunner2Callable.java:73)
> at
> org.apache.tez.runtime.task.TaskRunner2Callable$1.run(TaskRunner2Callable.java:61)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInforma
[jira] [Created] (AMBARI-18195) HST server down after deploy
Shreya Bhat created AMBARI-18195:
Summary: HST server down after deploy
Key: AMBARI-18195
URL: https://issues.apache.org/jira/browse/AMBARI-18195
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Shreya Bhat
Priority: Blocker
Fix For: 2.4.0
Deploy type : UI
Error in hst-server logs :
{code}
18 Aug 2016 03:50:07,620 INFO [main] HttpSecurityBeanDefinitionParser:264 -
Checking sorted filter chain: [Root bean: class
[org.springframework.security.web.context.SecurityContextPersistenceFilter];
scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
autowireCandidate=true; primary=false; factoryBeanName=null;
factoryMethodName=null; initMethodName=null; destroyMethodName=null, order =
300, Root bean: class
[org.springframework.security.web.authentication.www.BasicAuthenticationFilter];
scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
autowireCandidate=true; primary=false; factoryBeanName=null;
factoryMethodName=null; initMethodName=null; destroyMethodName=null, order =
1200, , order = 1201, Root bean: class
[org.springframework.security.web.savedrequest.RequestCacheAwareFilter];
scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
autowireCandidate=true; primary=false; factoryBeanName=null;
factoryMethodName=null; initMethodName=null; destroyMethodName=null, order =
1300, Root bean: class
[org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter];
scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
autowireCandidate=true; primary=false; factoryBeanName=null;
factoryMethodName=null; initMethodName=null; destroyMethodName=null, order =
1400, Root bean: class
[org.springframework.security.web.authentication.AnonymousAuthenticationFilter];
scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
autowireCandidate=true; primary=false; factoryBeanName=null;
factoryMethodName=null; initMethodName=null; destroyMethodName=null, order =
1700, Root bean: class
[org.springframework.security.web.session.SessionManagementFilter]; scope=;
abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
autowireCandidate=true; primary=false; factoryBeanName=null;
factoryMethodName=null; initMethodName=null; destroyMethodName=null, order =
1800, Root bean: class
[org.springframework.security.web.access.ExceptionTranslationFilter]; scope=;
abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
autowireCandidate=true; primary=false; factoryBeanName=null;
factoryMethodName=null; initMethodName=null; destroyMethodName=null, order =
1900,
,
order = 2000]
18 Aug 2016 03:50:07,772 INFO [main] DefaultSecurityFilterChain:28 - Creating
filter chain: org.springframework.security.web.util.AnyRequestMatcher@1,
[org.springframework.security.web.context.SecurityContextPersistenceFilter@58496c97,
org.springframework.security.web.authentication.www.BasicAuthenticationFilter@ad3324b,
com.hortonworks.support.tools.server.security.authorization.SupportToolAuthorizationFilter@3872bc37,
org.springframework.security.web.savedrequest.RequestCacheAwareFilter@1a87b51,
org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@12968227,
org.springframework.security.web.authentication.AnonymousAuthenticationFilter@144ab54,
org.springframework.security.web.session.SessionManagementFilter@2cfa2c4f,
org.springframework.security.web.access.ExceptionTranslationFilter@6ecab872,
org.springframework.security.web.access.intercept.FilterSecurityInterceptor@48eb9836]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18196) Generate REST API docs with Swagger for Log Search
Olivér Szabó created AMBARI-18196: - Summary: Generate REST API docs with Swagger for Log Search Key: AMBARI-18196 URL: https://issues.apache.org/jira/browse/AMBARI-18196 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.4.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18196) Generate REST API docs with Swagger for Log Search
[ https://issues.apache.org/jira/browse/AMBARI-18196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-18196: -- Attachment: AMBARI-18196.patch > Generate REST API docs with Swagger for Log Search > -- > > Key: AMBARI-18196 > URL: https://issues.apache.org/jira/browse/AMBARI-18196 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-18196.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18197) HBase region server start fails after disabling kerberos
[
https://issues.apache.org/jira/browse/AMBARI-18197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shreya Bhat updated AMBARI-18197:
-
Labels: system_test (was: )
Fix Version/s: 2.4.0
> HBase region server start fails after disabling kerberos
>
>
> Key: AMBARI-18197
> URL: https://issues.apache.org/jira/browse/AMBARI-18197
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
> Labels: system_test
> Fix For: 2.4.0
>
>
> STR :
> 1. Install cluster
> 2. Enable kerberos
> 3. Disable kerberos
> The disable process fails at start services
> Error :
> {code}
> "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py\",
> line 198, in \nHbaseRegionServer().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py\",
> line 124, in start\nself.post_start(env, upgrade_type=upgrade_type)\n
> File
> \"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py\",
> line 89, in post_start\nself.apply_atlas_acl(params.hbase_user)\n File
> \"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py\",
> line 114, in apply_atlas_acl\nshell.checked_call(format(\"{kinit_cmd};
> {perm_cmd}\"), user=params.hbase_user, tries=10, try_sleep=10)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 71, in inner\nresult = function(command, **kwargs)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 294, in _call\nraise
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/hbase.service.keytab
> hbase/nat-s11-4-kdxs-ambari-rbac-1-1.openstacklo...@hwqe.hortonworks.com;
> echo \"grant 'atlas', 'RWXCA', 'atlas_titan'\" | hbase shell -n' returned 1.
> ERROR ArgumentError: Can't find a table: atlas_titan",
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18197) HBase region server start fails after disabling kerberos
Shreya Bhat created AMBARI-18197:
Summary: HBase region server start fails after disabling kerberos
Key: AMBARI-18197
URL: https://issues.apache.org/jira/browse/AMBARI-18197
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Shreya Bhat
STR :
1. Install cluster
2. Enable kerberos
3. Disable kerberos
The disable process fails at start services
Error :
{code}
"Traceback (most recent call last):\n File
\"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py\",
line 198, in \nHbaseRegionServer().execute()\n File
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
line 280, in execute\nmethod(env)\n File
\"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py\",
line 124, in start\nself.post_start(env, upgrade_type=upgrade_type)\n
File
\"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py\",
line 89, in post_start\nself.apply_atlas_acl(params.hbase_user)\n File
\"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py\",
line 114, in apply_atlas_acl\nshell.checked_call(format(\"{kinit_cmd};
{perm_cmd}\"), user=params.hbase_user, tries=10, try_sleep=10)\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
71, in inner\nresult = function(command, **kwargs)\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
294, in _call\nraise
Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of
'/usr/bin/kinit -kt /etc/security/keytabs/hbase.service.keytab
hbase/nat-s11-4-kdxs-ambari-rbac-1-1.openstacklo...@hwqe.hortonworks.com; echo
\"grant 'atlas', 'RWXCA', 'atlas_titan'\" | hbase shell -n' returned 1. ERROR
ArgumentError: Can't find a table: atlas_titan",
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18198) Doc updates about ldap sync related properties
Olivér Szabó created AMBARI-18198: - Summary: Doc updates about ldap sync related properties Key: AMBARI-18198 URL: https://issues.apache.org/jira/browse/AMBARI-18198 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18198) Doc updates about ldap sync related properties
[ https://issues.apache.org/jira/browse/AMBARI-18198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-18198: -- Attachment: AMBARI-18198.patch > Doc updates about ldap sync related properties > -- > > Key: AMBARI-18198 > URL: https://issues.apache.org/jira/browse/AMBARI-18198 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-18198.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18157) Hive service check is failing after RU
[
https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18157:
Attachment: AMBARI-18157-trunk.patch
AMBARI-18157-branch24.patch
> Hive service check is failing after RU
> --
>
> Key: AMBARI-18157
> URL: https://issues.apache.org/jira/browse/AMBARI-18157
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: 240RMApproved, system_test
> Fix For: 2.4.0
>
> Attachments: AMBARI-18157-branch24.patch, AMBARI-18157-trunk.patch
>
>
> {code}
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh $HOSTNAME 50111
> idtest.ambari-qa.1471340206.23.pig
> /etc/security/keytabs/smokeuser.headless.keytab true /usr/bin/kinit
> ambari-qa@REALM_NAME /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke
> Test (ddl cmd): Failed. : {"error":"Unauthorized connection for super-user:
> HTTP/HOST_NAME@REALM_NAME from IP HOST_IP"}http_code <500>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18157) Hive service check is failing after cluster Kerberization
[
https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18157:
Summary: Hive service check is failing after cluster Kerberization (was:
Hive service check is failing after RU)
> Hive service check is failing after cluster Kerberization
> -
>
> Key: AMBARI-18157
> URL: https://issues.apache.org/jira/browse/AMBARI-18157
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: 240RMApproved, system_test
> Fix For: 2.4.0
>
> Attachments: AMBARI-18157-branch24.patch, AMBARI-18157-trunk.patch
>
>
> {code}
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh $HOSTNAME 50111
> idtest.ambari-qa.1471340206.23.pig
> /etc/security/keytabs/smokeuser.headless.keytab true /usr/bin/kinit
> ambari-qa@REALM_NAME /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke
> Test (ddl cmd): Failed. : {"error":"Unauthorized connection for super-user:
> HTTP/HOST_NAME@REALM_NAME from IP HOST_IP"}http_code <500>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18157) Hive service check is failing after cluster Kerberization
[
https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18157:
Status: Patch Available (was: Open)
> Hive service check is failing after cluster Kerberization
> -
>
> Key: AMBARI-18157
> URL: https://issues.apache.org/jira/browse/AMBARI-18157
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: 240RMApproved, system_test
> Fix For: 2.4.0
>
> Attachments: AMBARI-18157-branch24.patch, AMBARI-18157-trunk.patch
>
>
> {code}
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh $HOSTNAME 50111
> idtest.ambari-qa.1471340206.23.pig
> /etc/security/keytabs/smokeuser.headless.keytab true /usr/bin/kinit
> ambari-qa@REALM_NAME /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke
> Test (ddl cmd): Failed. : {"error":"Unauthorized connection for super-user:
> HTTP/HOST_NAME@REALM_NAME from IP HOST_IP"}http_code <500>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster
[
https://issues.apache.org/jira/browse/AMBARI-18167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley reopened AMBARI-18167:
--
Reopened due to unit test failures indicating that this patch didn't actually
work:
{code}
junit.framework.AssertionFailedError: Missing
hdp_2_4_0_0_kafka_broker_deprecate_port in upgrade from HDP-2.3 to HDP-2.5
(ROLLING)
at
org.apache.ambari.server.state.stack.ConfigUpgradeValidityTest.assertIdDefinitionExists(ConfigUpgradeValidityTest.java:190)
at
org.apache.ambari.server.state.stack.ConfigUpgradeValidityTest.testConfigurationDefinitionsExist(ConfigUpgradeValidityTest.java:134)
{code}
> RU: Kafka brokers restart was stopped during downgrade cluster
> --
>
> Key: AMBARI-18167
> URL: https://issues.apache.org/jira/browse/AMBARI-18167
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18167.patch
>
>
> Kafka broker restart failed due to below error:
> {noformat}
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'xasecure.audit.destination.db' was not found in configurations dictionary!
> {noformat}
> Solution:
> During RU downgrade, runs on downgrade as well, which deleted
> {{xasecure.audit.destination.db}} config property.
> {noformat}
>
>id="hdp_2_5_0_0_remove_ranger_kafka_audit_db" />
>
> {noformat}
> Need to override it with a blank element.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18194) Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException: Connection reset by peer"
[ https://issues.apache.org/jira/browse/AMBARI-18194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18194: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 > Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException: > Connection reset by peer" > - > > Key: AMBARI-18194 > URL: https://issues.apache.org/jira/browse/AMBARI-18194 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-18194.patch, AMBARI-18194.patch > > > I'd reported this issue previously in > not see this due to its intermitent nature. > In yesterdays nightly, around 8 tests had failed with this issue and on rerun > 48 failed. Hs2 logs are below: > > > > 2016-08-17T07:28:55,479 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Status: Running (Executing > on YARN cluster with App id application_1471417242320_0006) > > Map 1: 1/1 Reducer 2: 0(+1)/1 Reducer 3: 0/1 > 2016-08-17T07:28:55,480 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: > 0(+1)/1 Reducer 3: 0/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1 > 2016-08-17T07:28:55,681 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1 > 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-2)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1 > 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6507]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1 > 2016-08-17T07:28:58,955 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1 > 2016-08-17T07:29:00,566 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-3)/1 > 2016-08-17T07:29:00,633 INFO [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-3)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1 > 2016-08-17T07:29:00,635 INFO [HiveServer2-Background-Pool: Thread-6507]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-2)/1 > Status: Failed > 2016-08-17T07:29:00,708 ERROR [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printError(1084)) - Status: Failed > Vertex failed, vertexName=Reducer 3, > vertexId=vertex_1471417242320_0005_293_02, diagnostics=[Task failed, > taskId=task_1471417242320_0005_293_02_00, diagnostics=[TaskAttempt 0 > failed, info=[Error: Error while running task ( failure ) : > attempt_1471417242320_0005_293_02_00_0:java.lang.RuntimeException: > java.lang.RuntimeException: Hive Runtime Error while closing operators: > java.io.IOException: Connection reset by peer > at > org.apache.hadoop.hive.ql.exec.tez.TezProcessor.initializeAndRunProcessor(TezProcessor.java:211) > at > org.apache.hadoop.hive.ql.exec.tez.TezProcessor.run(TezProcessor.java:168) > at > org.apache.tez.runtime.LogicalIOProcessorRuntimeTask.run(LogicalIOProcessorRuntimeTask.java:370) > at > org.apache.tez.runtime.task.TaskRunner2Callable$1.run(TaskRunner2Callable.java:73) > at > org.apache.tez.runtime.task.TaskRunner2Callable$1.run(TaskRunner2Callable.java:61) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1724) > at > org.apache.tez.runtime.task.TaskRunner2Callable.callInternal(TaskRunner2Callable.java:61) > at > org.apache.tez.runtime.task.TaskRunner2Callable.callInternal(TaskRunner2Callable.java:37) > at > org.apache.tez.common.CallableWithNdc.call(CallableWithNdc.java:36) >
[jira] [Commented] (AMBARI-18157) Hive service check is failing after cluster Kerberization
[
https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426580#comment-15426580
]
Hadoop QA commented on AMBARI-18157:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824349/AMBARI-18157-trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8450//console
This message is automatically generated.
> Hive service check is failing after cluster Kerberization
> -
>
> Key: AMBARI-18157
> URL: https://issues.apache.org/jira/browse/AMBARI-18157
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: 240RMApproved, system_test
> Fix For: 2.4.0
>
> Attachments: AMBARI-18157-branch24.patch, AMBARI-18157-trunk.patch
>
>
> {code}
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh $HOSTNAME 50111
> idtest.ambari-qa.1471340206.23.pig
> /etc/security/keytabs/smokeuser.headless.keytab true /usr/bin/kinit
> ambari-qa@REALM_NAME /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke
> Test (ddl cmd): Failed. : {"error":"Unauthorized connection for super-user:
> HTTP/HOST_NAME@REALM_NAME from IP HOST_IP"}http_code <500>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18192) Can't build RPM package due to lack of upgradeHelper.py
[
https://issues.apache.org/jira/browse/AMBARI-18192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426583#comment-15426583
]
Hadoop QA commented on AMBARI-18192:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824300/AMBARI-18192.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8451//console
This message is automatically generated.
> Can't build RPM package due to lack of upgradeHelper.py
> ---
>
> Key: AMBARI-18192
> URL: https://issues.apache.org/jira/browse/AMBARI-18192
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-18192.patch
>
>
> When I ran {{mvn clean install package rpm:rpm -DskipTests}}, I got an error
> {code}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6:14.285s
> [INFO] Finished at: Thu Aug 18 03:53:29 UTC 2016
> [INFO] Final Memory: 226M/1125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single
> (make-assembly) on project ambari-server: Failed to create assembly: Error
> adding file to archive:
> /tmp/ambari/ambari-server/src/main/python/upgradeHelper.py isn't a file. ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18191) "Restart all required" services operation failed at Metrics Collector since HDFS was not yet up
[
https://issues.apache.org/jira/browse/AMBARI-18191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426588#comment-15426588
]
Hadoop QA commented on AMBARI-18191:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824277/AMBARI-18191.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8452//console
This message is automatically generated.
> "Restart all required" services operation failed at Metrics Collector since
> HDFS was not yet up
> ---
>
> Key: AMBARI-18191
> URL: https://issues.apache.org/jira/browse/AMBARI-18191
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18191.patch
>
>
> ambari-server --hash
> 4017036da951a10f519a578de934308cf866ba50
> *Steps*
> # Deploy HDP-2.3.6 cluster with Ambari 2.2.2.0 (AMS is configured in
> distributed mode)
> # Upgrade Ambari to 2.4.0.0 and let it complete
> # Open Ambari web UI and hit "Restart all required" under Actions menu
> *Result*
> The operation fails while trying to restart Metrics Collector as it tried to
> make a WebHDFS call while HDFS was not started:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 148, in
> AmsCollector().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 725, in restart
> self.start(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 46, in start
> self.configure(env, action = 'start') # for security
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 41, in configure
> hbase('master', action)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py",
> line 213, in hbase
> dfs_type=params.dfs_type
> 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/libraries/providers/hdfs_resource.py",
> line 459, in action_create_on_execute
> self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 456, in action_delayed
> self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 256, in action_delayed
> self._set_mode(self.target_status)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 363, in _set_mode
> self.util.run_command(self.main_resource.resource.target,
> 'SETPERMISSION', method='PUT', permission=self.mode, assertable_result=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 179, in run_command
> _, out, err = get_user_call_output(cmd, user=self.run_user,
> logoutput=self.logoutput, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 61, in get_user_call_output
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w
> '%{http_code}' -X PUT --negotiate -u :
> 'http://vsharma-eu-mt-5.openstacklocal:50070/webhdfs/v1/user/ams/hbase?op=SETPERMISSION&user.name=hdfs&permission=775'
> 1>/tmp/tmp8twcZt 2>/tmp/tmpLPih9a' returned 7. curl: (7) couldn't connect to
> host
> 401
> {code}
> Afterwards, restarted HDFS individually first and then hit "Restart all
> Required" - the operation was successful
> Looks like th
[jira] [Updated] (AMBARI-18165) Alert on Atlas after adding it to a secure cluster as HBase table initialization fails
[
https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18165:
---
Summary: Alert on Atlas after adding it to a secure cluster as HBase table
initialization fails (was: Hbase RegionServer start fails)
> Alert on Atlas after adding it to a secure cluster as HBase table
> initialization fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 198, in
> HbaseRegionServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"),
> user=params.hbase_user, tries=10, try_sleep=10)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1.
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18165) Alert on Atlas after adding it to a secure cluster as HBase table initialization fails
[
https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18165:
---
Attachment: AMBARI-18165.patch
> Alert on Atlas after adding it to a secure cluster as HBase table
> initialization fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 198, in
> HbaseRegionServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"),
> user=params.hbase_user, tries=10, try_sleep=10)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1.
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18165) Alert on Atlas after adding it to a secure cluster as HBase table initialization fails
[
https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18165:
---
Attachment: (was: AMBARI-18165.patch)
> Alert on Atlas after adding it to a secure cluster as HBase table
> initialization fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 198, in
> HbaseRegionServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"),
> user=params.hbase_user, tries=10, try_sleep=10)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1.
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18199) Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
Dmytro Sen created AMBARI-18199:
---
Summary: Wrong hostname in timeline.metrics.service.webapp.address
breaks AMS HA
Key: AMBARI-18199
URL: https://issues.apache.org/jira/browse/AMBARI-18199
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: trunk
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: trunk
On adding additional Collector the webapp address contains wrong hostname.
{noformat}
java.net.BindException: Port in use: ambari-sid-5.com:6188
at
org.apache.hadoop.http.HttpServer2.openListeners(HttpServer2.java:919)
at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:856)
at org.apache.hadoop.yarn.webapp.WebApps$Builder.start(WebApps.java:374)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.startWebApp(ApplicationHistoryServer.java:180)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceStart(ApplicationHistoryServer.java:92)
at
org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:138)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
Caused by: java.net.BindException: Cannot assign requested address
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18199) Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
[
https://issues.apache.org/jira/browse/AMBARI-18199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-18199:
Status: Patch Available (was: Open)
> Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
> ---
>
> Key: AMBARI-18199
> URL: https://issues.apache.org/jira/browse/AMBARI-18199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18199.patch
>
>
> On adding additional Collector the webapp address contains wrong hostname.
> {noformat}
> java.net.BindException: Port in use: ambari-sid-5.com:6188
> at
> org.apache.hadoop.http.HttpServer2.openListeners(HttpServer2.java:919)
> at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:856)
> at
> org.apache.hadoop.yarn.webapp.WebApps$Builder.start(WebApps.java:374)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.startWebApp(ApplicationHistoryServer.java:180)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceStart(ApplicationHistoryServer.java:92)
> at
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:138)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: java.net.BindException: Cannot assign requested address
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18199) Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
[
https://issues.apache.org/jira/browse/AMBARI-18199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-18199:
Attachment: AMBARI-18199.patch
> Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
> ---
>
> Key: AMBARI-18199
> URL: https://issues.apache.org/jira/browse/AMBARI-18199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18199.patch
>
>
> On adding additional Collector the webapp address contains wrong hostname.
> {noformat}
> java.net.BindException: Port in use: ambari-sid-5.com:6188
> at
> org.apache.hadoop.http.HttpServer2.openListeners(HttpServer2.java:919)
> at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:856)
> at
> org.apache.hadoop.yarn.webapp.WebApps$Builder.start(WebApps.java:374)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.startWebApp(ApplicationHistoryServer.java:180)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceStart(ApplicationHistoryServer.java:92)
> at
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:138)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: java.net.BindException: Cannot assign requested address
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18199) Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
[
https://issues.apache.org/jira/browse/AMBARI-18199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426669#comment-15426669
]
Hadoop QA commented on AMBARI-18199:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824391/AMBARI-18199.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8453//console
This message is automatically generated.
> Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
> ---
>
> Key: AMBARI-18199
> URL: https://issues.apache.org/jira/browse/AMBARI-18199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18199.patch
>
>
> On adding additional Collector the webapp address contains wrong hostname.
> {noformat}
> java.net.BindException: Port in use: ambari-sid-5.com:6188
> at
> org.apache.hadoop.http.HttpServer2.openListeners(HttpServer2.java:919)
> at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:856)
> at
> org.apache.hadoop.yarn.webapp.WebApps$Builder.start(WebApps.java:374)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.startWebApp(ApplicationHistoryServer.java:180)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceStart(ApplicationHistoryServer.java:92)
> at
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:138)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: java.net.BindException: Cannot assign requested address
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster
[
https://issues.apache.org/jira/browse/AMBARI-18167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426672#comment-15426672
]
Hudson commented on AMBARI-18167:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5547 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5547/])
Revert "AMBARI-18167: RU: Kafka brokers restart was stopped during (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=813938395f23ca1a70bf75b3bea3eeaa54ea1997])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml
> RU: Kafka brokers restart was stopped during downgrade cluster
> --
>
> Key: AMBARI-18167
> URL: https://issues.apache.org/jira/browse/AMBARI-18167
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18167.patch
>
>
> Kafka broker restart failed due to below error:
> {noformat}
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'xasecure.audit.destination.db' was not found in configurations dictionary!
> {noformat}
> Solution:
> During RU downgrade, runs on downgrade as well, which deleted
> {{xasecure.audit.destination.db}} config property.
> {noformat}
>
>id="hdp_2_5_0_0_remove_ranger_kafka_audit_db" />
>
> {noformat}
> Need to override it with a blank element.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18200) Add Service button is not disabled if all services are installed
Aleksandr Kovalenko created AMBARI-18200: Summary: Add Service button is not disabled if all services are installed Key: AMBARI-18200 URL: https://issues.apache.org/jira/browse/AMBARI-18200 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18165) Alert on Atlas after adding it to a secure cluster as HBase table initialization fails
[
https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18165:
---
Attachment: (was: AMBARI-18165.patch)
> Alert on Atlas after adding it to a secure cluster as HBase table
> initialization fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 198, in
> HbaseRegionServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"),
> user=params.hbase_user, tries=10, try_sleep=10)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1.
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18165) Alert on Atlas after adding it to a secure cluster as HBase table initialization fails
[
https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18165:
---
Attachment: AMBARI-18165.patch
> Alert on Atlas after adding it to a secure cluster as HBase table
> initialization fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 198, in
> HbaseRegionServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"),
> user=params.hbase_user, tries=10, try_sleep=10)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1.
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18200) Add Service button is not disabled if all services are installed
[ https://issues.apache.org/jira/browse/AMBARI-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-18200: - Attachment: AMBARI-18200.patch > Add Service button is not disabled if all services are installed > > > Key: AMBARI-18200 > URL: https://issues.apache.org/jira/browse/AMBARI-18200 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-18200.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18200) Add Service button is not disabled if all services are installed
[ https://issues.apache.org/jira/browse/AMBARI-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-18200: - Status: Patch Available (was: Open) > Add Service button is not disabled if all services are installed > > > Key: AMBARI-18200 > URL: https://issues.apache.org/jira/browse/AMBARI-18200 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-18200.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18201) Re-enable testDeleteHostComponentInVariousStates
Sumit Mohanty created AMBARI-18201:
--
Summary: Re-enable testDeleteHostComponentInVariousStates
Key: AMBARI-18201
URL: https://issues.apache.org/jira/browse/AMBARI-18201
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Sumit Mohanty
Assignee: Nahappan Somasundaram
Priority: Critical
Fix For: trunk
Builds on trunk have been failing due to AMBARI-18011:
{code}
Error Message
Exception [EclipseLink-4002] (Eclipse Persistence Services -
2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
statement was aborted because it would have caused a duplicate key value in a
unique or primary key constraint or unique index identified by
'SQL160810131838480' defined on 'REQUEST'.
Error Code: 2
Call: INSERT INTO request (request_id, cluster_id, command_name, create_time,
end_time, exclusive_execution, inputs, request_context, request_type,
start_time, status, request_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?)
bind => [12 parameters bound]
Query:
InsertObjectQuery(org.apache.ambari.server.orm.entities.StageEntity@2753fa)
Stacktrace
javax.persistence.RollbackException:
Exception [EclipseLink-4002] (Eclipse Persistence Services -
2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
statement was aborted because it would have caused a duplicate key value in a
unique or primary key constraint or unique index identified by
'SQL160810131838480' defined on 'REQUEST'.
Error Code: 2
Call: INSERT INTO request (request_id, cluster_id, command_name, create_time,
end_time, exclusive_execution, inputs, request_context, request_type,
start_time, status, request_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?)
bind => [12 parameters bound]
Query:
InsertObjectQuery(org.apache.ambari.server.orm.entities.StageEntity@2753fa)
at
org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
Caused by: org.eclipse.persistence.exceptions.DatabaseException:
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
statement was aborted because it would have caused a duplicate key value in a
unique or primary key constraint or unique index identified by
'SQL160810131838480' defined on 'REQUEST'.
Error Code: 2
Call: INSERT INTO request (request_id, cluster_id, command_name, create_time,
end_time, exclusive_execution, inputs, request_context, request_type,
start_time, status, request_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?)
bind => [12 parameters bound]
Query:
InsertObjectQuery(org.apache.ambari.server.orm.entities.StageEntity@2753fa)
at
org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
Caused by: java.sql.SQLIntegrityConstraintViolationException: The statement was
aborted because it would have caused a duplicate key value in a unique or
primary key constraint or unique index identified by 'SQL160810131838480'
defined on 'REQUEST'.
at
org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
Caused by: org.apache.derby.impl.jdbc.EmbedSQLException: The statement was
aborted because it would have caused a duplicate key value in a unique or
primary key constraint or unique index identified by 'SQL160810131838480'
defined on 'REQUEST'.
at
org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
Caused by: org.apache.derby.iapi.error.StandardException: The statement was
aborted because it would have caused a duplicate key value in a unique or
primary key constraint or unique index identified by 'SQL160810131838480'
defined on 'REQUEST'.
at
org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
{code}
{code}
Exception [EclipseLink-4002] (Eclipse Persistence Services -
2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
statement was aborted because it would have caused a duplicate key value in a
unique or primary key constraint or unique index identified by
'SQL160810131838480' defined on 'REQUEST'.
Error Code: 2
Call: INSERT INTO request (request_id, cluster_id, command_name, create_time,
end_time, exclusive_execution, inputs, request_context, request_type,
start_time, status, request_schedule_id) VALUES (
[jira] [Updated] (AMBARI-18104) Unit Tests Broken Due to AMBARI-18011
[
https://issues.apache.org/jira/browse/AMBARI-18104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-18104:
---
Fix Version/s: (was: 2.5.0)
trunk
> Unit Tests Broken Due to AMBARI-18011
> -
>
> Key: AMBARI-18104
> URL: https://issues.apache.org/jira/browse/AMBARI-18104
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Nahappan Somasundaram
>Priority: Blocker
> Fix For: trunk
>
>
> Builds on trunk have been failing due to AMBARI-18011:
> {code}
> Error Message
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
> statement was aborted because it would have caused a duplicate key value in a
> unique or primary key constraint or unique index identified by
> 'SQL160810131838480' defined on 'REQUEST'.
> Error Code: 2
> Call: INSERT INTO request (request_id, cluster_id, command_name, create_time,
> end_time, exclusive_execution, inputs, request_context, request_type,
> start_time, status, request_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?,
> ?, ?, ?)
> bind => [12 parameters bound]
> Query:
> InsertObjectQuery(org.apache.ambari.server.orm.entities.StageEntity@2753fa)
> Stacktrace
> javax.persistence.RollbackException:
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
> statement was aborted because it would have caused a duplicate key value in a
> unique or primary key constraint or unique index identified by
> 'SQL160810131838480' defined on 'REQUEST'.
> Error Code: 2
> Call: INSERT INTO request (request_id, cluster_id, command_name, create_time,
> end_time, exclusive_execution, inputs, request_context, request_type,
> start_time, status, request_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?,
> ?, ?, ?)
> bind => [12 parameters bound]
> Query:
> InsertObjectQuery(org.apache.ambari.server.orm.entities.StageEntity@2753fa)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> Caused by: org.eclipse.persistence.exceptions.DatabaseException:
> Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
> statement was aborted because it would have caused a duplicate key value in a
> unique or primary key constraint or unique index identified by
> 'SQL160810131838480' defined on 'REQUEST'.
> Error Code: 2
> Call: INSERT INTO request (request_id, cluster_id, command_name, create_time,
> end_time, exclusive_execution, inputs, request_context, request_type,
> start_time, status, request_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?,
> ?, ?, ?)
> bind => [12 parameters bound]
> Query:
> InsertObjectQuery(org.apache.ambari.server.orm.entities.StageEntity@2753fa)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> Caused by: java.sql.SQLIntegrityConstraintViolationException: The statement
> was aborted because it would have caused a duplicate key value in a unique or
> primary key constraint or unique index identified by 'SQL160810131838480'
> defined on 'REQUEST'.
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> Caused by: org.apache.derby.impl.jdbc.EmbedSQLException: The statement was
> aborted because it would have caused a duplicate key value in a unique or
> primary key constraint or unique index identified by 'SQL160810131838480'
> defined on 'REQUEST'.
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> Caused by: org.apache.derby.iapi.error.StandardException: The statement was
> aborted because it would have caused a duplicate key value in a unique or
> primary key constraint or unique index identified by 'SQL160810131838480'
> defined on 'REQUEST'.
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> {code}
> {code}
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
> statement was aborted because it would have caused a duplicate
[jira] [Updated] (AMBARI-18104) Unit Tests Broken Due to AMBARI-18011
[
https://issues.apache.org/jira/browse/AMBARI-18104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-18104:
---
Assignee: Nahappan Somasundaram
> Unit Tests Broken Due to AMBARI-18011
> -
>
> Key: AMBARI-18104
> URL: https://issues.apache.org/jira/browse/AMBARI-18104
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Nahappan Somasundaram
>Priority: Blocker
> Fix For: trunk
>
>
> Builds on trunk have been failing due to AMBARI-18011:
> {code}
> Error Message
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
> statement was aborted because it would have caused a duplicate key value in a
> unique or primary key constraint or unique index identified by
> 'SQL160810131838480' defined on 'REQUEST'.
> Error Code: 2
> Call: INSERT INTO request (request_id, cluster_id, command_name, create_time,
> end_time, exclusive_execution, inputs, request_context, request_type,
> start_time, status, request_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?,
> ?, ?, ?)
> bind => [12 parameters bound]
> Query:
> InsertObjectQuery(org.apache.ambari.server.orm.entities.StageEntity@2753fa)
> Stacktrace
> javax.persistence.RollbackException:
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
> statement was aborted because it would have caused a duplicate key value in a
> unique or primary key constraint or unique index identified by
> 'SQL160810131838480' defined on 'REQUEST'.
> Error Code: 2
> Call: INSERT INTO request (request_id, cluster_id, command_name, create_time,
> end_time, exclusive_execution, inputs, request_context, request_type,
> start_time, status, request_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?,
> ?, ?, ?)
> bind => [12 parameters bound]
> Query:
> InsertObjectQuery(org.apache.ambari.server.orm.entities.StageEntity@2753fa)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> Caused by: org.eclipse.persistence.exceptions.DatabaseException:
> Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
> statement was aborted because it would have caused a duplicate key value in a
> unique or primary key constraint or unique index identified by
> 'SQL160810131838480' defined on 'REQUEST'.
> Error Code: 2
> Call: INSERT INTO request (request_id, cluster_id, command_name, create_time,
> end_time, exclusive_execution, inputs, request_context, request_type,
> start_time, status, request_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?,
> ?, ?, ?)
> bind => [12 parameters bound]
> Query:
> InsertObjectQuery(org.apache.ambari.server.orm.entities.StageEntity@2753fa)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> Caused by: java.sql.SQLIntegrityConstraintViolationException: The statement
> was aborted because it would have caused a duplicate key value in a unique or
> primary key constraint or unique index identified by 'SQL160810131838480'
> defined on 'REQUEST'.
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> Caused by: org.apache.derby.impl.jdbc.EmbedSQLException: The statement was
> aborted because it would have caused a duplicate key value in a unique or
> primary key constraint or unique index identified by 'SQL160810131838480'
> defined on 'REQUEST'.
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> Caused by: org.apache.derby.iapi.error.StandardException: The statement was
> aborted because it would have caused a duplicate key value in a unique or
> primary key constraint or unique index identified by 'SQL160810131838480'
> defined on 'REQUEST'.
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> {code}
> {code}
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
> statement was aborted because it would have caused a duplicate key value in a
> unique
[jira] [Resolved] (AMBARI-18201) Re-enable testDeleteHostComponentInVariousStates
[
https://issues.apache.org/jira/browse/AMBARI-18201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty resolved AMBARI-18201.
Resolution: Duplicate
> Re-enable testDeleteHostComponentInVariousStates
>
>
> Key: AMBARI-18201
> URL: https://issues.apache.org/jira/browse/AMBARI-18201
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: trunk
>
>
> Builds on trunk have been failing due to AMBARI-18011:
> {code}
> Error Message
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
> statement was aborted because it would have caused a duplicate key value in a
> unique or primary key constraint or unique index identified by
> 'SQL160810131838480' defined on 'REQUEST'.
> Error Code: 2
> Call: INSERT INTO request (request_id, cluster_id, command_name, create_time,
> end_time, exclusive_execution, inputs, request_context, request_type,
> start_time, status, request_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?,
> ?, ?, ?)
> bind => [12 parameters bound]
> Query:
> InsertObjectQuery(org.apache.ambari.server.orm.entities.StageEntity@2753fa)
> Stacktrace
> javax.persistence.RollbackException:
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
> statement was aborted because it would have caused a duplicate key value in a
> unique or primary key constraint or unique index identified by
> 'SQL160810131838480' defined on 'REQUEST'.
> Error Code: 2
> Call: INSERT INTO request (request_id, cluster_id, command_name, create_time,
> end_time, exclusive_execution, inputs, request_context, request_type,
> start_time, status, request_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?,
> ?, ?, ?)
> bind => [12 parameters bound]
> Query:
> InsertObjectQuery(org.apache.ambari.server.orm.entities.StageEntity@2753fa)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> Caused by: org.eclipse.persistence.exceptions.DatabaseException:
> Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
> statement was aborted because it would have caused a duplicate key value in a
> unique or primary key constraint or unique index identified by
> 'SQL160810131838480' defined on 'REQUEST'.
> Error Code: 2
> Call: INSERT INTO request (request_id, cluster_id, command_name, create_time,
> end_time, exclusive_execution, inputs, request_context, request_type,
> start_time, status, request_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?,
> ?, ?, ?)
> bind => [12 parameters bound]
> Query:
> InsertObjectQuery(org.apache.ambari.server.orm.entities.StageEntity@2753fa)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> Caused by: java.sql.SQLIntegrityConstraintViolationException: The statement
> was aborted because it would have caused a duplicate key value in a unique or
> primary key constraint or unique index identified by 'SQL160810131838480'
> defined on 'REQUEST'.
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> Caused by: org.apache.derby.impl.jdbc.EmbedSQLException: The statement was
> aborted because it would have caused a duplicate key value in a unique or
> primary key constraint or unique index identified by 'SQL160810131838480'
> defined on 'REQUEST'.
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> Caused by: org.apache.derby.iapi.error.StandardException: The statement was
> aborted because it would have caused a duplicate key value in a unique or
> primary key constraint or unique index identified by 'SQL160810131838480'
> defined on 'REQUEST'.
> at
> org.apache.ambari.server.controller.AmbariManagementControllerTest.testScheduleSmokeTest(AmbariManagementControllerTest.java:9759)
> {code}
> {code}
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: java.sql.SQLIntegrityConstraintViolationException: The
> statement was aborted because it would have caused a duplicate key value i
[jira] [Commented] (AMBARI-18200) Add Service button is not disabled if all services are installed
[
https://issues.apache.org/jira/browse/AMBARI-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426713#comment-15426713
]
Hadoop QA commented on AMBARI-18200:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824394/AMBARI-18200.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8454//console
This message is automatically generated.
> Add Service button is not disabled if all services are installed
>
>
> Key: AMBARI-18200
> URL: https://issues.apache.org/jira/browse/AMBARI-18200
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-18200.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18200) Add Service button is not disabled if all services are installed
[ https://issues.apache.org/jira/browse/AMBARI-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-18200: - Fix Version/s: (was: 2.5.0) trunk > Add Service button is not disabled if all services are installed > > > Key: AMBARI-18200 > URL: https://issues.apache.org/jira/browse/AMBARI-18200 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: trunk > > Attachments: AMBARI-18200.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18200) Add Service button is not disabled if all services are installed
[ https://issues.apache.org/jira/browse/AMBARI-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426722#comment-15426722 ] Antonenko Alexander commented on AMBARI-18200: -- +1 for the patch > Add Service button is not disabled if all services are installed > > > Key: AMBARI-18200 > URL: https://issues.apache.org/jira/browse/AMBARI-18200 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: trunk > > Attachments: AMBARI-18200.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18193) Zeppelin logsearch configuration typo
[ https://issues.apache.org/jira/browse/AMBARI-18193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18193: Fix Version/s: (was: 2.4.0) 2.5.0 > Zeppelin logsearch configuration typo > - > > Key: AMBARI-18193 > URL: https://issues.apache.org/jira/browse/AMBARI-18193 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18193) Zeppelin logsearch configuration typo
[ https://issues.apache.org/jira/browse/AMBARI-18193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18193: Affects Version/s: (was: 2.4.0) 2.5.0 > Zeppelin logsearch configuration typo > - > > Key: AMBARI-18193 > URL: https://issues.apache.org/jira/browse/AMBARI-18193 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18200) Add Service button is not disabled if all services are installed
[ https://issues.apache.org/jira/browse/AMBARI-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426742#comment-15426742 ] Aleksandr Kovalenko commented on AMBARI-18200: -- committed to trunk > Add Service button is not disabled if all services are installed > > > Key: AMBARI-18200 > URL: https://issues.apache.org/jira/browse/AMBARI-18200 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: trunk > > Attachments: AMBARI-18200.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18200) Add Service button is not disabled if all services are installed
[ https://issues.apache.org/jira/browse/AMBARI-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-18200: - Resolution: Fixed Status: Resolved (was: Patch Available) Tested patch locally. Result of running unit tests: 29952 tests complete (32 seconds) 154 tests pending > Add Service button is not disabled if all services are installed > > > Key: AMBARI-18200 > URL: https://issues.apache.org/jira/browse/AMBARI-18200 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: trunk > > Attachments: AMBARI-18200.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18202) On UI Sometimes: after clicking delete property button, property does not deleted instead Configuration Group window is opened
Antonenko Alexander created AMBARI-18202: Summary: On UI Sometimes: after clicking delete property button, property does not deleted instead Configuration Group window is opened Key: AMBARI-18202 URL: https://issues.apache.org/jira/browse/AMBARI-18202 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Blocker Fix For: 2.4.0 Configuration Group window is opened instead deleting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18202) On UI Sometimes: after clicking delete property button, property does not deleted instead Configuration Group window is opened
[ https://issues.apache.org/jira/browse/AMBARI-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18202: - Attachment: AMBARI-18202.patch > On UI Sometimes: after clicking delete property button, property does not > deleted instead Configuration Group window is opened > -- > > Key: AMBARI-18202 > URL: https://issues.apache.org/jira/browse/AMBARI-18202 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18202.patch > > > Configuration Group window is opened instead deleting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18202) On UI Sometimes: after clicking delete property button, property does not deleted instead Configuration Group window is opened
[ https://issues.apache.org/jira/browse/AMBARI-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18202: - > On UI Sometimes: after clicking delete property button, property does not > deleted instead Configuration Group window is opened > -- > > Key: AMBARI-18202 > URL: https://issues.apache.org/jira/browse/AMBARI-18202 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18202.patch > > > Configuration Group window is opened instead deleting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18202) On UI Sometimes: after clicking delete property button, property does not deleted instead Configuration Group window is opened
[ https://issues.apache.org/jira/browse/AMBARI-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426754#comment-15426754 ] Aleksandr Kovalenko commented on AMBARI-18202: -- +1 for the patch > On UI Sometimes: after clicking delete property button, property does not > deleted instead Configuration Group window is opened > -- > > Key: AMBARI-18202 > URL: https://issues.apache.org/jira/browse/AMBARI-18202 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18202.patch > > > Configuration Group window is opened instead deleting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18202) On UI Sometimes: after clicking delete property button, property does not deleted instead Configuration Group window is opened
[
https://issues.apache.org/jira/browse/AMBARI-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426758#comment-15426758
]
Hadoop QA commented on AMBARI-18202:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824399/AMBARI-18202.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8455//console
This message is automatically generated.
> On UI Sometimes: after clicking delete property button, property does not
> deleted instead Configuration Group window is opened
> --
>
> Key: AMBARI-18202
> URL: https://issues.apache.org/jira/browse/AMBARI-18202
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18202.patch
>
>
> Configuration Group window is opened instead deleting
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18165) Alert on Atlas after adding it to a secure cluster as HBase table initialization fails
[
https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426759#comment-15426759
]
Hadoop QA commented on AMBARI-18165:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824393/AMBARI-18165.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/8456//console
This message is automatically generated.
> Alert on Atlas after adding it to a secure cluster as HBase table
> initialization fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 198, in
> HbaseRegionServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"),
> user=params.hbase_user, tries=10, try_sleep=10)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1.
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18199) Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
[
https://issues.apache.org/jira/browse/AMBARI-18199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426762#comment-15426762
]
Hadoop QA commented on AMBARI-18199:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824391/AMBARI-18199.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8457//console
This message is automatically generated.
> Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
> ---
>
> Key: AMBARI-18199
> URL: https://issues.apache.org/jira/browse/AMBARI-18199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18199.patch
>
>
> On adding additional Collector the webapp address contains wrong hostname.
> {noformat}
> java.net.BindException: Port in use: ambari-sid-5.com:6188
> at
> org.apache.hadoop.http.HttpServer2.openListeners(HttpServer2.java:919)
> at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:856)
> at
> org.apache.hadoop.yarn.webapp.WebApps$Builder.start(WebApps.java:374)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.startWebApp(ApplicationHistoryServer.java:180)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceStart(ApplicationHistoryServer.java:92)
> at
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:138)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: java.net.BindException: Cannot assign requested address
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18184) Hive Metastore restart failed during EU with 'Internal credentials cache error' while running kinit
[
https://issues.apache.org/jira/browse/AMBARI-18184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-18184:
---
Labels: 240RMApproved (was: )
> Hive Metastore restart failed during EU with 'Internal credentials cache
> error' while running kinit
> ---
>
> Key: AMBARI-18184
> URL: https://issues.apache.org/jira/browse/AMBARI-18184
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18184.patch
>
>
> ambari-server --hash
> 8250e90dc9ebcf1bd3dbac9b9eca8a6e21e073c9
> ambari-server-2.4.0.0-1127.x86_64
> Observed this issue in one EU run with below steps:
> # Install HDP-2.4.0.0 cluster with Ambari 2.2.1.1 (secure, HA cluster)
> # Upgrade Ambari to 2.4.0.0
> # Perform EU to 2.4.2.0 and let it complete
> # Start EU to 2.5.0.0
> Observed below error during Hive Metastore restart
> {code}
> Traceback (most recent call last):
> File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py\",
> line 254, in
> HiveMetastore().execute()
> File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute
> method(env)
> File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 696, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py\",
> line 114, in pre_upgrade_restart
> self.upgrade_schema(env)
> File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py\",
> line 193, in upgrade_schema
> Execute(kinit_command,user=params.smokeuser)
> 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 273, 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
> 71, in inner
> result = function(command, **kwargs)
> File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari...@example.com; '
> returned 1. kinit: Internal credentials cache error while storing credentials
> while getting initial credentials"
> {code}
> *A retry of the above failed task was successful and then EU proceeded to
> completion*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18202) On UI Sometimes: after clicking delete property button, property does not deleted instead Configuration Group window is opened
[ https://issues.apache.org/jira/browse/AMBARI-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18202: --- Labels: 240RMApproved (was: ) > On UI Sometimes: after clicking delete property button, property does not > deleted instead Configuration Group window is opened > -- > > Key: AMBARI-18202 > URL: https://issues.apache.org/jira/browse/AMBARI-18202 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18202.patch > > > Configuration Group window is opened instead deleting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18184) Hive Metastore restart failed during EU with 'Internal credentials cache error' while running kinit
[
https://issues.apache.org/jira/browse/AMBARI-18184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18184:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Hive Metastore restart failed during EU with 'Internal credentials cache
> error' while running kinit
> ---
>
> Key: AMBARI-18184
> URL: https://issues.apache.org/jira/browse/AMBARI-18184
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18184.patch
>
>
> ambari-server --hash
> 8250e90dc9ebcf1bd3dbac9b9eca8a6e21e073c9
> ambari-server-2.4.0.0-1127.x86_64
> Observed this issue in one EU run with below steps:
> # Install HDP-2.4.0.0 cluster with Ambari 2.2.1.1 (secure, HA cluster)
> # Upgrade Ambari to 2.4.0.0
> # Perform EU to 2.4.2.0 and let it complete
> # Start EU to 2.5.0.0
> Observed below error during Hive Metastore restart
> {code}
> Traceback (most recent call last):
> File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py\",
> line 254, in
> HiveMetastore().execute()
> File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute
> method(env)
> File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 696, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py\",
> line 114, in pre_upgrade_restart
> self.upgrade_schema(env)
> File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py\",
> line 193, in upgrade_schema
> Execute(kinit_command,user=params.smokeuser)
> 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 273, 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
> 71, in inner
> result = function(command, **kwargs)
> File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari...@example.com; '
> returned 1. kinit: Internal credentials cache error while storing credentials
> while getting initial credentials"
> {code}
> *A retry of the above failed task was successful and then EU proceeded to
> completion*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18202) On UI Sometimes: after clicking delete property button, property does not deleted instead Configuration Group window is opened
[ https://issues.apache.org/jira/browse/AMBARI-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18202: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.4 > On UI Sometimes: after clicking delete property button, property does not > deleted instead Configuration Group window is opened > -- > > Key: AMBARI-18202 > URL: https://issues.apache.org/jira/browse/AMBARI-18202 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18202.patch > > > Configuration Group window is opened instead deleting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18202) On UI Sometimes: after clicking delete property button, property does not deleted instead Configuration Group window is opened
[ https://issues.apache.org/jira/browse/AMBARI-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426836#comment-15426836 ] Antonenko Alexander commented on AMBARI-18202: -- As this changes are made to template only, no tests are required. Rat check passed > On UI Sometimes: after clicking delete property button, property does not > deleted instead Configuration Group window is opened > -- > > Key: AMBARI-18202 > URL: https://issues.apache.org/jira/browse/AMBARI-18202 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18202.patch > > > Configuration Group window is opened instead deleting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18156) Remove upgradeHelper.py and corresponding files due to drop of the manual upgrade
[
https://issues.apache.org/jira/browse/AMBARI-18156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426848#comment-15426848
]
Hudson commented on AMBARI-18156:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5548 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5548/])
Revert "AMBARI-18156 Remove upgradeHelper.py and corresponding files due
(smagyari:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c758b7ffe98f136590012867d4a2bba1484c051e])
* (add)
ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.1_to_2.2.4.json
* (add) ambari-server/src/test/python/TestUpgradeHelper.py
* (add)
ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.0_to_2.2.2.json
* (add)
ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.2_to_2.3.json
* (add)
ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.2_to_2.3_step2.json
* (add)
ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.1_to_2.2.2.json
* (add)
ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.0_to_2.2.json
* (add)
ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.0_to_2.2.4.json
* (add)
ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_1.3_to_2.2.json
* (add)
ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.1_to_2.2.json
* (add) ambari-server/src/main/python/upgradeHelper.py
* (add)
ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.1_to_2.3.json
> Remove upgradeHelper.py and corresponding files due to drop of the manual
> upgrade
> -
>
> Key: AMBARI-18156
> URL: https://issues.apache.org/jira/browse/AMBARI-18156
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Sen
> Fix For: trunk
>
> Attachments: AMBARI-18156.patch
>
>
> Due to drop of the manual upgrade and give this job to EU/RU/PU, unsupported
> files for the manual upgrade need to be removed:
> {code}
> - upgradeHelper.py
> - upgrade\catalog\*.json
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18194) Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException: Connection reset by peer"
[ https://issues.apache.org/jira/browse/AMBARI-18194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426850#comment-15426850 ] Hudson commented on AMBARI-18194: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5548 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5548/]) AMBARI-18194. Hsi-Hs2: Mondrian tests intermittently fail with (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2bc8690a33f48b61def8278dd8abba938456e5f2]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/configuration/hadoop-env.xml > Hsi-Hs2: Mondrian tests intermittently fail with "java.io.IOException: > Connection reset by peer" > - > > Key: AMBARI-18194 > URL: https://issues.apache.org/jira/browse/AMBARI-18194 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-18194.patch, AMBARI-18194.patch > > > I'd reported this issue previously in > not see this due to its intermitent nature. > In yesterdays nightly, around 8 tests had failed with this issue and on rerun > 48 failed. Hs2 logs are below: > > > > 2016-08-17T07:28:55,479 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Status: Running (Executing > on YARN cluster with App id application_1471417242320_0006) > > Map 1: 1/1 Reducer 2: 0(+1)/1 Reducer 3: 0/1 > 2016-08-17T07:28:55,480 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: > 0(+1)/1 Reducer 3: 0/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1 > 2016-08-17T07:28:55,681 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1 > 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-2)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1 > 2016-08-17T07:28:58,422 INFO [HiveServer2-Background-Pool: Thread-6507]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1)/1 > 2016-08-17T07:28:58,955 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-1)/1 > 2016-08-17T07:29:00,566 INFO [HiveServer2-Background-Pool: Thread-6508]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-1)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-3)/1 > 2016-08-17T07:29:00,633 INFO [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-3)/1 > Map 1: 1/1 Reducer 2: 1/1 Reducer 3: 0(+1,-2)/1 > 2016-08-17T07:29:00,635 INFO [HiveServer2-Background-Pool: Thread-6507]: > SessionState (SessionState.java:printInfo(1075)) - Map 1: 1/1 Reducer 2: 1/1 > Reducer 3: 0(+1,-2)/1 > Status: Failed > 2016-08-17T07:29:00,708 ERROR [HiveServer2-Background-Pool: Thread-6503]: > SessionState (SessionState.java:printError(1084)) - Status: Failed > Vertex failed, vertexName=Reducer 3, > vertexId=vertex_1471417242320_0005_293_02, diagnostics=[Task failed, > taskId=task_1471417242320_0005_293_02_00, diagnostics=[TaskAttempt 0 > failed, info=[Error: Error while running task ( failure ) : > attempt_1471417242320_0005_293_02_00_0:java.lang.RuntimeException: > java.lang.RuntimeException: Hive Runtime Error while closing operators: > java.io.IOException: Connection reset by peer > at > org.apache.hadoop.hive.ql.exec.tez.TezProcessor.initializeAndRunProcessor(TezProcessor.java:211) > at > org.apache.hadoop.hive.ql.exec.tez.TezProcessor.run(TezProcessor.java:168) > at > org.apache.tez.runtime.LogicalIOProcessorRuntimeTask.run(LogicalIOProcessorRuntimeTask.java:370) > at > org.apache.tez.runtime.task.TaskRunner2Callable$1.run(TaskRunner2Callable.java:73) > at > org.apache.tez.runtime.task.TaskRunner2Callable$1.run(TaskRunner2Callable.java:61) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Sub
[jira] [Updated] (AMBARI-18188) Typo in stack_advisor.py for KAFKA
[ https://issues.apache.org/jira/browse/AMBARI-18188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18188: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Typo in stack_advisor.py for KAFKA > -- > > Key: AMBARI-18188 > URL: https://issues.apache.org/jira/browse/AMBARI-18188 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-18188.patch > > > KAFKA is spelled as 'KAKFA' in stack_advisor.py because of which the function > validateKAFKAConfigurations will not be called -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18188) Typo in stack_advisor.py for KAFKA
[ https://issues.apache.org/jira/browse/AMBARI-18188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18188: -- Fix Version/s: 2.4.0 > Typo in stack_advisor.py for KAFKA > -- > > Key: AMBARI-18188 > URL: https://issues.apache.org/jira/browse/AMBARI-18188 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-18188.patch > > > KAFKA is spelled as 'KAKFA' in stack_advisor.py because of which the function > validateKAFKAConfigurations will not be called -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18188) Typo in stack_advisor.py for KAFKA
[ https://issues.apache.org/jira/browse/AMBARI-18188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426927#comment-15426927 ] Anita Gnanamalar Jebaraj commented on AMBARI-18188: --- Committed to trunk commit 712a12b6b3228d5bd532aa7a594544c8bd594d66 Author: Anita Jebaraj Date: Thu Aug 18 13:47:26 2016 -0400 Committed to branch-2.4 commit 3c51317e62efbdc213dab92f076c95126465387f Author: Anita Jebaraj Date: Thu Aug 18 13:53:26 2016 -0400 > Typo in stack_advisor.py for KAFKA > -- > > Key: AMBARI-18188 > URL: https://issues.apache.org/jira/browse/AMBARI-18188 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-18188.patch > > > KAFKA is spelled as 'KAKFA' in stack_advisor.py because of which the function > validateKAFKAConfigurations will not be called -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster
[
https://issues.apache.org/jira/browse/AMBARI-18167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-18167.
--
Resolution: Fixed
> RU: Kafka brokers restart was stopped during downgrade cluster
> --
>
> Key: AMBARI-18167
> URL: https://issues.apache.org/jira/browse/AMBARI-18167
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18167.patch
>
>
> Kafka broker restart failed due to below error:
> {noformat}
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'xasecure.audit.destination.db' was not found in configurations dictionary!
> {noformat}
> Solution:
> During RU downgrade, runs on downgrade as well, which deleted
> {{xasecure.audit.destination.db}} config property.
> {noformat}
>
>id="hdp_2_5_0_0_remove_ranger_kafka_audit_db" />
>
> {noformat}
> Need to override it with a blank element.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-18157) Hive service check is failing after cluster Kerberization
[
https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya reassigned AMBARI-18157:
--
Assignee: Jayush Luniya (was: Dmitry Lysnichenko)
> Hive service check is failing after cluster Kerberization
> -
>
> Key: AMBARI-18157
> URL: https://issues.apache.org/jira/browse/AMBARI-18157
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Assignee: Jayush Luniya
>Priority: Blocker
> Labels: 240RMApproved, system_test
> Fix For: 2.4.0
>
> Attachments: AMBARI-18157-branch24.patch, AMBARI-18157-trunk.patch
>
>
> {code}
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh $HOSTNAME 50111
> idtest.ambari-qa.1471340206.23.pig
> /etc/security/keytabs/smokeuser.headless.keytab true /usr/bin/kinit
> ambari-qa@REALM_NAME /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke
> Test (ddl cmd): Failed. : {"error":"Unauthorized connection for super-user:
> HTTP/HOST_NAME@REALM_NAME from IP HOST_IP"}http_code <500>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18203) maven packaging for ambari-server project fails
Jaimin D Jetly created AMBARI-18203: --- Summary: maven packaging for ambari-server project fails Key: AMBARI-18203 URL: https://issues.apache.org/jira/browse/AMBARI-18203 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Jaimin D Jetly Assignee: Jaimin D Jetly Fix For: trunk -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18203) maven packaging for ambari-server project fails
[ https://issues.apache.org/jira/browse/AMBARI-18203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18203: Priority: Critical (was: Major) > maven packaging for ambari-server project fails > --- > > Key: AMBARI-18203 > URL: https://issues.apache.org/jira/browse/AMBARI-18203 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18165) Alert on Atlas after adding it to a secure cluster as HBase table initialization fails
[
https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18165:
---
Attachment: (was: AMBARI-18165.patch)
> Alert on Atlas after adding it to a secure cluster as HBase table
> initialization fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 198, in
> HbaseRegionServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"),
> user=params.hbase_user, tries=10, try_sleep=10)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1.
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18165) Alert on Atlas after adding it to a secure cluster as HBase table initialization fails
[
https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18165:
---
Attachment: AMBARI-18165.patch
> Alert on Atlas after adding it to a secure cluster as HBase table
> initialization fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 198, in
> HbaseRegionServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"),
> user=params.hbase_user, tries=10, try_sleep=10)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1.
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18165) Alert on Atlas after adding it to a secure cluster as HBase table initialization fails
[
https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18165:
---
Attachment: AMBARI-18165.patch
> Alert on Atlas after adding it to a secure cluster as HBase table
> initialization fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 198, in
> HbaseRegionServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"),
> user=params.hbase_user, tries=10, try_sleep=10)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1.
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18165) Alert on Atlas after adding it to a secure cluster as HBase table initialization fails
[
https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18165:
---
Attachment: (was: AMBARI-18165.patch)
> Alert on Atlas after adding it to a secure cluster as HBase table
> initialization fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 198, in
> HbaseRegionServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"),
> user=params.hbase_user, tries=10, try_sleep=10)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1.
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18142) Define keytab/principal for Spark Thrift Server
[ https://issues.apache.org/jira/browse/AMBARI-18142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated AMBARI-18142: Attachment: AMBARI-18142.addendum.patch [~sumitmohanty] Attaching an addendum patch that brings back the kinit code that got removed for this fix in this Jira. This may help reduce ambari upgrade issues given lack of support for Kerberos.json changes during ambari upgrade. > Define keytab/principal for Spark Thrift Server > --- > > Key: AMBARI-18142 > URL: https://issues.apache.org/jira/browse/AMBARI-18142 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18142-1.patch, AMBARI-18142-2.patch, > AMBARI-18142.addendum.patch > > > PROBLEM: As of now spark thrift server seems to be picking up the tgt from > cache upon start up and will not renew the ticket when it expires. This > causes the spark thrift server processes only valid for 7 days. > Users need to created a script to manually renew the ticket , but this is > causing inconvenience. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18203) maven packaging for ambari-server project fails
[
https://issues.apache.org/jira/browse/AMBARI-18203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426985#comment-15426985
]
Jaimin D Jetly commented on AMBARI-18203:
-
Marking this as fixed as the commit that caused this issue has been reverted:
{code}
commit c758b7ffe98f136590012867d4a2bba1484c051e
Author: Sandor Magyari
Date: Thu Aug 18 16:14:55 2016 +0200
Revert "AMBARI-18156 Remove upgradeHelper.py and corresponding files due to
drop of the manual upgrade (dsen)"
This reverts commit 793adfe46a02e0870ae8aa4f334818d5fa401965.
{code}
> maven packaging for ambari-server project fails
> ---
>
> Key: AMBARI-18203
> URL: https://issues.apache.org/jira/browse/AMBARI-18203
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: trunk
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-18203) maven packaging for ambari-server project fails
[ https://issues.apache.org/jira/browse/AMBARI-18203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly resolved AMBARI-18203. - Resolution: Duplicate > maven packaging for ambari-server project fails > --- > > Key: AMBARI-18203 > URL: https://issues.apache.org/jira/browse/AMBARI-18203 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18157) Hive service check is failing after cluster Kerberization
[
https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426992#comment-15426992
]
Jayush Luniya commented on AMBARI-18157:
Trunk
commit 0e5fb8ee8e205ccb9da889e44ba77ffbde3f86dd
Author: Jayush Luniya
Date: Thu Aug 18 12:01:35 2016 -0700
AMBARI-18157: Hive service check is failing after cluster Kerberization
(jluniya)
> Hive service check is failing after cluster Kerberization
> -
>
> Key: AMBARI-18157
> URL: https://issues.apache.org/jira/browse/AMBARI-18157
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Assignee: Jayush Luniya
>Priority: Blocker
> Labels: 240RMApproved, system_test
> Fix For: 2.4.0
>
> Attachments: AMBARI-18157-branch24.patch, AMBARI-18157-trunk.patch
>
>
> {code}
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh $HOSTNAME 50111
> idtest.ambari-qa.1471340206.23.pig
> /etc/security/keytabs/smokeuser.headless.keytab true /usr/bin/kinit
> ambari-qa@REALM_NAME /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke
> Test (ddl cmd): Failed. : {"error":"Unauthorized connection for super-user:
> HTTP/HOST_NAME@REALM_NAME from IP HOST_IP"}http_code <500>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18157) Hive service check is failing after cluster Kerberization
[
https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-18157:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Hive service check is failing after cluster Kerberization
> -
>
> Key: AMBARI-18157
> URL: https://issues.apache.org/jira/browse/AMBARI-18157
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Assignee: Jayush Luniya
>Priority: Blocker
> Labels: 240RMApproved, system_test
> Fix For: 2.4.0
>
> Attachments: AMBARI-18157-branch24.patch, AMBARI-18157-trunk.patch
>
>
> {code}
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh $HOSTNAME 50111
> idtest.ambari-qa.1471340206.23.pig
> /etc/security/keytabs/smokeuser.headless.keytab true /usr/bin/kinit
> ambari-qa@REALM_NAME /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke
> Test (ddl cmd): Failed. : {"error":"Unauthorized connection for super-user:
> HTTP/HOST_NAME@REALM_NAME from IP HOST_IP"}http_code <500>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18157) Hive service check is failing after cluster Kerberization
[
https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426994#comment-15426994
]
Jayush Luniya commented on AMBARI-18157:
2.4
commit f5b3c238b84c4225603412d69b46bcc8243d56fb
Author: Jayush Luniya
Date: Thu Aug 18 12:01:35 2016 -0700
AMBARI-18157: Hive service check is failing after cluster Kerberization
(jluniya)
> Hive service check is failing after cluster Kerberization
> -
>
> Key: AMBARI-18157
> URL: https://issues.apache.org/jira/browse/AMBARI-18157
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Assignee: Jayush Luniya
>Priority: Blocker
> Labels: 240RMApproved, system_test
> Fix For: 2.4.0
>
> Attachments: AMBARI-18157-branch24.patch, AMBARI-18157-trunk.patch
>
>
> {code}
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh $HOSTNAME 50111
> idtest.ambari-qa.1471340206.23.pig
> /etc/security/keytabs/smokeuser.headless.keytab true /usr/bin/kinit
> ambari-qa@REALM_NAME /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke
> Test (ddl cmd): Failed. : {"error":"Unauthorized connection for super-user:
> HTTP/HOST_NAME@REALM_NAME from IP HOST_IP"}http_code <500>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18165) Alert on Atlas after adding it to a secure cluster as HBase table initialization fails
[
https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427031#comment-15427031
]
Hadoop QA commented on AMBARI-18165:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824416/AMBARI-18165.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/8458//console
This message is automatically generated.
> Alert on Atlas after adding it to a secure cluster as HBase table
> initialization fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 198, in
> HbaseRegionServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"),
> user=params.hbase_user, tries=10, try_sleep=10)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1.
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18165) Alert on Atlas after adding it to a secure cluster as HBase table initialization fails
[
https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18165:
---
Attachment: AMBARI-18165.patch
> Alert on Atlas after adding it to a secure cluster as HBase table
> initialization fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch, AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 198, in
> HbaseRegionServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"),
> user=params.hbase_user, tries=10, try_sleep=10)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1.
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18165) Alert on Atlas after adding it to a secure cluster as HBase table initialization fails
[
https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18165:
---
Attachment: (was: AMBARI-18165.patch)
> Alert on Atlas after adding it to a secure cluster as HBase table
> initialization fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 198, in
> HbaseRegionServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
> line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"),
> user=params.hbase_user, tries=10, try_sleep=10)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1.
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18142) Define keytab/principal for Spark Thrift Server
[ https://issues.apache.org/jira/browse/AMBARI-18142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427083#comment-15427083 ] Sumit Mohanty commented on AMBARI-18142: Addendum patch looks good +1. AMBARI-18204 is opened to track Ambari upgrade changes. > Define keytab/principal for Spark Thrift Server > --- > > Key: AMBARI-18142 > URL: https://issues.apache.org/jira/browse/AMBARI-18142 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18142-1.patch, AMBARI-18142-2.patch, > AMBARI-18142.addendum.patch > > > PROBLEM: As of now spark thrift server seems to be picking up the tgt from > cache upon start up and will not renew the ticket when it expires. This > causes the spark thrift server processes only valid for 7 days. > Users need to created a script to manually renew the ticket , but this is > causing inconvenience. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18204) Ambari upgrade should add/edit spark-env config type to add hive keytab and principals
Sumit Mohanty created AMBARI-18204:
--
Summary: Ambari upgrade should add/edit spark-env config type to
add hive keytab and principals
Key: AMBARI-18204
URL: https://issues.apache.org/jira/browse/AMBARI-18204
Project: Ambari
Issue Type: Bug
Components: ambari-server, stacks
Affects Versions: 2.4.0
Reporter: Sumit Mohanty
Assignee: Jeff Zhang
Priority: Critical
Fix For: 2.5.0
Two new config propertied got introduced in 2.4.0 in spark-env -
{{hive_kerberos_keytab}} and {{hive_kerberos_principal}}. This should be added
during Ambari upgrade to an already deployed secure cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18142) Define keytab/principal for Spark Thrift Server
[ https://issues.apache.org/jira/browse/AMBARI-18142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18142: --- Labels: 240RMApproved (was: ) > Define keytab/principal for Spark Thrift Server > --- > > Key: AMBARI-18142 > URL: https://issues.apache.org/jira/browse/AMBARI-18142 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang >Priority: Critical > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18142-1.patch, AMBARI-18142-2.patch, > AMBARI-18142.addendum.patch > > > PROBLEM: As of now spark thrift server seems to be picking up the tgt from > cache upon start up and will not renew the ticket when it expires. This > causes the spark thrift server processes only valid for 7 days. > Users need to created a script to manually renew the ticket , but this is > causing inconvenience. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18195) HST server down after deploy
[
https://issues.apache.org/jira/browse/AMBARI-18195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya resolved AMBARI-18195.
Resolution: Invalid
Smartsense was explicitly stopped
> HST server down after deploy
>
>
> Key: AMBARI-18195
> URL: https://issues.apache.org/jira/browse/AMBARI-18195
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Priority: Blocker
> Labels: system_test
> Fix For: 2.4.0
>
>
> Deploy type : UI
> Error in hst-server logs :
> {code}
> 18 Aug 2016 03:50:07,620 INFO [main] HttpSecurityBeanDefinitionParser:264 -
> Checking sorted filter chain: [Root bean: class
> [org.springframework.security.web.context.SecurityContextPersistenceFilter];
> scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
> autowireCandidate=true; primary=false; factoryBeanName=null;
> factoryMethodName=null; initMethodName=null; destroyMethodName=null, order =
> 300, Root bean: class
> [org.springframework.security.web.authentication.www.BasicAuthenticationFilter];
> scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
> autowireCandidate=true; primary=false; factoryBeanName=null;
> factoryMethodName=null; initMethodName=null; destroyMethodName=null, order =
> 1200, , order = 1201, Root bean: class
> [org.springframework.security.web.savedrequest.RequestCacheAwareFilter];
> scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
> autowireCandidate=true; primary=false; factoryBeanName=null;
> factoryMethodName=null; initMethodName=null; destroyMethodName=null, order =
> 1300, Root bean: class
> [org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter];
> scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
> autowireCandidate=true; primary=false; factoryBeanName=null;
> factoryMethodName=null; initMethodName=null; destroyMethodName=null, order =
> 1400, Root bean: class
> [org.springframework.security.web.authentication.AnonymousAuthenticationFilter];
> scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
> autowireCandidate=true; primary=false; factoryBeanName=null;
> factoryMethodName=null; initMethodName=null; destroyMethodName=null, order =
> 1700, Root bean: class
> [org.springframework.security.web.session.SessionManagementFilter]; scope=;
> abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
> autowireCandidate=true; primary=false; factoryBeanName=null;
> factoryMethodName=null; initMethodName=null; destroyMethodName=null, order =
> 1800, Root bean: class
> [org.springframework.security.web.access.ExceptionTranslationFilter]; scope=;
> abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
> autowireCandidate=true; primary=false; factoryBeanName=null;
> factoryMethodName=null; initMethodName=null; destroyMethodName=null, order =
> 1900,
> ,
> order = 2000]
> 18 Aug 2016 03:50:07,772 INFO [main] DefaultSecurityFilterChain:28 -
> Creating filter chain:
> org.springframework.security.web.util.AnyRequestMatcher@1,
> [org.springframework.security.web.context.SecurityContextPersistenceFilter@58496c97,
>
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter@ad3324b,
>
> com.hortonworks.support.tools.server.security.authorization.SupportToolAuthorizationFilter@3872bc37,
>
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter@1a87b51,
>
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@12968227,
>
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter@144ab54,
> org.springframework.security.web.session.SessionManagementFilter@2cfa2c4f,
> org.springframework.security.web.access.ExceptionTranslationFilter@6ecab872,
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor@48eb9836]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18142) Define keytab/principal for Spark Thrift Server
[ https://issues.apache.org/jira/browse/AMBARI-18142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427141#comment-15427141 ] Sumit Mohanty commented on AMBARI-18142: Ran unit tests locally and there are no failures. > Define keytab/principal for Spark Thrift Server > --- > > Key: AMBARI-18142 > URL: https://issues.apache.org/jira/browse/AMBARI-18142 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang >Priority: Critical > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18142-1.patch, AMBARI-18142-2.patch, > AMBARI-18142.addendum.patch > > > PROBLEM: As of now spark thrift server seems to be picking up the tgt from > cache upon start up and will not renew the ticket when it expires. This > causes the spark thrift server processes only valid for 7 days. > Users need to created a script to manually renew the ticket , but this is > causing inconvenience. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18197) HBase region server start fails after disabling kerberos
[
https://issues.apache.org/jira/browse/AMBARI-18197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya resolved AMBARI-18197.
Resolution: Duplicate
> HBase region server start fails after disabling kerberos
>
>
> Key: AMBARI-18197
> URL: https://issues.apache.org/jira/browse/AMBARI-18197
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
> Labels: system_test
> Fix For: 2.4.0
>
>
> STR :
> 1. Install cluster
> 2. Enable kerberos
> 3. Disable kerberos
> The disable process fails at start services
> Error :
> {code}
> "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py\",
> line 198, in \nHbaseRegionServer().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py\",
> line 124, in start\nself.post_start(env, upgrade_type=upgrade_type)\n
> File
> \"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py\",
> line 89, in post_start\nself.apply_atlas_acl(params.hbase_user)\n File
> \"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py\",
> line 114, in apply_atlas_acl\nshell.checked_call(format(\"{kinit_cmd};
> {perm_cmd}\"), user=params.hbase_user, tries=10, try_sleep=10)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 71, in inner\nresult = function(command, **kwargs)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 294, in _call\nraise
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/hbase.service.keytab
> hbase/nat-s11-4-kdxs-ambari-rbac-1-1.openstacklo...@hwqe.hortonworks.com;
> echo \"grant 'atlas', 'RWXCA', 'atlas_titan'\" | hbase shell -n' returned 1.
> ERROR ArgumentError: Can't find a table: atlas_titan",
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18205) RU, order Kafka right after Ranger and before HDFS in upgrade pack
Alejandro Fernandez created AMBARI-18205: Summary: RU, order Kafka right after Ranger and before HDFS in upgrade pack Key: AMBARI-18205 URL: https://issues.apache.org/jira/browse/AMBARI-18205 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.4.0 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 2.4.0 The Rolling Upgrade packs have the wrong order for Kafka since it should be right after Ranger and before HDFS. Kafka is one of the plugins supported by Ranger, so if the plugin is enabled, then during RU the "get repo call" fails with 25 tries. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18205) RU, order Kafka right after Ranger and before HDFS in upgrade pack
[ https://issues.apache.org/jira/browse/AMBARI-18205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18205: - Status: Patch Available (was: Open) > RU, order Kafka right after Ranger and before HDFS in upgrade pack > -- > > Key: AMBARI-18205 > URL: https://issues.apache.org/jira/browse/AMBARI-18205 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.4.0 > > Attachments: AMBARI-18205.patch > > > The Rolling Upgrade packs have the wrong order for Kafka since it should be > right after Ranger and before HDFS. > Kafka is one of the plugins supported by Ranger, so if the plugin is enabled, > then during RU the "get repo call" fails with 25 tries. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18205) RU, order Kafka right after Ranger and before HDFS in upgrade pack
[ https://issues.apache.org/jira/browse/AMBARI-18205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18205: - Attachment: AMBARI-18205.patch > RU, order Kafka right after Ranger and before HDFS in upgrade pack > -- > > Key: AMBARI-18205 > URL: https://issues.apache.org/jira/browse/AMBARI-18205 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.4.0 > > Attachments: AMBARI-18205.patch > > > The Rolling Upgrade packs have the wrong order for Kafka since it should be > right after Ranger and before HDFS. > Kafka is one of the plugins supported by Ranger, so if the plugin is enabled, > then during RU the "get repo call" fails with 25 tries. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18205) RU, order Kafka right after Ranger and before HDFS in upgrade pack
[ https://issues.apache.org/jira/browse/AMBARI-18205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18205: - Priority: Blocker (was: Major) > RU, order Kafka right after Ranger and before HDFS in upgrade pack > -- > > Key: AMBARI-18205 > URL: https://issues.apache.org/jira/browse/AMBARI-18205 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18205.patch > > > The Rolling Upgrade packs have the wrong order for Kafka since it should be > right after Ranger and before HDFS. > Kafka is one of the plugins supported by Ranger, so if the plugin is enabled, > then during RU the "get repo call" fails with 25 tries. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18191) "Restart all required" services operation failed at Metrics Collector since HDFS was not yet up
[
https://issues.apache.org/jira/browse/AMBARI-18191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18191:
---
Fix Version/s: (was: 2.4.0)
2.5.0
> "Restart all required" services operation failed at Metrics Collector since
> HDFS was not yet up
> ---
>
> Key: AMBARI-18191
> URL: https://issues.apache.org/jira/browse/AMBARI-18191
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18191.patch
>
>
> ambari-server --hash
> 4017036da951a10f519a578de934308cf866ba50
> *Steps*
> # Deploy HDP-2.3.6 cluster with Ambari 2.2.2.0 (AMS is configured in
> distributed mode)
> # Upgrade Ambari to 2.4.0.0 and let it complete
> # Open Ambari web UI and hit "Restart all required" under Actions menu
> *Result*
> The operation fails while trying to restart Metrics Collector as it tried to
> make a WebHDFS call while HDFS was not started:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 148, in
> AmsCollector().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 725, in restart
> self.start(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 46, in start
> self.configure(env, action = 'start') # for security
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 41, in configure
> hbase('master', action)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py",
> line 213, in hbase
> dfs_type=params.dfs_type
> 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/libraries/providers/hdfs_resource.py",
> line 459, in action_create_on_execute
> self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 456, in action_delayed
> self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 256, in action_delayed
> self._set_mode(self.target_status)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 363, in _set_mode
> self.util.run_command(self.main_resource.resource.target,
> 'SETPERMISSION', method='PUT', permission=self.mode, assertable_result=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 179, in run_command
> _, out, err = get_user_call_output(cmd, user=self.run_user,
> logoutput=self.logoutput, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 61, in get_user_call_output
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w
> '%{http_code}' -X PUT --negotiate -u :
> 'http://vsharma-eu-mt-5.openstacklocal:50070/webhdfs/v1/user/ams/hbase?op=SETPERMISSION&user.name=hdfs&permission=775'
> 1>/tmp/tmp8twcZt 2>/tmp/tmpLPih9a' returned 7. curl: (7) couldn't connect to
> host
> 401
> {code}
> Afterwards, restarted HDFS individually first and then hit "Restart all
> Required" - the operation was successful
> Looks like the issue is because the order of restart is incorrect across the
> hosts, hence the dependent services don't come up upfront
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18202) On UI Sometimes: after clicking delete property button, property does not deleted instead Configuration Group window is opened
[ https://issues.apache.org/jira/browse/AMBARI-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427194#comment-15427194 ] Hudson commented on AMBARI-18202: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #5549 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5549/]) AMBARI-18202. On UI Sometimes: after clicking delete property button, (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1d3f8a4ce7b847ca150c7276fc8a417488290e0a]) * (edit) ambari-web/app/templates/common/configs/controls.hbs > On UI Sometimes: after clicking delete property button, property does not > deleted instead Configuration Group window is opened > -- > > Key: AMBARI-18202 > URL: https://issues.apache.org/jira/browse/AMBARI-18202 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18202.patch > > > Configuration Group window is opened instead deleting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18200) Add Service button is not disabled if all services are installed
[ https://issues.apache.org/jira/browse/AMBARI-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427197#comment-15427197 ] Hudson commented on AMBARI-18200: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #5549 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5549/]) AMBARI-18200. Add Service button is not disabled if all services are (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d3bac1d45e9bf57d562b447d1d4540ac867ad602]) * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/test/controllers/main/service_test.js * (edit) ambari-web/app/templates/main/service/all_services_actions.hbs * (edit) ambari-web/app/controllers/main/service.js > Add Service button is not disabled if all services are installed > > > Key: AMBARI-18200 > URL: https://issues.apache.org/jira/browse/AMBARI-18200 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: trunk > > Attachments: AMBARI-18200.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18184) Hive Metastore restart failed during EU with 'Internal credentials cache error' while running kinit
[
https://issues.apache.org/jira/browse/AMBARI-18184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427199#comment-15427199
]
Hudson commented on AMBARI-18184:
-
ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #5549 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5549/])
AMBARI-18184 - Hive Metastore restart failed during EU with 'Internal (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=78886384b075f5e0108b587dbf1760d29848641d])
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py
> Hive Metastore restart failed during EU with 'Internal credentials cache
> error' while running kinit
> ---
>
> Key: AMBARI-18184
> URL: https://issues.apache.org/jira/browse/AMBARI-18184
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18184.patch
>
>
> ambari-server --hash
> 8250e90dc9ebcf1bd3dbac9b9eca8a6e21e073c9
> ambari-server-2.4.0.0-1127.x86_64
> Observed this issue in one EU run with below steps:
> # Install HDP-2.4.0.0 cluster with Ambari 2.2.1.1 (secure, HA cluster)
> # Upgrade Ambari to 2.4.0.0
> # Perform EU to 2.4.2.0 and let it complete
> # Start EU to 2.5.0.0
> Observed below error during Hive Metastore restart
> {code}
> Traceback (most recent call last):
> File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py\",
> line 254, in
> HiveMetastore().execute()
> File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute
> method(env)
> File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 696, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py\",
> line 114, in pre_upgrade_restart
> self.upgrade_schema(env)
> File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py\",
> line 193, in upgrade_schema
> Execute(kinit_command,user=params.smokeuser)
> 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 273, 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
> 71, in inner
> result = function(command, **kwargs)
> File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari...@example.com; '
> returned 1. kinit: Internal credentials cache error while storing credentials
> while getting initial credentials"
> {code}
> *A retry of the above failed task was successful and then EU proceeded to
> completion*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18188) Typo in stack_advisor.py for KAFKA
[ https://issues.apache.org/jira/browse/AMBARI-18188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427332#comment-15427332 ] Jayush Luniya commented on AMBARI-18188: -1 for 2.4.0. Backing this out from 2.4 branch as it does not meet the agreed upon bug bar. > Typo in stack_advisor.py for KAFKA > -- > > Key: AMBARI-18188 > URL: https://issues.apache.org/jira/browse/AMBARI-18188 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-18188.patch > > > KAFKA is spelled as 'KAKFA' in stack_advisor.py because of which the function > validateKAFKAConfigurations will not be called -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18188) Typo in stack_advisor.py for KAFKA
[ https://issues.apache.org/jira/browse/AMBARI-18188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427345#comment-15427345 ] Jayush Luniya commented on AMBARI-18188: commit 2d6ade5a21f2c055ef73a5b8d321a4265c41c6f9 Author: Jayush Luniya Date: Thu Aug 18 16:13:33 2016 -0700 Revert "AMBARI-18188. KAFKA is spelled as 'KAKFA' in stack_advisor.py because of which the function validate (Anita Jebaraj via rlevas)" This reverts commit 3c51317e62efbdc213dab92f076c95126465387f. > Typo in stack_advisor.py for KAFKA > -- > > Key: AMBARI-18188 > URL: https://issues.apache.org/jira/browse/AMBARI-18188 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-18188.patch > > > KAFKA is spelled as 'KAKFA' in stack_advisor.py because of which the function > validateKAFKAConfigurations will not be called -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18205) RU, order Kafka right after Ranger and before HDFS in upgrade pack
[ https://issues.apache.org/jira/browse/AMBARI-18205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18205: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit 125be0469998b608d541e00e1e2ae8b05223ab6d branch-2.4, commit 3643111292af73c7a78f22012f98bb9a0336f9f8 > RU, order Kafka right after Ranger and before HDFS in upgrade pack > -- > > Key: AMBARI-18205 > URL: https://issues.apache.org/jira/browse/AMBARI-18205 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18205.patch > > > The Rolling Upgrade packs have the wrong order for Kafka since it should be > right after Ranger and before HDFS. > Kafka is one of the plugins supported by Ranger, so if the plugin is enabled, > then during RU the "get repo call" fails with 25 tries. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
