[
https://issues.apache.org/jira/browse/HDDS-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496404#comment-17496404
]
Siyao Meng edited comment on HDDS-6327 at 2/23/22, 12:48 AM:
-------------------------------------------------------------
Got a repro in the multi-tenancy feature branch that has the patch applied:
https://github.com/smengcl/hadoop-ozone/runs/5295265595
It's got the upgrade test failure logs this time (nice):
[^acceptance-misc-397ffa5.zip]
The test is occasionally failing at "ozone sh key put" command seemingly due to
scm/datanodes not initialized in {{RUNNING WITH NEW VERSION 1.2.0 FINALIZED}}
phase:
{code}
14:21:15.779 INFO Running command 'ozone sh key put
/new2-volume/new2-bucket/new2-key /tmp/sourcekey 2>&1'.
14:21:18.480 INFO ${rc} = 255
14:21:18.480 INFO ${output} = INTERNAL_ERROR Allocated 0 blocks.
Requested 1 blocks
{code}
I recall seeing this {{INTERNAL_ERROR Allocated 0 blocks. Requested 1 blocks}}
error message in other the acceptance test suite. Doesn't seem related to
multi-tenancy. Could be related to some other master branch changes.
It would be great if there is a way to block test execution until om/scm/dns
are all ready.
was (Author: smeng):
Got a repro in the multi-tenancy feature branch that has the patch applied:
https://github.com/smengcl/hadoop-ozone/runs/5295265595
It's got the upgrade test failure logs this time (nice):
[^acceptance-misc-397ffa5.zip]
The test is occasionally failing at "ozone sh key put" command seemingly due to
scm/datanodes not initialized in {{RUNNING WITH NEW VERSION 1.2.0 FINALIZED}}
phase:
{code}
14:21:15.779 INFO Running command 'ozone sh key put
/new2-volume/new2-bucket/new2-key /tmp/sourcekey 2>&1'.
14:21:18.480 INFO ${rc} = 255
14:21:18.480 INFO ${output} = INTERNAL_ERROR Allocated 0 blocks.
Requested 1 blocks
{code}
I recall seeing this {{INTERNAL_ERROR Allocated 0 blocks. Requested 1 blocks}}
error message elsewhere is the acceptance test suite. Doesn't seem related to
multi-tenancy.
> Upgrade acceptance test doesn't collect logs when the test fails
> ----------------------------------------------------------------
>
> Key: HDDS-6327
> URL: https://issues.apache.org/jira/browse/HDDS-6327
> Project: Apache Ozone
> Issue Type: Bug
> Components: docker
> Reporter: Siyao Meng
> Assignee: Siyao Meng
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.3.0
>
> Attachments: acceptance-misc-397ffa5.zip
>
>
> Upgrade acceptance test is not collecting logs when the test fails:
> https://github.com/smengcl/hadoop-ozone/runs/5205586631
> https://github.com/smengcl/hadoop-ozone/runs/5207373946
> The log bundle is supposed to have these logs regardless of whether the
> upgrade test suite fails or not:
> {code}
> docker-1.1.0-downgraded.log
> docker-1.1.0.log
> docker-1.2.0-finalized.log
> docker-1.2.0-pre-finalized.log
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
