summaryrefslogtreecommitdiff
path: root/releasenotes
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Fix pxe image lookups"Zuul2022-08-081-0/+6
|\
| * Fix pxe image lookupsJulia Kreger2022-08-041-0/+6
| | | | | | | | | | | | | | | | | | | | Image lookups in the PXE interface, for anaconda specific code, were previously hard coded to try and invoke use of glance if needed. Except, not everything is glance. Change-Id: I8791623be95e7e47739ee051753de97eb0e5e2a3
* | Merge "Finally remove support for netboot and the boot_option capability"Zuul2022-08-051-0/+6
|\ \ | |/ |/|
| * Finally remove support for netboot and the boot_option capabilityDmitry Tantsur2022-08-021-0/+6
| | | | | | | | | | | | | | | | | | | | | | Instance network boot (not to be confused with ramdisk, iSCSI or anaconda deploy methods) is insecure, underused and difficult to maintain. This change removes a lot of related code from Ironic. The so called "netboot fallback" is still supported for legacy boot when boot device management is not available or is unreliable. Change-Id: Ia8510e4acac6dec0a1e4f5cb0e07008548a00c52
* | Merge "Exit ipxe script if enable_netboot_fallback failed"Zuul2022-08-031-0/+6
|\ \
| * | Exit ipxe script if enable_netboot_fallback failedDerek Higgins2022-08-011-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The sanboot trick to boot from local disk does not work on all hardware. If it fails exit 0 from the iPxe script so that boot continues on the next device which may be the local disk. Story: #2009258 Task: #43470 Change-Id: I1b6303a987a102dfbfd233334395321c25a55212
* | | Merge "Enable the ramdisk deploy by default"Zuul2022-08-031-0/+6
|\ \ \ | | |/ | |/|
| * | Enable the ramdisk deploy by defaultDmitry Tantsur2022-08-011-0/+6
| |/ | | | | | | | | | | | | It proved useful (supported by Metal3, used in OpenShift) and does not require any conductor-level configuration. Change-Id: I57e59ac21e3327b9ad2f1d1436e184b48999006b
* | Suppress Chassis Not Found on API OperationJulia Kreger2022-08-021-0/+9
|/ | | | | | | | | | | | | | | | | | | | | | | | | | When you have a multi-db deployment, or even just many different threads operating on the same server with different transactions, you can run into a situation where one thread initiates a transaction to get a list of nodes, and then another triggers a delete of the chassis (and most likely node, but hey, there is really no way to detect that and work.) So as the API is processing the response and making the json result set, the query to resolve a chassis_id on a node object can begin to fail. Before this patch, this would raise an exception to the client. Now, we just suppress the error, and return the field value as None. In the grand scheme, the node is likely has also already been deleted as well. Change-Id: I3594ac580c01454c70922a965a2a653a8b568cbb Closes-Bug: 1508995 Story: 1508995 Task: 10038
* Imported Translations from ZanataOpenStack Proposal Bot2022-07-282-164/+271
| | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I0a9b547e92b288a555c246d63d007b831a6e1190
* Merge "[iRMC] Add SNMPv3 authentication functionality"Zuul2022-07-221-0/+30
|\
| * [iRMC] Add SNMPv3 authentication functionalityShukun Song2022-07-151-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently when using SNMPv3, iRMC driver does not use SNMPv3 authentication parameters so the SNMPv3 authentication will always fail. And iRMC cannot recognize FIPS mode, so when FIPS mode is enabled, iRMC driver could still use non-FIPS-compliant algorithms. This commit changes iRMC driver to require and use SNMPv3 authentication parameters when 'irmc_snmp_version' is set to v3 and also makes iRMC driver to force 'irmc_snmp_version' to v3, 'irmc_snmp_auth_proto' to SHA and 'irmc_snmp_priv_proto' to AES when FIPS mode is enabled, because currently among the algorithms supported by iRMC, only SHA and AES are FIPS compliant. Change-Id: Id6f8996e4d103f849325f54fe0619b4acb43453a Story: 2010085 Task: 45590
* | Merge "Deprecate syslinux"Zuul2022-07-221-0/+26
|\ \
| * | Deprecate syslinuxJulia Kreger2022-07-131-0/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Syslinux is a functionally abandoned Legacy BIOS boot mode bootloader which has not seen updates since 2019, and is starting to see discussion amongst linux distributions to remove explicit support and packaging for Syslinux. Syslinux's relevance is also disappearing as UEFI booting is becoming the standard. While syslinux did go ahead and ensure their bootloader *could* be built and support UEFI, distributions also didn't uniformly adopt packaging and support for this bootloader. This change proposes to deprecate it and notates the areas in which functionality is deprecated. Change-Id: Ic52007fa4f207561d282eb5ae54273885c0ab0c0
* | | Merge "project scoped manager support"Zuul2022-07-221-0/+8
|\ \ \
| * | | project scoped manager supportJulia Kreger2022-07-201-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds support for project manager role support which is a state between project scoped admin and project scoped member. Finally enabling to be merged since the higher end goal/work finally merged on March 1st. Related: https://review.opendev.org/c/openstack/governance/+/815158 Change-Id: Ia35f4a4c3c2af68dc64bfe32f206e57056876dc7
* | | | Merge "Do not require stage2 for anaconda with standalone"Zuul2022-07-211-0/+11
|\ \ \ \
| * | | | Do not require stage2 for anaconda with standaloneJulia Kreger2022-07-201-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The use of the anaconda deployment interface can be confusing when using a standalone deployment model. Specifically this is because the anaconda deployment interface was primarily modeled for usage with glance and the inherent configuration of a fully integrated OpenStack deployment. The additional prameters are confusing, so this also (hopefully) provides clarity into use and options. Change-Id: I748fd86901bc05d3d003626b5e14e655b7905215
* | | | | Merge "Remove support for trusted boot"Zuul2022-07-201-0/+5
|\ \ \ \ \
| * | | | | Remove support for trusted bootDmitry Tantsur2022-07-181-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It requires network booting and legacy boot. While the latter will be supported for a long time, the former is being removed. Change-Id: Ie48e51fa95ba2059bd3cca6b8968f475934a75e5
* | | | | | Merge "Fix compatibility with jsonschema>=4.0.0"Zuul2022-07-181-0/+9
|\ \ \ \ \ \ | |/ / / / / |/| | | | |
| * | | | | Fix compatibility with jsonschema>=4.0.0Dmitry Tantsur2022-07-141-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specify the schema version for network_data and node, otherwise the latest one is used. Also fix one test where the error messages was changed. Change-Id: I4a614d7e73348bbe6c355a40881b013cbfe00b03
* | | | | | Merge "Allocation candidates prefer matching name"Zuul2022-07-151-0/+7
|\ \ \ \ \ \ | |/ / / / / |/| | | | |
| * | | | | Allocation candidates prefer matching nameSteve Baker2022-06-161-0/+7
| | |_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change finds a node with the same name as the allocation and moves it to the beginning of the shuffled candidate list so that node is the first allocation attempt. It is common for node naming scheme to match the node's role (such as compute-1, compute-2). Also this often matches the hostname (allocation name) scheme. Without this change, this scenario will generally result in swapped names (node compute-1 having hostname compute-2, etc). By preferring matching names this situation can be avoided in the majority of cases, while not otherwise affecting the candidiate allocation approach. Change-Id: Ie990bfc209959d58852b9080778602eab5aa30af
* | | | | Merge "Make anaconda non-image deploys sane"Zuul2022-07-141-0/+21
|\ \ \ \ \ | | |/ / / | |/| | |
| * | | | Make anaconda non-image deploys saneJulia Kreger2022-07-111-0/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ironic has a lot of logic built up around use of images for filesystems, however several recent additions, such as the ``ramdisk`` and ``anaconda`` deployment interfaces have started to break this mold. In working with some operators attempting to utilzie the anaconda deployment interface outside the context of full OpenStack, we discovered some issues which needed to be make simpler to help remove the need to route around data validation checks for things that are not required. Standalong users also have the ability to point to a URL with anaconda, where as Operators using OpenStack can only do so with customized kickstart files. While this is okay, the disparity in configuraiton checking was also creating additional issues. In this, we discovered we were not really graceful with redirects, so we're now a little more graceful with them. Story: 2009939 Story: 2009940 Task: 44834 Task: 44833 Change-Id: I8b0a50751014c6093faa26094d9f99e173dcdd38
* | | | | Update known issue for iDRAC Swift firmware updateAija Jauntēva2022-07-121-0/+8
| |_|_|/ |/| | | | | | | | | | | | | | | | | | | The issue is fixed in iDRAC firmware 6.00.00.00. Change-Id: Ie5b9ce3ed2a9b1cd61d51f64d72403f7dbc5367b
* | | | Merge "Prevent pxe retry when agent token exists"Zuul2022-07-111-0/+7
|\ \ \ \
| * | | | Prevent pxe retry when agent token existsJulia Kreger2022-06-231-0/+7
| | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A race condition can be observed in CI under heavy load where the conductor triggers are boot of the agent before it is fully online based upon state, but not considering the existence of an agent token. As a result, agent is never able to check in with Ironic and the overall operation fails. We now consider agent token's existence before retrying PXE as it is the very earliest indicator of a starting agent. Change-Id: Ice764866a08647031d16570860ec384204269501 Story: 2010107 Task: 45674
* | | | Merge "Prevent clear_job_queue and reset_idrac failures on older iDRACs"Zuul2022-07-061-0/+8
|\ \ \ \ | |_|/ / |/| | |
| * | | Prevent clear_job_queue and reset_idrac failures on older iDRACsJacob Anders2022-07-051-0/+8
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, clear_job_queue and reset_idrac steps are only supported on idrac-redfish driver on iDRAC9 hardware. However, Ironic still attempts to run these steps on iDRAC8 BMCs configured with idrac-redfish driver which results in verification failures. This change attempts to resolve it by catching the related exception, logging a warning and continuing verification. In case of cleaning, it still fails. Story: 2010091 Task: 45630 Change-Id: Icd8c5378469887962ff32eea2f38697c539f7e95
* | | Merge "Auto-populate lessee for deployments"Zuul2022-07-021-0/+11
|\ \ \
| * | | Auto-populate lessee for deploymentsJulia Kreger2022-05-231-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds a configuration option and capability to automatically record the lessee for a deployment based upon the original auth_token information provided in the request context. Additional token information is now shared through the context which is extended in the same fashion as most other projects saving request token information to their RequestContext, instead of triggering excess API calls in the background to Keystone to try and figure out requestor's information. Change-Id: I42a2ceb9d2e7dfdc575eb37ed773a1bc682cec23
* | | | Merge "Fix redfish-virtual-media for newer iDRACs"Zuul2022-07-011-0/+9
|\ \ \ \
| * | | | Fix redfish-virtual-media for newer iDRACsAija Jauntēva2022-06-291-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The issue with standard Redfish virtual media boot has been fixed now. Update to restrict use of redfish-virtual-media based on iDRAC firmware version. Change-Id: I8ead1d24a9bd502b64fe7dd058e77550fcee141c
* | | | | Merge "Fix Redfish RAID to update raid_config"Zuul2022-06-301-0/+6
|\ \ \ \ \ | |/ / / / |/| | | |
| * | | | Fix Redfish RAID to update raid_configAija Jauntēva2022-05-231-0/+6
| |/ / / | | | | | | | | | | | | | | | | | | | | Story: 2003514 Task: 41940 Change-Id: I753c4b00c0a64bcdc89c9bc0afd46f1211f7847b
* | | | No deploy_kernel/ramdisk with the ramdisk deploy and no cleaningDmitry Tantsur2022-06-231-0/+6
| |/ / |/| | | | | | | | | | | | | | | | | | | | | | | Ramdisk deploys don't use IPA, no need to provide it. Cleaning may need the agent, so only skip verification if cleaning is disabled. Other boot interfaces may need fixing as well, I haven't checked them. Change-Id: Ia2739311f065e19ba539fe3df7268075d6075787
* | | Remove unicode literal from codeLiZekun2022-06-021-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | All strings are considered as unicode literal string from Python 3. This patch drops the explicit unicode literal (u'...') appearances from the unicode strings. Change-Id: I52ae9180344baf408e6e8a932e9d59dc45ece9de
* | | Don't use URLs as part of temporary file names (part 2)Dmitry Tantsur2022-05-191-0/+5
|/ / | | | | | | | | | | | | | | | | | | | | First, it's leaking information. Second, the URLs can be really long and cause "OSError: [Errno 36] File name too long". The same issue has already been fixed in the image cache, this change updates building ISO. Since the files are created in a temporary location, just use constant names. Change-Id: Ie5e0523bb4a8941bcb8dc87c4a0b29cb28ddfe40
* | Exclude current conductor from offline_conductorsHarald Jensås2022-04-281-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In some cases the current conductor may have failed to updated the heartbeat timestamp due to failure of resource starvation. When this occurs the dbapi get_offline_conductors method will include the current conductor in its return value. In this scenario the conductor may end up forcefully remove node reservations or allocations from itself, triggering takeover which fail on-going operations. This change adds a wrapper to exclude the current conductor. The wrapper will log a warning to raise the issue. Related-Bug: #1970484 Stroy: 2010016 Task: 45204 Change-Id: I6a8f38934b475f792433be6f0882540b82ca26c1
* | [iRMC] Change the way to get irmc-info in raidZhou Hao2022-04-241-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When using the node managed by the `irmc` hardware type, if the port number of the bmc address is manually specified, the following error will occur when configuring raid: ``` %d format: a number is required, not str ``` Change raid to call parse_driver_info to get irmc_info, so that irmc-port can be converted to int type to avoid this error. Story: #2010009 Task: #45151 Signed-off-by: Zhou Hao <zhouhao@fujitsu.com> Change-Id: I35e0aa2a5e612e6e45c9489153dbb3ff3e500a66
* | Allow reusing defaults in per-node kernel_append_paramsDmitry Tantsur2022-04-111-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | It may be convenient to use [pxe/redfish/...]kernel_append_params as the universal defaults, while using {driver,instance}_info to only append values. This change allows that by replacing %default% with the value of the applicable configuration option. An example use case: CoreOS requires an additional artifact (root filesystem URL) when PXE booting. While here, fix the PXE/iPXE interface documentation. Change-Id: I829291ab5cc19ec2ca43bc45815d012697f0b408
* | Start API after conductor is started in the combined executableDmitry Tantsur2022-03-241-0/+6
| | | | | | | | Change-Id: Icaffb5d346001d62e5c9522708dd44f01faeb3a6
* | Update master for stable/yogaOpenStack Release Bot2022-03-242-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/yoga. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/yoga. Sem-Ver: feature Change-Id: I371614afe321758536d7840207c34329f9cba1c5
* | Fix 20.1 prelude releasenote20.1.0Iury Gregory Melo Ferreira2022-03-231-3/+4
| | | | | | | | Change-Id: I899e78da376c06d9f9d5bad95cdb0b494a3ca494
* | Prepare Yoga release with 20.1Iury Gregory Melo Ferreira2022-03-222-4/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | This is a pre-release commit for the Yoga release following our docs [1] * No API additions during this cycle (no need to update doc/source/contributor/webapi-version-history.rst) * Add prelude releasenote * Fix highlight in one releasenote [1] https://docs.openstack.org/ironic/latest/contributor/releasing.html Change-Id: If26019c5abc0643051f4b11186d7eb819f9c407b
* | Merge "Fix rebuilds using anaconda deploy interface"Zuul2022-03-121-0/+9
|\ \
| * | Fix rebuilds using anaconda deploy interfaceRuby Loo2022-03-041-0/+9
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | The anaconda deploy interface was saving internal information in the node's instance_info, in the user-facing 'stage2' and 'ks_template' fields. This broke rebuilds using a different image with different stage2 or template specified in the image properties. This has been fixed by saving the information in the node's driver_internal_info instead. Addresses comments/nits from https://review.opendev.org/c/openstack/ironic/+/827924. Change-Id: Id9428518d21290fb38a0f7471a2cb69a6cb3ffb2
* | Merge "Support img_type Glance property"Zuul2022-03-111-0/+2
|\ \
View Lorry Controller Status