Current Series Release Notes¶
7.3.0-5¶
New Features¶
The
ironic-python-agent-ramdiskelement has been split into a base element and a full element.ironic-python-agent-ramdisk-basebuilds a minimal ramdisk, andironic-python-agent-ramdiskextends it with additional functionality such as dhcp-all-interfaces.
Upgrade Notes¶
The
ironic-python-agent-podmanelement now verifies registry TLS by default. OverrideDIB_PULL_OPTIONSandDIB_RUN_OPTIONSto keep--tls-verify=falsefor a registry serving plain HTTP.
Bug Fixes¶
The
ironic-python-agent-podmanelement now writespull_optionsandrun_optionsinto the ramdisk configuration as comma separated lists. These are list valued options in the agent, and lists split on commas rather than whitespace, so the previous space separated defaults reached the container runtime as a single argument and every container step failed. A space separatedDIB_PULL_OPTIONSorDIB_RUN_OPTIONSsupplied at build time is converted automatically.
The
ironic-python-agent-podmanelement no longer fails the image build when no container steps file is present at the default path. A ramdisk with no baked steps is the normal case for the runbook and deploy template workflow, so requiring one made the primary documented workflow impossible to build for. A missing file is still an error whenDIB_STEPS_FILE_PATHwas set explicitly.
7.3.0¶
Bug Fixes¶
Fixes a delay of up to 30 seconds during boot when a node is deployed via virtual media without a configuration drive. The configuration drive resolution script now detects the Ironic boot device by its publisher id and, when that device has no
config-2label, concludes immediately that no configuration drive is present instead of polling for the full timeout. A staleconfig-2partition left on a local disk no longer stalls boot.
7.2.0¶
Bug Fixes¶
The ironic-python-agent-podman element was in a nonstandard subdirectory,
dib/elements/when all of the other elements are indib/directly.This element has been moved into the standard location.