[Yahoo-eng-team] [Bug 1240349] [NEW] publish_errors cfg option is broken
You have been subscribed to a public bug:
Our nova.conf contains a publish_errors option, which doesn't work
because we don't have the necessary oslo modules:
# publish error events (boolean value)
publish_errors=true
[root@ip9-12-17-141 ˜]# Traceback (most recent call last):
File "/usr/bin/nova-api", line 10, in
sys.exit(main())
File "/usr/lib/python2.6/site-packages/nova/cmd/api.py", line 41, in main
logging.setup("nova")
File "/usr/lib/python2.6/site-packages/nova/openstack/common/log.py", line
372, in setup
_setup_logging_from_conf()
File "/usr/lib/python2.6/site-packages/nova/openstack/common/log.py", line
472, in _setup_logging_from_conf
logging.ERROR)
File "/usr/lib/python2.6/site-packages/nova/openstack/common/importutils.py",
line 40, in import_object
return import_class(import_str)(*args, **kwargs)
File "/usr/lib/python2.6/site-packages/nova/openstack/common/importutils.py",
line 30, in import_class
__import__(mod_str)
ImportError: No module named log_handler
** Affects: nova
Importance: Undecided
Status: New
** Tags: log
--
publish_errors cfg option is broken
https://bugs.launchpad.net/bugs/1240349
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
--
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 1242820] Re: Nova docker virt driver triggers - AttributeError: 'Message' object has no attribute 'format'
** Changed in: oslo
Status: New => Invalid
** Changed in: nova
Status: New => In Progress
** Changed in: nova
Assignee: (unassigned) => Davanum Srinivas (DIMS) (dims-v)
--
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/1242820
Title:
Nova docker virt driver triggers - AttributeError: 'Message' object
has no attribute 'format'
Status in OpenStack Compute (Nova):
In Progress
Status in Oslo - a Library of Common OpenStack Code:
Invalid
Bug description:
Using the nova virt docker driver and when I try to deploy an instance
I get:
2013-10-21 12:18:39.229 20636 ERROR nova.compute.manager
[req-270deff8-b0dc-4a05-9923-417dc5b662db c99d13095fbd4605b36a802fd9539a4a
a03677565e97495fa798fe6cd2628180] [instance:
206bb110-4fa5-4999-be87-9b10951ad5dd] Error: 'Message' object has no attribute
'format'
2013-10-21 12:18:39.229 20636 TRACE nova.compute.manager [instance:
206bb110-4fa5-4999-be87-9b10951ad5dd] Traceback (most recent call last):
2013-10-21 12:18:39.229 20636 TRACE nova.compute.manager [instance:
206bb110-4fa5-4999-be87-9b10951ad5dd] File
"/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1045, in
_build_instance
2013-10-21 12:18:39.229 20636 TRACE nova.compute.manager [instance:
206bb110-4fa5-4999-be87-9b10951ad5dd] set_access_ip=set_access_ip)
2013-10-21 12:18:39.229 20636 TRACE nova.compute.manager [instance:
206bb110-4fa5-4999-be87-9b10951ad5dd] File
"/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1444, in _spawn
2013-10-21 12:18:39.229 20636 TRACE nova.compute.manager [instance:
206bb110-4fa5-4999-be87-9b10951ad5dd] LOG.exception(_('Instance failed to
spawn'), instance=instance)
2013-10-21 12:18:39.229 20636 TRACE nova.compute.manager [instance:
206bb110-4fa5-4999-be87-9b10951ad5dd] File
"/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1430, in _spawn
2013-10-21 12:18:39.229 20636 TRACE nova.compute.manager [instance:
206bb110-4fa5-4999-be87-9b10951ad5dd] block_device_info)
2013-10-21 12:18:39.229 20636 TRACE nova.compute.manager [instance:
206bb110-4fa5-4999-be87-9b10951ad5dd] File
"/usr/lib/python2.6/site-packages/nova/virt/docker/driver.py", line 297, in
spawn
2013-10-21 12:18:39.229 20636 TRACE nova.compute.manager [instance:
206bb110-4fa5-4999-be87-9b10951ad5dd] LOG.info(msg.format(image_name))
2013-10-21 12:18:39.229 20636 TRACE nova.compute.manager [instance:
206bb110-4fa5-4999-be87-9b10951ad5dd] File
"/usr/lib/python2.6/site-packages/nova/openstack/common/gettextutils.py", line
255, in __getattribute__
2013-10-21 12:18:39.229 20636 TRACE nova.compute.manager [instance:
206bb110-4fa5-4999-be87-9b10951ad5dd] return
UserString.UserString.__getattribute__(self, name)
2013-10-21 12:18:39.229 20636 TRACE nova.compute.manager [instance:
206bb110-4fa5-4999-be87-9b10951ad5dd] AttributeError: 'Message' object has no
attribute 'format'
On a boot VM flow.
Based on a tiny bit of poking it appears there is a common
gettextutils method to wrapper message/string access which does not
account for the use of Message.format() as used in the docker virt
driver.
Honestly based on the code I'm running I'm not sure how spawn worked
at all for docker as the use of Message.format() is in the boot
codepath:
296 msg = _('Image name "{0}" does not exist, fetching it...')
297 LOG.info(msg.format(image_name))
This always triggers the no attr message.
I'm not up to speed on the gettextutils wrapper, but I hacked around
this by adding 'format' to the list of ops in gettextutils.py:
def __getattribute__(self, name):
243 # NOTE(mrodden): handle lossy operations that we can't deal with
yet
244 # These override the UserString implementation, since UserString
245 # uses our __class__ attribute to try and build a new message
246 # after running the inner data string through the operation.
247 # At that point, we have lost the gettext message id and can just
248 # safely resolve to a string instead.
249 ops = ['capitalize', 'center', 'decode', 'encode',
250'expandtabs', 'ljust', 'lstrip', 'replace', 'rjust',
'rstrip',
251'strip', 'swapcase', 'title', 'translate', 'upper',
'zfill', 'format']
252 if name in ops:
253 return getattr(self.data, name)
254 else:
255 return UserString.UserString.__getattribute__(self, name)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1242820/+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 1243236] Re: test_keystoneclient inheritance is wrong
Oh wow, I just realized it's a weird and non-obvious way to run the same tests against multiple versions. ** 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/1243236 Title: test_keystoneclient inheritance is wrong Status in OpenStack Identity (Keystone): Invalid Bug description: The test_keystoneclient tests each inherit from each other, but this results in each test-case running all the tests from those in the chain of inheritance. Unless I'm mistaken, this is wrong, they should inherit instead from a common base-class containing only utility functions and no test_* tests. I guess (unless tox/testr does something clever I'm not aware of) this means we're running many of these tests more than once in the gate? To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1243236/+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 1235378] Re: 'image_download' role in v2 causes traceback
[OSSA 2013-027]
** Changed in: ossa
Status: Fix Committed => Fix Released
** Summary changed:
- 'image_download' role in v2 causes traceback
+ [OSSA 2013-027] 'image_download' role in v2 causes traceback
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1235378
Title:
[OSSA 2013-027] 'image_download' role in v2 causes traceback
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Status in Glance folsom series:
Fix Committed
Status in Glance grizzly series:
Fix Released
Status in OpenStack Security Advisories:
Fix Released
Bug description:
If you enable the 'image_download' policy as follows:
{
"context_is_admin": "role:admin",
"download_image": "role:admin", <<<
"default": "",
"manage_image_cache": "role:admin"
}
And attempt to download using the v2 api you get 200 rather than 403 (but,
correctly, no data)
and a stack trace on the server:
6234 DEBUG glance.api.policy [acaf8321-9f3c-439a-8028-46921ea56740
a9befd28bf704839b62aecbf6afacd37 f6e065403d57444aa973fc10c655dedd] Loaded
policy rules: {u'context_is_admin': 'role:admin', u'download_image':
'role:admin', u'default': '@', u'manage_image_cache': 'role:admin'}
6234 DEBUG glance.image_cache [acaf8321-9f3c-439a-8028-46921ea56740
a9befd28bf704839b62aecbf6afacd37 f6e065403d57444aa973fc10c655dedd] Tee'ing
image '42c834df-3b35-4982-aed6-ffa4a44d3778' into cache
6234 DEBUG glance.api.policy [acaf8321-9f3c-439a-8028-46921ea56740
a9befd28bf704839b62aecbf6afacd37 f6e065403d57444aa973fc10c655dedd] Loaded
policy rules: {u'context_is_admin': 'role:admin', u'download_image':
'role:admin', u'default': '@', u'manage_image_cache': 'role:admin'}
6234 DEBUG glance.image_cache.drivers.sqlite
[acaf8321-9f3c-439a-8028-46921ea56740 a9befd28bf704839b62aecbf6afacd37
f6e065403d57444aa973fc10c655dedd] Fetch of cache file failed (You are not
authorized to complete this action.), rolling back by moving
'/opt/stack/data/glance/cache/incomplete/42c834df-3b35-4982-aed6-ffa4a44d3778'
to '/opt/stack/data/glance/cache/invalid/42c834df-3b35-4982-aed6-ffa4a44d3778'
6234 ERROR glance.image_cache [acaf8321-9f3c-439a-8028-46921ea56740
a9befd28bf704839b62aecbf6afacd37 f6e065403d57444aa973fc10c655dedd] You are not
authorized to complete this action.
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache Traceback (most recent
call last):
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache File
"/opt/stack/glance/glance/image_cache/__init__.py", line 238, in cache_tee_iter
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache for chunk in
image_iter:
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache File
"/opt/stack/glance/glance/notifier/__init__.py", line 182, in get_data
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache for chunk in
self.image.get_data():
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache File
"/opt/stack/glance/glance/api/policy.py", line 225, in get_data
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache
self.policy.enforce(self.context, 'download_image', {})
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache File
"/opt/stack/glance/glance/api/policy.py", line 135, in enforce
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache
exception.Forbidden, action=action)
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache File
"/opt/stack/glance/glance/api/policy.py", line 123, in _check
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache return
policy.check(rule, target, credentials, *args, **kwargs)
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache File
"/opt/stack/glance/glance/openstack/common/policy.py", line 183, in check
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache raise exc(*args,
**kwargs)
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache Forbidden: You are not
authorized to complete this action.
2013-10-04 17:34:47.678 6234 TRACE glance.image_cache
6234 DEBUG eventlet.wsgi.server [acaf8321-9f3c-439a-8028-46921ea56740
a9befd28bf704839b62aecbf6afacd37 f6e065403d57444aa973fc10c655dedd] Traceback
(most recent call last):
File "/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py", line 402,
in handle_one_response
for data in result:
File "/opt/stack/glance/glance/image_cache/__init__.py", line 238, in
cache_tee_iter
for chunk in image_iter:
File "/opt/stack/glance/glance/notifier/__init__.py", line 182, in get_data
for chunk in self.image.get_data():
File "/opt/stack/glance/glance/api/policy.py", line 225, in get_data
self.policy.enforce(self.context, 'download_image', {})
File "/opt/stack/glance/glance/api/policy.py", line 135, in enforce
exception.Forbidden, action=action)
File "/opt/stack/glance/glance/api/policy.py", line 123, in _check
return policy.check(rule, tar
[Yahoo-eng-team] [Bug 1243301] [NEW] Changes-since not returning deleted servers
You have been subscribed to a public bug: Based on the OpenStack documentation at http://docs.openstack.org/api /openstack-compute/2/content/ChangesSince.html..."To allow clients to keep track of changes, the changes-since filter displays items that have been recently deleted. Both images and servers contain a DELETED status that indicates that the resource has been removed." This allows OpenStack consumers to determine when images and servers are deleted when using the changes-since support. OpenStack works as documented for images. However, changes-since support in OpenStack Havana may not return deleted servers with a DELETED status. The recreate scenario is as follows: 1) Boot a new server and wait for the boot to complete. 2) Save the current time 3) Use changes-since to get all servers changed since the time saved in step 2. It should be none. 4) Delete the server created in step 1 and wait for the delete to complete. 5) Use changes-since to get all servers changed since the time saved in step 2. It should include the server deleted in step 4 and the server's status should be DELETED. The actual result is that the server is included but its status is ERROR. For the above recreate scenario, the boot failed because no valid host was found. As a result, the server is in ERROR status after step 1. I have not tested with a successful boot. ** Affects: nova Importance: Undecided Status: New -- Changes-since not returning deleted servers https://bugs.launchpad.net/bugs/1243301 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). -- 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 1179007] Re: Migrate build system to pbr
** Changed in: heat-cfntools Milestone: v1.2.4 => None ** Changed in: heat-cfntools Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1179007 Title: Migrate build system to pbr Status in Ceilometer: Fix Released Status in Cinder: Fix Released Status in Python Gearman Interface: New Status in Git Review: Fix Committed Status in Orchestration API (Heat): Fix Released Status in Heat API Instance Tools: Fix Released Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Neutron (virtual network service): Fix Released Status in OpenStack Core Infrastructure: Triaged Status in Oslo - a Library of Common OpenStack Code: Fix Released Status in Python client library for Ceilometer: Fix Committed Status in Python client library for Cinder: Fix Committed Status in Python client library for Glance: Fix Committed Status in Python client library for heat: Fix Released Status in Python client library for Keystone: Fix Released Status in Python client library for Marconi: Fix Committed Status in Python client library for Neutron: Fix Committed Status in Python client library for Nova: Fix Released Status in OpenStack Command Line Client: Fix Committed Status in Python client library for Swift: New Status in OpenStack Object Storage (Swift): Fix Released Status in Trove - Database as a Service: Fix Released Status in Zuul: A project gating system: New Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 openstack.common.setup and openstack.common.version are now in the standalone library pbr. Migrating involves moving build config to setup.cfg, copying in a stub setup.py file, adding pbr and d2to1 to the build depends, removing openstack.common.(setup|version) from the filesystem and from openstack-common.conf and making sure *.egg is in .gitignore. affects ceilometer affects cinder affects git-review affects heat-cfntools affects heat affects keystone affects openstack-ci affects oslo affects python-ceilometerclient affects python-cinderclient affects python-gear affects python-glanceclient affects python-heatclient affects python-keystoneclient affects python-novaclient affects python-openstackclient affects python-quantumclient affects python-swiftclient affects reddwarf affects swift affects zuul -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlGObdUACgkQ2Jv7/VK1RgFlkACgzycOW0/rPvnLaXXX9/oqYA7q kGEAoMaEzGbFEAnsQA6+cEsKIUSMWAPD =W8F0 -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1179007/+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 1172444] Re: migrate all projects to flake8
** Changed in: heat-cfntools Milestone: v1.2.4 => None ** Changed in: heat-cfntools Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1172444 Title: migrate all projects to flake8 Status in Ceilometer: Fix Released Status in Cinder: Fix Released Status in Python Gearman Interface: Fix Released Status in Git Review: Fix Released Status in Orchestration API (Heat): Fix Released Status in Heat API Instance Tools: Fix Released Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Core Infrastructure: Triaged Status in Oslo - a Library of Common OpenStack Code: Fix Released Status in Python client library for Ceilometer: Fix Committed Status in Python client library for Cinder: Fix Committed Status in Python client library for Glance: Fix Committed Status in Python client library for heat: Fix Released Status in Python client library for Keystone: Fix Released Status in Python client library for Neutron: Fix Committed Status in Python client library for Nova: Fix Released Status in OpenStack Command Line Client: Fix Released Status in Python client library for Swift: Fix Released Status in Trove - Database as a Service: Fix Released Status in Zuul: A project gating system: Fix Released Bug description: affects openstack-ci milestone havana status triaged importance medium To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1172444/+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 1207402] Re: neutron should automatically stamp the database version when it is deployed
** Changed in: devstack Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1207402 Title: neutron should automatically stamp the database version when it is deployed Status in devstack - openstack dev environments: Fix Released Status in OpenStack Neutron (virtual network service): In Progress Bug description: When neutron automatically deploys the database schema it does not "stamp" the version. According to neutron/db/migration/README this means that I have to stamp it to manually. Neutron should automatically stamp the version to head when deploys the schema the first time. That way I don't have to determine what version I'm running so that I can do a schema migration. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1207402/+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
