Detailed bug description:
During upgrade MOS8.0 to MOS9.0 via Octane(stable/mitaka and master), I have faced with following bug.
By doing second controller upgrade via Octane (octane upgrade-db <original_env_id> <seed_env_id>), Octane fails with an error
2016-09-01 11:30:12 INFO octane.util.subprocess Started process nova-manage[at node-4]: nova-manage db migrate_flavor_data
2016-09-01 11:30:15 ERROR octane.util.subprocess nova-manage[at node-4] stderr: No handlers could be found for logger "oslo_config.cfg"
2016-09-01 11:30:15 ERROR octane.util.subprocess nova-manage[at node-4] stderr: usage: nova-manage db [-h]
2016-09-01 11:30:15 ERROR octane.util.subprocess nova-manage[at node-4] stderr: {archive_deleted_rows,contract,expand,migrate,null_instance_uuid_scan,sync,version}
2016-09-01 11:30:15 ERROR octane.util.subprocess nova-manage[at node-4] stderr: ...
2016-09-01 11:30:15 ERROR octane.util.subprocess nova-manage[at node-4] stderr: nova-manage db: error: argument action: invalid choice: 'migrate_flavor_data' (choose from 'archive_deleted_rows', 'contract', 'expand', 'migrate', 'null_instance_uuid_scan', 'sync', 'versi
on')
Steps to reproduce:
1) Have MOS8.0 environment
2) Backup environment settings, following documented process
3) Prepare new master node (fuel 9.0)
4) Restore the backup from second step
5) Upgrade restored environment via Octane
6) Upgrade primary controller via Octane
7) Upgrade DB via Octane
Expected results:
Database from original controllers has been copied to new one
Actual result:
Octane returns an error which in turn breaks data base migration
Reproducibility:
Octane from stable/mitaka and master branches
The data migration for flavors have to be executed only on the Kilo release and only for the next upgraded paths: 7.0 -> 9.0 and 7.0 -> 8.0.