yahoo-eng-team team mailing list archive

[David Ripton <dripton@xxxxxxxxxx>]

Unfortunately, this is a side effect of the way nova-manage parses
command-line arguments, and can't easily be fixed without large changes
that are unlikely to be accepted.  (Especially since nova-manage is
semi-deprecated and we try to move functionality over to the API and
novaclient.)  I'm going to close this as wontfix.

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

** Changed in: nova
       Status: New => Won't Fix

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

Title:
  nova-manage db archive_deleted_rows ugly interface for max_rows

Status in OpenStack Compute (Nova):
  Won't Fix

Bug description:
  Downstream bug report
  https://bugzilla.redhat.com/show_bug.cgi?id=960178

  "nova-manage db archive_deleted_rows" originally took an optional
  --max_rows argument (with an invisible default), but this was changed
  to a positional argument to be less magic.  However, the vestigial
  --max_rows option is still there and should be removed.

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