diff options
| author | Ruby Loo <rloo@verizonmedia.com> | 2022-02-04 22:14:45 +0000 |
|---|---|---|
| committer | Ruby Loo <rloo@verizonmedia.com> | 2022-03-03 15:28:09 +0000 |
| commit | 09d8a94d5a9b3cabdf7fddc483821fd0df69e5ee (patch) | |
| tree | 25f2959ed2fc31b864f4d4337fdb1f0201f23512 /releasenotes/notes/anaconda-config-drive-fixes-5880884e34584549.yaml | |
| parent | 4e6a3d52edc42b490c10c110dee5ea9e64fc3467 (diff) | |
| download | ironic-09d8a94d5a9b3cabdf7fddc483821fd0df69e5ee.tar.gz | |
Anaconda deploy handles configdrive correctly
The anaconda deploy interface wasn't handling configdrive
correctly. This fixes:
- the code was incorrectly treating the config drive as a dict,
whereas it could also be in iso6600 format,
gzipped and base64-encoded. It is handled properly now.
- kickstart commands that deal with the config drive were added
to the end of the kickstart file. Which means that they are
executed after an ironic API request is sent to ironic to
indicate that the node has been provisioned and is ready
to be rebooted. Which means that there is a possible race
condition wrt these commands being completed before the node
is powered off. This has been fixed by putting the API request
at the end of the kickstart file. Also, a sync was added to
ensure that all modifications are written to disk.
- extra newlines ('\n') were incorrectly added to the user data content.
This broke the content-type decoding and cloud-init was unable to
proces them. The extra newlines have been removed.
Change-Id: If00342a1bfa3e87b2094061b0e2b0b69de3a8a4f
Diffstat (limited to 'releasenotes/notes/anaconda-config-drive-fixes-5880884e34584549.yaml')
| -rw-r--r-- | releasenotes/notes/anaconda-config-drive-fixes-5880884e34584549.yaml | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/releasenotes/notes/anaconda-config-drive-fixes-5880884e34584549.yaml b/releasenotes/notes/anaconda-config-drive-fixes-5880884e34584549.yaml new file mode 100644 index 000000000..ca1a6a6e7 --- /dev/null +++ b/releasenotes/notes/anaconda-config-drive-fixes-5880884e34584549.yaml @@ -0,0 +1,19 @@ +--- +fixes: + - | + The anaconda deploy interface was treating the config drive + as a dict, whereas it could be a dict or in iso6600 format, + gzipped and base64-encoded. This has been fixed. + - | + The anaconda deploy interface was adding commands that deal with the + config drive, to the end of the kickstart config file. Which means + that they are handled after an ironic API request is sent (to the + conductor) to indicate that the node has been provisioned and is + ready to be rebooted. Which means that there is a possible race condition + wrt these commands being completed before the node is powered off. + A sync is added to ensure that all modifications have been written + to disk, before the API request is sent -- as the last thing. + - | + Extra newlines ('\n') were incorrectly added to the user data content. + This broke the content-type decoding and cloud-init was unable to + proces them. The extra newlines have been removed. |