1) ignoring user data passed into rebuild and
2) providing different behavior than other nova drivers (by preserving configdrive contents).
I instead propose that post-deployment, we remove the configdrive from the node immediately after deployment, and rebuilding in Ironic will always require re-adding configdrive information to the node.
I do not agree that the symptom described should be fixed by keeping the configdrive past server delete. For other Nova drivers, configdrive is regenerated on rebuild (https:/ /github. com/openstack/ nova/blob/ 0da6c6461177539 cf69c7c2998f3ce 8914112b0a/ nova/compute/ manager. py#L2576) based on user input, so that we are currently:
1) ignoring user data passed into rebuild and
2) providing different behavior than other nova drivers (by preserving configdrive contents).
I instead propose that post-deployment, we remove the configdrive from the node immediately after deployment, and rebuilding in Ironic will always require re-adding configdrive information to the node.