From 3895b3e00eb6610b6a911ce14c032a6fda14fb8c Mon Sep 17 00:00:00 2001 From: Pierre Riteau Date: Mon, 12 Feb 2018 19:58:31 +0000 Subject: [PATCH] Correct information in state machine release note The migration of the lease status is actually done by an Alembic migration script added in 5d3918c885f430e79e8283533ad5eb3a84ffecc7. Change-Id: I001a5adcd5892d0be74c1028b62a03b5ecb507a8 --- releasenotes/notes/state-machine-37be751ed54c1c75.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/releasenotes/notes/state-machine-37be751ed54c1c75.yaml b/releasenotes/notes/state-machine-37be751ed54c1c75.yaml index 1a1af862..e3549f95 100644 --- a/releasenotes/notes/state-machine-37be751ed54c1c75.yaml +++ b/releasenotes/notes/state-machine-37be751ed54c1c75.yaml @@ -5,7 +5,7 @@ features: With this change, transition graphs of statuses of leases, reservations, and events are redefined while keeping backward compatibility. If you update Blazar from an older version, the lease status is - automatically updated from *None* at the time of an event or an API call. + automatically updated from *None* by an Alembic database migration script. See `state machine documentation`_ for more details. - .. _state machine documentation: https://docs.openstack.org/blazar/latest/user/state-machines.html \ No newline at end of file + .. _state machine documentation: https://docs.openstack.org/blazar/latest/user/state-machines.html