Description of problem: Since I knew the scale up of the nodes via Director was going to fail (scheduling errors) I ctrl+ced out of the deeployment command and restarted heat-engine. Ideally this should set the stack in UPDATE_FAILED state, so that I can retry scaling. However, the stack continues to be stuck in UPDATE_IN_PROGRESS state. Version-Release number of selected component (if applicable): 11 How reproducible: 100% on the stack I tried Steps to Reproduce: 1. Deploy overcloud stack 2. Start scaling up stack 3. Exit from scale up and restart heat-engine Actual results: Stack is stuck in UPDATE_IN_PROGRESS Expected results: Stack should be set to UPDATE_FAILED Additional info: I had to use sudo heat-manage reset_stack_status to set stack tto UPDATTE_FAILED manually.
Do we have any logs form the engine startup? It's possible that the database inconsistency observed in bug 1464533 could have caused the DB transaction to fail.
Similar issue: bug 1445484.
Created attachment 1319527 [details] heat-engine log on startup Reproduced this on OSP10, on restarting heat-engine stack continues to be in CREATE_IN_PROGRESS,