target info is always None when policy_check is called

Bug #1600150 reported by Kenji Ishii
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
High
Kenji Ishii

Bug Description

Policy check method is configured in openstack_dashboard/settings.py (POLICY_CHECK_FUNCTION).
At the moment, when we call this method, target info will be always None.
Therefore, it cannot do policy check correctly.

Kenji Ishii (ken-ishii)
Changed in horizon:
assignee: nobody → Kenji Ishii (ken-ishii)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/339409

Changed in horizon:
status: New → In Progress
Changed in horizon:
milestone: none → newton-2
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/339409
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=712204e3587d9b0fd5d4f55b1aa2f4e4ee71d896
Submitter: Jenkins
Branch: master

commit 712204e3587d9b0fd5d4f55b1aa2f4e4ee71d896
Author: Kenji Ishii <email address hidden>
Date: Fri Jul 8 17:50:23 2016 +0900

    Fix the issue that it cannot do a policy check correctly

    At the moment, when we do a policy check, target info is always
    None even if we set these info.
    Therefore, in some case, policy check doesn't work well.
    This patch will fix it.

    Change-Id: I454b37f9709c246010292b950fcce38c3d2ad0f4
    Closes-Bug: #1600150

Changed in horizon:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/horizon 10.0.0.0b2

This issue was fixed in the openstack/horizon 10.0.0.0b2 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.