Wrong stack-restore behavior

Bug #1430673 reported by huangtianhua
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Medium
huangtianhua
Kilo
Fix Released
Undecided
Unassigned

Bug Description

1. create a stack with a nova server, and pass parameter -P name=old for server name
2. stack in CREATE_COMPLETE, nova server in active and has the name 'old'
3. snapshot for the stack
4. update the stack with the server name 'update'
5. stack updated successful, and the nova server has the new name 'update'
6. restore the stack with the snapshot
7. there are two problems:
   first, a new server will be created, and the old server be deleted, seems enter the updateReplacement flow.
   second, the new server with the name 'update', expected with the name 'old'

Changed in heat:
assignee: nobody → huangtianhua (huangtianhua)
description: updated
description: updated
Angus Salkeld (asalkeld)
Changed in heat:
status: New → Triaged
importance: Undecided → High
milestone: none → kilo-rc1
Angus Salkeld (asalkeld)
Changed in heat:
milestone: kilo-rc1 → next
tags: added: kilo-rc-potential
Changed in heat:
importance: High → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (master)

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

Changed in heat:
status: Triaged → In Progress
Revision history for this message
huangtianhua (huangtianhua) wrote :

The first problem of server replacement, after changing the property 'image_update_policy' to 'REBUILD', it will be ok.
For cinder volume restore may has the same problem, will propose patch for it later.

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

Reviewed: https://review.openstack.org/171533
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=3a5d124d5679ee56bfa4cb9b26e3ff0bf55656ad
Submitter: Jenkins
Branch: master

commit 3a5d124d5679ee56bfa4cb9b26e3ff0bf55656ad
Author: huangtianhua <email address hidden>
Date: Wed Apr 8 17:05:22 2015 +0800

    Use snapshot's environment when stack restore

    Using snapshot's enviroment instead of current stack's
    enviroment when stack restore.

    Change-Id: I7becfbe4b970820bd374560d00fa6f661a85bdab
    Closes-Bug: #1430673

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
tags: removed: kilo-rc-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (stable/kilo)

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/179693

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to heat (stable/kilo)

Reviewed: https://review.openstack.org/179693
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=d2e70e43b437b99bac6b846ee66a39ce9ac1f831
Submitter: Jenkins
Branch: stable/kilo

commit d2e70e43b437b99bac6b846ee66a39ce9ac1f831
Author: huangtianhua <email address hidden>
Date: Wed Apr 8 17:05:22 2015 +0800

    Use snapshot's environment when stack restore

    Using snapshot's enviroment instead of current stack's
    enviroment when stack restore.

    Change-Id: I7becfbe4b970820bd374560d00fa6f661a85bdab
    Closes-Bug: #1430673
    (cherry picked from commit 3a5d124d5679ee56bfa4cb9b26e3ff0bf55656ad)

tags: added: in-stable-kilo
Changed in heat:
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.