[jira] [Commented] (AMBARI-20379) Error during moving ResourceManager without Tez installed
[
https://issues.apache.org/jira/browse/AMBARI-20379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903259#comment-15903259
]
Hadoop QA commented on AMBARI-20379:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857019/AMBARI-20379.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10944//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10944//console
This message is automatically generated.
> Error during moving ResourceManager without Tez installed
> -
>
> Key: AMBARI-20379
> URL: https://issues.apache.org/jira/browse/AMBARI-20379
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20379_branch-2.5.patch, AMBARI-20379.patch
>
>
> Run Move Wizard for ResourceManager without Tez installed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20332) Few ambari agent unit tests are failing
[
https://issues.apache.org/jira/browse/AMBARI-20332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903221#comment-15903221
]
Hudson commented on AMBARI-20332:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6986 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6986/])
AMBARI-20332. Few ambari agent unit tests are failing (aonishuk) (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=af69dcc43a33682b393cd488458f9b3244b1a6db])
* (edit)
ambari-server/src/test/python/stacks/2.0.6/YARN/test_yarn_service_check.py
* (edit) ambari-agent/src/test/python/resource_management/TestDatanodeHelper.py
> Few ambari agent unit tests are failing
> ---
>
> Key: AMBARI-20332
> URL: https://issues.apache.org/jira/browse/AMBARI-20332
> Project: Ambari
> Issue Type: Bug
> Components: test
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-20332.patch
>
>
> Few ambari agent tests are failing as below.
> {code:title=test cmd}
> export MAVEN_OPTS="-Xmx8192m -XX:MaxPermSize=4096m"; mvn -B -nsu
> -DforkCount=4 -Dmaven.test.failure.ignore=true -fae clean test {code}
> {code}
> ==
> ERROR: test_may_manage_folder (TestDatanodeHelper.TestDatanodeHelper)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/resource_management/TestDatanodeHelper.py",
> line 179, in test_may_manage_folder
> self.assertSetEqual(dirs_unmounted, set())
> AttributeError: 'TestDatanodeHelper' object has no attribute 'assertSetEqual'
> ==
> FAIL: test_kill_process_with_children (TestShell.TestShell)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestShell.py",
> line 71, in test_kill_process_with_children
> self.assertTrue(sleep_cmd in out)
> AssertionError
> ==
> FAIL: test_facterMemInfoOutput (TestHardware.TestHardware)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestHardware.py", line
> 247, in test_facterMemInfoOutput
> self.assertEquals(result['memorysize'], 1832392)
> AssertionError: u'4194304' != 1832392
> --
> Ran 448 tests in 15.028s
> FAILED (failures=2, errors=1)
> [INFO] {code}
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 7.696
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.213
> s]
> [INFO] Ambari Web . SUCCESS [02:07
> min]
> [INFO] Ambari Views ... SUCCESS [ 6.316
> s]
> [INFO] Ambari Admin View .. SUCCESS [01:17
> min]
> [INFO] utility SUCCESS [ 3.209
> s]
> [INFO] ambari-metrics . SUCCESS [ 1.427
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 5.610
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 7.023
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 5.797
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 4.710
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.895
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 3.642
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [07:18
> min]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 5.923
> s]
> [INFO] Ambari Metrics Grafana . SUCCESS [ 3.769
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [ 7.651
> s]
> [INFO] Ambari Server .. FAILURE [15:35
> min]
> [INFO] Ambari Functional Tests SKIPPED
> [INFO] Ambari Agent
[jira] [Commented] (AMBARI-20375) Remove duplicate code from wizard menu
[
https://issues.apache.org/jira/browse/AMBARI-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903222#comment-15903222
]
Hudson commented on AMBARI-20375:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6986 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6986/])
AMBARI-20375. Remove duplicate code from wizard menu (onechiporenko)
(onechiporenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c3c3422e51c58c6e9ec3affd492f28a26499dc1e])
* (edit) ambari-web/app/views/main/service/reassign_view.js
* (edit) ambari-web/app/mixins/wizard/wizard_menu_view.js
> Remove duplicate code from wizard menu
> --
>
> Key: AMBARI-20375
> URL: https://issues.apache.org/jira/browse/AMBARI-20375
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20375.patch
>
>
> {{'isStep..Disabled'}} and {{'isStep..Completed'}} may be rewritten as
> computed macros
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20367) Update Zeppelin version on Ambari-2.5 from 0.6.2 to 0.7.0
[ https://issues.apache.org/jira/browse/AMBARI-20367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903219#comment-15903219 ] Hudson commented on AMBARI-20367: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6986 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6986/]) AMBARI-20367: Update Zeppelin version on Ambari-2.5 from 0.6.2 to 0.7.0 (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=573907754e6743729f4788187850ef844a95aaf7]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/ZEPPELIN/metainfo.xml > Update Zeppelin version on Ambari-2.5 from 0.6.2 to 0.7.0 > - > > Key: AMBARI-20367 > URL: https://issues.apache.org/jira/browse/AMBARI-20367 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20367_branch-2.5_v1.patch > > > Update Zeppelin version on Ambari-2.5 from 0.6.2 to 0.7.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20373) Complete button after move masters is grayed out even after move has completed
[ https://issues.apache.org/jira/browse/AMBARI-20373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903216#comment-15903216 ] Hudson commented on AMBARI-20373: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6986 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6986/]) AMBARI-20373. Complete button after move masters is grayed out even (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0ca474786dcbdf8cf249f4b04c0ee106ee61cc9a]) * (edit) ambari-web/app/routes/reassign_master_routes.js > Complete button after move masters is grayed out even after move has completed > -- > > Key: AMBARI-20373 > URL: https://issues.apache.org/jira/browse/AMBARI-20373 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20373_branch-2.5.patch, AMBARI-20373.patch > > > STR : > Move namenode from host1 to host2. > Complete the move. The complete button is grayed out and can't be clicked. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20344) RU: MR2 service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903213#comment-15903213
]
Hudson commented on AMBARI-20344:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6986 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6986/])
AMBARI-20344. RU: MR2 service check failed during rolling upgrade.
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d3f7c8fb3d518580c56d4247dbcf4d3293c04139])
* (edit)
ambari-server/src/main/resources/common-services/SLIDER/0.60.0.2.2/package/scripts/service_check.py
> RU: MR2 service check failed during rolling upgrade
> ---
>
> Key: AMBARI-20344
> URL: https://issues.apache.org/jira/browse/AMBARI-20344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-20344.patch
>
>
> During RU MapReduce Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
[jira] [Commented] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[
https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903210#comment-15903210
]
Hadoop QA commented on AMBARI-20323:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857003/AMBARI-20323.5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-agent.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10943//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10943//console
This message is automatically generated.
> Commands timed-out on ambari host without any error logs
>
>
> Key: AMBARI-20323
> URL: https://issues.apache.org/jira/browse/AMBARI-20323
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch,
> AMBARI-20323.4.patch, AMBARI-20323.5.patch, AMBARI-20323.patch
>
>
> Ambari-agent stop execution commands. It is happend because of threads
> blocking due to broken multiprocessing.Queue after killing
> StatusCommandsExecutor.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20349) When SPNEGO authentication is enabled for Hadoop in a cluster with NN HA, PXF Process alert fails
[
https://issues.apache.org/jira/browse/AMBARI-20349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-20349:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit a1012057452fde3f4b488dd1e0ebb83069fb29da
Author: Robert Levas
Date: Thu Mar 9 10:25:14 2017 -0500
{noformat}
Committed to branch-2.5
{noformat}
commit 245fd5cf3689097fdcdde6a75c39de9d38e0bde8
Author: Robert Levas
Date: Thu Mar 9 10:25:53 2017 -0500
{noformat}
> When SPNEGO authentication is enabled for Hadoop in a cluster with NN HA, PXF
> Process alert fails
> -
>
> Key: AMBARI-20349
> URL: https://issues.apache.org/jira/browse/AMBARI-20349
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: PHD, PXF, kerberos
> Fix For: 2.5.0
>
> Attachments: AMBARI-20349_branch-2.5_01.patch,
> AMBARI-20349_trunk_01.patch
>
>
> When SPNEGO authentication is enabled for Hadoop in a cluster where NN HA is
> enabled, PXF Process alert fails with the following errors in the
> ambari-agent.log file
> {noformat}
> ERROR 2017-03-07 18:03:58,417 jmx.py:44 - Getting jmx metrics from NN failed.
> URL:
> http://c6401.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesy
> stem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 41, in get_value_from_jmx
> data_dict = json.loads(data)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> INFO 2017-03-07 18:04:02,769 logger.py:71 - call['ambari-sudo.sh su hdfs -l
> -s /bin/bash -c 'curl --negotiate -u : -s
> '"'"'http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'"'"'
> 1>/tmp/tmphTXg76 2>/tmp/tmp5bm2nM''] {'quiet': False}
> INFO 2017-03-07 18:04:02,797 logger.py:71 - call returned (0, '')
> ERROR 2017-03-07 18:04:02,798 jmx.py:44 - Getting jmx metrics from NN failed.
> URL:
> http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 41, in get_value_from_jmx
> data_dict = json.loads(data)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> {noformat}
> *Cause*
> During the test for the {{PXF Process}} alert, the Active NN is found using a
> JMX call. This call requires SPNEGO authentication since SPNEGO
> authentication is turned on for the Hadoop web interfaces. However, a valid
> Kerberos ticket is not found in the configured user's Kerberos ticket cache.
> In this case, the configured users is the HDFS user - which technically is
> not necessary.
> This occurs in
> {code:title=common-services/PXF/3.0.0/package/alerts/api_status.py:137}
> if CLUSTER_ENV_SECURITY in configurations and
> configurations[CLUSTER_ENV_SECURITY].lower() == "true":
> if 'dfs.nameservices' in configurations[HDFS_SITE]:
> namenode_address =
> get_active_namenode(ConfigDictionary(configurations[HDFS_SITE]),
> configurations[CLUSTER_ENV_SECURITY], configurations[HADOOP_ENV_HDFS_USER])[1]
> else:
> namenode_address =
> configurations[HDFS_SITE]['dfs.namenode.http-address']
> token = _get_delegation_token(namenode_address,
> configurations[HADOOP_ENV_HDFS_USER],
>
> configurations[HADOOP_ENV_HDFS_USER_KEYTAB],
>
> configurations[HADOOP_ENV_HDFS_PRINCIPAL_NAME],
> None)
> commonPXFHeaders.update({"X-GP-TOKEN": token})
> {code}
> Inside the call at
[jira] [Commented] (AMBARI-20332) Few ambari agent unit tests are failing
[
https://issues.apache.org/jira/browse/AMBARI-20332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903207#comment-15903207
]
Hudson commented on AMBARI-20332:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1220 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1220/])
AMBARI-20332. Few ambari agent unit tests are failing (aonishuk) (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=95833865c3b2bb006ae44b355a3c597bd2cef3d7])
* (edit) ambari-agent/src/test/python/resource_management/TestDatanodeHelper.py
* (edit)
ambari-server/src/test/python/stacks/2.0.6/YARN/test_yarn_service_check.py
> Few ambari agent unit tests are failing
> ---
>
> Key: AMBARI-20332
> URL: https://issues.apache.org/jira/browse/AMBARI-20332
> Project: Ambari
> Issue Type: Bug
> Components: test
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-20332.patch
>
>
> Few ambari agent tests are failing as below.
> {code:title=test cmd}
> export MAVEN_OPTS="-Xmx8192m -XX:MaxPermSize=4096m"; mvn -B -nsu
> -DforkCount=4 -Dmaven.test.failure.ignore=true -fae clean test {code}
> {code}
> ==
> ERROR: test_may_manage_folder (TestDatanodeHelper.TestDatanodeHelper)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/resource_management/TestDatanodeHelper.py",
> line 179, in test_may_manage_folder
> self.assertSetEqual(dirs_unmounted, set())
> AttributeError: 'TestDatanodeHelper' object has no attribute 'assertSetEqual'
> ==
> FAIL: test_kill_process_with_children (TestShell.TestShell)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestShell.py",
> line 71, in test_kill_process_with_children
> self.assertTrue(sleep_cmd in out)
> AssertionError
> ==
> FAIL: test_facterMemInfoOutput (TestHardware.TestHardware)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestHardware.py", line
> 247, in test_facterMemInfoOutput
> self.assertEquals(result['memorysize'], 1832392)
> AssertionError: u'4194304' != 1832392
> --
> Ran 448 tests in 15.028s
> FAILED (failures=2, errors=1)
> [INFO] {code}
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 7.696
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.213
> s]
> [INFO] Ambari Web . SUCCESS [02:07
> min]
> [INFO] Ambari Views ... SUCCESS [ 6.316
> s]
> [INFO] Ambari Admin View .. SUCCESS [01:17
> min]
> [INFO] utility SUCCESS [ 3.209
> s]
> [INFO] ambari-metrics . SUCCESS [ 1.427
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 5.610
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 7.023
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 5.797
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 4.710
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.895
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 3.642
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [07:18
> min]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 5.923
> s]
> [INFO] Ambari Metrics Grafana . SUCCESS [ 3.769
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [ 7.651
> s]
> [INFO] Ambari Server .. FAILURE [15:35
> min]
> [INFO] Ambari Functional Tests SKIPPED
> [INFO] Ambari Agent
[jira] [Commented] (AMBARI-20367) Update Zeppelin version on Ambari-2.5 from 0.6.2 to 0.7.0
[ https://issues.apache.org/jira/browse/AMBARI-20367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903206#comment-15903206 ] Hudson commented on AMBARI-20367: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1220 (See [https://builds.apache.org/job/Ambari-branch-2.5/1220/]) AMBARI-20367: Update Zeppelin version on Ambari-2.5 from 0.6.2 to 0.7.0 (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e1cdfe4492c9bd8d9aa1a4151af5badfd93e6d95]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/ZEPPELIN/metainfo.xml > Update Zeppelin version on Ambari-2.5 from 0.6.2 to 0.7.0 > - > > Key: AMBARI-20367 > URL: https://issues.apache.org/jira/browse/AMBARI-20367 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20367_branch-2.5_v1.patch > > > Update Zeppelin version on Ambari-2.5 from 0.6.2 to 0.7.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20373) Complete button after move masters is grayed out even after move has completed
[ https://issues.apache.org/jira/browse/AMBARI-20373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903203#comment-15903203 ] Hudson commented on AMBARI-20373: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1220 (See [https://builds.apache.org/job/Ambari-branch-2.5/1220/]) AMBARI-20373. Complete button after move masters is grayed out even (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4534e0a5aa91f34b44ac32e492cc960d91c07046]) * (edit) ambari-web/app/routes/reassign_master_routes.js > Complete button after move masters is grayed out even after move has completed > -- > > Key: AMBARI-20373 > URL: https://issues.apache.org/jira/browse/AMBARI-20373 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20373_branch-2.5.patch, AMBARI-20373.patch > > > STR : > Move namenode from host1 to host2. > Complete the move. The complete button is grayed out and can't be clicked. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20380) RU: Slider service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-20380:
Fix Version/s: 2.5.0
> RU: Slider service check failed during rolling upgrade
> --
>
> Key: AMBARI-20380
> URL: https://issues.apache.org/jira/browse/AMBARI-20380
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20380.patch
>
>
> During RU Slider Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
> ... 36 more
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException:
[jira] [Updated] (AMBARI-20380) RU: Slider service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-20380:
Priority: Major (was: Blocker)
> RU: Slider service check failed during rolling upgrade
> --
>
> Key: AMBARI-20380
> URL: https://issues.apache.org/jira/browse/AMBARI-20380
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-20380.patch
>
>
> During RU Slider Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
> ... 36 more
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
>
[jira] [Commented] (AMBARI-20344) RU: MR2 service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903201#comment-15903201
]
Hudson commented on AMBARI-20344:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1220 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1220/])
AMBARI-20344. RU: MR2 service check failed during rolling upgrade.
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c52027c849038c11e58e1c0b4eecb740bc9d0a1a])
* (edit)
ambari-server/src/main/resources/common-services/SLIDER/0.60.0.2.2/package/scripts/service_check.py
> RU: MR2 service check failed during rolling upgrade
> ---
>
> Key: AMBARI-20344
> URL: https://issues.apache.org/jira/browse/AMBARI-20344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-20344.patch
>
>
> During RU MapReduce Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
>
[jira] [Updated] (AMBARI-20377) Usability: Hostname hover of master is not discoverable in Summary section
[ https://issues.apache.org/jira/browse/AMBARI-20377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-20377: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk > Usability: Hostname hover of master is not discoverable in Summary section > -- > > Key: AMBARI-20377 > URL: https://issues.apache.org/jira/browse/AMBARI-20377 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-20377.patch > > > Currently, if you hover over a master component in Services > Summary, you > can see the hostname (for example, hover over NameNode). > The current hover takes a while to show, and is more of a title/alt hover vs. > a tooltip (for example, like hover on the Service status icons). Should > switch from title/alt hover to tooltip hover like Service status icons. It > shows faster and looks better. This will make hostname more discoverable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20380) RU: Slider service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-20380:
Component/s: ambari-server
> RU: Slider service check failed during rolling upgrade
> --
>
> Key: AMBARI-20380
> URL: https://issues.apache.org/jira/browse/AMBARI-20380
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Attachments: AMBARI-20380.patch
>
>
> During RU Slider Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
> ... 36 more
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
>
[jira] [Updated] (AMBARI-20380) RU: Slider service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-20380:
Status: Patch Available (was: Open)
> RU: Slider service check failed during rolling upgrade
> --
>
> Key: AMBARI-20380
> URL: https://issues.apache.org/jira/browse/AMBARI-20380
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Attachments: AMBARI-20380.patch
>
>
> During RU Slider Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
> ... 36 more
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
>
[jira] [Updated] (AMBARI-20380) RU: Slider service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-20380:
Attachment: AMBARI-20380.patch
> RU: Slider service check failed during rolling upgrade
> --
>
> Key: AMBARI-20380
> URL: https://issues.apache.org/jira/browse/AMBARI-20380
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Attachments: AMBARI-20380.patch
>
>
> During RU Slider Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
> ... 36 more
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
>
[jira] [Created] (AMBARI-20380) RU: Slider service check failed during rolling upgrade
Dmitry Lysnichenko created AMBARI-20380:
---
Summary: RU: Slider service check failed during rolling upgrade
Key: AMBARI-20380
URL: https://issues.apache.org/jira/browse/AMBARI-20380
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Priority: Blocker
During RU Slider Service check failed with exception:
{code:java}
17/02/25 14:18:24 INFO service.AbstractService: Service
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state STARTED;
cause: java.lang.RuntimeException: java.lang.RuntimeException:
java.lang.ClassNotFoundException: Class
org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
java.lang.RuntimeException: java.lang.RuntimeException:
java.lang.ClassNotFoundException: Class
org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
at
org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
at
org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
at
org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: Class
org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
... 35 more
Caused by: java.lang.ClassNotFoundException: Class
org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
at org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
... 36 more
17/02/25 14:18:24 INFO service.AbstractService: Service
org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
java.lang.RuntimeException: java.lang.RuntimeException:
java.lang.ClassNotFoundException: Class
org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
java.lang.RuntimeException: java.lang.RuntimeException:
java.lang.ClassNotFoundException: Class
org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
at
org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
at
org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
at
[jira] [Updated] (AMBARI-20376) While Moving Namenode via Move Master wizard, datanodes reported as down
[
https://issues.apache.org/jira/browse/AMBARI-20376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-20376:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
pushed to 2.5 and trunk
> While Moving Namenode via Move Master wizard, datanodes reported as down
>
>
> Key: AMBARI-20376
> URL: https://issues.apache.org/jira/browse/AMBARI-20376
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20376.patch
>
>
> While Moving Namenode via Move Master wizard, datanodes reported as down
> while starting ATS.
> Seeing this in a couple of splits today. ATS fails to start showing there are
> no live datanodes
> {code}
> {
> "RemoteException": {
> "exception": "RetriableException",
> "javaClassName": "org.apache.hadoop.ipc.RetriableException",
> "message": "org.apache.hadoop.hdfs.server.namenode.SafeModeException:
> Cannot set permission for /ats/done. Name node is in safe mode.\nThe reported
> blocks 934 has reached the threshold 0.9900 of total blocks 934. The number
> of live datanodes 3 has reached the minimum number 0. In safe mode extension.
> Safe mode will be turned off automatically in 21 seconds."
> }
> }
> {code}
> The step before ATS start, starts datanode explicitly. On retry ATS will
> possibly come up. But no retries were needed before
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20362) Enable Authentication in Zeppelin out of Box
[ https://issues.apache.org/jira/browse/AMBARI-20362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-20362: - Assignee: Prabhjyot Singh (was: Renjith Kamath) Status: Patch Available (was: Open) > Enable Authentication in Zeppelin out of Box > > > Key: AMBARI-20362 > URL: https://issues.apache.org/jira/browse/AMBARI-20362 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.5.0 >Reporter: Kshitij Badani >Assignee: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-20362_brach-2.5_v1.patch > > > Right now Zeppelin does not have any authentication enabled out of the box. > As the security sensitivity is ever increasing we should enable > authentication by default. > We can use the same account Ambari Admin uses to authenticate with Zeppelin. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20362) Enable Authentication in Zeppelin out of Box
[ https://issues.apache.org/jira/browse/AMBARI-20362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath reassigned AMBARI-20362: --- Assignee: Renjith Kamath (was: Prabhjyot Singh) > Enable Authentication in Zeppelin out of Box > > > Key: AMBARI-20362 > URL: https://issues.apache.org/jira/browse/AMBARI-20362 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.5.0 >Reporter: Kshitij Badani >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-20362_brach-2.5_v1.patch > > > Right now Zeppelin does not have any authentication enabled out of the box. > As the security sensitivity is ever increasing we should enable > authentication by default. > We can use the same account Ambari Admin uses to authenticate with Zeppelin. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20362) Enable Authentication in Zeppelin out of Box
[ https://issues.apache.org/jira/browse/AMBARI-20362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-20362: Resolution: Fixed Status: Resolved (was: Patch Available) committed to branch-2.5 and trunk > Enable Authentication in Zeppelin out of Box > > > Key: AMBARI-20362 > URL: https://issues.apache.org/jira/browse/AMBARI-20362 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.5.0 >Reporter: Kshitij Badani >Assignee: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-20362_brach-2.5_v1.patch > > > Right now Zeppelin does not have any authentication enabled out of the box. > As the security sensitivity is ever increasing we should enable > authentication by default. > We can use the same account Ambari Admin uses to authenticate with Zeppelin. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20362) Enable Authentication in Zeppelin out of Box
[ https://issues.apache.org/jira/browse/AMBARI-20362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh reassigned AMBARI-20362: Assignee: Prabhjyot Singh > Enable Authentication in Zeppelin out of Box > > > Key: AMBARI-20362 > URL: https://issues.apache.org/jira/browse/AMBARI-20362 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.5.0 >Reporter: Kshitij Badani >Assignee: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-20362_brach-2.5_v1.patch > > > Right now Zeppelin does not have any authentication enabled out of the box. > As the security sensitivity is ever increasing we should enable > authentication by default. > We can use the same account Ambari Admin uses to authenticate with Zeppelin. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20377) Usability: Hostname hover of master is not discoverable in Summary section
[ https://issues.apache.org/jira/browse/AMBARI-20377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903171#comment-15903171 ] Aleksandr Kovalenko commented on AMBARI-20377: -- +1 for the patch > Usability: Hostname hover of master is not discoverable in Summary section > -- > > Key: AMBARI-20377 > URL: https://issues.apache.org/jira/browse/AMBARI-20377 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-20377.patch > > > Currently, if you hover over a master component in Services > Summary, you > can see the hostname (for example, hover over NameNode). > The current hover takes a while to show, and is more of a title/alt hover vs. > a tooltip (for example, like hover on the Service status icons). Should > switch from title/alt hover to tooltip hover like Service status icons. It > shows faster and looks better. This will make hostname more discoverable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20359) Not able to import workflow with fs action node
[
https://issues.apache.org/jira/browse/AMBARI-20359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallav Kulshreshtha updated AMBARI-20359:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk and branch-2.5
> Not able to import workflow with fs action node
> ---
>
> Key: AMBARI-20359
> URL: https://issues.apache.org/jira/browse/AMBARI-20359
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: M Madhan Mohan Reddy
>Priority: Critical
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20359_trunk.patch
>
>
> Not able to import workflow with fs action node.
> Seeing below error in UI console log :
> {code}
> Uncaught TypeError: Cannot read property '0' of undefined
> at n.handleImport
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:7:28237)
> at n [as handleImport]
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:18180)
> at n.handleImportNode
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:13846)
> at
> http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:27314
> at Array.forEach (native)
> at
> http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:27286
> at Array.forEach (native)
> at n.setupNodeMap
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:27188)
> at n.processWorkflowXml
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:26231)
> at n.importWorkflow
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:25548)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20377) Usability: Hostname hover of master is not discoverable in Summary section
[
https://issues.apache.org/jira/browse/AMBARI-20377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903158#comment-15903158
]
Hadoop QA commented on AMBARI-20377:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856996/AMBARI-20377.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10941//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10941//console
This message is automatically generated.
> Usability: Hostname hover of master is not discoverable in Summary section
> --
>
> Key: AMBARI-20377
> URL: https://issues.apache.org/jira/browse/AMBARI-20377
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-20377.patch
>
>
> Currently, if you hover over a master component in Services > Summary, you
> can see the hostname (for example, hover over NameNode).
> The current hover takes a while to show, and is more of a title/alt hover vs.
> a tooltip (for example, like hover on the Service status icons). Should
> switch from title/alt hover to tooltip hover like Service status icons. It
> shows faster and looks better. This will make hostname more discoverable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20371) WFM: Delete option in Manage recent list.
[ https://issues.apache.org/jira/browse/AMBARI-20371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-20371: Resolution: Fixed Status: Resolved (was: Patch Available) > WFM: Delete option in Manage recent list. > - > > Key: AMBARI-20371 > URL: https://issues.apache.org/jira/browse/AMBARI-20371 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20371_branch-2.5.patch > > > Provide option to delete workflows in Manage recent list. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20371) WFM: Delete option in Manage recent list.
[ https://issues.apache.org/jira/browse/AMBARI-20371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903141#comment-15903141 ] Hudson commented on AMBARI-20371: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6985 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6985/]) AMBARI-20371. WFM: Delete option in Manage recent list. (pallavkul) (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a3f593d8f83560b3496c87a08c9908fa6b0348d6]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/drafts-wf.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-workspace.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/styles/app.less * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/recent-projects.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/drafts-wf.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/designer-workspace.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/recent-projects.hbs Revert "AMBARI-20371. WFM: Delete option in Manage recent list. (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0ff34acb3cd9f71a82e8175a4d0086d16ddf01d0]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-workspace.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/styles/app.less * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/drafts-wf.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/recent-projects.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/drafts-wf.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/recent-projects.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/designer-workspace.js AMBARI-20371. WFM: Delete option in Manage recent list. (Venkata Sairam (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=625dc70b8c6803536f2a5b0f87904d26f8daae2c]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/recent-projects.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/styles/app.less * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/designer-workspace.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/recent-projects.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-workspace.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/drafts-wf.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/drafts-wf.hbs > WFM: Delete option in Manage recent list. > - > > Key: AMBARI-20371 > URL: https://issues.apache.org/jira/browse/AMBARI-20371 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20371_branch-2.5.patch > > > Provide option to delete workflows in Manage recent list. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20375) Remove duplicate code from wizard menu
[
https://issues.apache.org/jira/browse/AMBARI-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903139#comment-15903139
]
Oleg Nechiporenko commented on AMBARI-20375:
Committed to trunk
> Remove duplicate code from wizard menu
> --
>
> Key: AMBARI-20375
> URL: https://issues.apache.org/jira/browse/AMBARI-20375
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20375.patch
>
>
> {{'isStep..Disabled'}} and {{'isStep..Completed'}} may be rewritten as
> computed macros
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20379) Error during moving ResourceManager without Tez installed
[ https://issues.apache.org/jira/browse/AMBARI-20379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20379: - Attachment: AMBARI-20379.patch > Error during moving ResourceManager without Tez installed > - > > Key: AMBARI-20379 > URL: https://issues.apache.org/jira/browse/AMBARI-20379 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20379_branch-2.5.patch, AMBARI-20379.patch > > > Run Move Wizard for ResourceManager without Tez installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20379) Error during moving ResourceManager without Tez installed
[ https://issues.apache.org/jira/browse/AMBARI-20379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20379: - Status: Patch Available (was: Open) > Error during moving ResourceManager without Tez installed > - > > Key: AMBARI-20379 > URL: https://issues.apache.org/jira/browse/AMBARI-20379 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20379_branch-2.5.patch, AMBARI-20379.patch > > > Run Move Wizard for ResourceManager without Tez installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20379) Error during moving ResourceManager without Tez installed
[ https://issues.apache.org/jira/browse/AMBARI-20379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20379: - Attachment: AMBARI-20379_branch-2.5.patch > Error during moving ResourceManager without Tez installed > - > > Key: AMBARI-20379 > URL: https://issues.apache.org/jira/browse/AMBARI-20379 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20379_branch-2.5.patch > > > Run Move Wizard for ResourceManager without Tez installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20375) Remove duplicate code from wizard menu
[
https://issues.apache.org/jira/browse/AMBARI-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903137#comment-15903137
]
Oleg Nechiporenko commented on AMBARI-20375:
Tested manually on the real cluster
> Remove duplicate code from wizard menu
> --
>
> Key: AMBARI-20375
> URL: https://issues.apache.org/jira/browse/AMBARI-20375
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20375.patch
>
>
> {{'isStep..Disabled'}} and {{'isStep..Completed'}} may be rewritten as
> computed macros
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20367) Update Zeppelin version on Ambari-2.5 from 0.6.2 to 0.7.0
[ https://issues.apache.org/jira/browse/AMBARI-20367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-20367: Resolution: Fixed Status: Resolved (was: Patch Available) committed to branch-2.5 and trunk > Update Zeppelin version on Ambari-2.5 from 0.6.2 to 0.7.0 > - > > Key: AMBARI-20367 > URL: https://issues.apache.org/jira/browse/AMBARI-20367 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20367_branch-2.5_v1.patch > > > Update Zeppelin version on Ambari-2.5 from 0.6.2 to 0.7.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20379) Error during moving ResourceManager without Tez installed
Aleksandr Kovalenko created AMBARI-20379: Summary: Error during moving ResourceManager without Tez installed Key: AMBARI-20379 URL: https://issues.apache.org/jira/browse/AMBARI-20379 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 2.5.0 Run Move Wizard for ResourceManager without Tez installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20371) WFM: Delete option in Manage recent list.
[ https://issues.apache.org/jira/browse/AMBARI-20371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903131#comment-15903131 ] Hudson commented on AMBARI-20371: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1219 (See [https://builds.apache.org/job/Ambari-branch-2.5/1219/]) AMBARI-20371. WFM: Delete option in Manage recent list. (Venkata Sairam (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c9f70565538ea7710b2824c95c6190417711ff1b]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/styles/app.less * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/drafts-wf.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/designer-workspace.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/recent-projects.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-workspace.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/recent-projects.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/drafts-wf.js > WFM: Delete option in Manage recent list. > - > > Key: AMBARI-20371 > URL: https://issues.apache.org/jira/browse/AMBARI-20371 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20371_branch-2.5.patch > > > Provide option to delete workflows in Manage recent list. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20373) Complete button after move masters is grayed out even after move has completed
[ https://issues.apache.org/jira/browse/AMBARI-20373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903118#comment-15903118 ] Aleksandr Kovalenko commented on AMBARI-20373: -- changing router logic not covered by unit tests > Complete button after move masters is grayed out even after move has completed > -- > > Key: AMBARI-20373 > URL: https://issues.apache.org/jira/browse/AMBARI-20373 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20373_branch-2.5.patch, AMBARI-20373.patch > > > STR : > Move namenode from host1 to host2. > Complete the move. The complete button is grayed out and can't be clicked. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20332) Few ambari agent unit tests are failing
[
https://issues.apache.org/jira/browse/AMBARI-20332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-20332:
-
Fix Version/s: 2.5.0
> Few ambari agent unit tests are failing
> ---
>
> Key: AMBARI-20332
> URL: https://issues.apache.org/jira/browse/AMBARI-20332
> Project: Ambari
> Issue Type: Bug
> Components: test
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
> Fix For: 2.5.0
>
> Attachments: AMBARI-20332.patch
>
>
> Few ambari agent tests are failing as below.
> {code:title=test cmd}
> export MAVEN_OPTS="-Xmx8192m -XX:MaxPermSize=4096m"; mvn -B -nsu
> -DforkCount=4 -Dmaven.test.failure.ignore=true -fae clean test {code}
> {code}
> ==
> ERROR: test_may_manage_folder (TestDatanodeHelper.TestDatanodeHelper)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/resource_management/TestDatanodeHelper.py",
> line 179, in test_may_manage_folder
> self.assertSetEqual(dirs_unmounted, set())
> AttributeError: 'TestDatanodeHelper' object has no attribute 'assertSetEqual'
> ==
> FAIL: test_kill_process_with_children (TestShell.TestShell)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestShell.py",
> line 71, in test_kill_process_with_children
> self.assertTrue(sleep_cmd in out)
> AssertionError
> ==
> FAIL: test_facterMemInfoOutput (TestHardware.TestHardware)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestHardware.py", line
> 247, in test_facterMemInfoOutput
> self.assertEquals(result['memorysize'], 1832392)
> AssertionError: u'4194304' != 1832392
> --
> Ran 448 tests in 15.028s
> FAILED (failures=2, errors=1)
> [INFO] {code}
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 7.696
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.213
> s]
> [INFO] Ambari Web . SUCCESS [02:07
> min]
> [INFO] Ambari Views ... SUCCESS [ 6.316
> s]
> [INFO] Ambari Admin View .. SUCCESS [01:17
> min]
> [INFO] utility SUCCESS [ 3.209
> s]
> [INFO] ambari-metrics . SUCCESS [ 1.427
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 5.610
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 7.023
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 5.797
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 4.710
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.895
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 3.642
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [07:18
> min]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 5.923
> s]
> [INFO] Ambari Metrics Grafana . SUCCESS [ 3.769
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [ 7.651
> s]
> [INFO] Ambari Server .. FAILURE [15:35
> min]
> [INFO] Ambari Functional Tests SKIPPED
> [INFO] Ambari Agent ... FAILURE [ 42.590
> s]
> [INFO] Ambari Client .. SUCCESS [ 0.068
> s]
> [INFO] Ambari Python Client ... SUCCESS [ 2.080
> s]
> [INFO] Ambari Groovy Client ... SUCCESS [ 17.194
> s]
> [INFO] Ambari Shell ... SUCCESS [ 0.044
> s]
> [INFO] Ambari Python Shell SUCCESS [ 0.232
> s]
> [INFO] Ambari Groovy Shell
[jira] [Updated] (AMBARI-20332) Few ambari agent unit tests are failing
[
https://issues.apache.org/jira/browse/AMBARI-20332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-20332:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> Few ambari agent unit tests are failing
> ---
>
> Key: AMBARI-20332
> URL: https://issues.apache.org/jira/browse/AMBARI-20332
> Project: Ambari
> Issue Type: Bug
> Components: test
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-20332.patch
>
>
> Few ambari agent tests are failing as below.
> {code:title=test cmd}
> export MAVEN_OPTS="-Xmx8192m -XX:MaxPermSize=4096m"; mvn -B -nsu
> -DforkCount=4 -Dmaven.test.failure.ignore=true -fae clean test {code}
> {code}
> ==
> ERROR: test_may_manage_folder (TestDatanodeHelper.TestDatanodeHelper)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/resource_management/TestDatanodeHelper.py",
> line 179, in test_may_manage_folder
> self.assertSetEqual(dirs_unmounted, set())
> AttributeError: 'TestDatanodeHelper' object has no attribute 'assertSetEqual'
> ==
> FAIL: test_kill_process_with_children (TestShell.TestShell)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestShell.py",
> line 71, in test_kill_process_with_children
> self.assertTrue(sleep_cmd in out)
> AssertionError
> ==
> FAIL: test_facterMemInfoOutput (TestHardware.TestHardware)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestHardware.py", line
> 247, in test_facterMemInfoOutput
> self.assertEquals(result['memorysize'], 1832392)
> AssertionError: u'4194304' != 1832392
> --
> Ran 448 tests in 15.028s
> FAILED (failures=2, errors=1)
> [INFO] {code}
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 7.696
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.213
> s]
> [INFO] Ambari Web . SUCCESS [02:07
> min]
> [INFO] Ambari Views ... SUCCESS [ 6.316
> s]
> [INFO] Ambari Admin View .. SUCCESS [01:17
> min]
> [INFO] utility SUCCESS [ 3.209
> s]
> [INFO] ambari-metrics . SUCCESS [ 1.427
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 5.610
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 7.023
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 5.797
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 4.710
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.895
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 3.642
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [07:18
> min]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 5.923
> s]
> [INFO] Ambari Metrics Grafana . SUCCESS [ 3.769
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [ 7.651
> s]
> [INFO] Ambari Server .. FAILURE [15:35
> min]
> [INFO] Ambari Functional Tests SKIPPED
> [INFO] Ambari Agent ... FAILURE [ 42.590
> s]
> [INFO] Ambari Client .. SUCCESS [ 0.068
> s]
> [INFO] Ambari Python Client ... SUCCESS [ 2.080
> s]
> [INFO] Ambari Groovy Client ... SUCCESS [ 17.194
> s]
> [INFO] Ambari Shell ... SUCCESS [ 0.044
> s]
>
[jira] [Commented] (AMBARI-20332) Few ambari agent unit tests are failing
[
https://issues.apache.org/jira/browse/AMBARI-20332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903121#comment-15903121
]
Andrew Onischuk commented on AMBARI-20332:
--
{noformat}
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 156 licence.
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Views .. SUCCESS [4.894s]
[INFO] Ambari Metrics Common . SUCCESS [3.056s]
[INFO] Ambari Server . SUCCESS [1:40.982s]
[INFO] Ambari Agent .. SUCCESS [21.724s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2:11.962s
[INFO] Finished at: Thu Mar 09 15:58:32 EET 2017
[INFO] Final Memory: 72M/753M
[INFO]
{noformat}
> Few ambari agent unit tests are failing
> ---
>
> Key: AMBARI-20332
> URL: https://issues.apache.org/jira/browse/AMBARI-20332
> Project: Ambari
> Issue Type: Bug
> Components: test
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-20332.patch
>
>
> Few ambari agent tests are failing as below.
> {code:title=test cmd}
> export MAVEN_OPTS="-Xmx8192m -XX:MaxPermSize=4096m"; mvn -B -nsu
> -DforkCount=4 -Dmaven.test.failure.ignore=true -fae clean test {code}
> {code}
> ==
> ERROR: test_may_manage_folder (TestDatanodeHelper.TestDatanodeHelper)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/resource_management/TestDatanodeHelper.py",
> line 179, in test_may_manage_folder
> self.assertSetEqual(dirs_unmounted, set())
> AttributeError: 'TestDatanodeHelper' object has no attribute 'assertSetEqual'
> ==
> FAIL: test_kill_process_with_children (TestShell.TestShell)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestShell.py",
> line 71, in test_kill_process_with_children
> self.assertTrue(sleep_cmd in out)
> AssertionError
> ==
> FAIL: test_facterMemInfoOutput (TestHardware.TestHardware)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestHardware.py", line
> 247, in test_facterMemInfoOutput
> self.assertEquals(result['memorysize'], 1832392)
> AssertionError: u'4194304' != 1832392
> --
> Ran 448 tests in 15.028s
> FAILED (failures=2, errors=1)
> [INFO] {code}
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 7.696
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.213
> s]
> [INFO] Ambari Web . SUCCESS [02:07
> min]
> [INFO] Ambari Views ... SUCCESS [ 6.316
> s]
> [INFO] Ambari Admin View .. SUCCESS [01:17
> min]
> [INFO] utility SUCCESS [ 3.209
> s]
> [INFO] ambari-metrics . SUCCESS [ 1.427
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 5.610
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 7.023
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 5.797
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 4.710
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.895
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 3.642
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [07:18
>
[jira] [Updated] (AMBARI-20332) Few ambari agent unit tests are failing
[
https://issues.apache.org/jira/browse/AMBARI-20332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-20332:
-
Affects Version/s: 2.5.0
> Few ambari agent unit tests are failing
> ---
>
> Key: AMBARI-20332
> URL: https://issues.apache.org/jira/browse/AMBARI-20332
> Project: Ambari
> Issue Type: Bug
> Components: test
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
> Fix For: 2.5.0
>
> Attachments: AMBARI-20332.patch
>
>
> Few ambari agent tests are failing as below.
> {code:title=test cmd}
> export MAVEN_OPTS="-Xmx8192m -XX:MaxPermSize=4096m"; mvn -B -nsu
> -DforkCount=4 -Dmaven.test.failure.ignore=true -fae clean test {code}
> {code}
> ==
> ERROR: test_may_manage_folder (TestDatanodeHelper.TestDatanodeHelper)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/resource_management/TestDatanodeHelper.py",
> line 179, in test_may_manage_folder
> self.assertSetEqual(dirs_unmounted, set())
> AttributeError: 'TestDatanodeHelper' object has no attribute 'assertSetEqual'
> ==
> FAIL: test_kill_process_with_children (TestShell.TestShell)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestShell.py",
> line 71, in test_kill_process_with_children
> self.assertTrue(sleep_cmd in out)
> AssertionError
> ==
> FAIL: test_facterMemInfoOutput (TestHardware.TestHardware)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestHardware.py", line
> 247, in test_facterMemInfoOutput
> self.assertEquals(result['memorysize'], 1832392)
> AssertionError: u'4194304' != 1832392
> --
> Ran 448 tests in 15.028s
> FAILED (failures=2, errors=1)
> [INFO] {code}
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 7.696
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.213
> s]
> [INFO] Ambari Web . SUCCESS [02:07
> min]
> [INFO] Ambari Views ... SUCCESS [ 6.316
> s]
> [INFO] Ambari Admin View .. SUCCESS [01:17
> min]
> [INFO] utility SUCCESS [ 3.209
> s]
> [INFO] ambari-metrics . SUCCESS [ 1.427
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 5.610
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 7.023
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 5.797
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 4.710
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.895
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 3.642
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [07:18
> min]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 5.923
> s]
> [INFO] Ambari Metrics Grafana . SUCCESS [ 3.769
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [ 7.651
> s]
> [INFO] Ambari Server .. FAILURE [15:35
> min]
> [INFO] Ambari Functional Tests SKIPPED
> [INFO] Ambari Agent ... FAILURE [ 42.590
> s]
> [INFO] Ambari Client .. SUCCESS [ 0.068
> s]
> [INFO] Ambari Python Client ... SUCCESS [ 2.080
> s]
> [INFO] Ambari Groovy Client ... SUCCESS [ 17.194
> s]
> [INFO] Ambari Shell ... SUCCESS [ 0.044
> s]
> [INFO] Ambari Python Shell SUCCESS [ 0.232
> s]
> [INFO] Ambari Groovy Shell
[jira] [Assigned] (AMBARI-20332) Few ambari agent unit tests are failing
[
https://issues.apache.org/jira/browse/AMBARI-20332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk reassigned AMBARI-20332:
Assignee: Andrew Onischuk
> Few ambari agent unit tests are failing
> ---
>
> Key: AMBARI-20332
> URL: https://issues.apache.org/jira/browse/AMBARI-20332
> Project: Ambari
> Issue Type: Bug
> Components: test
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-20332.patch
>
>
> Few ambari agent tests are failing as below.
> {code:title=test cmd}
> export MAVEN_OPTS="-Xmx8192m -XX:MaxPermSize=4096m"; mvn -B -nsu
> -DforkCount=4 -Dmaven.test.failure.ignore=true -fae clean test {code}
> {code}
> ==
> ERROR: test_may_manage_folder (TestDatanodeHelper.TestDatanodeHelper)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/resource_management/TestDatanodeHelper.py",
> line 179, in test_may_manage_folder
> self.assertSetEqual(dirs_unmounted, set())
> AttributeError: 'TestDatanodeHelper' object has no attribute 'assertSetEqual'
> ==
> FAIL: test_kill_process_with_children (TestShell.TestShell)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestShell.py",
> line 71, in test_kill_process_with_children
> self.assertTrue(sleep_cmd in out)
> AssertionError
> ==
> FAIL: test_facterMemInfoOutput (TestHardware.TestHardware)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestHardware.py", line
> 247, in test_facterMemInfoOutput
> self.assertEquals(result['memorysize'], 1832392)
> AssertionError: u'4194304' != 1832392
> --
> Ran 448 tests in 15.028s
> FAILED (failures=2, errors=1)
> [INFO] {code}
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 7.696
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.213
> s]
> [INFO] Ambari Web . SUCCESS [02:07
> min]
> [INFO] Ambari Views ... SUCCESS [ 6.316
> s]
> [INFO] Ambari Admin View .. SUCCESS [01:17
> min]
> [INFO] utility SUCCESS [ 3.209
> s]
> [INFO] ambari-metrics . SUCCESS [ 1.427
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 5.610
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 7.023
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 5.797
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 4.710
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.895
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 3.642
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [07:18
> min]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 5.923
> s]
> [INFO] Ambari Metrics Grafana . SUCCESS [ 3.769
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [ 7.651
> s]
> [INFO] Ambari Server .. FAILURE [15:35
> min]
> [INFO] Ambari Functional Tests SKIPPED
> [INFO] Ambari Agent ... FAILURE [ 42.590
> s]
> [INFO] Ambari Client .. SUCCESS [ 0.068
> s]
> [INFO] Ambari Python Client ... SUCCESS [ 2.080
> s]
> [INFO] Ambari Groovy Client ... SUCCESS [ 17.194
> s]
> [INFO] Ambari Shell ... SUCCESS [ 0.044
> s]
> [INFO] Ambari Python Shell SUCCESS [
[jira] [Updated] (AMBARI-20373) Complete button after move masters is grayed out even after move has completed
[ https://issues.apache.org/jira/browse/AMBARI-20373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20373: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.5 > Complete button after move masters is grayed out even after move has completed > -- > > Key: AMBARI-20373 > URL: https://issues.apache.org/jira/browse/AMBARI-20373 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20373_branch-2.5.patch, AMBARI-20373.patch > > > STR : > Move namenode from host1 to host2. > Complete the move. The complete button is grayed out and can't be clicked. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20365) Display Ranger DB backup instruction in sections on the manual step during RU
[ https://issues.apache.org/jira/browse/AMBARI-20365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20365: --- Description: current approach is to use multiple sections. Alejandro also suggested an alternative where a single section can accept HTML markup for greater flexibility. The alternative approach will be treated as a feature request in a separate JIRA. (was: current approach is to use multiple sections. Alejandro also suggested an alternative where a single section can accept HTML markup for greater flexibility.) > Display Ranger DB backup instruction in sections on the manual step during RU > - > > Key: AMBARI-20365 > URL: https://issues.apache.org/jira/browse/AMBARI-20365 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20365.patch > > > current approach is to use multiple sections. Alejandro also > suggested an alternative where a single section can accept HTML > markup for greater flexibility. The alternative approach will be treated as a > feature request in a separate JIRA. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20376) While Moving Namenode via Move Master wizard, datanodes reported as down
[
https://issues.apache.org/jira/browse/AMBARI-20376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903116#comment-15903116
]
Hadoop QA commented on AMBARI-20376:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856993/AMBARI-20376.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10940//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10940//console
This message is automatically generated.
> While Moving Namenode via Move Master wizard, datanodes reported as down
>
>
> Key: AMBARI-20376
> URL: https://issues.apache.org/jira/browse/AMBARI-20376
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20376.patch
>
>
> While Moving Namenode via Move Master wizard, datanodes reported as down
> while starting ATS.
> Seeing this in a couple of splits today. ATS fails to start showing there are
> no live datanodes
> {code}
> {
> "RemoteException": {
> "exception": "RetriableException",
> "javaClassName": "org.apache.hadoop.ipc.RetriableException",
> "message": "org.apache.hadoop.hdfs.server.namenode.SafeModeException:
> Cannot set permission for /ats/done. Name node is in safe mode.\nThe reported
> blocks 934 has reached the threshold 0.9900 of total blocks 934. The number
> of live datanodes 3 has reached the minimum number 0. In safe mode extension.
> Safe mode will be turned off automatically in 21 seconds."
> }
> }
> {code}
> The step before ATS start, starts datanode explicitly. On retry ATS will
> possibly come up. But no retries were needed before
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20371) WFM: Delete option in Manage recent list.
[ https://issues.apache.org/jira/browse/AMBARI-20371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-20371: Status: Patch Available (was: Reopened) > WFM: Delete option in Manage recent list. > - > > Key: AMBARI-20371 > URL: https://issues.apache.org/jira/browse/AMBARI-20371 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20371_branch-2.5.patch > > > Provide option to delete workflows in Manage recent list. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-20371) WFM: Delete option in Manage recent list.
[ https://issues.apache.org/jira/browse/AMBARI-20371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat reopened AMBARI-20371: - > WFM: Delete option in Manage recent list. > - > > Key: AMBARI-20371 > URL: https://issues.apache.org/jira/browse/AMBARI-20371 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20371_branch-2.5.patch > > > Provide option to delete workflows in Manage recent list. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20371) WFM: Delete option in Manage recent list.
[ https://issues.apache.org/jira/browse/AMBARI-20371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-20371: Resolution: Fixed Status: Resolved (was: Patch Available) > WFM: Delete option in Manage recent list. > - > > Key: AMBARI-20371 > URL: https://issues.apache.org/jira/browse/AMBARI-20371 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20371_branch-2.5.patch > > > Provide option to delete workflows in Manage recent list. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20378) LogFeeder: Add de-duplication support
[
https://issues.apache.org/jira/browse/AMBARI-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-20378:
--
Description:
Add de-duplication support to logfeeder.
For handling duplications, it will be an LRU cache for every input.
It can be set up at input config block. For example (the values below are the
defaults):
{code:java}
{
"input": [
{
...
"cache_enabled" : "true",
"cache_size" : "100",
"cache_dedup_interval" : "1000",
"cache_last_dedup_enabled" : "false",
"cache_key_field" : "log_message"
}
] ...
{code}
{{cache_dedup_interval}} : if the interval (timestamp - date difference) is not
reached between 2 log messages (same content), then the new log will be
dropped.
{{cache_last_dedup_enabled}}: if its enabled and the new log message is the
same as the last one, the new log will be dropped. (dedup interval wont have
impact on that feature)
{{cache_key_field}} : field of the log message which will be compared and
stored in the cache (as keys)
> LogFeeder: Add de-duplication support
> -
>
> Key: AMBARI-20378
> URL: https://issues.apache.org/jira/browse/AMBARI-20378
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: trunk
>
> Attachments: AMBARI-20378.patch
>
>
> Add de-duplication support to logfeeder.
> For handling duplications, it will be an LRU cache for every input.
> It can be set up at input config block. For example (the values below are the
> defaults):
> {code:java}
> {
> "input": [
> {
> ...
> "cache_enabled" : "true",
> "cache_size" : "100",
> "cache_dedup_interval" : "1000",
> "cache_last_dedup_enabled" : "false",
> "cache_key_field" : "log_message"
> }
> ] ...
> {code}
> {{cache_dedup_interval}} : if the interval (timestamp - date difference) is
> not reached between 2 log messages (same content), then the new log will be
> dropped.
> {{cache_last_dedup_enabled}}: if its enabled and the new log message is the
> same as the last one, the new log will be dropped. (dedup interval wont have
> impact on that feature)
> {{cache_key_field}} : field of the log message which will be compared and
> stored in the cache (as keys)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20378) LogFeeder: Add de-duplication support
[ https://issues.apache.org/jira/browse/AMBARI-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-20378: -- Status: Patch Available (was: Open) > LogFeeder: Add de-duplication support > - > > Key: AMBARI-20378 > URL: https://issues.apache.org/jira/browse/AMBARI-20378 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: trunk > > Attachments: AMBARI-20378.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20378) LogFeeder: Add de-duplication support
[ https://issues.apache.org/jira/browse/AMBARI-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-20378: -- Attachment: AMBARI-20378.patch > LogFeeder: Add de-duplication support > - > > Key: AMBARI-20378 > URL: https://issues.apache.org/jira/browse/AMBARI-20378 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: trunk > > Attachments: AMBARI-20378.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20332) Few ambari agent unit tests are failing
[
https://issues.apache.org/jira/browse/AMBARI-20332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-20332:
-
Attachment: AMBARI-20332.patch
> Few ambari agent unit tests are failing
> ---
>
> Key: AMBARI-20332
> URL: https://issues.apache.org/jira/browse/AMBARI-20332
> Project: Ambari
> Issue Type: Bug
> Components: test
>Reporter: Yesha Vora
> Attachments: AMBARI-20332.patch
>
>
> Few ambari agent tests are failing as below.
> {code:title=test cmd}
> export MAVEN_OPTS="-Xmx8192m -XX:MaxPermSize=4096m"; mvn -B -nsu
> -DforkCount=4 -Dmaven.test.failure.ignore=true -fae clean test {code}
> {code}
> ==
> ERROR: test_may_manage_folder (TestDatanodeHelper.TestDatanodeHelper)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/resource_management/TestDatanodeHelper.py",
> line 179, in test_may_manage_folder
> self.assertSetEqual(dirs_unmounted, set())
> AttributeError: 'TestDatanodeHelper' object has no attribute 'assertSetEqual'
> ==
> FAIL: test_kill_process_with_children (TestShell.TestShell)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestShell.py",
> line 71, in test_kill_process_with_children
> self.assertTrue(sleep_cmd in out)
> AssertionError
> ==
> FAIL: test_facterMemInfoOutput (TestHardware.TestHardware)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestHardware.py", line
> 247, in test_facterMemInfoOutput
> self.assertEquals(result['memorysize'], 1832392)
> AssertionError: u'4194304' != 1832392
> --
> Ran 448 tests in 15.028s
> FAILED (failures=2, errors=1)
> [INFO] {code}
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 7.696
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.213
> s]
> [INFO] Ambari Web . SUCCESS [02:07
> min]
> [INFO] Ambari Views ... SUCCESS [ 6.316
> s]
> [INFO] Ambari Admin View .. SUCCESS [01:17
> min]
> [INFO] utility SUCCESS [ 3.209
> s]
> [INFO] ambari-metrics . SUCCESS [ 1.427
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 5.610
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 7.023
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 5.797
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 4.710
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.895
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 3.642
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [07:18
> min]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 5.923
> s]
> [INFO] Ambari Metrics Grafana . SUCCESS [ 3.769
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [ 7.651
> s]
> [INFO] Ambari Server .. FAILURE [15:35
> min]
> [INFO] Ambari Functional Tests SKIPPED
> [INFO] Ambari Agent ... FAILURE [ 42.590
> s]
> [INFO] Ambari Client .. SUCCESS [ 0.068
> s]
> [INFO] Ambari Python Client ... SUCCESS [ 2.080
> s]
> [INFO] Ambari Groovy Client ... SUCCESS [ 17.194
> s]
> [INFO] Ambari Shell ... SUCCESS [ 0.044
> s]
> [INFO] Ambari Python Shell SUCCESS [ 0.232
> s]
> [INFO] Ambari Groovy Shell SUCCESS [ 10.669
> s]
>
[jira] [Updated] (AMBARI-20332) Few ambari agent unit tests are failing
[
https://issues.apache.org/jira/browse/AMBARI-20332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-20332:
-
Status: Patch Available (was: Open)
> Few ambari agent unit tests are failing
> ---
>
> Key: AMBARI-20332
> URL: https://issues.apache.org/jira/browse/AMBARI-20332
> Project: Ambari
> Issue Type: Bug
> Components: test
>Reporter: Yesha Vora
> Attachments: AMBARI-20332.patch
>
>
> Few ambari agent tests are failing as below.
> {code:title=test cmd}
> export MAVEN_OPTS="-Xmx8192m -XX:MaxPermSize=4096m"; mvn -B -nsu
> -DforkCount=4 -Dmaven.test.failure.ignore=true -fae clean test {code}
> {code}
> ==
> ERROR: test_may_manage_folder (TestDatanodeHelper.TestDatanodeHelper)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/resource_management/TestDatanodeHelper.py",
> line 179, in test_may_manage_folder
> self.assertSetEqual(dirs_unmounted, set())
> AttributeError: 'TestDatanodeHelper' object has no attribute 'assertSetEqual'
> ==
> FAIL: test_kill_process_with_children (TestShell.TestShell)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestShell.py",
> line 71, in test_kill_process_with_children
> self.assertTrue(sleep_cmd in out)
> AssertionError
> ==
> FAIL: test_facterMemInfoOutput (TestHardware.TestHardware)
> --
> Traceback (most recent call last):
> File "/xxx/ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
> in patched
> return func(*args, **keywargs)
> File
> "/xxx/ambari/ambari-agent/src/test/python/ambari_agent/TestHardware.py", line
> 247, in test_facterMemInfoOutput
> self.assertEquals(result['memorysize'], 1832392)
> AssertionError: u'4194304' != 1832392
> --
> Ran 448 tests in 15.028s
> FAILED (failures=2, errors=1)
> [INFO] {code}
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 7.696
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.213
> s]
> [INFO] Ambari Web . SUCCESS [02:07
> min]
> [INFO] Ambari Views ... SUCCESS [ 6.316
> s]
> [INFO] Ambari Admin View .. SUCCESS [01:17
> min]
> [INFO] utility SUCCESS [ 3.209
> s]
> [INFO] ambari-metrics . SUCCESS [ 1.427
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 5.610
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 7.023
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 5.797
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 4.710
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.895
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 3.642
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [07:18
> min]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 5.923
> s]
> [INFO] Ambari Metrics Grafana . SUCCESS [ 3.769
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [ 7.651
> s]
> [INFO] Ambari Server .. FAILURE [15:35
> min]
> [INFO] Ambari Functional Tests SKIPPED
> [INFO] Ambari Agent ... FAILURE [ 42.590
> s]
> [INFO] Ambari Client .. SUCCESS [ 0.068
> s]
> [INFO] Ambari Python Client ... SUCCESS [ 2.080
> s]
> [INFO] Ambari Groovy Client ... SUCCESS [ 17.194
> s]
> [INFO] Ambari Shell ... SUCCESS [ 0.044
> s]
> [INFO] Ambari Python Shell SUCCESS [ 0.232
> s]
> [INFO] Ambari Groovy Shell SUCCESS [ 10.669
> s]
[jira] [Commented] (AMBARI-20375) Remove duplicate code from wizard menu
[
https://issues.apache.org/jira/browse/AMBARI-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903078#comment-15903078
]
Hadoop QA commented on AMBARI-20375:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856990/AMBARI-20375.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10939//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10939//console
This message is automatically generated.
> Remove duplicate code from wizard menu
> --
>
> Key: AMBARI-20375
> URL: https://issues.apache.org/jira/browse/AMBARI-20375
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20375.patch
>
>
> {{'isStep..Disabled'}} and {{'isStep..Completed'}} may be rewritten as
> computed macros
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20378) LogFeeder: Add de-duplication support
Olivér Szabó created AMBARI-20378: - Summary: LogFeeder: Add de-duplication support Key: AMBARI-20378 URL: https://issues.apache.org/jira/browse/AMBARI-20378 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.5.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: trunk -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20361) Stack Upgrade tests fail during Hive Metastore restart due to missing hive-site.jceks file
[
https://issues.apache.org/jira/browse/AMBARI-20361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-20361.
--
Resolution: Fixed
> Stack Upgrade tests fail during Hive Metastore restart due to missing
> hive-site.jceks file
> --
>
> Key: AMBARI-20361
> URL: https://issues.apache.org/jira/browse/AMBARI-20361
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Blocker
> Labels: express_upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-20361.patch
>
>
> *STR*
> # Deploy HDP-2.5.0.0 with Ambari-2.5.x
> # Register HDP-2.6 version and install the bits
> # Start Express Upgrade
> *Result:*
> Failed with below error during restart of Hive Metastore:
> {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 260, in
> HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 313, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 761, in restart
> self.start(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 58, in start
> self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 116, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 74, in configure
> hive(name = 'metastore')
> 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/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 228, in hive
> params.user_group
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/security_commons.py",
> line 55, in update_credential_provider_path
> content = StaticFile(src_provider_path)
> 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 123, in action_create
> content = self._get_content()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 160, in _get_content
> return content()
> File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
> line 52, in __call__
> return self.get_content()
> File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
> line 76, in get_content
> raise Fail("{0} Source file {1} is not found".format(repr(self), path))
> resource_management.core.exceptions.Fail:
> StaticFile('/usr/hdp/current/hive-metastore/conf/conf.server/hive-site.jceks')
> Source file /usr/hdp/current/hive-metastore/conf/conf.server/hive-site.jceks
> is not found
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-20323: --- Attachment: AMBARI-20323.5.patch > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch, > AMBARI-20323.4.patch, AMBARI-20323.5.patch, AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20372) RU: Oozie LR job failed
[
https://issues.apache.org/jira/browse/AMBARI-20372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-20372:
-
Status: Patch Available (was: In Progress)
> RU: Oozie LR job failed
> ---
>
> Key: AMBARI-20372
> URL: https://issues.apache.org/jira/browse/AMBARI-20372
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20372.patch
>
>
> {code}2017-03-06 06:37:37,166|INFO|MainThread|machine.py:152 -
> run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|001-170305223753594-oozie-oozi-C@249
>FAILED164-170306030147803-oozie-oozi-W - 2017-03-06 01:33
> GMT 2009-01-01 21:40 GMT
>
> 2017-03-06 06:37:37,260|INFO|MainThread|machine.py:177 -
> run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|Exit Code: 0
> 2017-03-06 06:37:37,261|INFO|MainThread|ruUpgrade.py:70 - reportProgress()|
> [FAILED][Oozie][test_oozie_long_running] job status: DONEWITHERROR
> {code}
> {code}
> [164-170306030147803-oozie-oozi-W@wc]. Failing this action!]
> org.apache.oozie.action.ActionExecutorException: JA017: Unknown hadoop job
> [job_1488762906035_0733] associated with action
> [164-170306030147803-oozie-oozi-W@wc]. Failing this action!
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.check(JavaActionExecutor.java:1488)
> at
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:182)
> at
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:56)
> at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 2017-03-06 05:30:52,958 WARN ActionCheckXCommand:523 - SERVER USER[hrt_qa]
> GROUP[-] TOKEN[-] APP[wordcount] JOB[164-170306030147803-oozie-oozi-W]
> ACTION[164-170306030147803-oozie-oozi-W@wc] Exception while executing
> check(). Error Code [JA017], Message[JA017: Unknown hadoop job
> [job_1488762906035_0733] associated with action
> [164-170306030147803-oozie-oozi-W@wc]. Failing this action!]
> org.apache.oozie.action.ActionExecutorException: JA017: Unknown hadoop job
> [job_1488762906035_0733] associated with action
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20372) RU: Oozie LR job failed
[
https://issues.apache.org/jira/browse/AMBARI-20372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-20372:
-
Attachment: AMBARI-20372.patch
> RU: Oozie LR job failed
> ---
>
> Key: AMBARI-20372
> URL: https://issues.apache.org/jira/browse/AMBARI-20372
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20372.patch
>
>
> {code}2017-03-06 06:37:37,166|INFO|MainThread|machine.py:152 -
> run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|001-170305223753594-oozie-oozi-C@249
>FAILED164-170306030147803-oozie-oozi-W - 2017-03-06 01:33
> GMT 2009-01-01 21:40 GMT
>
> 2017-03-06 06:37:37,260|INFO|MainThread|machine.py:177 -
> run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|Exit Code: 0
> 2017-03-06 06:37:37,261|INFO|MainThread|ruUpgrade.py:70 - reportProgress()|
> [FAILED][Oozie][test_oozie_long_running] job status: DONEWITHERROR
> {code}
> {code}
> [164-170306030147803-oozie-oozi-W@wc]. Failing this action!]
> org.apache.oozie.action.ActionExecutorException: JA017: Unknown hadoop job
> [job_1488762906035_0733] associated with action
> [164-170306030147803-oozie-oozi-W@wc]. Failing this action!
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.check(JavaActionExecutor.java:1488)
> at
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:182)
> at
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:56)
> at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 2017-03-06 05:30:52,958 WARN ActionCheckXCommand:523 - SERVER USER[hrt_qa]
> GROUP[-] TOKEN[-] APP[wordcount] JOB[164-170306030147803-oozie-oozi-W]
> ACTION[164-170306030147803-oozie-oozi-W@wc] Exception while executing
> check(). Error Code [JA017], Message[JA017: Unknown hadoop job
> [job_1488762906035_0733] associated with action
> [164-170306030147803-oozie-oozi-W@wc]. Failing this action!]
> org.apache.oozie.action.ActionExecutorException: JA017: Unknown hadoop job
> [job_1488762906035_0733] associated with action
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20377) Usability: Hostname hover of master is not discoverable in Summary section
[ https://issues.apache.org/jira/browse/AMBARI-20377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-20377: - Status: Patch Available (was: Open) > Usability: Hostname hover of master is not discoverable in Summary section > -- > > Key: AMBARI-20377 > URL: https://issues.apache.org/jira/browse/AMBARI-20377 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-20377.patch > > > Currently, if you hover over a master component in Services > Summary, you > can see the hostname (for example, hover over NameNode). > The current hover takes a while to show, and is more of a title/alt hover vs. > a tooltip (for example, like hover on the Service status icons). Should > switch from title/alt hover to tooltip hover like Service status icons. It > shows faster and looks better. This will make hostname more discoverable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20377) Usability: Hostname hover of master is not discoverable in Summary section
[ https://issues.apache.org/jira/browse/AMBARI-20377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-20377: - Attachment: AMBARI-20377.patch > Usability: Hostname hover of master is not discoverable in Summary section > -- > > Key: AMBARI-20377 > URL: https://issues.apache.org/jira/browse/AMBARI-20377 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-20377.patch > > > Currently, if you hover over a master component in Services > Summary, you > can see the hostname (for example, hover over NameNode). > The current hover takes a while to show, and is more of a title/alt hover vs. > a tooltip (for example, like hover on the Service status icons). Should > switch from title/alt hover to tooltip hover like Service status icons. It > shows faster and looks better. This will make hostname more discoverable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20373) Complete button after move masters is grayed out even after move has completed
[
https://issues.apache.org/jira/browse/AMBARI-20373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903004#comment-15903004
]
Hadoop QA commented on AMBARI-20373:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856977/AMBARI-20373.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10938//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10938//console
This message is automatically generated.
> Complete button after move masters is grayed out even after move has completed
> --
>
> Key: AMBARI-20373
> URL: https://issues.apache.org/jira/browse/AMBARI-20373
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20373_branch-2.5.patch, AMBARI-20373.patch
>
>
> STR :
> Move namenode from host1 to host2.
> Complete the move. The complete button is grayed out and can't be clicked.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20377) Usability: Hostname hover of master is not discoverable in Summary section
Antonenko Alexander created AMBARI-20377: Summary: Usability: Hostname hover of master is not discoverable in Summary section Key: AMBARI-20377 URL: https://issues.apache.org/jira/browse/AMBARI-20377 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Fix For: 3.0.0 Currently, if you hover over a master component in Services > Summary, you can see the hostname (for example, hover over NameNode). The current hover takes a while to show, and is more of a title/alt hover vs. a tooltip (for example, like hover on the Service status icons). Should switch from title/alt hover to tooltip hover like Service status icons. It shows faster and looks better. This will make hostname more discoverable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20376) While Moving Namenode via Move Master wizard, datanodes reported as down
[
https://issues.apache.org/jira/browse/AMBARI-20376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902987#comment-15902987
]
Oleg Nechiporenko commented on AMBARI-20376:
+1 for patch
> While Moving Namenode via Move Master wizard, datanodes reported as down
>
>
> Key: AMBARI-20376
> URL: https://issues.apache.org/jira/browse/AMBARI-20376
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20376.patch
>
>
> While Moving Namenode via Move Master wizard, datanodes reported as down
> while starting ATS.
> Seeing this in a couple of splits today. ATS fails to start showing there are
> no live datanodes
> {code}
> {
> "RemoteException": {
> "exception": "RetriableException",
> "javaClassName": "org.apache.hadoop.ipc.RetriableException",
> "message": "org.apache.hadoop.hdfs.server.namenode.SafeModeException:
> Cannot set permission for /ats/done. Name node is in safe mode.\nThe reported
> blocks 934 has reached the threshold 0.9900 of total blocks 934. The number
> of live datanodes 3 has reached the minimum number 0. In safe mode extension.
> Safe mode will be turned off automatically in 21 seconds."
> }
> }
> {code}
> The step before ATS start, starts datanode explicitly. On retry ATS will
> possibly come up. But no retries were needed before
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20376) While Moving Namenode via Move Master wizard, datanodes reported as down
[
https://issues.apache.org/jira/browse/AMBARI-20376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-20376:
-
Attachment: AMBARI-20376.patch
> While Moving Namenode via Move Master wizard, datanodes reported as down
>
>
> Key: AMBARI-20376
> URL: https://issues.apache.org/jira/browse/AMBARI-20376
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20376.patch
>
>
> While Moving Namenode via Move Master wizard, datanodes reported as down
> while starting ATS.
> Seeing this in a couple of splits today. ATS fails to start showing there are
> no live datanodes
> {code}
> {
> "RemoteException": {
> "exception": "RetriableException",
> "javaClassName": "org.apache.hadoop.ipc.RetriableException",
> "message": "org.apache.hadoop.hdfs.server.namenode.SafeModeException:
> Cannot set permission for /ats/done. Name node is in safe mode.\nThe reported
> blocks 934 has reached the threshold 0.9900 of total blocks 934. The number
> of live datanodes 3 has reached the minimum number 0. In safe mode extension.
> Safe mode will be turned off automatically in 21 seconds."
> }
> }
> {code}
> The step before ATS start, starts datanode explicitly. On retry ATS will
> possibly come up. But no retries were needed before
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20376) While Moving Namenode via Move Master wizard, datanodes reported as down
[
https://issues.apache.org/jira/browse/AMBARI-20376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-20376:
-
Status: Patch Available (was: Open)
> While Moving Namenode via Move Master wizard, datanodes reported as down
>
>
> Key: AMBARI-20376
> URL: https://issues.apache.org/jira/browse/AMBARI-20376
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20376.patch
>
>
> While Moving Namenode via Move Master wizard, datanodes reported as down
> while starting ATS.
> Seeing this in a couple of splits today. ATS fails to start showing there are
> no live datanodes
> {code}
> {
> "RemoteException": {
> "exception": "RetriableException",
> "javaClassName": "org.apache.hadoop.ipc.RetriableException",
> "message": "org.apache.hadoop.hdfs.server.namenode.SafeModeException:
> Cannot set permission for /ats/done. Name node is in safe mode.\nThe reported
> blocks 934 has reached the threshold 0.9900 of total blocks 934. The number
> of live datanodes 3 has reached the minimum number 0. In safe mode extension.
> Safe mode will be turned off automatically in 21 seconds."
> }
> }
> {code}
> The step before ATS start, starts datanode explicitly. On retry ATS will
> possibly come up. But no retries were needed before
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20376) While Moving Namenode via Move Master wizard, datanodes reported as down
Antonenko Alexander created AMBARI-20376:
Summary: While Moving Namenode via Move Master wizard, datanodes
reported as down
Key: AMBARI-20376
URL: https://issues.apache.org/jira/browse/AMBARI-20376
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.5.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
Priority: Critical
Fix For: 2.5.0
While Moving Namenode via Move Master wizard, datanodes reported as down while
starting ATS.
Seeing this in a couple of splits today. ATS fails to start showing there are
no live datanodes
{code}
{
"RemoteException": {
"exception": "RetriableException",
"javaClassName": "org.apache.hadoop.ipc.RetriableException",
"message": "org.apache.hadoop.hdfs.server.namenode.SafeModeException:
Cannot set permission for /ats/done. Name node is in safe mode.\nThe reported
blocks 934 has reached the threshold 0.9900 of total blocks 934. The number of
live datanodes 3 has reached the minimum number 0. In safe mode extension. Safe
mode will be turned off automatically in 21 seconds."
}
}
{code}
The step before ATS start, starts datanode explicitly. On retry ATS will
possibly come up. But no retries were needed before
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20375) Remove duplicate code from wizard menu
[
https://issues.apache.org/jira/browse/AMBARI-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20375:
---
Status: Patch Available (was: Open)
+1 by [~BuzhorDenys] on the review board
> Remove duplicate code from wizard menu
> --
>
> Key: AMBARI-20375
> URL: https://issues.apache.org/jira/browse/AMBARI-20375
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20375.patch
>
>
> {{'isStep..Disabled'}} and {{'isStep..Completed'}} may be rewritten as
> computed macros
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19835) HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, quicklinks, and themes
[
https://issues.apache.org/jira/browse/AMBARI-19835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902956#comment-15902956
]
Hadoop QA commented on AMBARI-19835:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856978/AMBARI-19835_3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10937//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10937//console
This message is automatically generated.
> HDP 3.0 support for Slider with configs, kerberos, widgets, metrics,
> quicklinks, and themes
> ---
>
> Key: AMBARI-19835
> URL: https://issues.apache.org/jira/browse/AMBARI-19835
> Project: Ambari
> Issue Type: Story
> Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Dmytro Sen
> Fix For: 3.0.0
>
> Attachments: AMBARI-19835_2.patch, AMBARI-19835_3.patch
>
>
> HDP 3.0 support for Slider with configs, kerberos, widgets, metrics,
> quicklinks, and themes
> Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0
> In HDP 3.0, we have created a new stack definition that does not inherit from
> other stacks, in order to reduce the complexity of having to analyze older
> stacks.
> This means that we need to create a service definition (metainfo.xml,
> configs, kerberos, widgets, metrics, quicklinks, and themes) that is
> equivalent to what is inherit and deleted from all of the previous stacks.
> A merge needs to account for additions, overrides, and deletions.
> metainfo.xml and configs perform a merge of older versions
> kerberos.json always seems to override the previous file
> Because the bits for this service may not yet be available in the HDP 3.0
> repo,
> the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/SLIDER
> (which uses inheritance) is equivalent to the flattening of
> /api/v1/stacks/HDP/versions/3.0/services/SLIDER .
> Please take a look at how this was done for ZK, HDFS, and YARN/MR.
> This means that you will not be able to actually install the service for now,
> but can still perform validation during the Install Wizard that the correct
> components and configs show up.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20278) Install Wizard > Select Services: Ambari warns me that "Ambari Infra is not selected" but it is selected
[ https://issues.apache.org/jira/browse/AMBARI-20278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-20278: - Fix Version/s: (was: 2.5.0) trunk > Install Wizard > Select Services: Ambari warns me that "Ambari Infra is not > selected" but it is selected > > > Key: AMBARI-20278 > URL: https://issues.apache.org/jira/browse/AMBARI-20278 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-20278_additional_trunk_fix.patch, > AMBARI-20278.patch, Screen Shot 2017-02-27 at 1.43.56 PM.png > > > See attached. > Most likely, I didn't select Ambari Infra originally, but then I cancelled > out of the series of warning popups. > Then I selected Ambari Infra. The warning does not go away. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20375) Remove duplicate code from wizard menu
[
https://issues.apache.org/jira/browse/AMBARI-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20375:
---
Attachment: AMBARI-20375.patch
> Remove duplicate code from wizard menu
> --
>
> Key: AMBARI-20375
> URL: https://issues.apache.org/jira/browse/AMBARI-20375
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20375.patch
>
>
> {{'isStep..Disabled'}} and {{'isStep..Completed'}} may be rewritten as
> computed macros
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20375) Remove duplicate code from wizard menu
Oleg Nechiporenko created AMBARI-20375:
--
Summary: Remove duplicate code from wizard menu
Key: AMBARI-20375
URL: https://issues.apache.org/jira/browse/AMBARI-20375
Project: Ambari
Issue Type: Task
Components: ambari-web
Affects Versions: 3.0.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Fix For: 3.0.0
{{'isStep..Disabled'}} and {{'isStep..Completed'}} may be rewritten as computed
macros
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20371) WFM: Delete option in Manage recent list.
[ https://issues.apache.org/jira/browse/AMBARI-20371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-20371: Attachment: AMBARI-20371_branch-2.5.patch > WFM: Delete option in Manage recent list. > - > > Key: AMBARI-20371 > URL: https://issues.apache.org/jira/browse/AMBARI-20371 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20371_branch-2.5.patch > > > Provide option to delete workflows in Manage recent list. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20371) WFM: Delete option in Manage recent list.
[ https://issues.apache.org/jira/browse/AMBARI-20371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-20371: Status: Patch Available (was: In Progress) > WFM: Delete option in Manage recent list. > - > > Key: AMBARI-20371 > URL: https://issues.apache.org/jira/browse/AMBARI-20371 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20371_branch-2.5.patch > > > Provide option to delete workflows in Manage recent list. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20374) Ambari stops showing Config page for HIVE
Szymon Czekajewski created AMBARI-20374:
---
Summary: Ambari stops showing Config page for HIVE
Key: AMBARI-20374
URL: https://issues.apache.org/jira/browse/AMBARI-20374
Project: Ambari
Issue Type: Improvement
Components: ambari-web
Reporter: Szymon Czekajewski
Priority: Trivial
Hi,
If you try to configure HIVE with Ambari to use repilicated MySQL as Metastore
backend, you'll try to enter database URL like:
jdbc:mysql:loadbalance://cent4/hive,cent5/hive?createDatabaseIfNotExist=true
Then Ambari will stop loading the "Config" screen, due to JavaScript error.
To fix this add this (or something similar):
mssql:
'jdbc:mysql:loadbalance://(({0}/{1})(,?))+?createDatabaseIfNotExist=true',
to app/utils/configs/database.js in line 65.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19835) HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19835: Status: Patch Available (was: Open) > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > --- > > Key: AMBARI-19835 > URL: https://issues.apache.org/jira/browse/AMBARI-19835 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 3.0.0 > > Attachments: AMBARI-19835_2.patch, AMBARI-19835_3.patch > > > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0 > In HDP 3.0, we have created a new stack definition that does not inherit from > other stacks, in order to reduce the complexity of having to analyze older > stacks. > This means that we need to create a service definition (metainfo.xml, > configs, kerberos, widgets, metrics, quicklinks, and themes) that is > equivalent to what is inherit and deleted from all of the previous stacks. > A merge needs to account for additions, overrides, and deletions. > metainfo.xml and configs perform a merge of older versions > kerberos.json always seems to override the previous file > Because the bits for this service may not yet be available in the HDP 3.0 > repo, > the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/SLIDER > (which uses inheritance) is equivalent to the flattening of > /api/v1/stacks/HDP/versions/3.0/services/SLIDER . > Please take a look at how this was done for ZK, HDFS, and YARN/MR. > This means that you will not be able to actually install the service for now, > but can still perform validation during the Install Wizard that the correct > components and configs show up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19835) HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19835: Attachment: AMBARI-19835_3.patch > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > --- > > Key: AMBARI-19835 > URL: https://issues.apache.org/jira/browse/AMBARI-19835 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 3.0.0 > > Attachments: AMBARI-19835_2.patch, AMBARI-19835_3.patch > > > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0 > In HDP 3.0, we have created a new stack definition that does not inherit from > other stacks, in order to reduce the complexity of having to analyze older > stacks. > This means that we need to create a service definition (metainfo.xml, > configs, kerberos, widgets, metrics, quicklinks, and themes) that is > equivalent to what is inherit and deleted from all of the previous stacks. > A merge needs to account for additions, overrides, and deletions. > metainfo.xml and configs perform a merge of older versions > kerberos.json always seems to override the previous file > Because the bits for this service may not yet be available in the HDP 3.0 > repo, > the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/SLIDER > (which uses inheritance) is equivalent to the flattening of > /api/v1/stacks/HDP/versions/3.0/services/SLIDER . > Please take a look at how this was done for ZK, HDFS, and YARN/MR. > This means that you will not be able to actually install the service for now, > but can still perform validation during the Install Wizard that the correct > components and configs show up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19835) HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19835: Status: Open (was: Patch Available) > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > --- > > Key: AMBARI-19835 > URL: https://issues.apache.org/jira/browse/AMBARI-19835 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 3.0.0 > > Attachments: AMBARI-19835_2.patch > > > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0 > In HDP 3.0, we have created a new stack definition that does not inherit from > other stacks, in order to reduce the complexity of having to analyze older > stacks. > This means that we need to create a service definition (metainfo.xml, > configs, kerberos, widgets, metrics, quicklinks, and themes) that is > equivalent to what is inherit and deleted from all of the previous stacks. > A merge needs to account for additions, overrides, and deletions. > metainfo.xml and configs perform a merge of older versions > kerberos.json always seems to override the previous file > Because the bits for this service may not yet be available in the HDP 3.0 > repo, > the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/SLIDER > (which uses inheritance) is equivalent to the flattening of > /api/v1/stacks/HDP/versions/3.0/services/SLIDER . > Please take a look at how this was done for ZK, HDFS, and YARN/MR. > This means that you will not be able to actually install the service for now, > but can still perform validation during the Install Wizard that the correct > components and configs show up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20373) Complete button after move masters is grayed out even after move has completed
[ https://issues.apache.org/jira/browse/AMBARI-20373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20373: - Status: Patch Available (was: Open) > Complete button after move masters is grayed out even after move has completed > -- > > Key: AMBARI-20373 > URL: https://issues.apache.org/jira/browse/AMBARI-20373 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20373_branch-2.5.patch, AMBARI-20373.patch > > > STR : > Move namenode from host1 to host2. > Complete the move. The complete button is grayed out and can't be clicked. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20373) Complete button after move masters is grayed out even after move has completed
[ https://issues.apache.org/jira/browse/AMBARI-20373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20373: - Attachment: AMBARI-20373.patch > Complete button after move masters is grayed out even after move has completed > -- > > Key: AMBARI-20373 > URL: https://issues.apache.org/jira/browse/AMBARI-20373 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20373_branch-2.5.patch, AMBARI-20373.patch > > > STR : > Move namenode from host1 to host2. > Complete the move. The complete button is grayed out and can't be clicked. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20373) Complete button after move masters is grayed out even after move has completed
[ https://issues.apache.org/jira/browse/AMBARI-20373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20373: - Attachment: AMBARI-20373_branch-2.5.patch > Complete button after move masters is grayed out even after move has completed > -- > > Key: AMBARI-20373 > URL: https://issues.apache.org/jira/browse/AMBARI-20373 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20373_branch-2.5.patch > > > STR : > Move namenode from host1 to host2. > Complete the move. The complete button is grayed out and can't be clicked. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20373) Complete button after move masters is grayed out even after move has completed
Aleksandr Kovalenko created AMBARI-20373: Summary: Complete button after move masters is grayed out even after move has completed Key: AMBARI-20373 URL: https://issues.apache.org/jira/browse/AMBARI-20373 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 2.5.0 STR : Move namenode from host1 to host2. Complete the move. The complete button is grayed out and can't be clicked. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20372) RU: Oozie LR job failed
[
https://issues.apache.org/jira/browse/AMBARI-20372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-20372:
-
Description:
{code}2017-03-06 06:37:37,166|INFO|MainThread|machine.py:152 -
run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|001-170305223753594-oozie-oozi-C@249
FAILED164-170306030147803-oozie-oozi-W - 2017-03-06 01:33
GMT 2009-01-01 21:40 GMT
2017-03-06 06:37:37,260|INFO|MainThread|machine.py:177 -
run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|Exit Code: 0
2017-03-06 06:37:37,261|INFO|MainThread|ruUpgrade.py:70 - reportProgress()|
[FAILED][Oozie][test_oozie_long_running] job status: DONEWITHERROR
{code}
{code}
[164-170306030147803-oozie-oozi-W@wc]. Failing this action!]
org.apache.oozie.action.ActionExecutorException: JA017: Unknown hadoop job
[job_1488762906035_0733] associated with action
[164-170306030147803-oozie-oozi-W@wc]. Failing this action!
at
org.apache.oozie.action.hadoop.JavaActionExecutor.check(JavaActionExecutor.java:1488)
at
org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:182)
at
org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:56)
at org.apache.oozie.command.XCommand.call(XCommand.java:287)
at
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
at
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
2017-03-06 05:30:52,958 WARN ActionCheckXCommand:523 - SERVER USER[hrt_qa]
GROUP[-] TOKEN[-] APP[wordcount] JOB[164-170306030147803-oozie-oozi-W]
ACTION[164-170306030147803-oozie-oozi-W@wc] Exception while executing
check(). Error Code [JA017], Message[JA017: Unknown hadoop job
[job_1488762906035_0733] associated with action
[164-170306030147803-oozie-oozi-W@wc]. Failing this action!]
org.apache.oozie.action.ActionExecutorException: JA017: Unknown hadoop job
[job_1488762906035_0733] associated with action
{code}
was:
{code}2017-03-06 06:37:37,166|INFO|MainThread|machine.py:152 -
run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|001-170305223753594-oozie-oozi-C@249
FAILED164-170306030147803-oozie-oozi-W - 2017-03-06 01:33
GMT 2009-01-01 21:40 GMT
2017-03-06 06:37:37,260|INFO|MainThread|machine.py:177 -
run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|Exit Code: 0
2017-03-06 06:37:37,261|INFO|MainThread|ruUpgrade.py:70 - reportProgress()|
[FAILED][Oozie][test_oozie_long_running] job status: DONEWITHERROR
{code}
{code}
[164-170306030147803-oozie-oozi-W@wc]. Failing this action!]
org.apache.oozie.action.ActionExecutorException: JA017: Unknown hadoop job
[job_1488762906035_0733] associated with action
[164-170306030147803-oozie-oozi-W@wc]. Failing this action!
at
org.apache.oozie.action.hadoop.JavaActionExecutor.check(JavaActionExecutor.java:1488)
at
org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:182)
at
org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:56)
at org.apache.oozie.command.XCommand.call(XCommand.java:287)
at
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
at
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
2017-03-06 05:30:52,958 WARN ActionCheckXCommand:523 -
SERVER[natr76-uods-dgm20tofnsecha-r7-11.openstacklocal] USER[hrt_qa] GROUP[-]
TOKEN[-] APP[wordcount] JOB[164-170306030147803-oozie-oozi-W]
ACTION[164-170306030147803-oozie-oozi-W@wc] Exception while executing
check(). Error Code [JA017], Message[JA017: Unknown hadoop job
[job_1488762906035_0733] associated with action
[164-170306030147803-oozie-oozi-W@wc]. Failing this action!]
org.apache.oozie.action.ActionExecutorException: JA017: Unknown hadoop job
[job_1488762906035_0733] associated with action
{code}
> RU: Oozie LR job failed
>
[jira] [Created] (AMBARI-20372) RU: Oozie LR job failed
Dmytro Grinenko created AMBARI-20372:
Summary: RU: Oozie LR job failed
Key: AMBARI-20372
URL: https://issues.apache.org/jira/browse/AMBARI-20372
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk, 2.5.0
Reporter: Dmytro Grinenko
Assignee: Dmytro Grinenko
Priority: Critical
Fix For: trunk, 2.5.0
{code}2017-03-06 06:37:37,166|INFO|MainThread|machine.py:152 -
run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|001-170305223753594-oozie-oozi-C@249
FAILED164-170306030147803-oozie-oozi-W - 2017-03-06 01:33
GMT 2009-01-01 21:40 GMT
2017-03-06 06:37:37,260|INFO|MainThread|machine.py:177 -
run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|Exit Code: 0
2017-03-06 06:37:37,261|INFO|MainThread|ruUpgrade.py:70 - reportProgress()|
[FAILED][Oozie][test_oozie_long_running] job status: DONEWITHERROR
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20372) RU: Oozie LR job failed
[
https://issues.apache.org/jira/browse/AMBARI-20372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-20372:
-
Description:
{code}2017-03-06 06:37:37,166|INFO|MainThread|machine.py:152 -
run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|001-170305223753594-oozie-oozi-C@249
FAILED164-170306030147803-oozie-oozi-W - 2017-03-06 01:33
GMT 2009-01-01 21:40 GMT
2017-03-06 06:37:37,260|INFO|MainThread|machine.py:177 -
run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|Exit Code: 0
2017-03-06 06:37:37,261|INFO|MainThread|ruUpgrade.py:70 - reportProgress()|
[FAILED][Oozie][test_oozie_long_running] job status: DONEWITHERROR
{code}
{code}
[164-170306030147803-oozie-oozi-W@wc]. Failing this action!]
org.apache.oozie.action.ActionExecutorException: JA017: Unknown hadoop job
[job_1488762906035_0733] associated with action
[164-170306030147803-oozie-oozi-W@wc]. Failing this action!
at
org.apache.oozie.action.hadoop.JavaActionExecutor.check(JavaActionExecutor.java:1488)
at
org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:182)
at
org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:56)
at org.apache.oozie.command.XCommand.call(XCommand.java:287)
at
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
at
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
2017-03-06 05:30:52,958 WARN ActionCheckXCommand:523 -
SERVER[natr76-uods-dgm20tofnsecha-r7-11.openstacklocal] USER[hrt_qa] GROUP[-]
TOKEN[-] APP[wordcount] JOB[164-170306030147803-oozie-oozi-W]
ACTION[164-170306030147803-oozie-oozi-W@wc] Exception while executing
check(). Error Code [JA017], Message[JA017: Unknown hadoop job
[job_1488762906035_0733] associated with action
[164-170306030147803-oozie-oozi-W@wc]. Failing this action!]
org.apache.oozie.action.ActionExecutorException: JA017: Unknown hadoop job
[job_1488762906035_0733] associated with action
{code}
was:
{code}2017-03-06 06:37:37,166|INFO|MainThread|machine.py:152 -
run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|001-170305223753594-oozie-oozi-C@249
FAILED164-170306030147803-oozie-oozi-W - 2017-03-06 01:33
GMT 2009-01-01 21:40 GMT
2017-03-06 06:37:37,260|INFO|MainThread|machine.py:177 -
run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|Exit Code: 0
2017-03-06 06:37:37,261|INFO|MainThread|ruUpgrade.py:70 - reportProgress()|
[FAILED][Oozie][test_oozie_long_running] job status: DONEWITHERROR
{code}
> RU: Oozie LR job failed
> ---
>
> Key: AMBARI-20372
> URL: https://issues.apache.org/jira/browse/AMBARI-20372
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
>
> {code}2017-03-06 06:37:37,166|INFO|MainThread|machine.py:152 -
> run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|001-170305223753594-oozie-oozi-C@249
>FAILED164-170306030147803-oozie-oozi-W - 2017-03-06 01:33
> GMT 2009-01-01 21:40 GMT
>
> 2017-03-06 06:37:37,260|INFO|MainThread|machine.py:177 -
> run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|Exit Code: 0
> 2017-03-06 06:37:37,261|INFO|MainThread|ruUpgrade.py:70 - reportProgress()|
> [FAILED][Oozie][test_oozie_long_running] job status: DONEWITHERROR
> {code}
> {code}
> [164-170306030147803-oozie-oozi-W@wc]. Failing this action!]
> org.apache.oozie.action.ActionExecutorException: JA017: Unknown hadoop job
> [job_1488762906035_0733] associated with action
> [164-170306030147803-oozie-oozi-W@wc]. Failing this action!
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.check(JavaActionExecutor.java:1488)
> at
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:182)
> at
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:56)
> at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> at
>
[jira] [Commented] (AMBARI-20367) Update Zeppelin version on Ambari-2.5 from 0.6.2 to 0.7.0
[
https://issues.apache.org/jira/browse/AMBARI-20367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902832#comment-15902832
]
Hadoop QA commented on AMBARI-20367:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856948/AMBARI-20367_branch-2.5_v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10934//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10934//console
This message is automatically generated.
> Update Zeppelin version on Ambari-2.5 from 0.6.2 to 0.7.0
> -
>
> Key: AMBARI-20367
> URL: https://issues.apache.org/jira/browse/AMBARI-20367
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Prabhjyot Singh
>Assignee: Prabhjyot Singh
> Attachments: AMBARI-20367_branch-2.5_v1.patch
>
>
> Update Zeppelin version on Ambari-2.5 from 0.6.2 to 0.7.0
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20370) Fix up tez view version
[ https://issues.apache.org/jira/browse/AMBARI-20370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20370: --- Attachment: AMBARI-20370_branch-2.5.patch > Fix up tez view version > --- > > Key: AMBARI-20370 > URL: https://issues.apache.org/jira/browse/AMBARI-20370 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-20370_branch-2.5.patch > > > Currently tez view version uses version and build in url. Because of this > everytime tez view is changed the value of tez.tez-ui.history-url.base needs > to be changed in tez-site. > This url should no be fixed to auto tez view instance's short url. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20370) Fix up tez view version
[ https://issues.apache.org/jira/browse/AMBARI-20370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20370: --- Status: Patch Available (was: Open) tez view version and build removed and short url of auto instance used for property tez.tez-ui.history-url.base in tez-site Removed change of tez version from AbstractUpgradeCatalog. UpgardeCatalog250 now contains code to change the previous value of tez.tez-ui.history-url.base to http://HOST:PORT/#/main/view/TEZ/tez_cluster_instance changed stack_advisor.py in 2.2 and 2.3 for this change to reflect during installation > Fix up tez view version > --- > > Key: AMBARI-20370 > URL: https://issues.apache.org/jira/browse/AMBARI-20370 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > > Currently tez view version uses version and build in url. Because of this > everytime tez view is changed the value of tez.tez-ui.history-url.base needs > to be changed in tez-site. > This url should no be fixed to auto tez view instance's short url. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20371) WFM: Delete option in Manage recent list.
venkat created AMBARI-20371: --- Summary: WFM: Delete option in Manage recent list. Key: AMBARI-20371 URL: https://issues.apache.org/jira/browse/AMBARI-20371 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: venkat Assignee: venkat Fix For: 2.5.0 Provide option to delete workflows in Manage recent list. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20369) Need hdfs-site for saving ranger audits to hdfs in namenode HA env
[
https://issues.apache.org/jira/browse/AMBARI-20369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-20369:
-
Labels: Ambari (was: )
> Need hdfs-site for saving ranger audits to hdfs in namenode HA env
> --
>
> Key: AMBARI-20369
> URL: https://issues.apache.org/jira/browse/AMBARI-20369
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Labels: Ambari
> Fix For: 2.5.0
>
> Attachments: AMBARI-20369.patch
>
>
> For {{KNOX}} and {{RANGER_KMS}} services which supports ranger plugin, need
> to have hdfs-site.xml available in respective services conf directory for
> saving ranger audits to hdfs in namenode HA env.
> Below error logs are found, if hdfs-site.xml is not available,
> {noformat}
> 2017-03-01 18:48:50,150 ERROR provider.BaseAuditHandler
> (BaseAuditHandler.java:logError(327)) - Error writing to log file.
> java.lang.IllegalArgumentException: java.net.UnknownHostException: mycluster
> at
> org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:438)
> at
> org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:311)
> at
> org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
> at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:690)
> at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:631)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:160)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.getLogFileStream(HDFSAuditDestination.java:271)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.access$000(HDFSAuditDestination.java:43)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:157)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:154)
> 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:1866)
> at
> org.apache.ranger.audit.provider.MiscUtil.executePrivilegedAction(MiscUtil.java:523)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.logJSON(HDFSAuditDestination.java:154)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.sendEvent(AuditFileSpool.java:880)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.runLogAudit(AuditFileSpool.java:828)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.run(AuditFileSpool.java:758)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.UnknownHostException: mycluster
> ... 24 more
> 2017-03-01 18:48:50,151 ERROR queue.AuditFileSpool
> (AuditFileSpool.java:logError(710)) - Error sending logs to consumer.
> provider=knox.async.multi_dest.batch,
> consumer=knox.async.multi_dest.batch.hdfs{{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20369) Need hdfs-site for saving ranger audits to hdfs in namenode HA env
[
https://issues.apache.org/jira/browse/AMBARI-20369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-20369:
-
Status: Patch Available (was: In Progress)
> Need hdfs-site for saving ranger audits to hdfs in namenode HA env
> --
>
> Key: AMBARI-20369
> URL: https://issues.apache.org/jira/browse/AMBARI-20369
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
> Attachments: AMBARI-20369.patch
>
>
> For {{KNOX}} and {{RANGER_KMS}} services which supports ranger plugin, need
> to have hdfs-site.xml available in respective services conf directory for
> saving ranger audits to hdfs in namenode HA env.
> Below error logs are found, if hdfs-site.xml is not available,
> {noformat}
> 2017-03-01 18:48:50,150 ERROR provider.BaseAuditHandler
> (BaseAuditHandler.java:logError(327)) - Error writing to log file.
> java.lang.IllegalArgumentException: java.net.UnknownHostException: mycluster
> at
> org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:438)
> at
> org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:311)
> at
> org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
> at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:690)
> at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:631)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:160)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.getLogFileStream(HDFSAuditDestination.java:271)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.access$000(HDFSAuditDestination.java:43)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:157)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:154)
> 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:1866)
> at
> org.apache.ranger.audit.provider.MiscUtil.executePrivilegedAction(MiscUtil.java:523)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.logJSON(HDFSAuditDestination.java:154)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.sendEvent(AuditFileSpool.java:880)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.runLogAudit(AuditFileSpool.java:828)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.run(AuditFileSpool.java:758)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.UnknownHostException: mycluster
> ... 24 more
> 2017-03-01 18:48:50,151 ERROR queue.AuditFileSpool
> (AuditFileSpool.java:logError(710)) - Error sending logs to consumer.
> provider=knox.async.multi_dest.batch,
> consumer=knox.async.multi_dest.batch.hdfs{{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20369) Need hdfs-site for saving ranger audits to hdfs in namenode HA env
[
https://issues.apache.org/jira/browse/AMBARI-20369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-20369:
-
Attachment: AMBARI-20369.patch
> Need hdfs-site for saving ranger audits to hdfs in namenode HA env
> --
>
> Key: AMBARI-20369
> URL: https://issues.apache.org/jira/browse/AMBARI-20369
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
> Attachments: AMBARI-20369.patch
>
>
> For {{KNOX}} and {{RANGER_KMS}} services which supports ranger plugin, need
> to have hdfs-site.xml available in respective services conf directory for
> saving ranger audits to hdfs in namenode HA env.
> Below error logs are found, if hdfs-site.xml is not available,
> {noformat}
> 2017-03-01 18:48:50,150 ERROR provider.BaseAuditHandler
> (BaseAuditHandler.java:logError(327)) - Error writing to log file.
> java.lang.IllegalArgumentException: java.net.UnknownHostException: mycluster
> at
> org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:438)
> at
> org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:311)
> at
> org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
> at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:690)
> at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:631)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:160)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.getLogFileStream(HDFSAuditDestination.java:271)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.access$000(HDFSAuditDestination.java:43)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:157)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:154)
> 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:1866)
> at
> org.apache.ranger.audit.provider.MiscUtil.executePrivilegedAction(MiscUtil.java:523)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.logJSON(HDFSAuditDestination.java:154)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.sendEvent(AuditFileSpool.java:880)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.runLogAudit(AuditFileSpool.java:828)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.run(AuditFileSpool.java:758)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.UnknownHostException: mycluster
> ... 24 more
> 2017-03-01 18:48:50,151 ERROR queue.AuditFileSpool
> (AuditFileSpool.java:logError(710)) - Error sending logs to consumer.
> provider=knox.async.multi_dest.batch,
> consumer=knox.async.multi_dest.batch.hdfs{{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20369) Need hdfs-site for saving ranger audits to hdfs in namenode HA env
[
https://issues.apache.org/jira/browse/AMBARI-20369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-20369:
-
Description:
For {{KNOX}} and {{RANGER_KMS}} services which supports ranger plugin, need to
have hdfs-site.xml available in respective services conf directory for saving
ranger audits to hdfs in namenode HA env.
Below error logs are found, if hdfs-site.xml is not available,
{noformat}
2017-03-01 18:48:50,150 ERROR provider.BaseAuditHandler
(BaseAuditHandler.java:logError(327)) - Error writing to log file.
java.lang.IllegalArgumentException: java.net.UnknownHostException: mycluster
at
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:438)
at
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:311)
at
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:690)
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:631)
at
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:160)
at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99)
at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390)
at
org.apache.ranger.audit.destination.HDFSAuditDestination.getLogFileStream(HDFSAuditDestination.java:271)
at
org.apache.ranger.audit.destination.HDFSAuditDestination.access$000(HDFSAuditDestination.java:43)
at
org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:157)
at
org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:154)
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:1866)
at
org.apache.ranger.audit.provider.MiscUtil.executePrivilegedAction(MiscUtil.java:523)
at
org.apache.ranger.audit.destination.HDFSAuditDestination.logJSON(HDFSAuditDestination.java:154)
at
org.apache.ranger.audit.queue.AuditFileSpool.sendEvent(AuditFileSpool.java:880)
at
org.apache.ranger.audit.queue.AuditFileSpool.runLogAudit(AuditFileSpool.java:828)
at
org.apache.ranger.audit.queue.AuditFileSpool.run(AuditFileSpool.java:758)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.UnknownHostException: mycluster
... 24 more
2017-03-01 18:48:50,151 ERROR queue.AuditFileSpool
(AuditFileSpool.java:logError(710)) - Error sending logs to consumer.
provider=knox.async.multi_dest.batch,
consumer=knox.async.multi_dest.batch.hdfs{{noformat}
was:
For {{KNOX}} and {{RANGER_KMS}} services which supports ranger plugin, need to
have hdfs-site.xml available in there conf directory for saving ranger audits
to hdfs in namenode HA env.
Below error logs are found, if hdfs-site.xml is not available,
{noformat}
2017-03-01 18:48:50,150 ERROR provider.BaseAuditHandler
(BaseAuditHandler.java:logError(327)) - Error writing to log file.
java.lang.IllegalArgumentException: java.net.UnknownHostException: mycluster
at
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:438)
at
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:311)
at
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:690)
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:631)
at
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:160)
at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99)
at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390)
at
org.apache.ranger.audit.destination.HDFSAuditDestination.getLogFileStream(HDFSAuditDestination.java:271)
at
org.apache.ranger.audit.destination.HDFSAuditDestination.access$000(HDFSAuditDestination.java:43)
at
org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:157)
at
org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:154)
at java.security.AccessController.doPrivileged(Native Method)
at
[jira] [Updated] (AMBARI-20369) Need hdfs-site for saving ranger audits to hdfs in namenode HA env
[
https://issues.apache.org/jira/browse/AMBARI-20369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-20369:
-
Description:
For {{KNOX}} and {{RANGER_KMS}} services which supports ranger plugin, need to
have hdfs-site.xml available in there conf directory for saving ranger audits
to hdfs in namenode HA env.
Below error logs are found, if hdfs-site.xml is not available,
{noformat}
2017-03-01 18:48:50,150 ERROR provider.BaseAuditHandler
(BaseAuditHandler.java:logError(327)) - Error writing to log file.
java.lang.IllegalArgumentException: java.net.UnknownHostException: mycluster
at
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:438)
at
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:311)
at
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:690)
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:631)
at
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:160)
at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99)
at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390)
at
org.apache.ranger.audit.destination.HDFSAuditDestination.getLogFileStream(HDFSAuditDestination.java:271)
at
org.apache.ranger.audit.destination.HDFSAuditDestination.access$000(HDFSAuditDestination.java:43)
at
org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:157)
at
org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:154)
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:1866)
at
org.apache.ranger.audit.provider.MiscUtil.executePrivilegedAction(MiscUtil.java:523)
at
org.apache.ranger.audit.destination.HDFSAuditDestination.logJSON(HDFSAuditDestination.java:154)
at
org.apache.ranger.audit.queue.AuditFileSpool.sendEvent(AuditFileSpool.java:880)
at
org.apache.ranger.audit.queue.AuditFileSpool.runLogAudit(AuditFileSpool.java:828)
at
org.apache.ranger.audit.queue.AuditFileSpool.run(AuditFileSpool.java:758)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.UnknownHostException: mycluster
... 24 more
2017-03-01 18:48:50,151 ERROR queue.AuditFileSpool
(AuditFileSpool.java:logError(710)) - Error sending logs to consumer.
provider=knox.async.multi_dest.batch,
consumer=knox.async.multi_dest.batch.hdfs{{noformat}
was:For {{KNOX}} and {{RANGER_KMS}} services which supports ranger plugin,
need to have hdfs-site for saving ranger audits to hdfs in namenode HA env if
plugin is enabled.
> Need hdfs-site for saving ranger audits to hdfs in namenode HA env
> --
>
> Key: AMBARI-20369
> URL: https://issues.apache.org/jira/browse/AMBARI-20369
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
>
> For {{KNOX}} and {{RANGER_KMS}} services which supports ranger plugin, need
> to have hdfs-site.xml available in there conf directory for saving ranger
> audits to hdfs in namenode HA env.
> Below error logs are found, if hdfs-site.xml is not available,
> {noformat}
> 2017-03-01 18:48:50,150 ERROR provider.BaseAuditHandler
> (BaseAuditHandler.java:logError(327)) - Error writing to log file.
> java.lang.IllegalArgumentException: java.net.UnknownHostException: mycluster
> at
> org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:438)
> at
> org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:311)
> at
> org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
> at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:690)
> at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:631)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:160)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829)
> at
[jira] [Created] (AMBARI-20369) Need hdfs-site for saving ranger audits to hdfs in namenode HA env
Mugdha Varadkar created AMBARI-20369:
Summary: Need hdfs-site for saving ranger audits to hdfs in
namenode HA env
Key: AMBARI-20369
URL: https://issues.apache.org/jira/browse/AMBARI-20369
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Fix For: 2.5.0
For {{KNOX}} and {{RANGER_KMS}} services which supports ranger plugin, need to
have hdfs-site for saving ranger audits to hdfs in namenode HA env if plugin is
enabled.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20368) Hbase-client installed failed when hdfs hasnot installed
[
https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902764#comment-15902764
]
Hadoop QA commented on AMBARI-20368:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856953/AMBARI-20368.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10933//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10933//console
This message is automatically generated.
> Hbase-client installed failed when hdfs hasnot installed
>
>
> Key: AMBARI-20368
> URL: https://issues.apache.org/jira/browse/AMBARI-20368
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2
>Reporter: zhangxiaolu
> Attachments: AMBARI-20368.patch, screenshot-1.png
>
>
> the problem is that the installing of hbase-client is before hdfs-client, and
> the hdfs-client installed failed because the hadoop-conf-dir didn't exist.
> so there are two ways to solve this problem.
> the first method is that create the hadoop-conf-dir in hbase.py
> the second method is that setting the orders in role_command_order.json.
> I think that we can take the first method.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20343) Zeppelin: Configure both Hive and Hive interactive interpreters whenever required
[ https://issues.apache.org/jira/browse/AMBARI-20343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902728#comment-15902728 ] Hudson commented on AMBARI-20343: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6984 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6984/]) AMBARI-20343 Zeppelin: Configure both Hive and Hive interactive (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=47c0c582b2fb59d567257d7c6784793fd0d0c06f]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py > Zeppelin: Configure both Hive and Hive interactive interpreters whenever > required > - > > Key: AMBARI-20343 > URL: https://issues.apache.org/jira/browse/AMBARI-20343 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.5.0 >Reporter: Kshitij Badani >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-20343-branch-2.5-v1.patch > > > Currently only jdbc(hive) is present in the interpreter config. But lets say > if we have only HSI (hive server interactive) present on our cluster , or if > we have both HSI and Hive present then we need some changes to the way > interpreters are being defined > We should use %jdbc(hive) refer Hive interactive when only Hive interactive > is present in the cluster. > Otherwise %jdbc(hive) for Hive and %jdbc(hive_interactive) for Hive > interactive based on the availability of Hive/Hive interactive. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20343) Zeppelin: Configure both Hive and Hive interactive interpreters whenever required
[ https://issues.apache.org/jira/browse/AMBARI-20343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902722#comment-15902722 ] Hudson commented on AMBARI-20343: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1218 (See [https://builds.apache.org/job/Ambari-branch-2.5/1218/]) AMBARI-20343 Zeppelin: Configure both Hive and Hive interactive (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c7086b11b7e5536e0c8b56130774e728aa3363f6]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py > Zeppelin: Configure both Hive and Hive interactive interpreters whenever > required > - > > Key: AMBARI-20343 > URL: https://issues.apache.org/jira/browse/AMBARI-20343 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.5.0 >Reporter: Kshitij Badani >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-20343-branch-2.5-v1.patch > > > Currently only jdbc(hive) is present in the interpreter config. But lets say > if we have only HSI (hive server interactive) present on our cluster , or if > we have both HSI and Hive present then we need some changes to the way > interpreters are being defined > We should use %jdbc(hive) refer Hive interactive when only Hive interactive > is present in the cluster. > Otherwise %jdbc(hive) for Hive and %jdbc(hive_interactive) for Hive > interactive based on the availability of Hive/Hive interactive. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
