HDDS-16200. Flaky container balancer robot test

[ChenSammi]

What changes were proposed in this pull request?

Random failures due to wait timeout.

Verify Container Balancer for RATIS/EC containers                     | FAIL |
Keyword 'Run Balancer Verbose History Status' failed after retrying for 40 seconds. The last error was: 'ContainerBalancer is Running.
--
ozone-balancer-EC :: Smoketest ozone cluster startup                  | FAIL |

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-16200

How was this patch tested?

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[ashishkumar50]

@ChenSammi Thanks for the fix, It seems before also in PR flaky test was fixed.
Change looks fine to me to increase time here.
Can you try to run flaky workflow to see if it is working always?

[ChenSammi]

@ChenSammi Thanks for the fix, It seems before also in PR flaky test was fixed. Change looks fine to me to increase time here. Can you try to run flaky workflow to see if it is working always?

@ashishkumar50 , usually rerun will solve the problem. So the root cause is the task cannot be finished in 40s. This #7569 changes the way from blind sleep 40s, to periodically check in 40s, but the max time wait is still 40s. I think extend max 40s to 90s should be enough to cover the execution according to this which I mentioned in the JIRA description.

ContainerBalancer is Running.
Started at: 2026-08-17 04:47:45
Balancing duration: 46s
Size scheduled to move 102 MB
Moved data size 62 MB
Scheduled to move containers 5
Already moved containers 3
Failed to move containers 0
Failed to move containers by timeout 0
...
Completed iteration history:

[priyeshkaratha]

Thanks @ChenSammi for working on this. Changes LGTM

[ashishkumar50]

Yes in the old PR time was not increased.
LGTM to increase time here.