Now we have `placement-manage db sync` CLI, which upgrades the
placement DB to the current version using alembic. However, if you
have already created tables in placement, the command fails on having
the initial upgrade: (initial) -> (b4ed3a175331). This is because it
assumes the initial DB has no contents and tries to create the tables.
Since this can be a problem for nova-api -> placement migration case,
where we expect placement DB has tables before starting alembic
version mangement via the migration script in `tools/*-migrate-db.sh`,
this patch provides a way to stamp the current version via the CLI:
`placement-manage db stamp <version>`.
Change-Id: I65fa8fd6e2479224f1b25cd62ca15a90d5948424
3d696b2207