Shouldn't be able to launch instance from syspanel

Bug #952609 reported by Gabriel Hurley on 2012-03-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Medium
Gabriel Hurley

Bug Description

The syspanel instances table has the same "launch" action as the instances table; however this action is inappropriate from a permissions standpoint, and is lacking the ability to specify which tenant the instance is launched into even if you wanted to allow it. The action should be removed from the table.

Changed in horizon:
assignee: nobody → Gabriel Hurley (gabriel-hurley)
importance: Undecided → Medium
milestone: none → essex-rc1
status: New → In Progress

Reviewed: https://review.openstack.org/5219
Committed: http://github.com/openstack/horizon/commit/44f670e1049a0c73fd2f7e7d52caa6e897142b06
Submitter: Jenkins
Branch: master

commit 44f670e1049a0c73fd2f7e7d52caa6e897142b06
Author: Gabriel Hurley <email address hidden>
Date: Sun Mar 11 16:11:38 2012 -0700

    Allows row status to be determined as the aggregate of multiple columns.

    Instances table handles both status columns correctly now. Fixes bug 948419.
    Syspanel instances table no longer has "launch instance" action. Fixes bug 952609.
    Allows ajax-updating for volumes table. Fixes bug 948396.

    Change-Id: I8657c79d0ab7ec5972cc7c4886d7f009a1710876

Changed in horizon:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2012-03-20
Changed in horizon:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in horizon:
milestone: essex-rc1 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers