[Yahoo-eng-team] [Bug 1398748] [NEW] MySQL engine doesn't specified at a table s with foreign key constraint.
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 Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1398748 Title: MySQL engine doesn't specified at a table s with foreign key constraint. Status in OpenStack Identity (Keystone): New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1398748/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1398756] [NEW] Foreign key exists in the oauth1 extension models but doesn't exist in the tables.
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 the oauth1 extension models but doesn't exist in the tables. ** Description changed: - The models contains a foreign keys which was deleted a few migrations - above. + The oauth1 extension models contains a foreign keys which was deleted a + few migrations above. -- 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 in the tables. Status in OpenStack Identity (Keystone): New Bug description: The oauth1 extension models contains a foreign keys which was deleted a few migrations above. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1398756/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1398756] Re: Foreign key exists in the oauth1 extension models but doesn't exist in the tables.
** 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 in the tables. Status in OpenStack Identity (Keystone): Invalid Bug description: The oauth1 extension models contains a foreign keys which was deleted a few migrations above. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1398756/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1397890] [NEW] Missing primary key constraint at endpoint_group.id column
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 pointed to endpoint_group.id column. Such a migration can't be applied with any sql backend except SQLite. ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1397890 Title: Missing primary key constraint at endpoint_group.id column Status in OpenStack Identity (Keystone): New Bug description: 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 pointed to endpoint_group.id column. Such a migration can't be applied with any sql backend except SQLite. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1397890/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1397894] [NEW] Migration helpers designed to sync database couldn't be used with shared engine.
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: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1397894 Title: Migration helpers designed to sync database couldn't be used with shared engine. Status in OpenStack Identity (Keystone): New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1397894/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1397899] [NEW] Database indexes missing or have inappropriate names.
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 Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1397899 Title: Database indexes missing or have inappropriate names. Status in OpenStack Identity (Keystone): In Progress Bug description: Database indexes missing in model class or have inappropriate names provided with migrations. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1397899/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1397903] [NEW] Hardcoded initial database version
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) Status: In Progress ** 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! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1397903 Title: Hardcoded initial database version Status in OpenStack Identity (Keystone): In Progress Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1397903/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1214341] Re: Not all db.sqal.session methods are wrapped by wrap_db_error
** 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! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1214341 Title: Not all db.sqal.session methods are wrapped by wrap_db_error Status in OpenStack Identity (Keystone): In Progress Status in Oslo - a Library of Common OpenStack Code: Fix Committed Bug description: first(), all(), begin(), commit() and other public methods could produce amount of exceptions, that should be wrapped in exception in any case. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1214341/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1319370] [NEW] Uncontested reflection models to a test database
Public bug reported: All the metadata models uncontested reflect to a test database even if migrations has been already synced. * In-file database synchronization https://github.com/openstack/keystone/blob/master/keystone/tests/ksfixtures/database.py#L46 * Uncontested metadata reflection https://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 in: keystone Status: New = In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1319370 Title: Uncontested reflection models to a test database Status in OpenStack Identity (Keystone): In Progress Bug description: All the metadata models uncontested reflect to a test database even if migrations has been already synced. * In-file database synchronization https://github.com/openstack/keystone/blob/master/keystone/tests/ksfixtures/database.py#L46 * Uncontested metadata reflection https://github.com/openstack/keystone/blob/master/keystone/tests/ksfixtures/database.py#L121 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1319370/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1288916] Re: Race in db test cases
** 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!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1288916
Title:
Race in db test cases
Status in OpenStack Identity (Keystone):
In Progress
Status in Oslo - a Library of Common OpenStack Code:
Fix Released
Bug description:
As I understand it, this is a known issue that's being worked, but
it's failing on a pretty regular basis in the oslo-incubator gate so
I'm filing a bug to recheck against. The problem manifests as
something like the following:
2014-03-06 17:59:21.354 | FAIL:
tests.unit.db.sqlalchemy.test_sqlalchemy.MySQLTraditionalModeTestCase.test_string_too_long
2014-03-06 17:59:21.355 | tags: worker-1
2014-03-06 17:59:21.355 |
--
2014-03-06 17:59:21.355 | Empty attachments:
2014-03-06 17:59:21.356 | stderr
2014-03-06 17:59:21.356 | stdout
2014-03-06 17:59:21.356 |
2014-03-06 17:59:21.357 | pythonlogging:'': {{{INFO
[openstack.common.db.sqlalchemy.session] MySQL server mode set to TRADITIONAL}}}
2014-03-06 17:59:21.357 |
2014-03-06 17:59:21.357 | Traceback (most recent call last):
2014-03-06 17:59:21.358 | File
tests/unit/db/sqlalchemy/test_sqlalchemy.py, line 278, in setUp
2014-03-06 17:59:21.358 | self.test_table.create()
2014-03-06 17:59:21.358 | File
/home/jenkins/workspace/gate-oslo-incubator-python26/.tox/py26/lib/python2.6/site-packages/sqlalchemy/schema.py,
line 616, in create
2014-03-06 17:59:21.359 | checkfirst=checkfirst)
2014-03-06 17:59:21.359 | File
/home/jenkins/workspace/gate-oslo-incubator-python26/.tox/py26/lib/python2.6/site-packages/sqlalchemy/engine/base.py,
line 1479, in _run_visitor
2014-03-06 17:59:21.359 | conn._run_visitor(visitorcallable, element,
**kwargs)
2014-03-06 17:59:37.780 | File
/home/jenkins/workspace/gate-oslo-incubator-python26/.tox/py26/lib/python2.6/site-packages/sqlalchemy/engine/base.py,
line 1122, in _run_visitor
2014-03-06 17:59:37.781 | **kwargs).traverse_single(element)
2014-03-06 17:59:37.781 | File
/home/jenkins/workspace/gate-oslo-incubator-python26/.tox/py26/lib/python2.6/site-packages/sqlalchemy/sql/visitors.py,
line 122, in traverse_single
2014-03-06 17:59:37.782 | return meth(obj, **kw)
2014-03-06 17:59:37.782 | File
/home/jenkins/workspace/gate-oslo-incubator-python26/.tox/py26/lib/python2.6/site-packages/sqlalchemy/engine/ddl.py,
line 89, in visit_table
2014-03-06 17:59:37.782 |
self.connection.execute(schema.CreateTable(table))
2014-03-06 17:59:37.783 | File
/home/jenkins/workspace/gate-oslo-incubator-python26/.tox/py26/lib/python2.6/site-packages/sqlalchemy/engine/base.py,
line 662, in execute
2014-03-06 17:59:37.783 | params)
2014-03-06 17:59:37.783 | File
/home/jenkins/workspace/gate-oslo-incubator-python26/.tox/py26/lib/python2.6/site-packages/sqlalchemy/engine/base.py,
line 720, in _execute_ddl
2014-03-06 17:59:37.784 | compiled
2014-03-06 17:59:37.784 | File
/home/jenkins/workspace/gate-oslo-incubator-python26/.tox/py26/lib/python2.6/site-packages/sqlalchemy/engine/base.py,
line 874, in _execute_context
2014-03-06 17:59:37.784 | context)
2014-03-06 17:59:37.784 | File
/home/jenkins/workspace/gate-oslo-incubator-python26/.tox/py26/lib/python2.6/site-packages/sqlalchemy/engine/base.py,
line 1024, in _handle_dbapi_exception
2014-03-06 17:59:37.785 | exc_info
2014-03-06 17:59:37.785 | File
/home/jenkins/workspace/gate-oslo-incubator-python26/.tox/py26/lib/python2.6/site-packages/sqlalchemy/util/compat.py,
line 196, in raise_from_cause
2014-03-06 17:59:37.785 | reraise(type(exception), exception, tb=exc_tb)
2014-03-06 17:59:37.786 | File
/home/jenkins/workspace/gate-oslo-incubator-python26/.tox/py26/lib/python2.6/site-packages/sqlalchemy/engine/base.py,
line 867, in _execute_context
2014-03-06 17:59:37.786 | context)
2014-03-06 17:59:37.786 | File
/home/jenkins/workspace/gate-oslo-incubator-python26/.tox/py26/lib/python2.6/site-packages/sqlalchemy/engine/default.py,
line 324, in do_execute
2014-03-06 17:59:37.787 | cursor.execute(statement, parameters)
2014-03-06 17:59:37.787 | File
/home/jenkins/workspace/gate-oslo-incubator-python26/.tox/py26/lib/python2.6/site-packages/MySQLdb/cursors.py,
line 205, in execute
2014-03-06 17:59:37.789 | self.errorhandler(self, exc, value)
2014-03-06 17:59:37.789 | File
/home/jenkins/workspace/gate-oslo-incubator-python26/.tox/py26/lib/python2.6/site-packages/MySQLdb/connections.py,
line 36, in defaulterrorhandler
2014-03-06 17:59:37.790 | raise errorclass, errorvalue
2014-03-06 17:59:37.790 | OperationalError
[Yahoo-eng-team] [Bug 1308593] [NEW] Migration INIT_VERSION in common place.
Public bug reported: Common code and tests use migrations. Init version value exists only in migration_helpers. It could be a good improvement to move INIT_VERSION into a common place to have access from any place of the project. ** Affects: keystone Importance: Undecided Assignee: 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 subscribed to Keystone. https://bugs.launchpad.net/bugs/1308593 Title: Migration INIT_VERSION in common place. Status in OpenStack Identity (Keystone): In Progress Bug description: Common code and tests use migrations. Init version value exists only in migration_helpers. It could be a good improvement to move INIT_VERSION into a common place to have access from any place of the project. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1308593/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1292591] [NEW] Database models differs from migrations.
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 example form Keystone:
AssertionError: Models and migration scripts aren't in sync:
[ [ ( 'modify_nullable',
None,
'federation_protocol',
'mapping_id',
{ 'existing_server_default': None,
'existing_type': VARCHAR(length=64)},
True,
False)],
[ ( 'modify_nullable',
None,
'region',
'description',
{ 'existing_server_default': None,
'existing_type': VARCHAR(length=255)},
False,
True)],
( 'remove_index',
Index(u'ix_revocation_event_revoked_at', Column(u'revoked_at', DATETIME(),
table=revocation_event, nullable=False))),
[ ( 'modify_nullable',
None,
'token',
'valid',
{ 'existing_server_default': None,
'existing_type': INTEGER()},
True,
False)]]
** Affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1292591
Title:
Database models differs from migrations.
Status in OpenStack Identity (Keystone):
New
Bug description:
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 example form Keystone:
AssertionError: Models and migration scripts aren't in sync:
[ [ ( 'modify_nullable',
None,
'federation_protocol',
'mapping_id',
{ 'existing_server_default': None,
'existing_type': VARCHAR(length=64)},
True,
False)],
[ ( 'modify_nullable',
None,
'region',
'description',
{ 'existing_server_default': None,
'existing_type': VARCHAR(length=255)},
False,
True)],
( 'remove_index',
Index(u'ix_revocation_event_revoked_at', Column(u'revoked_at',
DATETIME(), table=revocation_event, nullable=False))),
[ ( 'modify_nullable',
None,
'token',
'valid',
{ 'existing_server_default': None,
'existing_type': INTEGER()},
True,
False)]]
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1292591/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1255532] Re: Import of unexisting openstack.common.test.py file
** 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.test.py file Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Compute (Nova): New Bug description: In keystone/openstack/common/db/sqlalchemy/test_migrations.py, line 30 imports `test` what is not exists. Oslo project contains appropriate file. Solution — synchronize keystone.openstack.common with corresponding file in Oslo. The bug reproduces under nosetests. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1255532/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1273301] Re: Unit test failure: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead.
** 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, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1273301
Title:
Unit test failure: Message objects do not support str() because they
may contain non-ascii characters. Please use unicode() or translate()
instead.
Status in OpenStack Neutron (virtual network service):
New
Status in Oslo - a Library of Common OpenStack Code:
In Progress
Bug description:
FAIL:
neutron.tests.unit.test_neutron_manager.NeutronManagerTestCase.test_multiple_plugins_specified_for_service_type
tags: worker-3
--
Empty attachments:
stderr
stdout
pythonlogging:'': {{{
2014-01-17 09:03:30,605 INFO [neutron.manager] Loading core plugin:
neutron.db.db_base_plugin_v2.NeutronDbPluginV2
2014-01-17 09:03:30,698 INFO [neutron.manager] Loading Plugin:
neutron.tests.unit.dummy_plugin.DummyServicePlugin
2014-01-17 09:03:30,698 INFO [neutron.manager] Loading Plugin:
neutron.tests.unit.dummy_plugin.DummyServicePlugin
}}}
Traceback (most recent call last):
File neutron/tests/unit/test_neutron_manager.py, line 100, in
test_multiple_plugins_specified_for_service_type
NeutronManager.get_instance()
File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 866, in __exit__
mismatch = matcher.match((exc_type, exc_value, traceback))
File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py,
line 64, in match
return self.value_re.match(other[1])
File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_higherorder.py,
line 206, in match
after = self.preprocessor(value)
File neutron/openstack/common/gettextutils.py, line 264, in __str__
raise UnicodeError(msg)
UnicodeError: Message objects do not support str() because they may contain
non-ascii characters. Please use unicode() or translate() instead.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1273301/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1273301] Re: Unit test failure: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead.
** 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!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1273301
Title:
Unit test failure: Message objects do not support str() because they
may contain non-ascii characters. Please use unicode() or translate()
instead.
Status in OpenStack Identity (Keystone):
In Progress
Status in OpenStack Neutron (virtual network service):
New
Status in Oslo - a Library of Common OpenStack Code:
In Progress
Bug description:
FAIL:
neutron.tests.unit.test_neutron_manager.NeutronManagerTestCase.test_multiple_plugins_specified_for_service_type
tags: worker-3
--
Empty attachments:
stderr
stdout
pythonlogging:'': {{{
2014-01-17 09:03:30,605 INFO [neutron.manager] Loading core plugin:
neutron.db.db_base_plugin_v2.NeutronDbPluginV2
2014-01-17 09:03:30,698 INFO [neutron.manager] Loading Plugin:
neutron.tests.unit.dummy_plugin.DummyServicePlugin
2014-01-17 09:03:30,698 INFO [neutron.manager] Loading Plugin:
neutron.tests.unit.dummy_plugin.DummyServicePlugin
}}}
Traceback (most recent call last):
File neutron/tests/unit/test_neutron_manager.py, line 100, in
test_multiple_plugins_specified_for_service_type
NeutronManager.get_instance()
File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 866, in __exit__
mismatch = matcher.match((exc_type, exc_value, traceback))
File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py,
line 64, in match
return self.value_re.match(other[1])
File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_higherorder.py,
line 206, in match
after = self.preprocessor(value)
File neutron/openstack/common/gettextutils.py, line 264, in __str__
raise UnicodeError(msg)
UnicodeError: Message objects do not support str() because they may contain
non-ascii characters. Please use unicode() or translate() instead.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1273301/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275686] [NEW] Non-ascii characters does not handled correctly.
Public bug reported: We need to handle exception messages with `gettextutils` tools instead of using string message as is. Because every message can contain non-ascii characters and it can cause the unicode error: UnicodeError: Message objects do not support str() because they may contain 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 Status: New = In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1275686 Title: Non-ascii characters does not handled correctly. Status in OpenStack Identity (Keystone): In Progress Bug description: We need to handle exception messages with `gettextutils` tools instead of using string message as is. Because every message can contain non-ascii characters and it can cause the unicode error: UnicodeError: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1275686/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275686] Re: Non-ascii characters not handled correctly
** 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, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1275686 Title: Non-ascii characters not handled correctly Status in OpenStack Identity (Keystone): In Progress Status in Oslo - a Library of Common OpenStack Code: In Progress Bug description: We need to handle exception messages with `gettextutils` tools instead of using string message as is. Because every message can contain non-ascii characters and it can cause the unicode error: UnicodeError: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1275686/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1273336] [NEW] common.sql.migration.find_migrate_repo never used with an argument.
Public bug reported: If we look attentively to a `find_migrate_repo` usage we will see: $ grep -r find_migrate_repo keystone keystone/common/sql/migration.py:repo_path = find_migrate_repo() keystone/common/sql/migration.py:repo_path = find_migrate_repo() keystone/common/sql/migration.py:repo_path = find_migrate_repo() The function never been used with an argument. What does it mean? This mean that the only line is needed in this function https://github.com/openstack/keystone/blob/master/keystone/common/sql/migration.py#L87. And at this 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 because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1273336 Title: common.sql.migration.find_migrate_repo never used with an argument. Status in OpenStack Identity (Keystone): New Bug description: If we look attentively to a `find_migrate_repo` usage we will see: $ grep -r find_migrate_repo keystone keystone/common/sql/migration.py:repo_path = find_migrate_repo() keystone/common/sql/migration.py:repo_path = find_migrate_repo() keystone/common/sql/migration.py:repo_path = find_migrate_repo() The function never been used with an argument. What does it mean? This mean that the only line is needed in this function https://github.com/openstack/keystone/blob/master/keystone/common/sql/migration.py#L87. And at this point the function is redundant in the current state. Must be refactored. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1273336/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1259229] [NEW] Undesired migrate repository path caching.
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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
