Comment 4 for bug 1698900

Reviewed: https://review.openstack.org/475472
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=2a2f8535e2858400d68af74a8d813ca278f7a1b6
Submitter: Jenkins
Branch: master

commit 2a2f8535e2858400d68af74a8d813ca278f7a1b6
Author: Lance Bragstad <email address hidden>
Date: Mon Jun 19 17:41:13 2017 +0000

    Improve handling of database migration checks

    The `--check` subcommand is suppose to provide useful information
    and status codes depending on the state of the keystone database.
    Operators and automation use this information to determine what their
    next step is in a rolling upgrade. The current logic is broken
    becuase it doesn't account for new installations that might be
    relying on this information.

    This change breaks that case into multiple try/except statements and
    handles each appropriately so that the status code and logging
    information is accurate for operators and automation using this
    information for upgrading a new keystone database.

    Change-Id: I331fa663a99f79ea9a79a75e4ae07c45278556bf
    Closes-Bug: 1698900