06cc5d47dc
The anaconda deploy interface has a few issues that are addressed here: - fixes logic in get_instance_image_info() for anaconda. If the ironic node's instance_info doesn't have both 'stage2' and 'ks_template' specified, we weren't using any values from the instance_info. This has been fixed to use values from instance_info if specified. Otherwise, they are set as follows: The 'stage2' value is taken from the image properties. We use the value for 'ks_template' if it is specified in the image properties. If not (since it is optional), we use the config option's '[anaconda]default_ks_template' value. setting. - For anaconda's stage2 directory, we were incorrectly creating a directory using the full path of the stage2 file. It now correctly creates the right directory. - The anaconda deploy interface expects the node's instance_info to be populated with the 'image_url'; added code to do that in PXEAnacondaDeploy's prepare() method. - When the deploy is finished and the bm node is being rebooted, we incorrectly set the node's provision state to 'active' instead of doing it via the provisioning state machine mechanism. - The code that was doing the validation of the kickstart file was incorrect and resulted in errors; this has been addressed. - The '%traceback' section in the packaged 'ks.cfg.template' file is deprecated and fails validation, so it has been removed. Change-Id: I953e948bcfa108d4c8e7b145da2f52b652e52a10
34 lines
1.5 KiB
YAML
34 lines
1.5 KiB
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes the logic for the anaconda deploy interface. If the
|
|
ironic node's instance_info doesn't have both 'stage2' and
|
|
'ks_template' specified, we weren't using the instance_info
|
|
at all. This has been fixed to use the instance_info if it
|
|
was specified. Otherwise, 'stage2' is taken from the
|
|
image's properties (assumed that it is set there).
|
|
'ks_template' value is from the image properties if specified
|
|
there (since it is optional); else we use the config setting
|
|
'[anaconda] default_ks_template'.
|
|
- |
|
|
For the anaconda deploy interface, the 'stage2' directory was
|
|
incorrectly being created using the full path of the stage2 file;
|
|
this has been fixed.
|
|
- |
|
|
The anaconda deploy interface expects the node's instance_info
|
|
to be populated with the 'image_url'; this is now populated
|
|
(via PXEAnacondaDeploy's prepare() method).
|
|
- |
|
|
For the anaconda deploy interface, when the deploy was finished
|
|
and the bm node was being rebooted, the node's provision state was
|
|
incorrectly being set to 'active' -- the provisioning state-machine
|
|
mechanism now handles that.
|
|
- |
|
|
For the anaconda deploy interface, the code that was doing the
|
|
validation of the kickstart file was incorrect and resulted in
|
|
errors; this has been addressed.
|
|
- |
|
|
For the anaconda deploy interface, the '%traceback' section in the
|
|
packaged 'ks.cfg.template' file is deprecated and fails validation,
|
|
so it has been removed.
|