[ironic] force_persistent_boot_device can only be configured from env, when mode ramdisk (deployIso) is used #2613
Description
What steps did you take and what happened:
I found the env variable LIVE_ISO_FORCE_PERSISTENT_BOOT_DEVICE which can configure the persistent boot device flag for all bmhs a bmo manages. Unfortunately the flag only works as indicated by the name for Live ISO or deploy_interface ramdisk.
As you could also run a Live ISO like system using the direct deploy_interface, the flag should also allow overwriting for this deploy_interface.
What did you expect to happen:
The variable can configure both deploy_interfaces and overwrite driver_info: force_persistent_boot_device: "Default" when configured to be Never or Always.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
- Baremetal Operator version: v0.9.1
- Environment (metal3-dev-env or other): production deloyment
/kind bug