yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

nova-manage is more or less deprecated in place of using the nova apis
when possible except for things you want to do directly against the
database like managing services and doing db migrations.

In Icehouse Steve Kaufer added paging support for nova api so servers
list should having that working, so marking this as invalid in light of
that.

Plus the patch was abandoned.

** Changed in: nova
       Status: In Progress => Invalid

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

Title:
  nova-manage vm list produces monster query

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Marking this as a security vulnerability because this can be used to
  essentially flood the database server and cause an entire Nova MySQL
  database to slow to a crawl.

  This issue was discovered by HP database admins investigating slow
  performance on the Nova database nodes. The DBA was seeing the
  following PROCESSLIST in MySQL:

  http://pastebin.ca/2130819

  With this being the query predominantly running, with a status of
  "Sending data":

  http://pastebin.ca/2130818

  Code in trunk:

  https://github.com/openstack/nova/blob/master/bin/nova-manage#L902

  AFAICT, no limit/marker offset is ever passed to the query, and so the
  command by default lists every VM, with joins to all related tables.

  The  short-term solution would be to put a pagination mechanism into
  nova-manage.

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