summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat
-rw-r--r--doc/source/admin/troubleshooting.rst44
-rw-r--r--doc/source/contributor/releasing.rst20
-rw-r--r--ironic/common/rpc.py7
-rw-r--r--ironic/conf/default.py2
-rw-r--r--releasenotes/config.yaml (renamed from reno.yaml)4
-rw-r--r--releasenotes/notes/fix-grub2-uefi-config-path-f1b4c5083cc97ee5.yaml14
-rw-r--r--releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po284
-rw-r--r--requirements.txt2
-rw-r--r--zuul.d/ironic-jobs.yaml6
9 files changed, 127 insertions, 256 deletions
diff --git a/doc/source/admin/troubleshooting.rst b/doc/source/admin/troubleshooting.rst
index 7a9ddb0ab..72e969b6e 100644
--- a/doc/source/admin/troubleshooting.rst
+++ b/doc/source/admin/troubleshooting.rst
@@ -1100,3 +1100,47 @@ of other variables, you may be able to leverage the `RAID <raid>`_
configuration interface to delete volumes/disks, and recreate them. This may
have the same effect as a clean disk, however that too is RAID controller
dependent behavior.
+
+I'm in "clean failed" state, what do I do?
+==========================================
+
+There is only one way to exit the ``clean failed`` state. But before we visit
+the answer as to **how**, we need to stress the importance of attempting to
+understand **why** cleaning failed. On the simple side of things, this may be
+as simple as a DHCP failure, but on a complex side of things, it could be that
+a cleaning action failed against the underlying hardware, possibly due to
+a hardware failure.
+
+As such, we encourage everyone to attempt to understand **why** before exiting
+the ``clean failed`` state, because you could potentially make things worse
+for yourself. For example if firmware updates were being performed, you may
+need to perform a rollback operation against the physical server, depending on
+what, and how the firmware was being updated. Unfortunately this also borders
+the territory of "no simple answer".
+
+This can be counter balanced with sometimes there is a transient networking
+failure and a DHCP address was not obtained. An example of this would be
+suggested by the ``last_error`` field indicating something about "Timeout
+reached while cleaning the node", however we recommend following several
+basic troubleshooting steps:
+
+* Consult the ``last_error`` field on the node, utilizing the
+ ``baremetal node show <uuid>`` command.
+* If the version of ironic supports the feature, consult the node history
+ log, ``baremetal node history list`` and
+ ``baremetal node history get <uuid>``.
+* Consult the acutal console screen of the physical machine. *If* the ramdisk
+ booted, you will generally want to investigate the controller logs and see
+ if an uploaded agent log is being stored on the conductor responsible for
+ the baremetal node. Consult `Retrieving logs from the deploy ramdisk`_.
+ If the node did not boot for some reason, you can typically just retry
+ at this point and move on.
+
+How to get out of the state, once you've understood **why** you reached it
+in the first place, is to utilize the ``baremetal node manage <node_id>``
+command. This returns the node to ``manageable`` state, from where you can
+retry "cleaning" through automated cleaning with the ``provide`` command,
+or manual cleaning with ``clean`` command. or the next appropriate action
+in the workflow process you are attempting to follow, which may be
+ultimately be decommissioning the node because it could have failed and is
+being removed or replaced.
diff --git a/doc/source/contributor/releasing.rst b/doc/source/contributor/releasing.rst
index eab0649c6..3c0732c5b 100644
--- a/doc/source/contributor/releasing.rst
+++ b/doc/source/contributor/releasing.rst
@@ -125,19 +125,23 @@ openstack ``stable/NAME`` branches:
* ironic-inspector
* ironic-python-agent
-They are also released on a regular cadence as opposed to on-demand, namely
-three times a release cycle (roughly a release every 2 months). One of the
-releases corresponds to the coordinated OpenStack released and receives a
-``stable/NAME`` branch. The other two happen during the cycle and receive a
-``bugfix/X.Y`` branch, where ``X.Y`` consists of the major and the minor
-component of the version (e.g. ``bugfix/8.1`` for 8.1.0).
+These projects receive releases every six months as part of the coordinated
+OpenStack release that happens semi-annually. These releases can be
+found in a ``stable/NAME`` branch.
+
+They are also evaluated for additional bugfix releases between scheduled
+stable releases at the two and four month milestore between stable releases
+(roughly every 2 months). These releases can be found in a ``bugfix/X.Y``
+branch. A bugfix release is only created if there are significant
+beneficial changes and a known downstream operator or distributor will consume
+the release.
To leave some version space for releases from these branches, releases of these
projects from the master branch always increase either the major or the minor
version.
-Currently releases from bugfix branches cannot be automated and must be done by
-the release team manually.
+Currently releases and retirements from bugfix branches cannot be automated and
+must be done by the release team manually.
After the creation of a bugfix branch it is utmost important to update the
upper-constraints link for the tests in the tox.ini file, plus override the
diff --git a/ironic/common/rpc.py b/ironic/common/rpc.py
index 285ee1f06..710c7a943 100644
--- a/ironic/common/rpc.py
+++ b/ironic/common/rpc.py
@@ -122,10 +122,9 @@ def get_transport_url(url_str=None):
def get_client(target, version_cap=None, serializer=None):
assert TRANSPORT is not None
serializer = RequestContextSerializer(serializer)
- return messaging.RPCClient(TRANSPORT,
- target,
- version_cap=version_cap,
- serializer=serializer)
+ return messaging.get_rpc_client(
+ TRANSPORT, target, version_cap=version_cap,
+ serializer=serializer)
def get_server(target, endpoints, serializer=None):
diff --git a/ironic/conf/default.py b/ironic/conf/default.py
index 0e3c32bd1..c7aff69cc 100644
--- a/ironic/conf/default.py
+++ b/ironic/conf/default.py
@@ -216,7 +216,7 @@ image_opts = [
'common/isolinux_config.template'),
help=_('Template file for isolinux configuration file.')),
cfg.StrOpt('grub_config_path',
- default='/boot/grub/grub.cfg',
+ default='EFI/BOOT/grub.cfg',
help=_('GRUB2 configuration file location on the UEFI ISO '
'images produced by ironic. The default value is '
'usually incorrect and should not be relied on. '
diff --git a/reno.yaml b/releasenotes/config.yaml
index 3265dd332..26538010e 100644
--- a/reno.yaml
+++ b/releasenotes/config.yaml
@@ -1,5 +1,5 @@
---
# Ignore the kilo-eol tag because that branch does not work with reno
# and contains no release notes.
-# Ignore bugfix tags because their releasenotes are covered under stabl
-closed_branch_tag_re: "(?!^(kilo|bugfix-)).+-eol$"
+# Ignore bugfix tags because their releasenotes are covered under stable
+closed_branch_tag_re: 'r"(?!^(kilo-|bugfix-)).+-eol$"'
diff --git a/releasenotes/notes/fix-grub2-uefi-config-path-f1b4c5083cc97ee5.yaml b/releasenotes/notes/fix-grub2-uefi-config-path-f1b4c5083cc97ee5.yaml
new file mode 100644
index 000000000..ddb6c86cb
--- /dev/null
+++ b/releasenotes/notes/fix-grub2-uefi-config-path-f1b4c5083cc97ee5.yaml
@@ -0,0 +1,14 @@
+---
+fixes:
+ - |
+ Fixes the default value for the ``[DEFAULT]grub_config_path`` variable to
+ be the default path for UEFI bootloader configurations, where as the
+ default was previously the BIOS grub2 configuration path.
+upgrades:
+ - |
+ The default configuration value for ``[DEFAULT]grub_config_path`` has
+ been changed from ``/boot/grub/grub.conf`` to ``EFI/BOOT/grub.efi`` as
+ the configuration parameter was for UEFI boot configuration, and the
+ ``/boot/grub/grub2.conf`` path is for BIOS booting. This was verified
+ by referencing several working UEFI virtual media examples where this
+ value was overridden to the new configuration value.
diff --git a/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po b/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po
index af7fb4e03..46124265e 100644
--- a/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po
+++ b/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po
@@ -3,15 +3,16 @@
# Andi Chandler <andi@gowling.com>, 2019. #zanata
# Andi Chandler <andi@gowling.com>, 2020. #zanata
# Andi Chandler <andi@gowling.com>, 2022. #zanata
+# Andi Chandler <andi@gowling.com>, 2023. #zanata
msgid ""
msgstr ""
"Project-Id-Version: Ironic Release Notes\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-11-04 18:03+0000\n"
+"POT-Creation-Date: 2023-01-27 22:13+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2022-11-04 10:34+0000\n"
+"PO-Revision-Date: 2023-01-26 10:06+0000\n"
"Last-Translator: Andi Chandler <andi@gowling.com>\n"
"Language-Team: English (United Kingdom)\n"
"Language: en_GB\n"
@@ -136,9 +137,6 @@ msgstr "10.1.8"
msgid "10.1.9"
msgstr "10.1.9"
-msgid "11.0.0"
-msgstr "11.0.0"
-
msgid "11.1.0"
msgstr "11.1.0"
@@ -157,9 +155,6 @@ msgstr "11.1.4"
msgid "11.1.4-12"
msgstr "11.1.4-12"
-msgid "12.0.0"
-msgstr "12.0.0"
-
msgid "12.1.0"
msgstr "12.1.0"
@@ -184,9 +179,6 @@ msgstr "12.1.6"
msgid "12.1.6-3"
msgstr "12.1.6-3"
-msgid "12.2.0"
-msgstr "12.2.0"
-
msgid "13.0.0"
msgstr "13.0.0"
@@ -211,8 +203,8 @@ msgstr "13.0.6"
msgid "13.0.7"
msgstr "13.0.7"
-msgid "13.0.7-28"
-msgstr "13.0.7-28"
+msgid "13.0.7-29"
+msgstr "13.0.7-29"
msgid "14.0.0"
msgstr "14.0.0"
@@ -226,9 +218,6 @@ msgstr "15.0.1"
msgid "15.0.2"
msgstr "15.0.2"
-msgid "15.0.2-22"
-msgstr "15.0.2-22"
-
msgid "15.1.0"
msgstr "15.1.0"
@@ -253,9 +242,6 @@ msgstr "16.0.4"
msgid "16.0.5"
msgstr "16.0.5"
-msgid "16.0.5-9"
-msgstr "16.0.5-9"
-
msgid "16.1.0"
msgstr "16.1.0"
@@ -277,6 +263,9 @@ msgstr "17.0.4"
msgid "17.1.0"
msgstr "17.1.0"
+msgid "17.1.0-5"
+msgstr "17.1.0-5"
+
msgid "18.0.0"
msgstr "18.0.0"
@@ -289,8 +278,8 @@ msgstr "18.2.0"
msgid "18.2.1"
msgstr "18.2.1"
-msgid "18.2.1-31"
-msgstr "18.2.1-31"
+msgid "18.2.2"
+msgstr "18.2.2"
msgid "19.0.0"
msgstr "19.0.0"
@@ -301,8 +290,11 @@ msgstr "20.0.0"
msgid "20.1.0"
msgstr "20.1.0"
-msgid "20.1.0-29"
-msgstr "20.1.0-29"
+msgid "20.1.1"
+msgstr "20.1.1"
+
+msgid "20.1.1-4"
+msgstr "20.1.1-4"
msgid "20.2.0"
msgstr "20.2.0"
@@ -313,8 +305,8 @@ msgstr "21.0.0"
msgid "21.1.0"
msgstr "21.1.0"
-msgid "21.1.0-25"
-msgstr "21.1.0-25"
+msgid "21.2.0"
+msgstr "21.2.0"
msgid "4.0.0 First semver release"
msgstr "4.0.0 First semver release"
@@ -551,21 +543,6 @@ msgstr "A few major changes since 9.1.x (Pike) are worth mentioning:"
msgid ""
"A future release will change the default value of ``[deploy]/"
-"default_boot_mode`` from \"bios\" to \"uefi\". It is recommended to set an "
-"explicit value for this option. For hardware types which don't support "
-"setting boot mode, a future release will assume boot mode is set to UEFI if "
-"no boot mode is set to node's capabilities. It is also recommended to set "
-"``boot_mode`` into ``properties/capabilities`` of a node."
-msgstr ""
-"A future release will change the default value of ``[deploy]/"
-"default_boot_mode`` from \"bios\" to \"uefi\". It is recommended to set an "
-"explicit value for this option. For hardware types which don't support "
-"setting boot mode, a future release will assume boot mode is set to UEFI if "
-"no boot mode is set to node's capabilities. It is also recommended to set "
-"``boot_mode`` into ``properties/capabilities`` of a node."
-
-msgid ""
-"A future release will change the default value of ``[deploy]/"
"default_boot_option`` from \"netboot\" to \"local\". To avoid disruptions, "
"it is recommended to set an explicit value for this option."
msgstr ""
@@ -867,10 +844,6 @@ msgstr ""
"Driver needs this verification because the machine is going to use a MAC "
"that will only be specified at the profile application."
-msgid "A warning is logged for any changes to immutable configuration options."
-msgstr ""
-"A warning is logged for any changes to immutable configuration options."
-
msgid "API fields to support node ``description`` and ``owner`` values."
msgstr "API fields to support node ``description`` and ``owner`` values."
@@ -882,20 +855,6 @@ msgstr ""
"net/ironic/+bug/1536828 for details."
msgid ""
-"API version 1.57 adds a REST API endpoint for updating an existing "
-"allocation. Only ``name`` and ``extra`` fields are allowed to be updated."
-msgstr ""
-"API version 1.57 adds a REST API endpoint for updating an existing "
-"allocation. Only ``name`` and ``extra`` fields are allowed to be updated."
-
-msgid ""
-"API version 1.58 allows backfilling allocations for existing deployed nodes "
-"by providing ``node`` to ``POST /v1/allocations``."
-msgstr ""
-"API version 1.58 allows backfilling allocations for existing deployed nodes "
-"by providing ``node`` to ``POST /v1/allocations``."
-
-msgid ""
"Ability to create an allocation has been restricted by a new policy rule "
"``baremetal::allocation::create_pre_rbac`` which prevents creation of "
"allocations by any project administrator when operating with the new Role "
@@ -941,15 +900,6 @@ msgid "Add Wake-On-Lan Power Driver"
msgstr "Add Wake-On-LAN Power Driver"
msgid ""
-"Add ``?detail=`` boolean query to the API list endpoints to provide a more "
-"RESTful alternative to the existing ``/nodes/detail`` and similar endpoints. "
-"The default is False. Now these API requests are possible:"
-msgstr ""
-"Add ``?detail=`` boolean query to the API list endpoints to provide a more "
-"RESTful alternative to the existing ``/nodes/detail`` and similar endpoints. "
-"The default is False. Now these API requests are possible:"
-
-msgid ""
"Add ``choices`` parameter to config options. Invalid values will be rejected "
"when first accessing them, which can happen in the middle of deployment."
msgstr ""
@@ -1211,15 +1161,6 @@ msgstr ""
"udp_transport_timeout`` allow to change the number of retries and the "
"timeout values respectively for the the SNMP driver."
-msgid ""
-"Adds SNMPv3 message authentication and encryption features to ironic "
-"``snmp`` hardware type. To enable these features, the following parameters "
-"should be used in the node's ``driver_info``:"
-msgstr ""
-"Adds SNMPv3 message authentication and encryption features to ironic "
-"``snmp`` hardware type. To enable these features, the following parameters "
-"should be used in the node's ``driver_info``:"
-
msgid "Adds ShellinaboxConsole support for virsh SSH driver."
msgstr "Adds ShellinaboxConsole support for virsh SSH driver."
@@ -1288,9 +1229,6 @@ msgstr "Adds ``bios_interface`` to the node list and node show api-ref."
msgid "Adds ``bios_interface`` to the node validate api-ref."
msgstr "Adds ``bios_interface`` to the node validate api-ref."
-msgid "Adds ``bios`` interface to the ``redfish`` hardware type."
-msgstr "Adds ``bios`` interface to the ``redfish`` hardware type."
-
msgid ""
"Adds ``command_timeout`` and ``max_command_attempts`` configuration options "
"to IPA, so when connection errors occur the command will be executed again."
@@ -1299,15 +1237,6 @@ msgstr ""
"to IPA, so when connection errors occur the command will be executed again."
msgid ""
-"Adds ``command_timeout`` and ``max_command_attempts`` configuration options "
-"to IPA, so when connection errors occur the command will be executed again. "
-"The options are located in the ``[agent]`` section."
-msgstr ""
-"Adds ``command_timeout`` and ``max_command_attempts`` configuration options "
-"to IPA, so when connection errors occur the command will be executed again. "
-"The options are located in the ``[agent]`` section."
-
-msgid ""
"Adds ``driver_internal_info`` field to the node-related notification "
"``baremetal.node.provision_set.*``, new payload version 1.16."
msgstr ""
@@ -1315,28 +1244,6 @@ msgstr ""
"``baremetal.node.provision_set.*``, new payload version 1.16."
msgid ""
-"Adds ``external`` storage interface which is short for \"externally managed"
-"\". This adds logic to allow the Bare Metal service to identify when a BFV "
-"scenario is being requested based upon the configuration set for ``volume "
-"targets``."
-msgstr ""
-"Adds ``external`` storage interface which is short for \"externally managed"
-"\". This adds logic to allow the Bare Metal service to identify when a BFV "
-"scenario is being requested based upon the configuration set for ``volume "
-"targets``."
-
-msgid ""
-"Adds ``get_boot_mode``, ``set_boot_mode`` and ``get_supported_boot_modes`` "
-"methods to driver management interface. Drivers can override these methods "
-"implementing boot mode management calls to the BMC of the baremetal nodes "
-"being managed."
-msgstr ""
-"Adds ``get_boot_mode``, ``set_boot_mode`` and ``get_supported_boot_modes`` "
-"methods to driver management interface. Drivers can override these methods "
-"implementing boot mode management calls to the BMC of the baremetal nodes "
-"being managed."
-
-msgid ""
"Adds ``idrac`` hardware type support of a virtual media boot interface "
"implementation that utilizes the Redfish out-of-band (OOB) management "
"protocol and is compatible with the integrated Dell Remote Access Controller "
@@ -1415,17 +1322,6 @@ msgid ""
msgstr ""
"Adds ``rescue_interface`` field to the following node-related notifications:"
-msgid ""
-"Adds ``reset_idrac`` and ``known_good_state`` cleaning steps to hardware "
-"type ``idrac``. ``reset_idrac`` actually resets the iDRAC; "
-"``known_good_state`` also resets the iDRAC and clears the Lifecycle "
-"Controller job queue to make sure the iDRAC is in good state."
-msgstr ""
-"Adds ``reset_idrac`` and ``known_good_state`` cleaning steps to hardware "
-"type ``idrac``. ``reset_idrac`` actually resets the iDRAC; "
-"``known_good_state`` also resets the iDRAC and clears the Lifecycle "
-"Controller job queue to make sure the iDRAC is in good state."
-
msgid "Adds ``storage_interface`` field to the node-related notifications:"
msgstr "Adds ``storage_interface`` field to the node-related notifications:"
@@ -1485,27 +1381,6 @@ msgstr ""
"notifications."
msgid ""
-"Adds a ``[conductor]send_sensor_data_for_undeployed_nodes`` option to enable "
-"ironic to collect and transmit sensor data for all nodes for which sensor "
-"data collection is available. By default, this option is not enabled which "
-"aligns with the prior behavior of sensor data collection and transmission "
-"where such data was only collected if an ``instance_uuid`` was present to "
-"signify that the node has been or is being deployed. With this option set to "
-"``True``, operators may be able to identify hardware in a faulty state "
-"through the sensor data and take action before an instance workload is "
-"deployed."
-msgstr ""
-"Adds a ``[conductor]send_sensor_data_for_undeployed_nodes`` option to enable "
-"ironic to collect and transmit sensor data for all nodes for which sensor "
-"data collection is available. By default, this option is not enabled which "
-"aligns with the prior behaviour of sensor data collection and transmission "
-"where such data was only collected if an ``instance_uuid`` was present to "
-"signify that the node has been or is being deployed. With this option set to "
-"``True``, operators may be able to identify hardware in a faulty state "
-"through the sensor data and take action before an instance workload is "
-"deployed."
-
-msgid ""
"Adds a ``clear_job_queue`` cleaning step to the ``idrac-wsman`` management "
"interface. The ``clear_job_queue`` cleaning step clears the Lifecycle "
"Controller job queue including any pending jobs."
@@ -1639,38 +1514,6 @@ msgstr ""
"return tracebacks in API responses in an error condition."
msgid ""
-"Adds a configuration option ``[deploy]disk_erasure_concurrency`` to define "
-"the target pool size used by Ironic Python Agent ramdisk to erase disk "
-"devices. The number of threads created by IPA to erase disk devices is the "
-"minimum value of target pool size and the number of disks to be erased. This "
-"feature can greatly reduce the operation time for baremetals with multiple "
-"disks. For the backwards compatibility, the default value is 1."
-msgstr ""
-"Adds a configuration option ``[deploy]disk_erasure_concurrency`` to define "
-"the target pool size used by Ironic Python Agent ramdisk to erase disk "
-"devices. The number of threads created by IPA to erase disk devices is the "
-"minimum value of target pool size and the number of disks to be erased. This "
-"feature can greatly reduce the operation time for baremetals with multiple "
-"disks. For the backwards compatibility, the default value is 1."
-
-msgid ""
-"Adds a configuration option ``[ipmi]disable_boot_timeout`` which is used to "
-"set the default behavior whether ironic should send a raw IPMI command to "
-"disable timeout. This configuration option can be overidden by the per-node "
-"option ``ipmi_disable_boot_timeout`` in node's ``driver_info`` field. See "
-"`story 2004266 <https://storyboard.openstack.org/#!/story/2004266>`_ and "
-"`Story 2002977 <https://storyboard.openstack.org/#!/story/2002977>`_ for "
-"additional information."
-msgstr ""
-"Adds a configuration option ``[ipmi]disable_boot_timeout`` which is used to "
-"set the default behaviour whether ironic should send a raw IPMI command to "
-"disable timeout. This configuration option can be overridden by the per-node "
-"option ``ipmi_disable_boot_timeout`` in node's ``driver_info`` field. See "
-"`story 2004266 <https://storyboard.openstack.org/#!/story/2004266>`_ and "
-"`Story 2002977 <https://storyboard.openstack.org/#!/story/2002977>`_ for "
-"additional information."
-
-msgid ""
"Adds a configuration option ``webserver_verify_ca`` to support custom "
"certificates to validate URLs hosted on a HTTPS webserver."
msgstr ""
@@ -1770,30 +1613,6 @@ msgstr ""
"allocated from the configured port range for further use."
msgid ""
-"Adds a new configuration option ``[disk_utils]partprobe_attempts`` which "
-"defaults to 10. This is the maximum number of times to try to read a "
-"partition (if creating a config drive) via a ``partprobe`` command. "
-"Previously, no retries were done which caused failures. This addresses `bug "
-"1756760 <https://storyboard.openstack.org/#!/story/1756760>`_."
-msgstr ""
-"Adds a new configuration option ``[disk_utils]partprobe_attempts`` which "
-"defaults to 10. This is the maximum number of times to try to read a "
-"partition (if creating a config drive) via a ``partprobe`` command. "
-"Previously, no retries were done which caused failures. This addresses `bug "
-"1756760 <https://storyboard.openstack.org/#!/story/1756760>`_."
-
-msgid ""
-"Adds a new configuration option ``[disk_utils]partprobe_attempts`` which "
-"defaults to 10. This is the maximum number of times to try to read a "
-"partition (if creating a config drive) via a ``partprobe`` command. Set it "
-"to 1 if you want the previous behavior, where no retries were done."
-msgstr ""
-"Adds a new configuration option ``[disk_utils]partprobe_attempts`` which "
-"defaults to 10. This is the maximum number of times to try to read a "
-"partition (if creating a config drive) via a ``partprobe`` command. Set it "
-"to 1 if you want the previous behaviour, where no retries were done."
-
-msgid ""
"Adds a new configuration option ``[drac]boot_device_job_status_timeout`` "
"that specifies the maximum amount of time (in seconds) to wait for the boot "
"device configuration job to transition to the scheduled state to allow a "
@@ -1890,45 +1709,6 @@ msgstr ""
"v1/drivers/<name>."
msgid ""
-"Adds an ``inspect wait`` state to handle asynchronous hardware "
-"introspection. Caution should be taken due to the timeout monitoring is "
-"shifted from ``inspecting`` to ``inspect wait``, please stop all running "
-"asynchronous hardware inspection or wait until it is finished before "
-"upgrading to the Rocky release. Otherwise nodes in asynchronous inspection "
-"will be left at ``inspecting`` state forever unless the database is manually "
-"updated."
-msgstr ""
-"Adds an ``inspect wait`` state to handle asynchronous hardware "
-"introspection. Caution should be taken due to the timeout monitoring is "
-"shifted from ``inspecting`` to ``inspect wait``, please stop all running "
-"asynchronous hardware inspection or wait until it is finished before "
-"upgrading to the Rocky release. Otherwise nodes in asynchronous inspection "
-"will be left at ``inspecting`` state forever unless the database is manually "
-"updated."
-
-msgid ""
-"Adds an ``inspect wait`` state to handle asynchronous hardware "
-"introspection. Returning ``INSPECTING`` from the ``inspect_hardware`` method "
-"of inspect interface is deprecated, ``INSPECTWAIT`` should be returned "
-"instead."
-msgstr ""
-"Adds an ``inspect wait`` state to handle asynchronous hardware "
-"introspection. Returning ``INSPECTING`` from the ``inspect_hardware`` method "
-"of inspect interface is deprecated, ``INSPECTWAIT`` should be returned "
-"instead."
-
-msgid ""
-"Adds an ``inspect wait`` state to handle asynchronous hardware "
-"introspection. The ``[conductor]inspect_timeout`` configuration option is "
-"deprecated for removal, please use ``[conductor]inspect_wait_timeout`` "
-"instead to specify the timeout of inspection process."
-msgstr ""
-"Adds an ``inspect wait`` state to handle asynchronous hardware "
-"introspection. The ``[conductor]inspect_timeout`` configuration option is "
-"deprecated for removal, please use ``[conductor]inspect_wait_timeout`` "
-"instead to specify the timeout of inspection process."
-
-msgid ""
"Adds an `agent_iboot` driver to allow use of the Iboot power driver with the "
"Agent deploy driver."
msgstr ""
@@ -2008,6 +1788,20 @@ msgstr ""
"Drivers may optionally add a new BootInterface. This is merely a refactoring "
"of the Driver API to support future improvements."
+msgid ""
+"Drivers using the \"agent\" deploy mechanism do not support \"rebuild --"
+"preserve-ephemeral\""
+msgstr ""
+"Drivers using the \"agent\" deploy mechanism do not support \"rebuild --"
+"preserve-ephemeral\""
+
+msgid ""
+"IPMI Passwords are now obfuscated in REST API responses. This may be "
+"disabled by changing API policy settings."
+msgstr ""
+"IPMI Passwords are now obfuscated in REST API responses. This may be "
+"disabled by changing API policy settings."
+
msgid "Implemented a new Boot interface for drivers"
msgstr "Implemented a new Boot interface for drivers"
@@ -2091,6 +1885,13 @@ msgid "Support for the new ENROLL workflow during Node creation"
msgstr "Support for the new ENROLL workflow during Node creation"
msgid ""
+"The \"agent\" class of drivers now support both whole-disk and partition "
+"based images."
+msgstr ""
+"The \"agent\" class of drivers now support both whole-disk and partition "
+"based images."
+
+msgid ""
"The Ironic API now has support for CORS requests, that may be used by, for "
"example, web browser-based clients. This is configured in the [cors] section "
"of ironic.conf."
@@ -2173,6 +1974,15 @@ msgstr "Victoria Series (15.1.0 - 16.0.x) Release Notes"
msgid "Wallaby Series (16.1.0 - 17.0.x) Release Notes"
msgstr "Wallaby Series (16.1.0 - 17.0.x) Release Notes"
+msgid ""
+"While Ironic does include a ClusteredComputeManager, which allows running "
+"more than one nova-compute process with Ironic, it should be considered "
+"experimental and has many known problems."
+msgstr ""
+"While Ironic does include a ClusteredComputeManager, which allows running "
+"more than one nova-compute process with Ironic, it should be considered "
+"experimental and has many known problems."
+
msgid "Xena Series (18.0.0 - 18.2.x) Release Notes"
msgstr "Xena Series (18.0.0 - 18.2.x) Release Notes"
diff --git a/requirements.txt b/requirements.txt
index 8a57727ec..0c73e632e 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -39,7 +39,7 @@ rfc3986>=1.2.0 # Apache-2.0
jsonpatch!=1.20,>=1.16 # BSD
Jinja2>=3.0.0 # BSD License (3 clause)
keystonemiddleware>=9.5.0 # Apache-2.0
-oslo.messaging>=5.29.0 # Apache-2.0
+oslo.messaging>=14.1.0 # Apache-2.0
tenacity>=6.2.0 # Apache-2.0
oslo.versionedobjects>=1.31.2 # Apache-2.0
jsonschema>=3.2.0 # MIT
diff --git a/zuul.d/ironic-jobs.yaml b/zuul.d/ironic-jobs.yaml
index c59c54e86..ca1757417 100644
--- a/zuul.d/ironic-jobs.yaml
+++ b/zuul.d/ironic-jobs.yaml
@@ -250,9 +250,9 @@
# a small root partition, so use /opt which is mounted from a bigger
# ephemeral partition on such nodes
LIBVIRT_STORAGE_POOL_PATH: /opt/libvirt/images
- IRONIC_ANACONDA_IMAGE_REF: http://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/
- IRONIC_ANACONDA_KERNEL_REF: http://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/images/pxeboot/vmlinuz
- IRONIC_ANACONDA_RAMDISK_REF: http://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/images/pxeboot/initrd.img
+ IRONIC_ANACONDA_IMAGE_REF: https://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/
+ IRONIC_ANACONDA_KERNEL_REF: https://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/images/pxeboot/vmlinuz
+ IRONIC_ANACONDA_RAMDISK_REF: https://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/images/pxeboot/initrd.img
IRONIC_ANACONDA_INSECURE_HEARTBEAT: True
IRONIC_DEPLOY_CALLBACK_WAIT_TIMEOUT: 3600
IRONIC_PXE_BOOT_RETRY_TIMEOUT: 3600
View Lorry Controller Status