[
https://issues.apache.org/jira/browse/HDDS-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862278#comment-16862278
]
Eric Yang commented on HDDS-1667:
---------------------------------
{quote}1. Can you please rebase it (or please upload it as a PR, that could be
tested even if conflicted with the current trunk)
The trunk code is a bit hard to follow, please bare with me to understand your
request. Trunk hadoop/hadoop-ozone/dist/pom.xml define properties:
{code}
<docker.image>apache/hadoop:${project.version}</docker.image>
<docker.hadoop-runner.version>jdk11</docker.hadoop-runner.version>
{code}
There is no apache/hadoop image. There is only apache/hadoop-runner. Should
this line up to hadoop-runner? The docker-build profile will override
docker.image variable, as the resulting docker artifact is named
${user.name}/ozone:${project.version}. Should the docker-build generate image
that is not used in Kubernetes yaml template?
> Docker compose file may referring to incorrect docker image name
> ----------------------------------------------------------------
>
> Key: HDDS-1667
> URL: https://issues.apache.org/jira/browse/HDDS-1667
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Trivial
> Fix For: 0.4.1
>
> Attachments: HDDS-1667.001.patch, HDDS-1667.002.patch
>
>
> In fault injection test, the docker compose file is templated using:
> ${user.name}/ozone:${project.version}
> If user pass in parameter -Ddocker.image to cause docker build to generate a
> different name. This can cause fault injection test to fail/stuck because it
> could not find the required docker image. The fix is simply use docker.image
> token to filter docker compose file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
