← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1175808] Re: Qpid cannot serialize objects containing strings longer than 65535 characters

 

The code is in oslo-incubator but does need to be synced across to Nova,
so think we should keep a Nova task open

** Tags added: grizzly-backport-potential

** Changed in: oslo
   Importance: Undecided => Critical

** Changed in: nova
       Status: Invalid => Triaged

** Changed in: nova
   Importance: Undecided => Critical

** Also affects: nova/grizzly
   Importance: Undecided
       Status: New

** Changed in: nova/grizzly
       Status: New => Triaged

** Changed in: nova/grizzly
   Importance: Undecided => Critical

-- 
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/1175808

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

Status in OpenStack Compute (Nova):
  Triaged
Status in OpenStack Compute (nova) grizzly series:
  Triaged
Status in Oslo - a Library of Common OpenStack Code:
  In Progress

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/nova/+bug/1175808/+subscriptions