inconsistent use of 'status' values

Bug #1036054 reported by dan wendlandt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Jiajun Liu

Bug Description

the new v2 spec indicates that 'status' should have values of 'ACTIVE', 'ERROR', 'DOWN', and 'BUILD'. Yet it seems like some plugins are still using 'UP'/'DOWN', which is from v1.

dan wendlandt (danwent)
Changed in python-quantumclient:
status: New → Confirmed
tags: added: low-hanging-fruit
affects: python-quantumclient → quantum
Changed in quantum:
milestone: none → folsom-3
importance: Undecided → Medium
dan wendlandt (danwent)
Changed in quantum:
milestone: folsom-3 → folsom-rc1
Jiajun Liu (ljjjustin)
Changed in quantum:
assignee: nobody → ljjjustin (ljjjustin)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to quantum (master)

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

Changed in quantum:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to quantum (master)

Reviewed: https://review.openstack.org/11386
Committed: http://github.com/openstack/quantum/commit/7d29b163fa662abc37b0e3e96c334856d1254c61
Submitter: Jenkins
Branch: master

commit 7d29b163fa662abc37b0e3e96c334856d1254c61
Author: justin ljj <email address hidden>
Date: Wed Aug 15 12:11:56 2012 +0800

    Use a common constant for the port/network 'status' value

    Fixes bug 1036054.

    'status' have four values 'ACTIVE/DOWN/ERROR/BUILD' in v2 spec.
    However, some plugins still using 'UP/DOWN' from v1. In order to
    consistent the use of 'status' value. A common constant file was
    created and modified all plugins to use the same constant value.

    Change-Id: I865dffbe031d9a3e76e52e334db3050a3ef11ed0

Changed in quantum:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in quantum:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in quantum:
milestone: folsom-rc1 → 2012.2
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.