[
https://issues.apache.org/jira/browse/HDDS-2225?focusedWorklogId=321815&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-321815
]
ASF GitHub Bot logged work on HDDS-2225:
----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Oct/19 10:54
Start Date: 02/Oct/19 10:54
Worklog Time Spent: 10m
Work Description: elek commented on issue #1568: HDDS-2225. SCM fails to
start in most unsecure environments due to leftover secure config
URL: https://github.com/apache/hadoop/pull/1568#issuecomment-537440726
Somewhat drastic but effective solution ;-) I am fine with removing it for
now, but we need to create a proper ozone-spark later (with smoketest).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 321815)
Time Spent: 1h 10m (was: 1h)
> SCM fails to start in most unsecure environments due to leftover secure config
> ------------------------------------------------------------------------------
>
> Key: HDDS-2225
> URL: https://issues.apache.org/jira/browse/HDDS-2225
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: docker
> Reporter: Attila Doroszlai
> Assignee: Attila Doroszlai
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Intermittent failure of {{ozone-recon}} and some other acceptance tests where
> SCM container is not available is caused by leftover secure config in
> {{core-site.xml}}.
> Initially the config file is
> [empty|https://raw.githubusercontent.com/apache/hadoop/trunk/hadoop-hdds/common/src/main/conf/core-site.xml].
> Various test environments populate it with different settings. The problem
> happens when a test does not specify any config for {{core-site.xml}}, in
> which case the previous test's config file is retained.
> {code}
> scm_1 | 2019-10-01 19:42:05 WARN WebAppContext:531 - Failed startup of
> context
> o.e.j.w.WebAppContext@1cc680e{/,file:///tmp/jetty-0.0.0.0-9876-scm-_-any-1272594486261557815.dir/webapp/,UNAVAILABLE}{/scm}
> scm_1 | javax.servlet.ServletException: javax.servlet.ServletException:
> Keytab does not exist: /etc/security/keytabs/HTTP.keytab
> scm_1 | at
> org.apache.hadoop.security.authentication.server.KerberosAuthenticationHandler.init(KerberosAuthenticationHandler.java:188)
> ...
> scm_1 | at
> org.apache.hadoop.hdds.scm.server.StorageContainerManager.start(StorageContainerManager.java:791)
> ...
> scm_1 | Unable to initialize WebAppContext
> scm_1 | 2019-10-01 19:42:05 INFO StorageContainerManagerStarter:51 -
> SHUTDOWN_MSG:
> scm_1 | /************************************************************
> scm_1 | SHUTDOWN_MSG: Shutting down StorageContainerManager at
> 8724df7131bb/192.168.128.6
> scm_1 | ************************************************************/
> {code}
> The problem is intermittent due to ordering of test cases being different in
> different runs. If a secure test is run earlier, more tests are affected.
> If secure tests are run last, the issue does not happen.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
