yahoo-eng-team team mailing list archive

[Ilya Pekelny <pekelny@xxxxxxxxx>]

Public bug reported:

Oslo.db migration.py uses singleton to store defined
`migrate.versioning.repository.Repository` instance containing migration
repository path. Most of plugins have its own migrate repo. Usage of
singleton in point of Repository instances causes implicit and
unexpected behavior therefore as current Repository instance may contain
inappropriate path to migrate repo.

Solution: do not use singleton.

** Affects: keystone
     Importance: Undecided
     Assignee: Ilya Pekelny (i159)
         Status: New

** Affects: oslo
     Importance: Undecided
     Assignee: Ilya Pekelny (i159)
         Status: New

** Also affects: keystone
   Importance: Undecided
       Status: New

** Changed in: oslo
     Assignee: (unassigned) => Ilya Pekelny (i159)

** Changed in: keystone
     Assignee: (unassigned) => Ilya Pekelny (i159)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1259229

Title:
  Undesired migrate repository path caching.

Status in OpenStack Identity (Keystone):
  New
Status in Oslo - a Library of Common OpenStack Code:
  New

Bug description:
  Oslo.db migration.py uses singleton to store defined
  `migrate.versioning.repository.Repository` instance containing
  migration repository path. Most of plugins have its own migrate repo.
  Usage of singleton in point of Repository instances causes implicit
  and unexpected behavior therefore as current Repository instance may
  contain inappropriate path to migrate repo.

  Solution: do not use singleton.

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