[ https://issues.apache.org/jira/browse/HDDS-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863430#comment-16863430 ]
Eric Yang commented on HDDS-1667: --------------------------------- [~elek] Patch 004 added more changes into dist project compose files and removed changes related to k8s. I see there are references to ${HADOOP_IMAGE}:${HADOOP_VERSION} in existing docker compose files. I think this is probably ok, if Jenkins pass in HADOOP_IMAGE, and HADOOP_VERSION. Hence, I made some reference change to ozonesecure-mr, ozonesecure to make them consistent. Let me know if it's ok to change those, and if you want a specific default for those two properties. > 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, > HDDS-1667.003.patch, HDDS-1667.004.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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org