yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


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

** Changed in: nova
       Status: Confirmed => Expired

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

Title:
  nova-manage command when executed by non-root user, should give
  "authorization error" instead of low level database error

Status in OpenStack Compute (nova):
  Expired
Status in nova package in Ubuntu:
  Confirmed

Bug description:
  Version of nova-compute and distribution/package
  (1:2014.1.2-0ubuntu1.1)

  1) Execute below command using "non-root" user.
  ubuntu@mc1:~$ nova-manage flavor list

  It gives below error:

  Command failed, please check log for more info
  2014-09-11 13:43:17.501 12857 CRITICAL nova [req-07bc6065-3ece-4fd5-b478-48d37c63a2c6 None None] OperationalError: (OperationalError) unable to open database file None None

  2) Execute above command using "root" user:
  ubuntu@mc1:~$ sudo su -
  root@mc1:~# nova-manage flavor list
  m1.medium: Memory: 4096MB, VCPUS: 2, Root: 40GB, Ephemeral: 0Gb, FlavorID: 3, Swap: 0MB, RXTX Factor: 1.0, public, ExtraSpecs {}
  m1.tiny: Memory: 512MB, VCPUS: 1, Root: 1GB, Ephemeral: 0Gb, FlavorID: 1, Swap: 0MB, RXTX Factor: 1.0, public, ExtraSpecs {}
  m1.large: Memory: 8192MB, VCPUS: 4, Root: 80GB, Ephemeral: 0Gb, FlavorID: 4, Swap: 0MB, RXTX Factor: 1.0, public, ExtraSpecs {}
  m1.xlarge: Memory: 16384MB, VCPUS: 8, Root: 160GB, Ephemeral: 0Gb, FlavorID: 5, Swap: 0MB, RXTX Factor: 1.0, public, ExtraSpecs {}
  m1.small: Memory: 2048MB, VCPUS: 1, Root: 20GB, Ephemeral: 0Gb, FlavorID: 2, Swap: 0MB, RXTX Factor: 1.0, public, ExtraSpecs {}

  So instead of low level database error, it should give kind of
  "authorization error" to operator or end-user of "nova-manage" CLI.

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