[Yahoo-eng-team] [Bug 1480808] [NEW] got an unexpected keyword argument 'exception_checker' when migrate neutron db
Public bug reported: + /usr/bin/neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head Traceback (most recent call last): File /usr/bin/neutron-db-manage, line 10, in module sys.exit(main()) File /usr/lib/python2.7/site-packages/neutron/db/migration/cli.py, line 366, in main CONF.command.func(config, CONF.command.name) File /usr/lib/python2.7/site-packages/neutron/db/migration/cli.py, line 119, in do_upgrade run_sanity_checks(config, revision) File /usr/lib/python2.7/site-packages/neutron/db/migration/cli.py, line 357, in run_sanity_checks script_dir.run_env() File /usr/lib/python2.7/site-packages/alembic/script.py, line 382, in run_env util.load_python_file(self.dir, 'env.py') File /usr/lib/python2.7/site-packages/alembic/util.py, line 241, in load_python_file module = load_module_py(module_id, path) File /usr/lib/python2.7/site-packages/alembic/compat.py, line 79, in load_module_py mod = imp.load_source(module_id, path, fp) File /usr/lib/python2.7/site-packages/neutron/db/migration/alembic_migrations/env.py, line 24, in module from neutron.db.migration.models import head # noqa File /usr/lib/python2.7/site-packages/neutron/db/migration/models/head.py, line 24, in module from neutron.db import address_scope_db # noqa File /usr/lib/python2.7/site-packages/neutron/db/address_scope_db.py, line 22, in module from neutron.extensions import address_scope as ext_address_scope File /usr/lib/python2.7/site-packages/neutron/extensions/address_scope.py, line 19, in module from neutron.api.v2 import base File /usr/lib/python2.7/site-packages/neutron/api/v2/base.py, line 36, in module from neutron import quota File /usr/lib/python2.7/site-packages/neutron/quota/__init__.py, line 28, in module from neutron.quota import resource_registry File /usr/lib/python2.7/site-packages/neutron/quota/resource_registry.py, line 18, in module from neutron.quota import resource File /usr/lib/python2.7/site-packages/neutron/quota/resource.py, line 139, in module class TrackedResource(BaseResource): File /usr/lib/python2.7/site-packages/neutron/quota/resource.py, line 209, in TrackedResource exception_checker=lambda exc: TypeError: __init__() got an unexpected keyword argument 'exception_checker' /usr/lib/python2.7/site-packages/oslo_db/api.py class wrap_db_retry(object): def __init__(self, retry_interval=0, max_retries=0, inc_retry_interval=0, max_retry_interval=0, retry_on_disconnect=False, retry_on_deadlock=False, retry_on_request=False): super(wrap_db_retry, self).__init__() did not contain the param exception_checker ** Affects: neutron Importance: Undecided Assignee: Song Li (lisong-cruise) Status: Invalid ** Changed in: neutron Assignee: (unassigned) = Song Li (lisong-cruise) ** Changed in: neutron Status: New = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1480808 Title: got an unexpected keyword argument 'exception_checker' when migrate neutron db Status in neutron: Invalid Bug description: + /usr/bin/neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head Traceback (most recent call last): File /usr/bin/neutron-db-manage, line 10, in module sys.exit(main()) File /usr/lib/python2.7/site-packages/neutron/db/migration/cli.py, line 366, in main CONF.command.func(config, CONF.command.name) File /usr/lib/python2.7/site-packages/neutron/db/migration/cli.py, line 119, in do_upgrade run_sanity_checks(config, revision) File /usr/lib/python2.7/site-packages/neutron/db/migration/cli.py, line 357, in run_sanity_checks script_dir.run_env() File /usr/lib/python2.7/site-packages/alembic/script.py, line 382, in run_env util.load_python_file(self.dir, 'env.py') File /usr/lib/python2.7/site-packages/alembic/util.py, line 241, in load_python_file module = load_module_py(module_id, path) File /usr/lib/python2.7/site-packages/alembic/compat.py, line 79, in load_module_py mod = imp.load_source(module_id, path, fp) File /usr/lib/python2.7/site-packages/neutron/db/migration/alembic_migrations/env.py, line 24, in module from neutron.db.migration.models import head # noqa File /usr/lib/python2.7/site-packages/neutron/db/migration/models/head.py, line 24, in module from neutron.db import address_scope_db # noqa File /usr/lib/python2.7/site-packages/neutron/db/address_scope_db.py, line 22, in module from neutron.extensions import address_scope as ext_address_scope File /usr/lib/python2.7/site-packages
[Yahoo-eng-team] [Bug 1444940] [NEW] gate-neutron-lbaas-pep8 cannot ignore the # noqa
Public bug reported: when I submit a patch, there is a dynamic import with # noqa but the gate-neutron-lbaas-pep8 cannot ignore the # noqa and report a pep8 problem for the line ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1444940 Title: gate-neutron-lbaas-pep8 cannot ignore the # noqa Status in OpenStack Neutron (virtual network service): New Bug description: when I submit a patch, there is a dynamic import with # noqa but the gate-neutron-lbaas-pep8 cannot ignore the # noqa and report a pep8 problem for the line To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1444940/+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 1442524] Re: Operation not allowed errors when execute db migration when using DB2 for lbaas
it was caused by not import db2 driver in env.py ** Changed in: neutron Status: New = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1442524 Title: Operation not allowed errors when execute db migration when using DB2 for lbaas Status in OpenStack Neutron (virtual network service): Invalid Bug description: when using db2 as the database for neutron, we execute: neutron-db-manage --service lbaas --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini upgrade head faced problem: INFO [alembic.migration] Context impl IBMDBImpl. INFO [alembic.migration] Will assume transactional DDL. INFO [alembic.migration] Context impl IBMDBImpl. INFO [alembic.migration] Will assume transactional DDL. INFO [alembic.migration] Running upgrade - start_neutron_lbaas, start neutron-lbaas chain INFO [alembic.migration] Running upgrade start_neutron_lbaas - lbaasv2, lbaas version 2 api INFO [alembic.migration] Running upgrade lbaasv2 - 4deef6d81931, add provisioning and operating statuses INFO [alembic.migration] Running upgrade 4deef6d81931 - 4b6d8d5310b8, add_index_tenant_id Traceback (most recent call last): File /usr/bin/neutron-db-manage, line 10, in module sys.exit(main()) File /usr/lib/python2.7/site-packages/neutron/db/migration/cli.py, line 238, in main CONF.command.func(config, CONF.command.name) File /usr/lib/python2.7/site-packages/neutron/db/migration/cli.py, line 106, in do_upgrade do_alembic_command(config, cmd, revision, sql=CONF.command.sql) File /usr/lib/python2.7/site-packages/neutron/db/migration/cli.py, line 72, in do_alembic_command getattr(alembic_command, cmd)(config, *args, **kwargs) File /usr/lib/python2.7/site-packages/alembic/command.py, line 165, in upgrade script.run_env() File /usr/lib/python2.7/site-packages/alembic/script.py, line 382, in run_env util.load_python_file(self.dir, 'env.py') File /usr/lib/python2.7/site-packages/alembic/util.py, line 241, in load_python_file module = load_module_py(module_id, path) File /usr/lib/python2.7/site-packages/alembic/compat.py, line 79, in load_module_py mod = imp.load_source(module_id, path, fp) File /usr/lib/python2.7/site-packages/neutron_lbaas/db/migration/alembic_migrations/env.py, line 85, in module run_migrations_online() File /usr/lib/python2.7/site-packages/neutron_lbaas/db/migration/alembic_migrations/env.py, line 76, in run_migrations_online context.run_migrations() File string, line 7, in run_migrations File /usr/lib/python2.7/site-packages/alembic/environment.py, line 742, in run_migrations self.get_context().run_migrations(**kw) File /usr/lib/python2.7/site-packages/alembic/migration.py, line 305, in run_migrations step.migration_fn(**kw) File /usr/lib/python2.7/site-packages/neutron_lbaas/db/migration/alembic_migrations/versions/4b6d8d5310b8_add_index_tenant_id.py, line 38, in upgrade table, ['tenant_id'], unique=False) File string, line 7, in create_index File /usr/lib/python2.7/site-packages/alembic/operations.py, line 1019, in create_index unique=unique, quote=quote, **kw) File /usr/lib/python2.7/site-packages/alembic/ddl/impl.py, line 194, in create_index self._exec(schema.CreateIndex(index)) File /usr/lib/python2.7/site-packages/alembic/ddl/impl.py, line 106, in _exec return conn.execute(construct, *multiparams, **params) File /usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py, line 729, in execute return meth(self, multiparams, params) File /usr/lib64/python2.7/site-packages/sqlalchemy/sql/ddl.py, line 69, in _execute_on_connection return connection._execute_ddl(self, multiparams, params) File /usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py, line 783, in _execute_ddl compiled File /usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py, line 958, in _execute_context context) File /usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/compat/handle_error.py, line 261, in _handle_dbapi_exception e, statement, parameters, cursor, context) File /usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py, line 1155, in _handle_dbapi_exception util.raise_from_cause(newraise, exc_info) File /usr/lib64/python2.7/site-packages/sqlalchemy/util/compat.py, line 199, in raise_from_cause reraise(type(exception), exception, tb=exc_tb) File /usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py, line 951, in _execute_context context) File /usr/lib/python2.7/site-packages/ibm_db_sa/ibm_db.py, line 106, in do_execute cursor.execute(statement, parameters) File /usr/lib64/python2.7/site-packages/ibm_db_dbi.py, line 1335, in execute
[Yahoo-eng-team] [Bug 968696] Re: admin-ness not properly scoped
Admin of one tenant can also create networks, routers and so on in other tenants, and take other actions. It might be a big risk for the security. So I think it also affect the Neutron. ** Also affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/968696 Title: admin-ness not properly scoped Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Identity (Keystone): Confirmed Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): Fix Released Bug description: Fact: Keystone's rbac model grants roles to users on specific tenants, and post-keystone redux, there are no longer global roles. Problem: Granting a user an admin role on ANY tenant grants them unlimited admin-ness throughout the system because there is no differentiation between a scoped admin-ness and a global admin-ness. I don't have a specific solution to advocate, but being an admin on *any* tenant simply *cannot* allow you to administer all of keystone. Steps to reproduce (from Horizon, though you could do this with the CLI, too): 1. User A (existing admin) creates Project B and User B. 2. User A adds User B to Project B with the admin role on Project B. 3. User B logs in and now has unlimited admin rights not only to view things in the dashboard, but to take actions like creating new projects and users, managing existing projects and users, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/968696/+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 1291949] Re: novncproxy logging is not configurable
** Changed in: nova Status: Opinion = In Progress -- 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/1291949 Title: novncproxy logging is not configurable Status in OpenStack Compute (Nova): In Progress Bug description: nova-novncproxy only seems able to log to stdout. The --log- file/logfile flags seem to have no effect, and looking at nova.cmd.novncproxy, it seems that no logging parameters are read. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1291949/+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 1287678] Re: ImportError : No module named config for glance-manage db_syn
I have met the problem too, I think it was a devstack issue. ** Project changed: glance = devstack ** Changed in: devstack Assignee: (unassigned) = Song Li (lisong-cruise) ** Changed in: devstack Status: New = In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1287678 Title: ImportError : No module named config for glance-manage db_syn Status in devstack - openstack dev environments: In Progress Bug description: I'm a new one to use devstack, and download devstack directly by git clone https://github.com/openstack-dev/devstack.git;. But when I execute stack.sh, there is always an error: + /usr/local/bin/glance-manage db_sync Traceback (most recent call last): File /usr/local/bin/glance-manage, line 6, in module from glance.cmd.manage import main File /opt/stack/glance/glance/cmd/manage.py, line 41, in module from oslo.config import cfg From this report, I check /opt/stack/oslo.config. I found there isn't file named cfg! But just setup.cfg. I'm not sure it's a bug or not. I hope it will help you, and wait for your reply. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1287678/+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
