[Yahoo-eng-team] [Bug 1661679] [NEW] Removing ConfigDrive causes network info to fallback to DHCP on reboot
Public bug reported: Using Ubuntu 16.04.1 ppc64le and cloud-init 0.7.7~bzr1256-0ubuntu1~16.04.1 and deploying via Openstack Newton using ConfigDrive datasource. Initial boot of the vm applies the static networking correctly from the config drive, however, if the config drive is removed and the vm is rebooted, the static network info that was applied on initial boot is wiped and replaced with fallback DHCP network. Attaching logs from original boot and then second boot ( where the networking is wrong ). ** Affects: cloud-init Importance: Undecided Status: New ** Attachment added: "Logs" https://bugs.launchpad.net/bugs/1661679/+attachment/4812609/+files/logs.tar -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1661679 Title: Removing ConfigDrive causes network info to fallback to DHCP on reboot Status in cloud-init: New Bug description: Using Ubuntu 16.04.1 ppc64le and cloud-init 0.7.7~bzr1256-0ubuntu1~16.04.1 and deploying via Openstack Newton using ConfigDrive datasource. Initial boot of the vm applies the static networking correctly from the config drive, however, if the config drive is removed and the vm is rebooted, the static network info that was applied on initial boot is wiped and replaced with fallback DHCP network. Attaching logs from original boot and then second boot ( where the networking is wrong ). To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1661679/+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 1627838] [NEW] Context is reset to by ClientRouter in nova/rpc.py
Public bug reported: The following line in the constructor of ClientRouter in nova/rpc.py is resetting the context on the threading.local to an invalid context. self.run_periodic_tasks(nova.context.RequestContext()) Rather than creating a new context here, I believe it should either be: self.run_periodic_tasks(nova.context.RequestContext(overwrite=False)) or from oslo_context import context curr_context = context.get_current() self.run_periodic_tasks(curr_context) Before the call https://ip9-114-192-147.pok.stglabs.ibm.com:9000/v2/cd65f1b0d9f6410c92101ed1211b74ea', u'region': u'RegionOne', u'internalURL': u'http://127.0.0.1:9000/v2/cd65f1b0d9f6410c92101ed1211b74ea', u'publicURL': u'https://X:9000/v2/cd65f1b0d9f6410c92101ed1211b74ea'}], u'type': u'volume', u'name': u'cinder'}], 'tenant': u'cd65f1b0d9f6410c92101ed1211b74ea', 'read_only': False, 'project_id': u'cd65f1b0d9f6410c92101ed1211b74ea', 'user_id': u'0688b01e6439ca32d698d20789d52169126fb41fb1a4ddafcebb97d854e836c9', 'show_deleted': False, 'roles': [u'admin'], 'user_identity': u'0688b01e6439ca32d698d20789d52169126fb41fb1a4ddafcebb97d854e836c9 cd65f1b0d9f6410c92101ed1211b74ea - - -', 'is_admin_project': True, 'read_deleted': u'no', 'request_id': u'req- f5b85c48-a3b5-4fc0-bf36-3cf7c66182ed', 'instance_lock_checked': False, 'user_domain': None, 'user_name': u'root'}> After the call (auth_token, user props, etc. are gone ) ** Affects: nova Importance: Undecided Status: Confirmed ** Tags: newton-rc-potential rpc -- 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/1627838 Title: Context is reset to by ClientRouter in nova/rpc.py Status in OpenStack Compute (nova): Confirmed Bug description: The following line in the constructor of ClientRouter in nova/rpc.py is resetting the context on the threading.local to an invalid context. self.run_periodic_tasks(nova.context.RequestContext()) Rather than creating a new context here, I believe it should either be: self.run_periodic_tasks(nova.context.RequestContext(overwrite=False)) or from oslo_context import context curr_context = context.get_current() self.run_periodic_tasks(curr_context) Before the call https://ip9-114-192-147.pok.stglabs.ibm.com:9000/v2/cd65f1b0d9f6410c92101ed1211b74ea', u'region': u'RegionOne', u'internalURL': u'http://127.0.0.1:9000/v2/cd65f1b0d9f6410c92101ed1211b74ea', u'publicURL': u'https://X:9000/v2/cd65f1b0d9f6410c92101ed1211b74ea'}], u'type': u'volume', u'name': u'cinder'}], 'tenant': u'cd65f1b0d9f6410c92101ed1211b74ea', 'read_only': False, 'project_id': u'cd65f1b0d9f6410c92101ed1211b74ea', 'user_id': u'0688b01e6439ca32d698d20789d52169126fb41fb1a4ddafcebb97d854e836c9', 'show_deleted': False, 'roles': [u'admin'], 'user_identity': u'0688b01e6439ca32d698d20789d52169126fb41fb1a4ddafcebb97d854e836c9 cd65f1b0d9f6410c92101ed1211b74ea - - -', 'is_admin_project': True, 'read_deleted': u'no', 'request_id': u'req- f5b85c48-a3b5-4fc0-bf36-3cf7c66182ed', 'instance_lock_checked': False, 'user_domain': None, 'user_name': u'root'}> After the call (auth_token, user props, etc. are gone ) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1627838/+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 1621138] [NEW] block_device_mappings column is not large enough in table build_requests
Public bug reported: When deploying with several volumes the block_device_mappings column in table build_requests can run out of space causing the below error. 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters Traceback (most recent call last): 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1139, in _execute_context 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters context) 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py", line 450, in do_execute 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters cursor.execute(statement, parameters) 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters File "/usr/lib64/python2.7/site-packages/MySQLdb/cursors.py", line 174, in execute 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters self.errorhandler(self, exc, value) 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters File "/usr/lib64/python2.7/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters raise errorclass, errorvalue 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters DataError: (1406, "Data too long for column 'block_device_mappings' at row 1") ** Affects: nova Importance: Undecided Assignee: Kenneth Burger (burgerk) Status: New ** Changed in: nova Assignee: (unassigned) => Kenneth Burger (burgerk) -- 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/1621138 Title: block_device_mappings column is not large enough in table build_requests Status in OpenStack Compute (nova): New Bug description: When deploying with several volumes the block_device_mappings column in table build_requests can run out of space causing the below error. 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters Traceback (most recent call last): 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1139, in _execute_context 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters context) 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py", line 450, in do_execute 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters cursor.execute(statement, parameters) 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters File "/usr/lib64/python2.7/site-packages/MySQLdb/cursors.py", line 174, in execute 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters self.errorhandler(self, exc, value) 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters File "/usr/lib64/python2.7/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters raise errorclass, errorvalue 2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters DataError: (1406, "Data too long for column 'block_device_mappings' at row 1") To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1621138/+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 1604943] [NEW] non-ASCII chars ( Chinese ) not allowed in Keypair name
Public bug reported: On a create (POST) request on /os-keypairs API, using a non-ASCII character such as Chinese or Japanese characters for the name parameter produces a 400 error return. "POST /v2.1/f60dbb1f1d2e4f8cb2434f0ed1016d97/os-keypairs HTTP/1.1" status: 400 len: 401 time: 0.0861628 Openstack version is mitaka. ** 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/1604943 Title: non-ASCII chars ( Chinese ) not allowed in Keypair name Status in OpenStack Compute (nova): New Bug description: On a create (POST) request on /os-keypairs API, using a non-ASCII character such as Chinese or Japanese characters for the name parameter produces a 400 error return. "POST /v2.1/f60dbb1f1d2e4f8cb2434f0ed1016d97/os-keypairs HTTP/1.1" status: 400 len: 401 time: 0.0861628 Openstack version is mitaka. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1604943/+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 1549428] [NEW] castellan unnecessarily included in requirements.txt
Public bug reported: The castellan dependency is only used for glance/common/signature_utils.get_certificate. This import should be moved into that function and made optional for glance and not a requirement. ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1549428 Title: castellan unnecessarily included in requirements.txt Status in Glance: New Bug description: The castellan dependency is only used for glance/common/signature_utils.get_certificate. This import should be moved into that function and made optional for glance and not a requirement. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1549428/+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 1476770] Re: _translate_from_glance fails with "AttributeError: id" in grenade
I saw this issue as well updating to urllib3 in nova image-show nova/image/glance.py's show() method following is not getting properties image = self._client.call(context, version, 'get', image_id) glance api returns image properties with same case as • X-Image-Meta-Checksum →d41d8cd98f00b204e9800998ecf8427e • X-Image-Meta-Container_format →bare • X-Image-Meta-Created_at →2015-08-13T19:12:26.235339 • X-Image-Meta-Deleted →False • X-Image-Meta-Disk_format →raw • X-Image-Meta-Id →03dc7a38-6b1b-4464-b2b5-7e517a8bbbcc • X-Image-Meta-Is_public →True, etc... So when glance client calls the api, request/adapters.py build_response() , should convert them into case insensitive like x-image-meta-checksum, but this is not happening with new urllib3 response object. They are not converted as expected by the glance client. and then glance client treats this as no properties retrieved for the image. In fact the glance api is returning proper response. But because of this conversion failure, its throwing attribute error. ** Also affects: python-glanceclient Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1476770 Title: _translate_from_glance fails with "AttributeError: id" in grenade Status in Glance: Invalid Status in OpenStack-Gate: Fix Committed Status in oslo.vmware: Fix Released Status in python-glanceclient: New Bug description: http://logs.openstack.org/28/204128/2/check/gate-grenade- dsvm/80607dc/logs/old/screen-n-api.txt.gz?level=TRACE 2015-07-21 17:05:37.447 ERROR nova.api.openstack [req-9854210d-b9fc-47ff-9f00-1a0270266e2a tempest-ServersTestJSON-34270062 tempest-ServersTestJSON-745803609] Caught error: id 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack Traceback (most recent call last): 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/opt/stack/old/nova/nova/api/openstack/__init__.py", line 125, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return req.get_response(self.application) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1317, in send 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack application, catch_exc_info=False) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1281, in call_application 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack app_iter = application(self.environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return resp(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 634, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return self._call_app(env, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 554, in _call_app 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return self._app(env, _fake_start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return resp(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return resp(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/routes/middleware.py", line 136, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack response = self.app(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return resp(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack resp = self.call_func(req, *args, **self.kwargs) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return self.func(req, *args, **kwargs) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack Fi
[Yahoo-eng-team] [Bug 1367342] [NEW] call to _set_instance_error_state is incorrect in do_build_and_run_instance
Public bug reported: nova/compute/manager.py in do_build_and_run_instance Under except exception.RescheduledException as e: ... self._set_instance_error_state(context, instance.uuid) This should be passing instance only not instance.uuid ** 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/1367342 Title: call to _set_instance_error_state is incorrect in do_build_and_run_instance Status in OpenStack Compute (Nova): New Bug description: nova/compute/manager.py in do_build_and_run_instance Under except exception.RescheduledException as e: ... self._set_instance_error_state(context, instance.uuid) This should be passing instance only not instance.uuid To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1367342/+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
