if MAX_NUMBER is not defined it will run "cinder-manage db online_data_migrations --max_count", which is invalid.
I'm using the containers without kolla-ansible, and I'm not setting the MAX_NUMBER variable. This happens on stein for centos-binary containers, but looking at the stable branches and master it is probably happening everywhere.
From what I've seen kolla-ansible always defines the MAX_NUMBER variable but I don't think it's actually used with that test.
if MAX_NUMBER is not defined it will run "cinder-manage db online_ data_migrations --max_count", which is invalid.
I'm using the containers without kolla-ansible, and I'm not setting the MAX_NUMBER variable. This happens on stein for centos-binary containers, but looking at the stable branches and master it is probably happening everywhere.
From what I've seen kolla-ansible always defines the MAX_NUMBER variable but I don't think it's actually used with that test.