Ask Your Question

How do I resync openstack heat after manually deleting nova host?

asked 2017-08-21 12:20:10 -0500

xrl gravatar image

I had a Heat-managed Nova host put in a bad configuration and I wanted to just recreate the one host (without destroying all the hosts). So I issued a manual delete. I mistakenly thought Heat would do a state-sync and notice the host was gone and recreate it -- but now when rerunning the template against the stack it fails.

Now my heat events read:

prod2nodessdsf02 704ed947-d0fe-4e2a-ab85-988cd5e4d740 0 minutes Update Failed NotFound: resources.prod2nodessdsf02: Instance 704ed947-d0fe-4e2a-ab85-988cd5e4d740 could not be found. (HTTP 404) (Request-ID: req-1be64f7c-1b68-4002-9b44-66f41a57b0d8)

and it bails out of running the template. What should I do now?

edit retag flag offensive close merge delete


You need to comment out the instance (prod2nodessdsf02) in template file and update the stack with new commented out template file (heat stack-update).

Senol Erdogan gravatar imageSenol Erdogan ( 2017-08-26 02:29:33 -0500 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2017-09-19 14:44:11 -0500

zaneb gravatar image

You can tell Heat that the resource is unhealthy, using the openstack stack resource mark unhealthy command. On the next stack update, Heat will create a replacement resource and delete it's original representation of the previous (now gone) server.

In general, this is a better way of handling your initial issue as well (rather than deleting the server using the Nova API).

edit flag offensive delete link more

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



Asked: 2017-08-21 12:20:10 -0500

Seen: 262 times

Last updated: Sep 19 '17