summaryrefslogtreecommitdiff
path: root/releasenotes
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Enables boot modes switching with Anaconda deploy for ilo driver"Zuul2023-03-271-0/+5
|\
| * Enables boot modes switching with Anaconda deploy for ilo driverNisha Agarwal2023-03-171-0/+5
| | | | | | | | | | | | | | | | | | Enables boot modes switching with Anaconda deploy for ilo driver Story: 2010357 Task: 46530 Change-Id: I383cdd5c9d45b074d351ec98b1145fd68e2f3ac3
* | Merge "Fixes Secureboot with Anaconda deploy"Zuul2023-03-201-0/+4
|\ \ | |/
| * Fixes Secureboot with Anaconda deployNisha Agarwal2023-03-161-0/+4
| | | | | | | | | | | | | | | | | | Fixes Secureboot with Anaconda deploy with PXE and iPXE Story:2010356 Task: 46529 Change-Id: Id6262654bb5e41e02c7d90b9a9aaf395e7b6a088
* | Merge "Fix auth_protocol and priv_protocol for SNMP v3"Zuul2023-03-171-0/+7
|\ \ | |/ |/|
| * Fix auth_protocol and priv_protocol for SNMP v3Duc Truong2023-03-011-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SNMP driver was using the wrong dictionary key to retrieve auth_protocol and priv_protocol from driver info. As a result, the SNMP client was created with empty strings for both those fields. Any nodes configured to use SNMP v3 with those fields failed because the SNMP driver was unable to perform power related operations due to authentication error. - Use correct keys for snmp auth_protocol and priv_protocol when creating SNMP client - Sanitize snmp auth_key and priv_key in API results Story: 2010613 Task: 47535 Change-Id: I5efd3c9f79a021f1a8e613c3d13b6596a7972672
* | Merge "Wipe Agent Token when cleaning timeout occcurs"Zuul2023-03-141-0/+7
|\ \
| * | Wipe Agent Token when cleaning timeout occcursJulia Kreger2023-03-021-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In a relatively odd turn of events, should cleaning have started, but then timed out due to lost communications or a hard failure of the machine, an agent token could previously be orphaned preventing re-cleaning. We now explicitly remove the token in this case. Change-Id: I236cdf6ddb040284e9fd1fa10136ad17ef665638
* | | Merge "Clean out agent token even if power is already off"Zuul2023-03-131-0/+6
|\ \ \
| * | | Clean out agent token even if power is already offJulia Kreger2023-03-021-0/+6
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While investigating a very curious report, I discovered that if somehow the power was *already* turned off to a node, say through an incorrect BMC *or* human action, and Ironic were to pick it up (as it does by default, because it checks before applying the power state, then it would not wipe the token information, preventing the agent from connecting on the next action/attempt/operation. We now remove the token on all calls to conductor utilities node_power_action method when appropriate, even if no other work is required. Change-Id: Ie89e8be9ad2887467f277772445d4bef79fa5ea1
* | | Merge "Do not recalculate checksum if disk_format is not changed"Zuul2023-03-131-0/+5
|\ \ \
| * | | Do not recalculate checksum if disk_format is not changedDmitry Tantsur2023-03-071-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Even if a glance image is raw, we still recalculate the checksum after "converting" it to raw. This process may take exceptionally long. Change-Id: Id93d518b8d2b8064ff901f1a0452abd825e366c0
* | | | Merge "Update master for stable/2023.1"Zuul2023-03-102-0/+7
|\ \ \ \
| * | | | Update master for stable/2023.1OpenStack Release Bot2023-03-092-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/2023.1. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/2023.1. Sem-Ver: feature Change-Id: Iabfa1f9b492c85be185c6993a016a6dd88ed9f9a
* | | | | Imported Translations from ZanataOpenStack Proposal Bot2023-03-102-10/+160
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I40870112f420690bde769c94740602e29ca34183
* | | | Merge "Fix online upgrades for Bios/Traits"Zuul2023-03-071-0/+14
|\ \ \ \
| * | | | Fix online upgrades for Bios/TraitsJulia Kreger2023-03-071-0/+14
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ... And tags, but nobody uses tags since it is not available via the API. Anyhow, the online upgrade code was written under the assumption that *all* tables had an "id" column. This is not always true in the ironic data model for tables which started as pure extensions of the Nodes table, and fails in particular when: 1) A database row has data stored in an ealier version of the object 2) That same object gets a version upgrade. In the case which discovered this, BIOSSetting was added at version 1.0, and later updated to include additional fields which incremented the version to 1.1. When the upgrade went to evaluate and iterate through the fields, the command failed because the table was designed around "node_id" instead of "id". Story: 2010632 Task: 47590 Change-Id: I7bec6cfacb9d1558bc514c07386583436759f4df
* | | | Add prelude for OpenStack 2023.1 Ironic releaseJay Faulkner2023-03-061-0/+14
|/ / / | | | | | | | | | | | | | | | We need a prelude. I added one. Change-Id: I48a7ca99439ce2ac3f954ec382971c1a4382ac58
* | | Merge "Do not move nodes to CLEAN FAILED with empty last_error"Zuul2023-03-021-0/+8
|\ \ \
| * | | Do not move nodes to CLEAN FAILED with empty last_errorDmitry Tantsur2023-03-011-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When cleaning fails, we power off the node, unless it has been running a clean step already. This happens when aborting cleaning or on a boot failure. This change makes sure that the power action does not wipe the last_error field, resulting in a node with provision_state=CLEANFAIL and last_error=None for several seconds. I've hit this in Metal3. Also when aborting cleaning, make sure last_error is set during the transition to CLEANFAIL, not when the clean up thread starts running. While here, make sure to log the current step in all cases, not only when aborting a non-abortable step. Change-Id: Id21dd7eb44dad149661ebe2d75a9b030aa70526f Story: #2010603 Task: #47476
* | | | Merge "Respond to rpc requests on stop until hash ring reset"Zuul2023-02-281-0/+13
|\ \ \ \ | |_|/ / |/| | |
| * | | Respond to rpc requests on stop until hash ring resetSteve Baker2023-02-271-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently when a conductor is stopped, the rpc service stops responding to requests as soon as self.manager.del_host returns. This means that until the hash ring is reset on the whole cluster, requests can be sent to a service which is stopped. This change waits for the remaining seconds to delay stopping until CONF.hash_ring_reset_interval has elapsed. This will improve the reliability of the cluster when scaling down or rolling out updates. This delay only occurs when there is more than one online conductor, to allow fast restarts on single-node ironic installs (bifrost, metal3). Change-Id: I643eb34f9605532c5c12dd2a42f4ea67bf3e0b40
* | | | Merge "Add configurable delays to the fake drivers"Zuul2023-02-271-0/+8
|\ \ \ \
| * | | | Add configurable delays to the fake driversSteve Baker2022-10-131-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Simulating workloads with the fake driver currently misses the reality that some operations take time to complete, rather than occuring instantly. This makes it difficult to mock real workloads for performance and functional testing of ironic itself. This change adds configurable random wait times for fake drivers in a new ironic.conf [fake] section. Each supported driver having one configuration option controlling the delay. These delays are applied to operations which typically block in other drivers. The default value of zero continues the existing behaviour of no delay. A single integer value will result in a constant delay in seconds. Two values separated by a comma will result in a triangular distribution weighted by the first value, specifically in python[1]: random.triangular(a, b, a) Change-Id: I7cb1b50d035939e6c4538b3373002a309bfedea4 [1] https://docs.python.org/3/library/random.html#random.triangular
* | | | | Merge "Get conductor metric data"Zuul2023-02-271-0/+39
|\ \ \ \ \ | |_|/ / / |/| | | |
| * | | | Get conductor metric dataJulia Kreger2023-02-231-0/+39
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change adds the capability for the ironic-conductor and standalone service process to transmit timer and counter metrics to the message bus notifier which may be consumed by a ceilometer, ironic-prometheus-exporter, or other consumer of metrics event data on to the message bus. This functionality is not presently supported on dedicated API services such as those running as an ``ironic-api`` application process, or Ironic WSGI application. This is due to the lack of an internal trigger mechanism to transmit the data in a metrics update to the message bus and/or notifier plugin. This change requires ironic-lib 5.4.0 to collect and ship metrics via the message bus. Depends-On: https://review.opendev.org/c/openstack/ironic-lib/+/865311 Change-Id: If6941f970241a22d96e06d88365f76edc4683364
* | | | Merge "Set lockutils default logging"Zuul2023-02-231-0/+8
|\ \ \ \
| * | | | Set lockutils default loggingJulia Kreger2023-02-201-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While developing some internal metrics collection capability, and the realization that a lock was needed, we realized that the lock activity itself would be a bit noisy. And image actions also get lock logging, and it is just really noisy, but not super helpful for troubleshooting. So, set it to WARNING instead. Discussion wise, see: https://review.opendev.org/c/openstack/ironic-lib/+/865311 Change-Id: I3ab14ee5b5cc063784d26e3c760f1422c692060d
* | | | | Merge "Relaxing console pid looking"Zuul2023-02-231-0/+6
|\ \ \ \ \
| * | | | | Relaxing console pid lookingKaifeng Wang2023-02-151-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Recently we hit an issue that the pid file is missing, current logic simply removes pid file if the corresponding process is not found, but if the pid file is lost then the console could never be stopped and futher more, be restarted, regardless if the process is there or not. This patch captures FileNotFound to the exception handling to allow console recovery. Change-Id: I1a0b8347e960c6cff8aca10a22c67b710f7d617e
* | | | | | Merge "fix inspectwait logic"Zuul2023-02-231-0/+5
|\ \ \ \ \ \ | |_|_|_|_|/ |/| | | | |
| * | | | | fix inspectwait logicJulia Kreger2023-02-151-0/+5
| | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The tl;dr is that we changed ``inspecting`` to include a ``inspect wait`` state. Unfortunately we never spotted the logic inside of the db API. We never spotted it because our testing in inspection code uses a mocked task manager... and we *really* don't have intense db testing because we expect the objects and higher level interactions to validate the lowest db level. Unfortunately, because of the out of band inspection workflow, we have to cover both cases in terms of what the starting state and ending state could be, but we've added tests to validate this is handled as we expect. Change-Id: Icccbc6d65531e460c55555e021bf81d362f5fc8b
* | | | | Merge "Add release note for node sharding"Zuul2023-02-201-0/+14
|\ \ \ \ \
| * | | | | Add release note for node shardingJay Faulkner2023-02-171-0/+14
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | Release note covers changes in the previous 4 commits in this chain. Change-Id: I5388e82e958acd930295215c9f9427080650866d
* | | | | Merge "Make metrics names a little more consistent"Zuul2023-02-201-0/+9
|\ \ \ \ \
| * | | | | Make metrics names a little more consistentJulia Kreger2023-01-181-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some of these metrics decorator were unlabeled without a class which would result in semi-confusing structures for the metrics counters. Now, we should be semi-consistent. Change-Id: Ie2795419991dc941f2a2b2bc0c6116b92d285041
* | | | | | Merge "Fixes console port conflict occurs in certain path"Zuul2023-02-201-0/+8
|\ \ \ \ \ \ | |_|/ / / / |/| | | | |
| * | | | | Fixes console port conflict occurs in certain pathKaifeng Wang2023-02-151-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The dynamically allocated console port for a node is saved into database and reused on subsequent console operations. In certain code path the port record cann't be trusted and we should do a re-allocation. This patch fixes the issue by ignores previous allocation record. The extra cleanup in the takeover is not required anymore and removed as well. Change-Id: I1a07ea9b30a2c760af7a6a4e39f3ff227df28fff Story: 2010489 Task: 47061
* | | | | | Imported Translations from ZanataOpenStack Proposal Bot2023-02-041-6/+86
| |_|_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I2f70fbaeab4b1bdf3b9104887534f0e7bcc0d337
* | | | | Merge "Add `service` role RBAC policy support"Zuul2023-01-311-0/+13
|\ \ \ \ \
| * | | | | Add `service` role RBAC policy supportJulia Kreger2023-01-181-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change adds support for the ``service`` role, which is intended largely for service to service communiation, such as if one wanted to utilzie a "nova" project, and have an ironic service user within it, and then configure the ``nova-compute`` service utilizing those credentials. Or vice versa, an "ironic" project, with a nova user. In this case, access is exceptionally similar to the rights afforded to a "project scoped manager" or an "owner-admin". Change-Id: Ifd098a4567d60c90550afe5236ae2af143b6bac2
* | | | | | Imported Translations from ZanataOpenStack Proposal Bot2023-01-281-237/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: Ic09d2611553534416d94343c16fbd5b5168be883
* | | | | | Merge "Fix grub config path default"21.3.0Zuul2023-01-271-0/+14
|\ \ \ \ \ \
| * | | | | | Fix grub config path defaultJulia Kreger2023-01-111-0/+14
| | |/ / / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Grub2 looks for files in different paths depending on the boot mode of the binary. Previously the grub_config_path setting was defaulted to the path used exclusively for BIOS booting, which meant anyone using it had to override the setting. Now, we've set the default to the default for UEFI booting, and the world should be a happier, and less override filled place. Change-Id: Id6723e92efb62f8ca03099f15c90580cec887ddd
* | | | | | Move and fix reno config for releasenotes jobJay Faulkner2023-01-261-0/+5
| |_|_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In its current place, reno config changes will not cause build-openstack-releasenotes job to run, which means changes can land to that config without being tested. Yikes! Also fixes error in regexp which was preventing this from actually fixing the build-openstack-releasenotes job. Change-Id: I4d46ba06ada1afb5fd1c63db5850a1983e502a6c
* | | | | Merge "[iRMC] Handle IPMI incompatibility in iRMC S6 2.x"Zuul2023-01-181-0/+15
|\ \ \ \ \
| * | | | | [iRMC] Handle IPMI incompatibility in iRMC S6 2.xVanou Ishii2023-01-171-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since iRMC S6 2.00, iRMC firmware disables IPMI over LAN with default iRMC firmware configuration. To deal with this firmware incompatibility, this commit modifies driver's methods which use IPMI to first try IPMI and, if IPMI fails, try to use Redfish API. Story: 2010396 Task: 46746 Change-Id: I1730279d2225f1248ecf7fe403a5e503b6c3ff87
* | | | | | Merge "[iRMC] identify BMC firmware version"Zuul2023-01-181-0/+19
|\ \ \ \ \ \ | |/ / / / / | | | / / / | |_|/ / / |/| | | |
| * | | | [iRMC] identify BMC firmware versionVanou Ishii2023-01-161-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since iRMC S6 2.00, iRMC firmware doesn't support HTTP connection to REST API. To deal with this firmware incompatibility, this commit adds verify step to check connection to REST API and adds node vendor passthru to fetch&cache version of iRMC firmware. Story: 2010396 Task: 46745 Change-Id: Ib04b66b0c7b1ef1c4175841689c16a7fbc0b1e54
* | | | | Merge "Fix selinux context of published image hardlink"Zuul2023-01-171-0/+7
|\ \ \ \ \
View Lorry Controller Status