If node holds in progress state node status does not resolved properly in transaction manager
Bug #1622972 reported by
Bulat Gaifullin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Bulat Gaifullin |
Bug Description
In progress status for node has high priority, so lcm engine cannot calculate current status of node properly in this case.
that means if node was provisioned and during deployment astute crashes and node hangs in deploying state the re-deploy for this node does not start because lcm engine does not recognise that node was in provisioned status.
tags: | added: dev-to-verify |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/369314
Review: https:/