Public bug reported:
The index added in the 54 version was named inappropriate to the naming
convention used by models. Need to fix index name.
** Affects: keystone
Importance: Undecided
Assignee: Ilya Pekelny (i159)
Status: In Progress
** Changed in: keystone
Assignee
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1398756
Title:
Foreign key exists in the oauth1 extension models but doesn't exist i
Public bug reported:
The oauth1 extension models contains a foreign keys which was deleted a
few migrations above.
** Affects: keystone
Importance: Undecided
Status: New
** Summary changed:
- Foreign key exists in the models but doesn't exist in the tables.
+ Foreign key exists in
Public bug reported:
By default the CI uses MyISAM MySQL engine which doesn't support foreign
key constraint. Thus we must explicitly sign MySQL engine as InnoDB at
every table declares foreign keys or which is a fk target. Otherwise
foreign keys can't be declared.
** Affects: keystone
Impo
Public bug reported:
Migration repositories provide hardcoded initial version value or even
missing it at all. Need to provide single automated tool to get real
initial version from any migration repo.
** Affects: keystone
Importance: Undecided
Assignee: Ilya Pekelny (i159
Public bug reported:
Database indexes missing in model class or have inappropriate names
provided with migrations.
** Affects: keystone
Importance: Undecided
Assignee: Ilya Pekelny (i159)
Status: In Progress
--
You received this bug notification because you are a member of
Public bug reported:
When test cases or any real app need to provide database migration and
use synced database required to share engine between helpers and app
(test case). The helpers need to have access to share engine to apply
migrations to the same database as application uses.
** Affects: k
Public bug reported:
Most tables should have a primary key, and each table can have only ONE
primary key. The PRIMARY KEY constraint uniquely identifies each record
in a database table. The endpoint_group has no primary key. But
project_endpoint_group table provides a primary key constraint pointe
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
Assignee: (unassigned) => Ilya Pekelny (i159)
** Changed in: keystone
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineerin
://github.com/openstack/keystone/blob/master/keystone/tests/ksfixtures/database.py#L121
** Affects: keystone
Importance: Undecided
Assignee: Ilya Pekelny (i159)
Status: In Progress
** Changed in: keystone
Assignee: (unassigned) => Ilya Pekelny (i159)
** Changed
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => In Progress
** Changed in: keystone
Assignee: (unassigned) => Ilya Pekelny (i159)
--
You received this bug notification because you are a member of Yahoo!
Engineerin
: Ilya Pekelny (i159)
Status: In Progress
** Changed in: keystone
Assignee: (unassigned) => Ilya Pekelny (i159)
** Changed in: keystone
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscri
Public bug reported:
As models and migrations don't have any logical relation in code, so
differences are possible. Furthermore in most of cases differences
exists. The only way to solve this problem is using of specific test
such as this https://review.openstack.org/#/c/74081/ .
This is a diff
** Also affects: nova
Importance: Undecided
Status: New
--
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/1255532
Title:
Import of unexisting openstack.common.tes
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => In Progress
** Changed in: keystone
Assignee: (unassigned) => Ilya Pekelny (i159)
--
You received this bug notification because you are a member of Yahoo!
Engineerin
** Also affects: oslo
Importance: Undecided
Status: New
** Changed in: oslo
Status: New => In Progress
** Changed in: oslo
Assignee: (unassigned) => Ilya Pekelny (i159)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, wh
** Also affects: oslo
Importance: Undecided
Status: New
** Changed in: oslo
Assignee: (unassigned) => Ilya Pekelny (i159)
** Changed in: oslo
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, wh
non-ascii characters. Please use unicode() or translate() instead."
** Affects: keystone
Importance: Undecided
Assignee: Ilya Pekelny (i159)
Status: In Progress
** Changed in: keystone
Assignee: (unassigned) => Ilya Pekelny (i159)
** Changed in: keystone
point the function is redundant in the current state. Must
be refactored.
** Affects: keystone
Importance: Undecided
Assignee: Ilya Pekelny (i159)
Status: New
** Changed in: keystone
Assignee: (unassigned) => Ilya Pekelny (i159)
--
You received this bug notification be
Status: New
** Affects: oslo
Importance: Undecided
Assignee: Ilya Pekelny (i159)
Status: New
** Summary changed:
- Oslo migrate.py have no functionality to compute path to `migrate_repo`s
+ Oslo migrate.py does not have functionality to compute path to `migrate_repo`s
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
21 matches
Mail list logo
