[ 
https://issues.apache.org/jira/browse/HDDS-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906761#comment-16906761
 ] 

Anu Engineer commented on HDDS-1928:
------------------------------------

I have committed this to trunk and ozone-0.4.1. [~adoroszlai] Thanks for your 
contribution. [~vivekratnavel] Thanks for the review.

 
{noformat}
3 datanodes are up and registered to the scm
==============================================================================
ozone-recon-basic :: Smoketest ozone cluster startup
==============================================================================
Check webui static resources | PASS |
------------------------------------------------------------------------------
Start freon testing | FAIL |
255 != 0
------------------------------------------------------------------------------{noformat}
 

There was a failure on my laptop, but this fix is correct and needed. Hence I 
have committed this. FYI, [~nandakumar131]

> Cannot run ozone-recon compose due to syntax error
> --------------------------------------------------
>
>                 Key: HDDS-1928
>                 URL: https://issues.apache.org/jira/browse/HDDS-1928
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: docker
>    Affects Versions: 0.4.1
>            Reporter: Doroszlai, Attila
>            Assignee: Doroszlai, Attila
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> {noformat}
> $ cd hadoop-ozone/dist/target/ozone-0.5.0-SNAPSHOT/compose/ozone-recon
> $ docker-compose up -d --scale datanode=3
> ERROR: yaml.scanner.ScannerError: mapping values are not allowed here
>   in "./docker-compose.yaml", line 20, column 33
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to