[Yahoo-eng-team] [Bug 1396671] Re: Cannot Migrate OpenStack (Juno) Neutron's database
sqlite is not a supported backend. If you have this problem with mysql then please file a new bug with logs showing what went wrong. ** Tags added: db ** Changed in: neutron Status: Confirmed => 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/1396671 Title: Cannot Migrate OpenStack (Juno) Neutron's database Status in neutron: Invalid Bug description: I am following the Openstack documentation (http://docs.openstack.org/juno/install-guide/install/apt/content/) for installing Openstack on Ubuntu 14.04. At page 59, there is an instruction to finalize the installation of Neutron on the controller node with the following command; # su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade juno" neutron However, I get the following error; # su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade juno" neutron INFO [alembic.migration] Context impl SQLiteImpl. INFO [alembic.migration] Will assume non-transactional DDL. INFO [alembic.migration] Running upgrade havana -> e197124d4b9, add unique constraint to members Traceback (most recent call last): File "/usr/bin/neutron-db-manage", line 10, in sys.exit(main()) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 173, in main CONF.command.func(config, CONF.command.name) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 83, in do_upgrade_downgrade do_alembic_command(config, cmd, revision, sql=CONF.command.sql) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 61, in do_alembic_command getattr(alembic_command, cmd)(config, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/alembic/command.py", line 125, in upgrade script.run_env() File "/usr/lib/python2.7/dist-packages/alembic/script.py", line 203, in run_env util.load_python_file(self.dir, 'env.py') File "/usr/lib/python2.7/dist-packages/alembic/util.py", line 212, in load_python_file module = load_module_py(module_id, path) File "/usr/lib/python2.7/dist-packages/alembic/compat.py", line 58, in load_module_py mod = imp.load_source(module_id, path, fp) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/env.py", line 108, in run_migrations_online() File "/usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/env.py", line 100, in run_migrations_online context.run_migrations() File "", line 7, in run_migrations File "/usr/lib/python2.7/dist-packages/alembic/environment.py", line 688, in run_migrations self.get_context().run_migrations(**kw) File "/usr/lib/python2.7/dist-packages/alembic/migration.py", line 258, in run_migrations change(**kw) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/versions/e197124d4b9_add_unique_constrain.py", line 42, in upgrade local_cols=['pool_id', 'address', 'protocol_port'] File "", line 7, in create_unique_constraint File "/usr/lib/python2.7/dist-packages/alembic/operations.py", line 621, in create_unique_constraint schema=schema, **kw) File "/usr/lib/python2.7/dist-packages/alembic/ddl/sqlite.py", line 21, in add_constraint "No support for ALTER of constraints in SQLite dialect") NotImplementedError: No support for ALTER of constraints in SQLite dialect I am pretty sure that I followed all the steps in the right order. I hope I have not raised a false alarm. Cheers, Simon. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1396671/+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 1396671] Re: Cannot Migrate OpenStack (Juno) Neutron's database
** Changed in: neutron Status: Invalid => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1396671 Title: Cannot Migrate OpenStack (Juno) Neutron's database Status in neutron: Confirmed Bug description: I am following the Openstack documentation (http://docs.openstack.org/juno/install-guide/install/apt/content/) for installing Openstack on Ubuntu 14.04. At page 59, there is an instruction to finalize the installation of Neutron on the controller node with the following command; # su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade juno" neutron However, I get the following error; # su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade juno" neutron INFO [alembic.migration] Context impl SQLiteImpl. INFO [alembic.migration] Will assume non-transactional DDL. INFO [alembic.migration] Running upgrade havana -> e197124d4b9, add unique constraint to members Traceback (most recent call last): File "/usr/bin/neutron-db-manage", line 10, in sys.exit(main()) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 173, in main CONF.command.func(config, CONF.command.name) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 83, in do_upgrade_downgrade do_alembic_command(config, cmd, revision, sql=CONF.command.sql) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 61, in do_alembic_command getattr(alembic_command, cmd)(config, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/alembic/command.py", line 125, in upgrade script.run_env() File "/usr/lib/python2.7/dist-packages/alembic/script.py", line 203, in run_env util.load_python_file(self.dir, 'env.py') File "/usr/lib/python2.7/dist-packages/alembic/util.py", line 212, in load_python_file module = load_module_py(module_id, path) File "/usr/lib/python2.7/dist-packages/alembic/compat.py", line 58, in load_module_py mod = imp.load_source(module_id, path, fp) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/env.py", line 108, in run_migrations_online() File "/usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/env.py", line 100, in run_migrations_online context.run_migrations() File "", line 7, in run_migrations File "/usr/lib/python2.7/dist-packages/alembic/environment.py", line 688, in run_migrations self.get_context().run_migrations(**kw) File "/usr/lib/python2.7/dist-packages/alembic/migration.py", line 258, in run_migrations change(**kw) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/versions/e197124d4b9_add_unique_constrain.py", line 42, in upgrade local_cols=['pool_id', 'address', 'protocol_port'] File "", line 7, in create_unique_constraint File "/usr/lib/python2.7/dist-packages/alembic/operations.py", line 621, in create_unique_constraint schema=schema, **kw) File "/usr/lib/python2.7/dist-packages/alembic/ddl/sqlite.py", line 21, in add_constraint "No support for ALTER of constraints in SQLite dialect") NotImplementedError: No support for ALTER of constraints in SQLite dialect I am pretty sure that I followed all the steps in the right order. I hope I have not raised a false alarm. Cheers, Simon. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1396671/+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 1405726] Re: getting scoped federation token fails when using db2
[Expired for OpenStack Identity (keystone) because there has been no
activity for 60 days.]
** Changed in: keystone
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1405726
Title:
getting scoped federation token fails when using db2
Status in OpenStack Identity (keystone):
Expired
Bug description:
I am using federation.
Following are the commands I executed.
I already have an admin_group created that is gets mapped to when user is
back from doing saml authentication with IdP.
I then do
openstack role add --group admin_group --domain default admin
curl --insecure -X GET https://172.20.14.16:35357/v3/OS-FEDERATION/domains
-H "User-Agent: python-keystoneclient" -H "Content-Type: application/json" -H
"X-Auth-Token: 58e6ceef8dcf4aceb508323e5a2a7c35"
{"domains": [{"links": {"self":
"https://172.20.14.16:5000/v3/domains/default"}, "enabled": true,
"description": "Owns users and tenants (i.e. projects) available on Identity
API v2.", "name": "Default", "id": "default"}], "links": {"self":
"https://172.20.14.16:5000/v3/OS-FEDERATION/domains";, "previous": null, "next":
null}}
openstack role add --group admin_group --project admin admin
curl --insecure -X GET https://172.20.14.16:35357/v3/OS-FEDERATION/projects
-H "User-Agent: python-keystoneclient" -H "Content-Type: application/json" -H
"X-Auth-Token: 58e6ceef8dcf4aceb508323e5a2a7c35"
command to get scoped token*
curl --insecure -X POST POST https://sp.machine:35357/v3/auth/tokens -H
"User-Agent: python-keystoneclient" -H "Content-Type: application/json" -H
"X-Auth-Token: 58e6ceef8dcf4aceb508323e5a2a7c35" -d
'{"auth":{"identity":{"methods":["saml2"],"saml2":{"id":"58e6ceef8dcf4aceb508323e5a2a7c35"}},"scope":{"project":{"domain":
{"id": "default"},"name":"admin"'
This gives an error as follows
2014-12-26 05:58:14.622 26820 ERROR keystone.common.wsgi [-]
(ProgrammingError) ibm_db_dbi::ProgrammingError: SQLNumResultCols failed:
[IBM][CLI Driver][DB2/LINUXX8664] SQL0134N Improper use of a string column,
host variable, constant, or function "ROLE_EXTRA". SQLSTATE=42907 SQLCODE=-134
'SELECT DISTINCT role.id AS role_id, role.name AS role_name, role.extra AS
role_extra \nFROM role, assignment \nWHERE assignment."type" = ? AND
assignment.target_id = ? AND role.id = assignment.role_id AND
assignment.actor_id IN (?)' ('GroupProject',
'c9efdd57ae9d4f5f97d07424c5c4da90', '83ef4a24bf18480f849e903ddfaba7a9')
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi Traceback (most
recent call last):
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/common/wsgi.py", line 207, in
__call__
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi result =
method(context, **params)
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/auth/controllers.py", line 343, in
authenticate_for_token
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi domain_id,
auth_context, trust, metadata_ref, include_catalog)
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/common/manager.py", line 78, in
_wrapper
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi return f(*args,
**kw)
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/token/providers/common.py", line
428, in issue_v3_token
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi domain_id)
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/token/providers/common.py", line
503, in _handle_saml2_tokens
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi group_ids,
project_id, domain_id, user_id)
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/token/providers/common.py", line
199, in _populate_roles_for_groups
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi domain_id)
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/common/manager.py", line 78, in
_wrapper
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi return f(*args,
**kw)
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/assignment/backends/sql.py", line
320, in get_roles_for_groups
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi return
[role.to_dict() for role in query.all()]
2014-12-26 05:58:14.622 26820 TRACE keystone.common.wsgi File
"/usr/lib64/python2.6/site-packages/sqlalchemy/orm/query.py", line 2115, in all
2014-1
[Yahoo-eng-team] [Bug 1496219] Re: get image error when boot a instance
[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.] ** Changed in: nova Status: Incomplete => Expired -- 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/1496219 Title: get image error when boot a instance Status in OpenStack Compute (nova): Expired Bug description: 2015-09-16 11:26:10.018 DEBUG nova.quota [req-4d4a1b1e-3ea3-41bd-b0d4-8b3adf2a1fd0 admin admin] Getting all quota usages for project: 457fcc6f0fb049a89bef6271495788c6 from (pid=5839) get_project_quotas /opt/stack/nova/nova/quota.py:290 2015-09-16 11:26:10.030 INFO nova.osapi_compute.wsgi.server [req-4d4a1b1e-3ea3-41bd-b0d4-8b3adf2a1fd0 admin admin] 10.0.10.50 "GET /v2.1/457fcc6f0fb049a89bef6271495788c6/limits?reserved=1 HTTP/1.1" status: 200 len: 779 time: 0.0331810 ^C [stack@devstack logs]$ less -R n-api.log.2015-09-15-171330 2015-09-16 11:26:09.816 ERROR nova.api.openstack.extensions [req-27b137d8-77da-4082-8553-05598efff073 admin admin] Unexpected exception in API method 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions Traceback (most recent call last): 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/api/openstack/extensions.py", line 478, in wrapped 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions return f(*args, **kwargs) 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/api/validation/__init__.py", line 73, in wrapper 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions return func(*args, **kwargs) 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/api/openstack/compute/servers.py", line 597, in create 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions **create_kwargs) 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/hooks.py", line 149, in inner 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions rv = f(*args, **kwargs) 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/compute/api.py", line 1557, in create 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions check_server_group_quota=check_server_group_quota) 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/compute/api.py", line 1139, in _create_instance 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions image_id, boot_meta = self._get_image(context, image_href) 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/compute/api.py", line 849, in _get_image 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions image = self.image_api.get(context, image_href) 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/image/api.py", line 93, in get 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions show_deleted=show_deleted) 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/image/glance.py", line 320, in show 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions include_locations=include_locations) 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/image/glance.py", line 497, in _translate_from_glance 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions include_locations=include_locations) 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/image/glance.py", line 559, in _extract_attributes 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions queued = getattr(image, 'status') == 'queued' 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/glanceclient/openstack/common/apiclient/base.py", line 490, in __getattr__ 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions self.get() 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/glanceclient/openstack/common/apiclient/base.py", line 508, in get 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions new = self.manager.get(self.id) 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/glanceclient/openstack/common/apiclient/base.py", line 493, in __getattr__ 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions raise AttributeError(k) 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions AttributeError: id 2015-09-16 11:26:09.816 TRACE nova.api.openstack.extensions 2015-09-16 11:26:09.817 INFO nova.api.openstack.wsgi [req-27b137d8-77da-4082-8553-05598efff073 admin admin] HTTP exception thrown: Unexpected API Error. Please report this at http:/
[Yahoo-eng-team] [Bug 1516489] [NEW] networking-midonet stable/kilo release request
Public bug reported: please push 2015.1.1 tag on the tip of stable/kilo. namely, commit bcdc794fe969041b55e6731e48e38c12cda45f1e . ** Affects: networking-midonet Importance: High Status: New ** Affects: neutron Importance: Undecided Status: New ** Tags: release-subproject ** Also affects: neutron Importance: Undecided Status: New ** Tags added: release-subproject ** Changed in: networking-midonet Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1516489 Title: networking-midonet stable/kilo release request Status in networking-midonet: New Status in neutron: New Bug description: please push 2015.1.1 tag on the tip of stable/kilo. namely, commit bcdc794fe969041b55e6731e48e38c12cda45f1e . To manage notifications about this bug go to: https://bugs.launchpad.net/networking-midonet/+bug/1516489/+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 1504641] Re: Listing volumes respects osapi_max_limit but does not provide a link to the next element
Tempest will validate volume list response body.
It didn't accept unexpected attribute volumes_links.
We need to add volumes_links attribute in tempest first.
** Also affects: tempest
Importance: Undecided
Status: New
** Changed in: tempest
Assignee: (unassigned) => Chung Chih, Hung (lyanchih)
--
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/1504641
Title:
Listing volumes respects osapi_max_limit but does not provide a link
to the next element
Status in OpenStack Compute (nova):
In Progress
Status in tempest:
In Progress
Bug description:
When GETting os-volumes, the returned list of volumes respects the
osapi_max_limit configuration parameter but does not provide a link to
the next element in the list. For example, with two volumes configured
and osapi_max_limit set to 1, GETting volumes results in the
following:
{
"volumes": [
{
"attachments": [
{}
],
"availabilityZone": "nova",
"createdAt": "2015-10-09T18:12:04.00",
"displayDescription": null,
"displayName": null,
"id": "08792e26-204b-4bb9-8e9b-0e37331de51c",
"metadata": {},
"size": 1,
"snapshotId": null,
"status": "error",
"volumeType": "lvmdriver-1"
}
]
}
Unsetting osapi_max_limit results in both volumes being listed:
{
"volumes": [
{
"attachments": [
{}
],
"availabilityZone": "nova",
"createdAt": "2015-10-09T18:12:04.00",
"displayDescription": null,
"displayName": null,
"id": "08792e26-204b-4bb9-8e9b-0e37331de51c",
"metadata": {},
"size": 1,
"snapshotId": null,
"status": "error",
"volumeType": "lvmdriver-1"
},
{
"attachments": [
{}
],
"availabilityZone": "nova",
"createdAt": "2015-10-09T18:12:00.00",
"displayDescription": null,
"displayName": null,
"id": "5cf46cd2-8914-4ffd-9037-abd53c55ca76",
"metadata": {},
"size": 1,
"snapshotId": null,
"status": "error",
"volumeType": "lvmdriver-1"
}
]
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1504641/+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 1318528] Re: DHCP agent creates new instance of driver for each action
I would set the status to opinion based on comment #15. ** Changed in: neutron Status: In Progress => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1318528 Title: DHCP agent creates new instance of driver for each action Status in neutron: Opinion Bug description: Working on rootwrap daemon [0] I've found out that DCHP agent asks for root_helper too often. [1] shows traceback for each place where get_root_helper is being called. It appeared that in [2] DHCP agent creates an instance of driver class for every single action it needs to run. That involves both lots of initialization code and very expensive dynamic import_object routine being run. [2] shows that the only thing that changes between driver instances is a network. I suggest we make network an argument for every action instead to avoid expensive dynamic driver instantiation. Links: [0] https://review.openstack.org/84667 [1] http://logs.openstack.org/67/84667/20/check/check-tempest-dsvm-neutron/3a7768e/logs/screen-q-dhcp.txt.gz?level=INFO [2] https://github.com/openstack/neutron/blob/master/neutron/agent/dhcp_agent.py#L122 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1318528/+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 1516479] [NEW] pillow installed error when run 'tox -e py27' in neutron-spec
Public bug reported:
not sure it's a bug, just list here.
in neutron-spec master branch, run
#tox -e py27 -vvv -r
will get a installation error like below, seems lack of some jpeg support
and work around in my ubuntu 12.04 64bit host is
#sudo ln -s /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib
#sudo ln -s /usr/lib/x86_64-linux-gnu/libfreetype.so /usr/lib
#sudo ln -s /usr/lib/x86_64-linux-gnu/libz.so /usr/lib
#apt-get install libjpeg-dev
===
writing manifest file 'Pillow.egg-info/SOURCES.txt'
copying PIL/OleFileIO-README.md -> build/lib.linux-x86_64-2.7/PIL
running build_ext
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-build-tLnh3m/Pillow/setup.py", line 767, in
zip_safe=not debug_build(),
File "/usr/lib/python2.7/distutils/core.py", line 152, in setup
dist.run_commands()
File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File
"/opt/stack/neutron-specs/.tox/py27/local/lib/python2.7/site-packages/wheel/bdist_wheel.py",
line 175, in run
self.run_command('build')
File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "/usr/lib/python2.7/distutils/command/build.py", line 128, in run
self.run_command(cmd_name)
File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "/usr/lib/python2.7/distutils/command/build_ext.py", line 339, in run
self.build_extensions()
File "/tmp/pip-build-tLnh3m/Pillow/setup.py", line 515, in build_extensions
% (f, f))
ValueError: --enable-jpeg requested but jpeg not found, aborting.
** Affects: neutron
Importance: Undecided
Assignee: yalei wang (yalei-wang)
Status: New
** Changed in: neutron
Assignee: (unassigned) => yalei wang (yalei-wang)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1516479
Title:
pillow installed error when run 'tox -e py27' in neutron-spec
Status in neutron:
New
Bug description:
not sure it's a bug, just list here.
in neutron-spec master branch, run
#tox -e py27 -vvv -r
will get a installation error like below, seems lack of some jpeg support
and work around in my ubuntu 12.04 64bit host is
#sudo ln -s /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib
#sudo ln -s /usr/lib/x86_64-linux-gnu/libfreetype.so /usr/lib
#sudo ln -s /usr/lib/x86_64-linux-gnu/libz.so /usr/lib
#apt-get install libjpeg-dev
===
writing manifest file 'Pillow.egg-info/SOURCES.txt'
copying PIL/OleFileIO-README.md -> build/lib.linux-x86_64-2.7/PIL
running build_ext
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-build-tLnh3m/Pillow/setup.py", line 767, in
zip_safe=not debug_build(),
File "/usr/lib/python2.7/distutils/core.py", line 152, in setup
dist.run_commands()
File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File
"/opt/stack/neutron-specs/.tox/py27/local/lib/python2.7/site-packages/wheel/bdist_wheel.py",
line 175, in run
self.run_command('build')
File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "/usr/lib/python2.7/distutils/command/build.py", line 128, in run
self.run_command(cmd_name)
File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "/usr/lib/python2.7/distutils/command/build_ext.py", line 339, in run
self.build_extensions()
File "/tmp/pip-build-tLnh3m/Pillow/setup.py", line 515, in
build_extensions
% (f, f))
ValueError: --enable-jpeg requested but jpeg not found, aborting.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1516479/+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://
[Yahoo-eng-team] [Bug 1516469] [NEW] endpoints not show correctly when using "endpoint_filter.sql" as catalog's backend driver
Public bug reported:
If the endpoint group project association was created, and set
"endpoint_filter.sql" as catalog's backend driver. All of the endpoints
associated with the project and match the criterion defined in the
"endpoint group" should be given after a project scoped token was
return.
But currently, those endpoints can *only* be show if using call
`list_endpoints_for_project` API explictly but cannot get back when the
project scoped token was issued.
Steps to reproduce this issue.
-Create endpoint group.
$curl -g -i -X POST http://10.239.48.36:5000/v3/OS-EP-
FILTER/endpoint_groups -H "X-Auth-
Token:a85e07129aa54f61a46395543a3146af" -H "Content-Type:
application/json" -d '{"endpoint_group": {"description": "endpoint group
description", "filters": {"interface": "admin"}, "name":
"endpoint_group_name"}}'
- Create endpoint_group project association
$curl -g -i -X PUT http://10.239.48.36:5000/v3/OS-EP-
FILTER/endpoint_groups/ea1af6e153bf4b87a88b5962de8cdae8/projects/927e252fb44d4b5cac9d4fb24d85be41
-H "X-Auth-Token:a85e07129aa54f61a46395543a3146af" -H "Content-Type:
application/json"
- Get endpoint for the project
$curl -g -i -X GET
http://10.239.48.36:5000/v3/OS-EP-FILTER/projects/927e252fb44d4b5cac9d4fb24d85be41/endpoints
-H "X-Auth-Token:a85e07129aa54f61a46395543a3146af" -H "Content-Type:
application/json"
...
{
"endpoints": [
{
"region_id": "RegionOne",
"links": {
"self":
"http://10.239.48.36:5000/v3/endpoints/3f6fb8738db8427a997dbcc791b7901d";
},
"url": "http://10.239.48.36:8773/";,
"region": "RegionOne",
"enabled": true,
"interface": "admin",
"service_id": "a3338a6847e94766831ea7d9d43598cc",
"id": "3f6fb8738db8427a997dbcc791b7901d"
},
{
"region_id": "RegionOne",
"links": {
"self":
"http://10.239.48.36:5000/v3/endpoints/dd69f161f8a24612a7ffe796b45b8cd2";
},
"url": "http://10.239.48.36:8774/v2.1/$(tenant_id)s",
"region": "RegionOne",
"enabled": true,
"interface": "admin",
"service_id": "a147aa8896c4429aacf0f2eefd39098e",
"id": "dd69f161f8a24612a7ffe796b45b8cd2"
},
{
"region_id": "RegionOne",
"links": {
"self":
"http://10.239.48.36:5000/v3/endpoints/0d70f9fd5a85446c99fee79388adf9dc";
},
"url": "http://10.239.48.36:9292";,
"region": "RegionOne",
"enabled": true,
"interface": "admin",
"service_id": "4c367805e2a147589a14310d1486ab01",
"id": "0d70f9fd5a85446c99fee79388adf9dc"
},
{
"region_id": null,
"links": {
"self":
"http://10.239.48.36:5000/v3/endpoints/5be3023ddf984fcf942b2a396eb0167b";
},
"url": "http://127.0.0.0:20";,
"region": null,
"enabled": true,
"interface": "internal",
"service_id": "69da5bbf65aa4565b9833655075e7a8a",
"id": "5be3023ddf984fcf942b2a396eb0167b"
},
{
"region_id": "RegionOne",
"links": {
"self":
"http://10.239.48.36:5000/v3/endpoints/9393be9c7eda41d89a28f2ffb486dc7c";
},
"url": "http://10.239.48.36:35357/v2.0";,
"region": "RegionOne",
"enabled": true,
"interface": "admin",
"service_id": "ef49d941aed34d39b8b49fce27c83a50",
"id": "9393be9c7eda41d89a28f2ffb486dc7c"
},
{
"region_id": "RegionOne",
"links": {
"self":
"http://10.239.48.36:5000/v3/endpoints/151b9f8b132f4c26a562872e09389a69";
},
"url": "http://10.239.48.36:8774/v2/$(tenant_id)s",
"region": "RegionOne",
"enabled": true,
"interface": "admin",
"service_id": "8bb4bdc9fcac4fb5bec4f6779268f0d0",
"id": "151b9f8b132f4c26a562872e09389a69"
},
{
"region_id": "RegionOne",
"links": {
"self":
"http://10.239.48.36:5000/v3/endpoints/bff53486b72c44e9b00cf69184b66ce9";
},
"url": "http://10.239.48.36:";,
"region": "RegionOne",
"enabled": true,
"interface": "admin",
"service_id": "69da5bbf65aa4565b9833655075e7a8a",
"id": "bff53486b72c44e9b00cf69184b66ce9"
},
{
"region_id": "RegionOne",
"links": {
"self":
"http://10.239.48.36:5000/v3/endpoints/d0ee548da623477eb73b60018c3e5ab8";
},
"url": "http://10.239.48.36:8776/v1/$(tenant_id)s",
"region": "RegionOne",
"enabled": true,
"interface": "admin",
"service_id": "928eb1b536464e238e573284760
[Yahoo-eng-team] [Bug 1516468] [NEW] miss the testcase for caching to get_catalog/get_v3_catalog in endpoint filter extension
Public bug reported: With the patch [1] got merged, keystone has the ablity to cache catalog/v3 catalog, and will invalidate the cache when there is any changes about the catalog, i.e. add_endpoint_to_project, remove_endpoint_from_project. But the testcase was missed there, this means there is no testcase covered in keystone even the API in the Manager layer was not defined correctly [2]. The bug will focus on `add_endpoint_to_project` and `remove_endpoint_from_project` and leave `add_endpoint_group_to_project` and `remove_endpoint_group_from_project` as it is, this is beacuse these two API should impact the endpoints in theory but it's not in practice. So, add some testcase to test its impact on catalog is impossible. There should be anothor bug filed and testcase will be added when that bug was fixed. [1] https://review.openstack.org/#/c/215212/ [2] https://review.openstack.org/#/c/243951/ ** Affects: keystone Importance: Undecided Assignee: Dave Chen (wei-d-chen) Status: New ** Description changed: With the patch [1] got merged, keystone has the ablity to cache catalog/v3 catalog, and will invalidate the cache when there is any changes about the catalog, i.e. add_endpoint_to_project, remove_endpoint_from_project. But the testcase was missed there, this means there is no testcase covered in keystone even the API in the Manager layer was not defined correctly [2]. - The bug will focus on `add_endpoint_to_project` and `remove_endpoint_from_project` and leave `add_endpoint_group_to_project` - and `remove_endpoint_group_from_project` as it is, this is beacuse these two should be impact the endpoints but in theory but it's not in practice. So, add some testcase to test it impact catalog is impossible. There should be anthor bug filed and will add the testcase when that bug was fixed. + and `remove_endpoint_group_from_project` as it is, this is beacuse these two API should impact the endpoints in theory but it's not in practice. So, add some testcase to test its impact on catalog is impossible. There should be anothor bug filed and testcase will be added when that bug was fixed. [1] https://review.openstack.org/#/c/215212/ [2] https://review.openstack.org/#/c/243951/ ** Changed in: keystone Assignee: (unassigned) => Dave Chen (wei-d-chen) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1516468 Title: miss the testcase for caching to get_catalog/get_v3_catalog in endpoint filter extension Status in OpenStack Identity (keystone): New Bug description: With the patch [1] got merged, keystone has the ablity to cache catalog/v3 catalog, and will invalidate the cache when there is any changes about the catalog, i.e. add_endpoint_to_project, remove_endpoint_from_project. But the testcase was missed there, this means there is no testcase covered in keystone even the API in the Manager layer was not defined correctly [2]. The bug will focus on `add_endpoint_to_project` and `remove_endpoint_from_project` and leave `add_endpoint_group_to_project` and `remove_endpoint_group_from_project` as it is, this is beacuse these two API should impact the endpoints in theory but it's not in practice. So, add some testcase to test its impact on catalog is impossible. There should be anothor bug filed and testcase will be added when that bug was fixed. [1] https://review.openstack.org/#/c/215212/ [2] https://review.openstack.org/#/c/243951/ To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1516468/+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 1046121] Re: dhcp should never be enabled for a router external net
Technically speaking, nothing disallows to deploy vms on ext-nets even if i doubt that's the aim of ext-nets. According to the discussion, i update the bug status to invalid ** Changed in: neutron Status: Confirmed => 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/1046121 Title: dhcp should never be enabled for a router external net Status in neutron: Invalid Status in openstack-manuals: Confirmed Bug description: it doesn't make sense in the existing model, as the router IPs and the floating IPs allocated from an external net never make DHCP requests. I don't believe there is any significant additional harm caused by this though, other than unneeded CPU churn from DHCP agent and dnsmasq, and a burned IP address allocated for a DHCP port. One tricky issue is that DHCP is enabled by default, so the question is whether we should fail if the user does not explicitly disable it when creating a network, or if we should just automatically set it to False. Unfortunately, I don't think we can tell the difference between a this value default to true and it being explicitly set to true, so it seems that if we want to prevent it from being set to true in the API, we should require it to be set to False. We also need to prevent it from being set to True on an update. Another option would be to ignore the value set in the API and just have the DHCP agent ignore networks for which router:external =True. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1046121/+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 1465922] Re: Password visible in clear text in keystone.log when user created and keystone debug logging is enabled
We would typically issue an OSSN for such behaviour, it's somewhat
boilerplate but it's important to document the issue, particularly as a
number of production workloads run in debug mode.
I also think it's interesting that Bandit didn't catch this, it's pretty
good at finding these sorts of issues.
** Also affects: bandit
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1465922
Title:
Password visible in clear text in keystone.log when user created and
keystone debug logging is enabled
Status in Bandit:
New
Status in OpenStack Identity (keystone):
Fix Released
Status in OpenStack Identity (keystone) juno series:
Fix Committed
Status in OpenStack Identity (keystone) kilo series:
Fix Released
Status in OpenStack Security Advisory:
Won't Fix
Bug description:
grep CLEARTEXTPASSWORD keystone.log
2015-06-16 06:44:39.770 20986 DEBUG keystone.common.controller [-]
RBAC: Authorizing identity:create_user(user={u'domain_id': u'default',
u'password': u'CLEARTEXTPASSWORD', u'enabled': True,
u'default_project_id': u'0175b43419064ae38c4b74006baaeb8d', u'name':
u'DermotJ'}) _build_policy_check_credentials /usr/lib/python2.7/site-
packages/keystone/common/controller.py:57
Issue code:
https://github.com/openstack/keystone/blob/master/keystone/common/controller.py#L57
LOG.debug('RBAC: Authorizing %(action)s(%(kwargs)s)', {
'action': action,
'kwargs': ', '.join(['%s=%s' % (k, kwargs[k]) for k in kwargs])})
Shadow the values of sensitive fields like 'password' by some
meaningless garbled text like "X" is one way to fix.
Well, in addition to this, I think we should never pass the 'password'
with its original value along the code and save it in any persistence,
instead we should convert it to a strong hash value as early as
possible. With the help of a good hash system, we never have to need
the original value of the password, right?
To manage notifications about this bug go to:
https://bugs.launchpad.net/bandit/+bug/1465922/+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 1516387] [NEW] Duplicated functions in agent/utils and common/utils
Public bug reported: Both modules have "replace_file" functions. It should be unified and just one method left. ** 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/1516387 Title: Duplicated functions in agent/utils and common/utils Status in neutron: New Bug description: Both modules have "replace_file" functions. It should be unified and just one method left. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1516387/+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
