ironic/releasenotes/notes/non-persistent-boot-5e3a0cd78e9dc91b.yaml
Fellype Cavalcante c7091fb8e2 Using non-persistent boot in PXE interface
Non-persistent boot device change is not being used in places
where it should be during cleaning and deployment phases,
due to the default behavior of PXE interface forcing a
persistent change when using legacy function
deploy_utils.try_set_boot_device.
For some drivers, e.g. OneView, a persistent change is far more
costly than a non-persistent one, so this fix can bring
performance improvements.

Change-Id: I213e9c6173ee9c7c6c31064afcfae07764af0f7b
Closes-Bug: 1701721
Co-Authored-By: Stenio Araujo <steniaraujo@lsd.ufcg.edu.br>
2017-07-13 13:23:57 -03:00

8 lines
314 B
YAML

fixes:
- |
Fixes a bug which caused boot device changes to be persistent in
places where they did not need to be during cleaning and deployment
phases, due to the default behavior of PXE interface forcing a persistent
change.
For more info, see https://bugs.launchpad.net/ironic/+bug/1701721