[Bug 1582725] Re: cinder_policy.json action does not match the Cinder policy.json file

James Page james.page at ubuntu.com
Thu Feb 8 10:01:37 UTC 2018

** Also affects: horizon (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: horizon (Ubuntu)
       Status: New => Fix Released

** Also affects: cloud-archive/mitaka
   Importance: Undecided
       Status: New

** Changed in: cloud-archive
       Status: New => Fix Released

** Changed in: cloud-archive/mitaka
       Status: New => Triaged

** Changed in: cloud-archive/mitaka
   Importance: Undecided => Medium

** Changed in: horizon (Ubuntu Xenial)
       Status: New => Triaged

** Changed in: horizon (Ubuntu Xenial)
   Importance: Undecided => Medium

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

  cinder_policy.json action does not match the Cinder policy.json file

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Xenial:

Bug description:
  cinder policies are not in horizon's policy.json
  so unset tab "consistency groups" is enabled by default.

  Affected to Xenial, UCA_Mitaka

  [Test Case]
  1. deploy simple openstack deployments via juju
  2. horizon -> volume -> check if there is consistency groups tab

  after this patch, horizon needs to be restarted. so it is down shortly. this patch is actually config file changed ( and little source code ). so limited affection to behavior it self.


  related commit


  [Original Description]

  The horizon/openstack_dashboard/conf/cinder_policy.json actions do not match the policy action that are used by the Cinder component.
  Cinder uses "volume_extension:volume_actions:upload_public"
  and Horizon policy.json and code uses "volume:upload_to_image"

  This is the only miss match of policy action between the 2 components.
  This also does not allow a user of Cinder and Horizon to update the
  Cinder policy.json and copy it to the Horizon directly and have the
  button function according to Cinder policy.json rules.

  This can be missed as the Cinder policy.json file is update and the
  Horizon file is updated.

  I think that the action that the Horizon code is using should match it
  component that it is supporting.

To manage notifications about this bug go to:

More information about the Ubuntu-openstack-bugs mailing list