Ah, the question was answered above: We are compiling nova.mo's using babel with the --use-fuzzy option so it was compiling these fuzzy translations. Our workaround is to not compile the fuzzy translations.
I think it's a case of "just don't compile with --use-fuzzy" The question of whether our transifex automation should pass --no-fuzzy- matching to update_catalog is really a question for translators. Does fuzzy matches in the .po file help them? If so, I think we should keep using them. ** Changed in: nova Status: New => Invalid ** Also affects: openstack-ci Importance: Undecided Status: New ** Summary changed: - Tempest fails due to KeyError from fuzzy translations + Consider using update_catalog --no-fuzzy-matching in transifex automation scripts -- 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/1176164 Title: Consider using update_catalog --no-fuzzy-matching in transifex automation scripts Status in OpenStack Compute (Nova): Invalid Status in OpenStack Core Infrastructure: New Bug description: Running tempest on a RHEL 6.3 installation of Havana with this test class: tempest.tests.compute.images.test_images_oneserver.py:ImagesOneServerTestJSON Is hitting this failure: 2013-05-02 17:03:55 ERROR [nova.compute.manager] DB error: ['Traceback (most recent call last):\n', ' File "/usr/lib/python2.6 /site-packages/nova/compute/manager.py", line 920, in _build_instance\n with rt.instance_claim(context, instance, limits):\n', ' File "/usr/lib/python2.6/site- packages/nova/openstack/common/lockutils.py", line 242, in inner\n retval = f(*args, **kwargs)\n', ' File "/usr/lib/python2.6/site- packages/nova/compute/resource_tracker.py", line 103, in instance_claim\n if claim.test(self.compute_node, limits):\n', ' File "/usr/lib/python2.6/site-packages/nova/compute/claims.py", line 120, in test\n can_claim = (self._test_memory(resources, memory_mb_limit) and\n', ' File "/usr/lib/python2.6/site- packages/nova/compute/claims.py", line 138, in _test_memory\n return self._test(type_, unit, total, used, requested, limit)\n', ' File "/usr/lib/python2.6/site-packages/nova/compute/claims.py", line 163, in _test\n LOG.audit(msg % locals(), instance=self.instance)\n', "KeyError: u'total_vcpus'\n"] We're at this level of code for nova: https://github.com/openstack/nova/commit/46a93678e8e49c3c695a47084b012eea88bae969 We've traced the errors to bad translations in nova.po here: https://github.com/openstack/nova/blob/master/nova/locale/en_US/LC_MESSAGES/nova.po#L4215 and here: https://github.com/openstack/nova/blob/master/nova/locale/en_US/LC_MESSAGES/nova.po#L4225 We are compiling nova.mo's using babel with the --use-fuzzy option so it was compiling these fuzzy translations. Our workaround is to not compile the fuzzy translations. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1176164/+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