[
https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928861#comment-15928861
]
Alejandro Fernandez commented on AMBARI-20368:
----------------------------------------------
-1 for patch.
18 python unit tests are failing,
e.g.,
{noformat}
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/Users/afernandez/Documents/git/ambari-vagrant/centos6.4/ambari/ambari-common/src/test/python/mock/mock.py",
line 1199, in patched
return func(*args, **keywargs)
File
"/Users/afernandez/Documents/git/ambari-vagrant/centos6.4/ambari/ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_master.py",
line 224, in test_configure_secured
self.assert_configure_secured()
File
"/Users/afernandez/Documents/git/ambari-vagrant/centos6.4/ambari/ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_master.py",
line 437, in assert_configure_secured
mode = 0777
File
"/Users/afernandez/Documents/git/ambari-vagrant/centos6.4/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 281, in assertResourceCalled
self.assertEquals(name, resource.name)
AssertionError: '/tmp' != '/etc/hadoop/conf'
FAIL: test_start_default (test_hbase_master.TestHBaseMaster)
{noformat}
> HBase-client install fails when HDFS has not been 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
> Assignee: zhangxiaolu
> Fix For: trunk, 2.5.0
>
> 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)
