floating ip disassociate alert should use floating ip, not floating ip id

Bug #944478 reported by Brian Waldon on 2012-03-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
High
Tihomir Trifonov

Bug Description

Devin Carlen (devcamcar) on 2012-03-02
Changed in horizon:
status: New → Confirmed
importance: Undecided → High
milestone: none → essex-rc1
Changed in horizon:
assignee: nobody → Tihomir Trifonov (ttrifonov)

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

Changed in horizon:
status: Confirmed → In Progress

Reviewed: https://review.openstack.org/4812
Committed: http://github.com/openstack/horizon/commit/d2324b8c35e6874b8ecbba4015eed3f41616ae6d
Submitter: Jenkins
Branch: master

commit d2324b8c35e6874b8ecbba4015eed3f41616ae6d
Author: Tihomir Trifonov <email address hidden>
Date: Thu Mar 1 17:00:26 2012 +0200

    Changed alert message to show actual IP instead of obj_id
    for 'Disassociate IP' action.

    Fixes bug 944478.

    Change-Id: I5a5fbd649ce1235de032c0de846e9f353ebb1576

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