Currently if configdrive_use_swift is set, config drive will be uploaded to swift with header:
{'X-Delete-After': timeout}
Which means config drive will be removed after "timeout" seconds.
If the server is rebuilt "timeout" seconds later, config drive won't be available, provisioning will fail.
Proposal:
1. Do not pass 'X-Delete-After' header
2. Delete config drive during deletion
3. If config drive is allowed in "rebuild" call (Bug 1575935), override previous config drive.
Currently if configdrive_ use_swift is set, config drive will be uploaded to swift with header:
{'X-Delete-After': timeout}
Which means config drive will be removed after "timeout" seconds.
If the server is rebuilt "timeout" seconds later, config drive won't be available, provisioning will fail.
Proposal:
1. Do not pass 'X-Delete-After' header
2. Delete config drive during deletion
3. If config drive is allowed in "rebuild" call (Bug 1575935), override previous config drive.