We need to add status that can update the stack

Bug #1538447 reported by space
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
space

Bug Description

  When I create a bay,I also create a stack in the heat.But if I do some operations on the stack,such as "Suspend Stack","Resume Stack" and so on,the stack's status will change to "Resume Complete","Check Complete" or some other status.The stack is in normal operation,but we could't update the bay because the stack's status is not "Create Complete" or "Update Complete".I think it is not friendly to people.

space (fengzhr)
summary: - We need a status that contains the normal status of the stack
+ We need to add status that can update the stack
Changed in magnum:
assignee: nobody → space (fengzhr)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

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

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

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

commit 36a6fde15a022b20f41897555c78c367b0649c24
Author: space <email address hidden>
Date: Wed Jan 27 17:50:04 2016 +0800

    Add more types of status to Bay's status

    Added more types of status which can be updated to Bay's status field:
    'RESUME_COMPLETE'
    'RESTORE_COMPLETE'
    'ROLLBACK_COMPLETE'
    'SNAPSHOT_COMPLETE'
    'CHECK_COMPLETE'
    Added these states so that the bay_update code have better resiliency
    If the user operates the stack,he(she) could still update the bay.

    Change-Id: Ia71ca90742a7e23bbf2c0c9254951db7e06faf28
    Closes-Bug: #1538447

Changed in magnum:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 2.0.0

This issue was fixed in the openstack/magnum 2.0.0 release.

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.