OpenStack Identity (keystone)

  1. Bug #1702211
  2. Comment #9

Comment 9 for bug 1702211

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to keystone (stable/pike)

Reviewed: https://review.openstack.org/493260
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=66a1047e8c9b58a1d52f8f4417ca5d4c74a4997f
Submitter: Jenkins
Branch: stable/pike

commit 66a1047e8c9b58a1d52f8f4417ca5d4c74a4997f
Author: Morgan Fainberg <email address hidden>
Date: Fri Aug 11 14:56:30 2017 -0700

    Add int storage of datetime for password created/expires

    Due to MySQL (in some versions) not storing datetime resolution below
    one second, keystone occasionally ends up with weird behavior such as
    a New password not being valid. The password created at and expires at
    columns now store both datetime (for rolling upgrades) and integers.

    Keystone from Pike and beyond leans on the new created_at_int column
    and expires_at_int column.

    Change-Id: I2c219b4b9b353f1e2cce6088849a773196f0e443
    Closes-Bug: #1702211