[Bug 1748123] Re: Policy "os_compute_api:os-server-usage":"rule:admin_or_owner" was deprecated for removal in 17.0.0

ChristianEhrhardt 1748123 at bugs.launchpad.net
Thu Feb 8 09:17:38 UTC 2018

Version https://launchpad.net/ubuntu/+source/nova/2:17.0.0~b3-0ubuntu4
with a fix inbound (allow stderr for now).

Thanks James for the quick response!

You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova in Ubuntu.

  Policy "os_compute_api:os-server-usage":"rule:admin_or_owner" was
  deprecated for removal in 17.0.0

Status in nova package in Ubuntu:

Bug description:
  Nova fails in autopkgtest
  autopkgtest [15:24:49]: test nova-daemons: [-----------------------
  /usr/lib/python2.7/dist-packages/oslo_policy/policy.py:623: UserWarning: Policy "os_compute_api:os-extended-volumes":"rule:admin_or_owner" was deprecated for removal in 17.0.0. Reason: Nova API extension concept has been removed in Pike. Those extensions have their own policies enforcement. As there is no extensions now, "os_compute_api:os-extended-volumes" policy which was added for extensions is not needed any more. Its value may be silently ignored in the future.
    'reason': default.deprecated_reason

  All other tests work well, only nova-daemon is affected

  Testing in a Bionic container showed:
  - 17.0.0~b3-0ubuntu3 "fails" but works

  That means it actually works:
  root at bionic-test:~/nova-17.0.0~b3/debian/tests# echo $?

  But due to lib changes in python the above warning pops out on stderr.
  Since it doesn't have allow-stderr it fails.

  This is NOT due to the libvirt or qemu uploads (tested, is the same
  with old/new versions).

  For now I'll add a badtest for now to avoid blocking everybody with
  this false-positive of a autopkgtest, but I'd ask to adapt nova to
  either add allow-stderr or update nova to handle the deprecation

  By the message it seems it really is something that changed in Pike
  queens should have proper code for that I'd expect?

To manage notifications about this bug go to:

More information about the Ubuntu-openstack-bugs mailing list