yahoo-eng-team team mailing list archive

[OpenStack Infra <1804652@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/619622
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9c0d188988eb86f9186bca98e544ba15105072e8
Submitter: Zuul
Branch:    master

commit 9c0d188988eb86f9186bca98e544ba15105072e8
Author: Matthew Booth <mbooth@xxxxxxxxxx>
Date:   Thu Nov 22 14:06:53 2018 +0000

    Workaround a race initialising version control in db_version()
    
    Closes-Bug: #1804652
    
    Change-Id: I18e682d7aa5ebbddec7e22e1a504888a83b9be12


** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1804652

Title:
  nova.db.sqlalchemy.migration.db_version is racy

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  db_version() attempts to initialise versioning if the db is not
  versioned. However, it doesn't consider concurrency, so we can get
  errors if multiple watchers try to get the db version before the db is
  initialised. We are seeing this in practise during tripleo deployments
  in a script which waits on multiple controller nodes for db sync to
  complete.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1804652/+subscriptions