[
https://issues.apache.org/jira/browse/HDDS-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751017#comment-16751017
]
Elek, Marton commented on HDDS-1002:
------------------------------------
Thanks [~adoroszlai] to fix this. The container rename LGTM:
{code:java}
- om:
+ ozoneManager:{code}
But is there any specific reason to use
{code:java}
image: om{code}
If I understood well it just tags the built (secure base)image as _om_, but I
can't see any immediate benefit...
> ozonesecure compose incompatible with smoke test
> ------------------------------------------------
>
> Key: HDDS-1002
> URL: https://issues.apache.org/jira/browse/HDDS-1002
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: docker
> Reporter: Doroszlai, Attila
> Assignee: Doroszlai, Attila
> Priority: Major
> Attachments: HDDS-1002.001.patch
>
>
> {code:title=hadoop-ozone/dist/target/ozone-0.4.0-SNAPSHOT/smoketest/test.sh
> --keep --env ozonesecure security}
> Creating network "ozonesecure_default" with the default driver
> Creating ozonesecure_kdc_1 ... done
> Creating ozonesecure_scm_1 ... done
> Creating ozonesecure_datanode_1 ... done
> Creating ozonesecure_datanode_2 ... done
> Creating ozonesecure_datanode_3 ... done
> Creating ozonesecure_om_1 ... done
> 0 datanode is up and healhty (until now)
> 3 datanodes are up and registered to the scm
> ERROR: No such service: ozoneManager
> [ ERROR ] Reading XML source 'smoketest/result/robot-*.xml' failed: No such
> file or directory
> Try --help for usage information.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
