yahoo-eng-team team mailing list archive

[OpenStack Hudson <1176164@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/31472
Committed: http://github.com/openstack-infra/config/commit/ba288616a4a40aaebcf1fd6338935ef0cdd05fb9
Submitter: Jenkins
Branch:    master

commit ba288616a4a40aaebcf1fd6338935ef0cdd05fb9
Author: daisy-ycguo <guoyingc@xxxxxxxxxx>
Date:   Mon Jun 3 16:42:53 2013 +0800

    Disable fuzzy matching in transifex automation scripts
    
    Fuzzy matching can cause unexpected problems.
    So add option "--no-fuzzy-matching" to command "python setup.py update_catalog"
    in propose_translation_update and upstream_translation_update scripts.
    
    Bug 1176164
    
    Change-Id: I632d6eb9280ca11883760f17fc4363275692b38b


** Changed in: openstack-ci
       Status: In Progress => Fix Released

-- 
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:
  Fix Released

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