Comment 3 for bug 1880753

It's not clear in what circumstances it is important to use a custom max_count. Note that if max_count is not passed to cinder-manage, it will run batches of 50 migrations until complete (i.e. only one invocation should be needed).

If someone wants to implement the loop logic, I would suggest defaulting to no sleep but allowing to customize it via a variable. But if no one really needs to use that feature, let's stop passing max_count.