e32db7ae75
According to the placement upgrade process, online_data_migrations should be triggered right after upgrading database schema and placement services on all controller nodes [1] We also replace usage of `need_service_restart` local fact with `need_online_data_migrations` as first one is never actually used. [1] https://docs.openstack.org/placement/latest/cli/placement-manage.html#placement-database Change-Id: I430ea45fe321440d832a0a90747b80f5d197f073 |
||
|---|---|---|
| .. | ||
| main.yml | ||
| placement_db_post_setup.yml | ||
| placement_db_sync.yml | ||
| placement_install.yml | ||
| placement_post_install.yml | ||
| placement_pre_install.yml | ||