yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: heat
       Status: Fix Committed => Fix Released

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: neutron
       Status: Fix Committed => Fix Released

** Changed in: oslo
       Status: Fix Committed => Fix Released

** Changed in: oslo
    Milestone: None => havana-2

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1175808

Title:
  Qpid cannot serialize objects containing strings longer than 65535
  characters

Status in Orchestration API (Heat):
  Fix Released
Status in OpenStack Neutron (virtual network service):
  Fix Released
Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) grizzly series:
  Fix Committed
Status in Oslo - a Library of Common OpenStack Code:
  Fix Released

Bug description:
  Qpid has a limitation where it cannot serialize a Python dict
  containing a string longer than 65535 characters.  This can result in
  problems when making a conductor call that returns a large structure -
  for example, instance_get_all_by_host on one of my systems returns 38
  instances, which when serialized as JSON is too long for Qpid to
  handle.

  There's a discussion of the limitation here:
  https://issues.apache.org/jira/browse/QPID-4583

  I believe the best fix here is to wrap the string in a buffer as
  suggested in the link above.  This works fine on my local system and
  seems to fix the problem (note: I haven't tested against RabbitMQ yet,
  and right now I put the change in common code so that will need to be
  done).  However, that will be a backward compatibility breaking change
  because it will need to be handled differently on the receiving end as
  well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/heat/+bug/1175808/+subscriptions