status defined in bay object Status class never be used

Bug #1459104 reported by Eli Qiao
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
Unassigned

Bug Description

    Currently, we defined a status class in bay object file, it will be indicate
    the bay's status(actually, it reuses heat's stack status), but we don't use
    Status anywhere.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/185831
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=b9b3b29f8e980c407b743d236643eece7771915b
Submitter: Jenkins
Branch: master

commit b9b3b29f8e980c407b743d236643eece7771915b
Author: Eli Qiao <email address hidden>
Date: Wed May 27 10:50:06 2015 +0800

    Use the status defined in bay object Status class

    Currently, we defined a status class in bay object file, it will be indicate
    the bay's status(actually, it reuses heat's stack status), but we don't use
    Status anywhere, this patch uses there status defined in Status.

    Closes-Bug: #1459104
    Change-Id: I5ed40bfb93f5246777643912de3e98bc3400bcab

Changed in magnum:
status: New → Fix Committed
Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
status: Fix Committed → Fix Released
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.