Joseph Percivall created MINIFI-416:
---------------------------------------
Summary: Integration tests fail with "Cannot start service minifi:
oci runtime error"
Key: MINIFI-416
URL: https://issues.apache.org/jira/browse/MINIFI-416
Project: Apache NiFi MiNiFi
Issue Type: Bug
Reporter: Joseph Percivall
I am attempting to run the MiNiFi integration tests and they all fail with the
following error:
{quote}verifyLogEntries[6: Schema Version: v2 Name:
StressTestFramework](org.apache.nifi.minifi.integration.standalone.test.StandaloneYamlTest)
Time elapsed: 17.289 sec <<< ERROR!
com.palantir.docker.compose.execution.DockerExecutionException: 'docker-compose
up -d' returned exit code 1
The output was:
Starting c39d2544_minifi_1 ...
Starting c39d2544_minifi_1 ... error
ERROR: for c39d2544_minifi_1 Cannot start service minifi: oci runtime error:
container_linux.go:265: starting container process caused "exec: \"bash\":
executable file not found in $PATH"
ERROR: for minifi Cannot start service minifi: oci runtime error:
container_linux.go:265: starting container process caused "exec: \"bash\":
executable file not found in $PATH"
Encountered errors while bringing up the project.
at
com.palantir.docker.compose.execution.Command.lambda$throwingOnError$12(Command.java:60)
at
com.palantir.docker.compose.execution.Command.execute(Command.java:50)
at
com.palantir.docker.compose.execution.DefaultDockerCompose.up(DefaultDockerCompose.java:79)
at
com.palantir.docker.compose.execution.DelegatingDockerCompose.up(DelegatingDockerCompose.java:45)
at
com.palantir.docker.compose.execution.RetryingDockerCompose.lambda$up$27(RetryingDockerCompose.java:37)
at
com.palantir.docker.compose.execution.Retryer.runWithRetries(Retryer.java:44)
at
com.palantir.docker.compose.execution.RetryingDockerCompose.up(RetryingDockerCompose.java:36)
at
com.palantir.docker.compose.execution.ConflictingContainerRemovingDockerCompose.up(ConflictingContainerRemovingDockerCompose.java:51)
at
com.palantir.docker.compose.DockerComposeRule.before(DockerComposeRule.java:149)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
{quote}
I am able to run all the other tests just fine. I'm running the RC-1 for 0.3.0.
On one hand, I'm not convinced that it's not something local on my end since
all the tests are failing. On the other, I see a similar error here[1] and
that's supposedly due to the base layer not having any tooling.
A complete output of all the tests failing:
{quote}Tests in error:
HierarchicalC2IntegrationTest.initCertificates:94 » DockerExecution
'docker-co...
StandaloneXmlTest.verifyLogEntries[0: Schema Version: v1 Name: CsvToJson] »
DockerExecution
StandaloneXmlTest.verifyLogEntries[1: Schema Version: v1 Name:
DecompressionCircularFlow] » DockerExecution
StandaloneXmlTest.verifyLogEntries[2: Schema Version: v1 Name:
MiNiFiTailLogAttribute] » DockerExecution
StandaloneXmlTest.verifyLogEntries[3: Schema Version: v1 Name:
ReplaceTextExpressionLanguageCSVReformatting] » DockerExecution
StandaloneXmlTest.verifyLogEntries[4: Schema Version: v2 Name:
MultipleRelationships] » DockerExecution
StandaloneXmlTest.verifyLogEntries[5: Schema Version: v2 Name: ProcessGroups]
» DockerExecution
StandaloneXmlTest.verifyLogEntries[6: Schema Version: v2 Name:
StressTestFramework] » DockerExecution
StandaloneYamlTest.verifyLogEntries[0: Schema Version: v1 Name: CsvToJson] »
DockerExecution
StandaloneYamlTest.verifyLogEntries[1: Schema Version: v1 Name:
DecompressionCircularFlow] » DockerExecution
StandaloneYamlTest.verifyLogEntries[2: Schema Version: v1 Name:
MiNiFiTailLogAttribute] » DockerExecution
StandaloneYamlTest.verifyLogEntries[3: Schema Version: v1 Name:
ReplaceTextExpressionLanguageCSVReformatting] » DockerExecution
StandaloneYamlTest.verifyLogEntries[4: Schema Version: v2 Name:
MultipleRelationships] » DockerExecution
StandaloneYamlTest.verifyLogEntries[5: Schema Version: v2 Name:
ProcessGroups] » DockerExecution
StandaloneYamlTest.verifyLogEntries[6: Schema Version: v2 Name:
StressTestFramework] » DockerExecution{quote}
[1] https://github.com/jaegertracing/jaeger/issues/264
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
