adoroszlai commented on issue #1171: HDDS-1834. parent directories not found in 
secure setup due to ACL check
URL: https://github.com/apache/hadoop/pull/1171#issuecomment-516158468
 
 
   Thanks @lokeshj1703 for the review.
   
   > There are couple of test failures. Can we please verify those are not 
related?
   
   I think all failing integration tests have been having problems 
intermittently or consistently without this patch:
   
    * `TestOzoneRpcClientWithRatis` 
([testNativeAclsForBucket](https://ci.anzix.net/job/ozone-nightly/188/testReport/junit/org.apache.hadoop.ozone.client.rpc/TestOzoneRpcClientWithRatis/integration___testNativeAclsForBucket/),
 
[testNativeAclsForKey](https://ci.anzix.net/job/ozone-nightly/188/testReport/junit/org.apache.hadoop.ozone.client.rpc/TestOzoneRpcClientWithRatis/integration___testNativeAclsForKey/),
 
[testNativeAclsForPrefix](https://ci.anzix.net/job/ozone-nightly/188/testReport/junit/org.apache.hadoop.ozone.client.rpc/TestOzoneRpcClientWithRatis/integration___testNativeAclsForPrefix/))
 and `TestRatisPipelineCreateAndDestory` 
([testPipelineCreationOnNodeRestart](https://ci.anzix.net/job/ozone-nightly/188/testReport/junit/org.apache.hadoop.hdds.scm.pipeline/TestRatisPipelineCreateAndDestory/integration___testPipelineCreationOnNodeRestart/))
 have been consistently failing in nightly
    * `TestScmSafeMode` 
([testSCMSafeModeRestrictedOp](https://ci.anzix.net/job/ozone-nightly/188/testReport/junit/org.apache.hadoop.ozone.om/TestScmSafeMode/integration___testSCMSafeModeRestrictedOp/))
 and `TestMultiBlockWritesWithDnFailures` 
([testMultiBlockWritesWithDnFailures](https://ci.anzix.net/job/ozone-nightly/188/testReport/junit/org.apache.hadoop.ozone.client.rpc/TestMultiBlockWritesWithDnFailures/integration___testMultiBlockWritesWithDnFailures/))
 are also failing a bit more recently in nightly
    * `TestBlockOutputStreamWithFailures` 
([test2DatanodesFailure](https://ci.anzix.net/job/ozone-nightly/186/testReport/junit/org.apache.hadoop.ozone.client.rpc/TestBlockOutputStreamWithFailures/integration___test2DatanodesFailure/),
 
[testExceptionDuringClose](https://ci.anzix.net/job/ozone-nightly/184/testReport/org.apache.hadoop.ozone.client.rpc/TestBlockOutputStreamWithFailures/integration___testExceptionDuringClose/),
 
[testWatchForCommitWithCloseContainerException](https://ci.anzix.net/job/ozone-nightly/186/testReport/junit/org.apache.hadoop.ozone.client.rpc/TestBlockOutputStreamWithFailures/integration___testWatchForCommitWithCloseContainerException/)),
 `TestOzoneClientRetriesOnException` 
([testMaxRetriesByOzoneClient](https://ci.anzix.net/job/ozone-nightly/185/testReport/junit/org.apache.hadoop.ozone.client.rpc/TestOzoneClientRetriesOnException/integration___testMaxRetriesByOzoneClient/)),
 `Test2WayCommitInRatis` 
([test2WayCommitForRetryfailure](https://ci.anzix.net/job/ozone-nightly/186/testReport/junit/org.apache.hadoop.ozone.client.rpc/Test2WayCommitInRatis/integration___test2WayCommitForRetryfailure/))
 and `TestWatchForCommit` 
([testWatchForCommitWithSmallerTimeoutValue](https://ci.anzix.net/job/ozone-nightly/180/testReport/junit/org.apache.hadoop.ozone.client.rpc/TestWatchForCommit/integration___testWatchForCommitWithSmallerTimeoutValue/))
 failed in some of the nightlies
   
   The only test failure I haven't found in nightlies is 
testWatchForCommitForRetryfailure in `TestWatchForCommit`, but it happened in 
some [other PR test 
run](https://ci.anzix.net/job/ozone/17480/testReport/org.apache.hadoop.ozone.client.rpc/TestWatchForCommit/integration___testWatchForCommitForRetryfailure/)

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

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

Reply via email to