Release note clean-ups for ironic release

Lots of misc fixes and changes to make the release notes
a little more consistent.

Change-Id: I8ed616f27a393d5adf015743fc1810a3d9955c55
This commit is contained in:
Julia Kreger 2018-06-19 09:06:40 -07:00
parent 94526fd977
commit b2ecd08924
18 changed files with 56 additions and 54 deletions

View File

@ -3,6 +3,7 @@ features:
- |
Adds support to abort the inspection of a node in the ``inspect wait``
state, as long as this operation is supported by the inspect interface in
use. Starting from API 1.41, the node in the ``inspect wait`` state
accepts ``abort`` provisioning verb to initiate the abort process.
This feature is supported by the ``inspector`` inspect interface.
use. A node in the ``inspect wait`` state accepts the ``abort``
provisioning verb to initiate the abort process.
This feature is supported by the ``inspector`` inspect interface and
is available starting with API version 1.41.

View File

@ -6,11 +6,11 @@ other:
calls to the BMC of the baremetal nodes being managed.
features:
- The new ironic configuration setting ``[deploy]/default_boot_mode``
allows to set the default boot mode when ironic can't pick boot mode
automatically based on node configuration, hardware capabilities,
bare-metal machine configuration.
allows the operator to set the default boot mode when ironic can't
pick boot mode automatically based on node configuration, hardware
capabilities, or bare-metal machine configuration.
fixes:
- If the bare metal machine's boot mode differs from the requested one,
ironic will attempt to set requested boot mode on the bare metal
ironic will now attempt to set requested boot mode on the bare metal
machine and fail explicitly if the driver does not support setting
boot mode on the node.

View File

@ -1,4 +1,4 @@
---
features:
- Adds support for reading and setting bare metal node's boot mode
using the ``redfish`` management interface.
- Adds support to the ``redfish`` management interface for reading
and setting bare metal node's boot mode.

View File

@ -1,8 +0,0 @@
---
fixes:
- |
Fixes a bug to get a node stuck in ``deploying`` state when the size of
the configdrive exceeds the limitation of the database. In MySQL, the
limitation is about 64KiB. With this fix, the provision state gets
``deploy failed`` in this case. See `bug 1745630
<https://bugs.launchpad.net/ironic/+bug/1745630>`_ for details.

View File

@ -1,5 +1,6 @@
---
fixes:
- |
Fix an issue with iPXE is used for authentication during boot from volume
with multi attached volumes.
Fixes an issue with iPXE where the incorrect iscsi volume
authentication data was being used with boot from volume when
multi-attach volumes were present.

View File

@ -1,6 +1,6 @@
---
fixes:
- |
When a node is found to be locked when a heart beat arrives, no longer
records the error in node's ``last_error`` field, since it's not
an error in most cases.
Fixes an issue where node ramdisk heartbeat operations would collide
with conductor locks and erroniously record an error in node's
``last_error`` field.

View File

@ -1,7 +1,8 @@
---
fixes:
- |
The iPXE template kernel command line argument ``ip`` has been removed as it
is incompatible with the ``BOOTIF`` and missing ``autoconf`` parameters with
dracut. Further details can be found in
Fixes a compatability issue where the iPXE kernel command line was no
longe compatible with dracut. The ``ip`` parameter has been removed
as it is incompatible with the ``BOOTIF`` and missing ``autoconf``
parameters when dracut is used. Further details can be found in
`storyboard <https://storyboard.openstack.org/#!/story/2001969>`_.

View File

@ -1,4 +1,4 @@
---
features:
- |
Adds support for ``ipmitool`` power interface to ``irmc`` hardware type.
Adds support for the ``ipmitool`` power interface to the ``irmc`` hardware type.

View File

@ -8,6 +8,6 @@ upgrade:
the port's or port group's extra['vif_port_id'] will not be supported
starting with the Stein release.
Any out-of-tree network interface implementation that had a different
Any out-of-tree network interface implementations that had a different
behavior in support of attach/detach VIFs via the port or port group's
extra['vif_port_id'] must be updated appropriately.

View File

@ -1,4 +1,5 @@
---
fixes:
- No longer tries to collect or report sensors data for nodes in maintenance
mode. See `bug 1652741 <https://bugs.launchpad.net/bugs/1652741>`_.
other:
- The conductor no longer tries to collect or report sensors data for
nodes in maintenance mode.
See `bug 1652741 <https://bugs.launchpad.net/bugs/1652741>`_.

