927c487a0f
When configdrive is too large, a node object cannot be saved to DB. If it happens, the node cannot moved to DEPLOYFAIL because saving the node is prevented again by the large configdrive in the object. In this case, the node gets stuck in DEPLOYING, which doesn't allow any state transition. This patch removes the configdrive from a node object when storing the configdrive fails. This also catches ConfigInvalid exception, which is mentioned in the docsting, and any unexpected exception from _store_configdrive() to avoid getting a node stuck in DEPLOYING. Change-Id: I83cf3e02622fc3ed8f5b5389f533e374c1b985f3 Closes-Bug: 1745630
9 lines
359 B
YAML
9 lines
359 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes a bug to get a node stuck in ``deploying`` state when the size of
|
|
the configdrive exceeds the limitation of the database. In MySQL, the
|
|
limitation is about 64KiB. With this fix, the provision state gets
|
|
``deploy failed`` in this case. See `bug 1745630
|
|
<https://bugs.launchpad.net/ironic/+bug/1745630>`_ for details.
|