Ask Your Question
0

stack tags set to null after update failed

asked 2017-06-28 13:48:53 -0600

Tori gravatar image

If i perform a stack update on a stack and the update goes to UPDATE_FAILED for any reason the tags I had associated with that stack are set to null. If i then stack update again and this succeeds the tags are not re-applied and remain null

Any idea how I can avoid this?

edit retag flag offensive close merge delete

Comments

https://bugs.launchpad.net/heat/+filebug

zaneb gravatar imagezaneb ( 2017-06-28 16:19:01 -0600 )edit
add a comment

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-06-28 17:10:39 -0600

Tori gravatar image

updated 2017-06-28 17:12:20 -0600

Bug written:https://bugs.launchpad.net/heat/+bug/1701098 (Link to Bug)

edit flag offensive delete link more

Comments

i don't have the requisite Karma points to post a properly formatted link....

Tori gravatar imageTori ( 2017-06-28 17:13:04 -0600 )edit
add a comment

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2017-06-28 13:48:53 -0600

Seen: 38 times

Last updated: Jun 28 '17

Related questions

How to modify a heat template to update a stack

ERROR: Template not in valid format: while parsing a block mapping

boot from volume with heat resource group

Use Celiometer and Heat to spin up more vm when required

publicURL endpoint for orchestration not found [closed]

Any way to tag hypervisors?

Heat-api startup Error

What is the best way to make condition to "openstack update stack" ?

output stack Heat with java

CFN image for Heat Orchestration