View File

@ -4,7 +4,8 @@ features:
Adds support for the ``fault`` field in the node, beginning with API
version 1.42. This field records the fault, if any, detected by ironic for
a node. If no fault is detected, the ``fault`` is ``None``. The ``fault``
is set to one of following values according to different circumstances:
field value is set to one of following values according to
different circumstances:
* ``power failure``: when a node is put into maintenance due to power sync
failures that exceed max retries.
@ -13,6 +14,6 @@ features:
* ``rescue abort failure``: when a node is put into maintenance due to
failure of cleaning up during rescue abort.
The ``fault`` will be set to ``None`` if an operator manually set
The ``fault`` field will be set to ``None`` if an operator manually set
maintenance to ``False``. The ``fault`` field can be used as a filter for
querying nodes.

View File

@ -1,9 +1,10 @@
---
fixes:
- |
On node take over, any locks that are left from the old conductor are
cleared by the new one. Previously it only happened for nodes in
``DEPLOYING`` state.
Fixes an issue where only nodes in ``DEPLOYING`` state would have
locks cleared for the nodes. Now upon node take over, any locks
that are left from the old conductor are cleared by the new one.
other:
- |
On taking over nodes in ``CLEANING`` state, the new conductor moves them
to ``CLEAN FAIL`` and set maintenance.
to the ``CLEAN FAIL`` state and sets maintenance.

View File

@ -13,6 +13,8 @@ upgrade:
``[conductor]power_failure_recovery_interval``, which is enabled and set
to 300 seconds by default. In case the default value is not suitable for
the needs or scale of a deployment, please make adjustment or turn it off
during upgrade. The power failure recovery does not apply to nodes that
were in maintenance mode due to power failure before upgrade, they have
to be manually moved out of maintenance mode.
during upgrade.
- |
Power failure recovery does not apply to nodes that were in maintenance
mode due to power failure before upgrade, they have to be manually moved
out of maintenance mode.

View File

@ -1,6 +1,7 @@
---
fixes:
- |
When creating a neutron port for booting a ramdisk, an error is raised if
there are no PXE-enabled ports available for the node. See `bug 2001811
Fixes an issue where no error was raised if there were no PXE-enabled
ports available for the node, when creating a neutron port.
See `bug 2001811
<https://storyboard.openstack.org/#!/story/2001811>`_ for more details.

View File

@ -9,7 +9,8 @@ upgrade:
re-add the VIF attachments prior to deployment.
fixes:
- |
Removes all records of VIF attachments upon the teardown of a deployed
Fixes potential case of VIF records being orphaned as the service
now removes all records of VIF attachments upon the teardown of a deployed
node. This is in order to resolve issues related to where it is
operationally impossible in some circumstances to remove a VIF
attachment while a node is being undeployed as the Compute service

View File

@ -1,7 +1,7 @@
---
features:
- |
Adds support for rescue interface ``agent`` for ``ilo`` hardware type
when corresponding boot interface being used is ``ilo-virtual-media``.
The supported values of rescue interface for ``ilo`` hardware type
Adds support for rescue interface ``agent`` for the ``ilo`` hardware type
when the corresponding boot interface being used is ``ilo-virtual-media``.
The supported values of the rescue interface for the ``ilo`` hardware type
are ``agent`` and ``no-rescue``. The default value is ``no-rescue``.

View File

@ -1,7 +1,7 @@
---
features:
- |
Adds support for rescue interface ``agent`` for ``irmc`` hardware type
when corresponding boot interface is ``irmc-virtual-media``.
Adds support for rescue interface ``agent`` for the ``irmc`` hardware type
when the corresponding boot interface is ``irmc-virtual-media``.
The supported values of rescue interface for ``irmc`` hardware type
are ``agent`` and ``no-rescue``. The default value is ``no-rescue``.

View File

@ -1,8 +1,8 @@
---
fixes:
- |
Updates the boot mode on the baremetal for cleaning scenario as per
given ``boot_mode`` in node's properties/capabilities. This change
is for ``ilo`` hardware type.
Fixes an issue where the ``ilo`` hardware type would not properly
update the boot mode on the bare metal machine for cleaning as per
given ``boot_mode`` in node's properties/capabilities.
See `bug 1559835 <https://bugs.launchpad.net/ironic/+bug/1559835>`_
for more details.