Node gets stuck in 'deploying' when configdrive is too large
Bug #1745630 reported by
Hironori Shiina
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Low
|
Hironori Shiina |
Bug Description
As mentioned in another rfe[1], configdrive may be larger than the size of the instance_info field in DB. In this case, a node gets stuck in 'deploying' state. After the configdrive is set to the node object[1], an exception is raised when node.save() is called. The node cannot be moved to 'deploy failed' because the node cannot be saved with the new provision state since the large configdrive remains in instance_info of the node object.
[1] https:/
[2] https:/
Changed in ironic: | |
status: | Incomplete → Triaged |
Changed in ironic: | |
assignee: | nobody → Hironori Shiina (shiina-hironori) |
To post a comment you must log in.
So looking through the links Hironori provided, this is happening when the config drive is larger than 64KiB (as the max size for a Text field is 2^16 - 1).
@hshiina - can you detail what exception gets thrown and possibly provide some logs around the exception being thrown? I would guess that we need to catch this in do_node_deploy and do a handle_failure there.