Christos Bisias

> Raised a new ticket [HDDS-7383](https://issues.apache.org/jira/browse/HDDS-7383) for better review. Please have a look. The other PRs will be on the way. @symious Can you add to the PR's description or...

> Did you get a chance to try the downgrade to 1.1.0 testing I mentioned earlier? @errose28 I was able to run this script successfully twice `hadoop-ozone/dist/target/ozone-1.3.0-SNAPSHOT/compose/upgrade/test.sh`, once with `run_test...

@errose28 thanks for reviewing this. I made the changes and updated the tests. Also, added an scm exception in case moving the container failed. Let me know how it looks.

hey @DaveTeng0, if you are referring to the workflow, it's unrelated to the PR. I got a green workflow for the latest 2 commits on my fork. Check below [cleanup](https://github.com/xBis7/ozone/actions/runs/3876726389)...

@neils-dev I've updated the patch.

@neils-dev I've expanded the test for checking that the container has been removed from the DB during tmp dir cleanup.

@errose28 The point is not the `ClientVersion` but the `BucketLayout` used due to the version. All the existing tests are covering [this code block](https://github.com/xBis7/ozone/blob/HDDS-7280/hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/request/bucket/OMBucketCreateRequest.java#L275-L285). The purpose of the test changes...

> can you just check if the test failures are related? @errose28 Both of them passed on my fork's workflow. Check [here](https://github.com/xBis7/ozone/actions/runs/3517471959).

@errose28 Different failure this time. If you could retrigger it.

@ayushtkn Can you take a look at this PR?