Ask Your Question

Revision history [back]

stack-check checks each of the resources to make sure they're still valid (in practice this means they haven't been deleted, and aren't in an error state). If any resources fail this check they'll be put into a CHECK_FAILED state, and like any other resources in a FAILED state they'll get replaced on the next stack update.

Evidently this command shouldn't be used while a stack is suspended - both because some suspended resources will fail the check, and because the resume code expects resources to be in a SUSPEND_COMPLETE state. That Heat allows it and it fails is definitely a bug.