summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fixes for tox 4.0stable/trainJay Faulkner2022-12-151-2/+7
| | | | | | Formatting changes in config file required for tox 4.0. Change-Id: I84202ac10e9195647162f0b5737ebb610ef1ef93
* CI: Pin train to use only basic standalone testsJulia Kreger2022-10-141-1/+1
| | | | | | | | | | The tempest tests involve cleaning which attempts software raid, however this doesn't really work on Train, As this is the only standalone test, restrict the regex to: ironic_standalone.test_basic to match what we expect to test and pass on Train. Change-Id: I86d63c43e4d057ec5b3e23c2e8311f9f0be4299a
* Merge "Fix iRMC driver to use certification file in HTTPS" into stable/trainZuul2022-09-2811-54/+501
|\
| * Fix iRMC driver to use certification file in HTTPSVanou Ishii2022-09-1811-54/+501
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch modifies iRMC driver to use certification file when it connects to iRMC via HTTPS Conflicts: doc/source/admin/drivers/irmc.rst driver-requirements.txt ironic/drivers/modules/irmc/common.py ironic/drivers/modules/irmc/raid.py ironic/tests/unit/drivers/modules/irmc/test_common.py ironic/tests/unit/drivers/modules/irmc/test_power.py lower-constraints.txt releasenotes/notes/irmc-add-certification-file-option-34e7a0062c768e58.yaml Change-Id: If69ce1cf2789d9d60fb8e544596cf7d29eab514d Co-authored-by: Kobayashi Daisuke <kobayashi.da-06@fujitsu.com> Co-authored-by: Song Shukun <song.shukun@jp.fujitsu.com> Story: 2009801 Task: 44345 (cherry picked from commit 64d7a7f3077bc000a18c4a0c56f122941b262483) (cherry picked from commit 6c0152afa141d05ee28cba81178622021574ae17) (cherry picked from commit 931f13d3c547928d57052eeae1d8d2fb8c6bd194) (cherry picked from commit 6177b244a55a1a92dddc6a6763137db608c6c59e) (cherry picked from commit 37a9a95e7703f612e107a617700e189abea977e5) (cherry picked from commit e5b913a042dfdf0977df6c5009f554dd9773ab8c)
* | Make test-setup.sh compatible with mysql8Sean McGinnis2022-09-121-2/+2
|/ | | | | | | | | | | | | Starting from mysql version 8 it's not possible to create a user implictly when using GRANT. This patch makes the behavior compatible with that. Change-Id: I2b73a532deb8782c2c0bb05070b727e9edc6e9d8 Co-written-by: Riccardo Pittau <elfosardo@gmail.com> Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com> (cherry picked from commit 58693c7f4db0c65c8a0ed8037bcacbbf07a7346e) (cherry picked from commit 8d6cf57bb4417115f6640c714d53e5e723b2d40f)
* Modify test code to avoid CONF modification affectionVanou Ishii2022-08-095-55/+56
| | | | | | | | | | | | | | | | | | | | | Few unit tests change attribute of CONF variable via Python assignment. This changes attribute of CONF, which is instance of XxxOpt class defined in oslo_config, to Python literal value. This affects result of another unit test. To avoid this, we should change attribute of CONF variable with set_override method. Change-Id: I4bd8b1b4ea974834f1149fcaa79de85d24f5f7d1 Story: 2010214 Task: 45956 (cherry picked from commit 3b28d0984d5eb82320c632dd5840cebf6d0762ad) (cherry picked from commit 593a547a8dbbbeee2225520812f8b235c39656b0) (cherry picked from commit 3f624e5caa83acf9b98443cf32cb0cd69143c6e2) (cherry picked from commit 35e20b62de1a867534d54de844496072ae291eac) (cherry picked from commit 7d47ee3344c6a8fc81c039fe21cc83645d3c63d9) (cherry picked from commit f2431ed1f4112a4781362229b75af2353b24dbfd)
* CI: Removing ironic job queueJulia Kreger2022-05-261-1/+0
| | | | | | Change-Id: Idf7991d8f8a8cebcdc0413f26ad31542f8ffa8a8 See: https://zuul-ci.org/docs/zuul/latest/releasenotes.html#relnotes-4-1-0-deprecation-notes (cherry picked from commit 63e53797adca625edd2fdacd16a025bedccf8731)
* Remove redfish cache entry upon errorsJulia Kreger2022-03-154-1/+115
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some transient errors can ultimately cause the client to need to be completely restarted due to cached connection data. Ironic now explicitly removes the cache entry when a sushy AccessError or python AttributeError is detected originating from the library. This will now result in the prior cached connection object to be discarded, and upon the next attempt to interact with the same node, a new connection will be launched. This will result in new sessions being created, but in all likelihood the prior session had already timed out or had been administratively removed. Sushy's code, as of https://review.opendev.org/c/openstack/sushy/+/820076 will raise SessionService lookup access errors as AccessErrors. Prior to that change, they should have been raised as AttributeError as the previous call sould have returned None to be used as an object. *Also* Includes follow-up change Ia59f774c9340e3a6fa63418afedf12098c709052 squashed into this change, and necessary backport friendly mock of AccessError which had changed since this release of ironic. Change-Id: Icc6e5dd74d9f15e679a7e764fe49238ed6b8dc1e Story: 2009719 Task: 44107 (cherry picked from commit 1439af27ba2bd31fb85369754c648a45ee9ca14b) (cherry picked from commit 01997c8418b9e6ade47437b09dd9412310b90eac) (cherry picked from commit e3e7deaf48a5315fe10350e8a87b2fcc4e189406) (cherry picked from commit ab5495eecb409b37ad853a679032d6cdb4fefc72) (cherry picked from commit e57aa7598b220bb2d1fd8fcc0aab6132926d5cce) (cherry picked from commit 3e3afc3254aa7bf2c27033ac9f0aa5f503dff9b0) (cherry picked from commit 4b6b63ac6617bcdb21fdd16e3f2b991536635a2d)
* Fix Train CIJulia Kreger2022-03-153-9/+7
| | | | | | | | | | | | | | | | | CI for stable/train presently fails on: ./ironic/drivers/modules/drac/power.py:174:22: F821 undefined name '_' Which was used for translations, but translations are not used in the file, as such stripped away the _ method invocation. Additionally, we have some semi-random job failures due to dual jobs running. In particular we fixed this in the Ussuri branch previously in Iea06632feee59714238f3b5b144bdadb733a0c35, but this change also applies this, and comments out jobs which we know are no longer functional or able to be run due to aspects outside of our control. Change-Id: I98d0c92d17e78aa5624f969710090f668df8eb0f
* Merge "CI: Work around tinyipa build issues" into stable/trainZuul2021-11-232-0/+14
|\
| * CI: Work around tinyipa build issuesJulia Kreger2021-11-222-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The qemu git server has updated it's ssl certificate, and can no longer be verified by the software libraries and embedded tinycore data for the 10.x release. Unfortunately, we have CI hard coded to an older release and we cannot release a newer, older version of the tinycore 10.x supporting packages. So, for our CI purposes, we just need a working build, so that is all this patch attempts to do, get our CI in a working state for the older branches. It is an awful change. None of us like it, but we're stuck and this is the only path forward short of completely abandoning the use of the software builds on these branches. Change-Id: I44f2a05c3f37a6dad0b9c88e2a7f6c66be8a1b78 (cherry picked from commit 6478d03d2973928a63163d931173d79acfcf849e)
* | Fix redfish-virtual-media file permissionSteve Baker2021-11-224-5/+45
|/ | | | | | | | | | | | When not using swift with the redfish virtual media boot interface, in other words local file storage, the file permissions for the /httpboot/redfish folder was incorrect upon initially being created, and new file ISOs were being created with permissions based upon the conductor process umask value which is OS environment dependent. Change-Id: I038ca335efa9b5443469ab8c8af12863deea0e38 (cherry picked from commit af6cd1093d7b4be25a8bfbbdf1fb13226f6bfa7e) (cherry picked from commit b1c8976d4bed3ab818fa7dd5b16e24a7507333aa)
* Fix idrac-wsman deploy with existing non-BIOS jobsAija Jauntēva2021-11-083-4/+19
| | | | | | | | | | | | | | | | | | | | As with WS-Man iDRAC API setting boot device requires creating BIOS job and there can be only 1 open job per subsystem present in iDRAC, there is validation to check that the job queue is empty before continuing setting boot device. This does not work well for cases when using autoupdatescheduler that creates `Repository Update` job that stays Scheduled until executed and then followed by new Scheduled `Repository Update` job. This patch allows non-BIOS jobs to be present in the queue when setting boot device. This will still fail for cases when there are BIOS jobs present. In such cases should consider moving to idrac-redfish that does not create BIOS or any other job to set boot device. Story: 2009251 Task: 43437 Change-Id: I91e9ba3024a85897aeead21cede57464294b409b (cherry picked from commit b1d08ae80542b6b3aa9fab99cdc64b449d113115)
* Extend power sync timeout for Ericsson SDIJulia Kreger2021-10-272-1/+10
| | | | | | | | | | | | | | | | | Ericsson SDI uses cached power state data in what is returned to the API user, and typically this takes longer than 30 seconds to provide an updated value to the API user. As such, if we do not extend the timeout value, such users of Ironic's Redfish API interface will have deployments fail as the power state timeout will be encountered. This change landed in ussuri, and is proposed to stable/train due to TripleO CI failures. Related-Bug: #1947403 Change-Id: I0aa5131504b60b13d43c73c9a3be1f50f7855cbc (cherry picked from commit 4383303dfbfe15f3dfbd8be8d4cc6d70aa703019)
* [Stable only] remove require_exclusive_lock from detect_vendorDmitry Tantsur2021-09-271-1/+0
| | | | | | | | | | Presumably it was added by a mistake in the Ussuri backport. Functions that only read data from the BMC must not require an exclusive lock, and this bug causes a failure when syncing power state. Change-Id: I051da583ef6e5131ce36b70b862e91cfdae2b213 (cherry picked from commit e9b16d026171436c66d1651e38c71c9f20acb144)
* Merge "Update the clear job id's constant" into stable/trainZuul2021-09-173-3/+10
|\
| * Update the clear job id's constantDhuldev Valekar2021-06-293-3/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | Fixes an issue of powering off with the ``idrac-wsman`` management interface while the execution of a clear job queue cleaning step is proceeding. Prior to this fix, the clean step would fail when powering off a node. Story: 2008988 Task: 42641 Change-Id: Ib4ab755c806f028d97379b80a8c27d6ade63cba1 (cherry picked from commit 741a4d8a88bbc51f5903fc00cc4f1decf8f4ea1a)
* | Merge "Fix idrac-wsman set_power_state to wait on HW" into stable/trainZuul2021-09-173-25/+44
|\ \
| * | Fix idrac-wsman set_power_state to wait on HWAija Jauntēva2021-09-143-25/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | set_power_state has returned to the caller immediately without confirming the system has reached the requested state. This fixes that by synchronously waiting until the target state has been read before returning. That bug can cause instance workload deployments to fail on Dell EMC PowerEdge server models on which IPA ramdisk soft power off fails and ironic employs its OOB fallback strategy. After an otherwise successful deployment, the node is active, but is powered off. No error is reported in last_error. If the subsequent instance workflow expects the system to be powered on into the operating system, it fails. Story: 2009204 Task: 43261 Change-Id: I3112a22149c07e5508f26c79f33d09aeb905c308 (cherry picked from commit 2a0fd1d13f178c9872330cf6498dc25572a721da)
* | | Use shim-signed on Ubuntu, shim is empty nowDmitry Tantsur2021-09-164-9/+12
| | | | | | | | | | | | | | | | | | | | | | | | Also fix the documentation to use the correct paths and versions. Change-Id: I7f004d40c1b8c617f9a456216df091e44d69693f (cherry picked from commit 294046befae669dacd159d9f26bcdd3bc8ff26c9) (cherry picked from commit 87dee0250c43e059db727e76b407a0f67c719f43)
* | | Fix Redfish jobs by pinning sushy-toolsJulia Kreger2021-09-162-2/+6
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Sushy-tools pulls in master branch by default based on the job configuration, however we recently merged support into sushy-tools which requires a version of ironic-lib, which is unavailable to this system resulting in an exception. File "/opt/stack/sushy-tools/sushy_tools/emulator/main.py", line 24, in <module> from ironic_lib import auth_basic ImportError: cannot import name 'auth_basic' *Also* Temporarily disables the grub2 jobs to allow multiple fixes to be merged in sequence. Change-Id: Ie8c10db135a77bd4cc2e17a266a45cca65100199
* | Merge "Provide a path to set explicit ipxe bootloaders" into stable/trainZuul2021-07-2811-42/+224
|\ \
| * | Provide a path to set explicit ipxe bootloadersJulia Kreger2021-07-2711-42/+224
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I did something stupid when started driving forth the split of ipxe from the pxe interface: I didn't think about the need to actually separate bootloaders. In part, because the use case was a mixed Power8/Power9 and x86 cluster. Mainly because the Power hardware does not honor or care about the bootfile name provided over DHCP. The firmware knows how to read the PXELINUX boot file format and the machines are able to boot from there. Where this all goes sideways is when: * Enabled boot interfaces are set to ipxe,pxe * No default boot interface is set * Node is created without a default for x86 hardware. * Node uses ipxe boot_interface, and creates files under /httpboot * bootfile transmitted via DHCP is pxelinux.0. Fun right? The simple workaround for the power user is to just define the iPXE loader, or maybe use UEFI. But that is neither here nor there, this is still a bug and a possible use case is GRUB2 via PXE and iPXE. Not that would really work via ipxe, but hopefully people get the idea. The solution kind of seems clear, duplicate configuration and fallback if not defined. This is backported to stable/train as a prerequisite to backporting https://review.opendev.org/c/openstack/puppet-ironic/+/797683 Story: #2007003 Task: #40282 Change-Id: I4419254c23095929e52a0fda11789f2f5167dc6b (cherry picked from commit 5f7d84f483be165fde04954453e156ceefc43d28)
* | Set driver lib tox jobs to utilize openstack-toxJulia Kreger2021-07-271-2/+2
|/ | | | | | | | | | | | The standard tox job is not version aware for the nodeset which can result in the job pulling in things such as higher python versions which are not supported. The openstack-tox job *is* aware and apparently does the right thing. This should correct failures with the driver-libs test jobs. Change-Id: Ib4788a6a610c688483425a6253cea43ce12bf94b
* Merge "update grub2 file name" into stable/trainZuul2021-04-213-5/+48
|\
| * update grub2 file nameArmstrong Liu2021-04-123-5/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Some higher versions of grub2 (e.g. 2.05 or 2.06-rc1) use grub.cfg-01-MAC, while another lower versions of grub2 (e.g. 2.04) use MAC.conf, so we generate both paths in order to be compatible with both. For more information we can see: https://docs.oracle.com/en/operating-systems/oracle-linux/7/install/ol7-install-prepare.html#ol7-install-pxe-boot-uefi Change-Id: Icbdd284de38b8e54c52cdbba709bba0e644c35cd Signed-off-by: Armstrong Liu <vpbvmw651078@gmail.com> (cherry picked from commit 8f474bfe598849d0dfffb4ede11057f0411dde3c)
* | Merge "Restrict syncing of boot mode to Supermicro" into stable/trainZuul2021-04-203-13/+30
|\ \
| * | Restrict syncing of boot mode to SupermicroBob Fournier2021-04-153-13/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The fix for https://storyboard.openstack.org/#!/story/2008252 synced the boot mode after changing the boot device, because Supermicro nodes reset the boot mode if not included in the boot device set. However this can cause a problem on Dell nodes when changing the mode uefi->bios or bios->uefi. Restrict the syncing of the boot mode to Supermicro. Story: 2008712 Task: 42046 Change-Id: I9f305cb3f33766c1c93cf4347368b1ce025fc635 (cherry picked from commit 8bd25a9882e64ae378974e974c39b874d4b9b0e8) (cherry picked from commit 72fd48b9cb9593dc864de05c4f8ff48829024689)
* | | Merge "For Supermicro BMCs set enable when changing boot device" into ↵Zuul2021-04-203-5/+64
|\ \ \ | |/ / | | | | | | stable/train
| * | For Supermicro BMCs set enable when changing boot deviceBob Fournier2021-04-153-5/+64
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When setting the boot settings on Supermicro BMCs, the BootSourceOverrideEnabled must be set to the desired value whenever the BootSourceOverrideTarget is set or it will revert to the default value (Once). This is different than what is currently implemented for other BMCs in which the BootSourceOverrideEnabled is not set if it matches the current setting. This change uses the vendor setting to determine if it's a Supermicro BMC. Story: 2008547 Task: 41652 Change-Id: I1b1a6baafd4cc4daa2fbdb82f69ded6253b1fcbf (cherry picked from commit 4a7d50ce56b88c82e95665ac6df44666d3e647ed) (cherry picked from commit 7d74ea0eee8f935f5b6c8406e6997d4143fce01e) (cherry picked from commit 2e4e8755680080fca2a31adf7a1dfec7b1c10d0a)
* | | Merge "Refactor vendor detection and add Redfish implementation" into ↵Zuul2021-04-207-21/+163
|\ \ \ | |/ / | | | | | | stable/train
| * | Refactor vendor detection and add Redfish implementationDmitry Tantsur2021-04-157-21/+163
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Get rid of the TODO in the code and prepare for more management interfaces supporting detect_vendor(). Vendor detecting now runs during transition to manageable and on power state sync (essentially same as before but for all drivers not only IPMI). Update the IPMI implementation to no longer hide exceptions since they're not handled on the upper level. Simplify the regex and fix the docstring. Add the Redfish implementation as a foundation for future vendor-specific changes. Change-Id: Ie521cf2295613dde5842cbf9a053540a40be4b9c (cherry picked from commit 121b3348c813eb075ca38bd264a9315ee3acc2fe) (cherry picked from commit 4df73e47e1042dcd3cc693520cf63712df0bb875)
* | | Merge "Allow unsupported redfish set_boot_mode" into stable/trainZuul2021-04-194-1/+57
|\ \ \ | |/ / |/| |
| * | Allow unsupported redfish set_boot_modeSteve Baker2021-03-224-1/+57
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently if the baremetal boot mode is unknown and the driver doesn't support setting the boot mode then the error is logged and deployment continues. However if the BMC doesn't support getting or setting the boot mode then setting the boot mode raises an error which results in the deploy failing. This is the case for HPE Gen9 baremetal, which doesn't have a 'BootSourceOverrideMode' attribute in its system Boot field, and raises a 400 iLO.2.14.UnsupportedOperation in response to setting the boot mode. This is raised from set_boot_mode as a RedfishError. This change raises UnsupportedDriverExtension exception when the 'mode' attribute is missing from the 'boot' field, allowing the deployment to continue. Change-Id: I360ff8180be252de21f5fcd2208947087e332a39 (cherry picked from commit 9f221a7d42350f38bc502c1fd79232593cff7ab2)
* | | IPMI: Handle vendor set boot device differencesJulia Kreger2021-04-155-17/+321
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Supermicro machines, when in UEFI mode, have a different device number, in binary, to represent the hard disk from other vendors such as Fujitsu which actually has somewhat similar code in their driver. This means we need to be somewhat cognizent of the vendor of the BMC and possibly update the device mapping based upon that vendor. This may ultimately fix a number of IPMI related problems, because there is a reliance upon the text output of ipmitool, which only reads the bytes retured by the BMC, which may not be reality after the next reset, espescialy if ipmitool doesn't know of the UEFI operating difference. NOTE: This had to be a direct cherry-pick from the original change as the intermediate branch that we normally would have cherry-picked from has had other changes made to it, which resulted in an unclean backport, where as with the original change it was clean. This was then backported from stable/ussuri to stable/train, where test_ipmitool.py conflicted slightly due to later eventlet changes. Change-Id: Ie19db9e0cf1eafdfc9bb46248f4d457337821f94 Story: 2008241 Task: 41085 (cherry picked from commit a7ac9ce8cd53fdebdf0d9aaeaf439da08a0b3ec8) (cherry picked from commit 8bf3f47476ba685a2aa696aa413b4706f71a4f7a)
* | Merge "DRAC: Fix a failure to create virtual disk" into stable/trainZuul2021-03-224-5/+355
|\ \ | |/ |/|
| * DRAC: Fix a failure to create virtual diskRachit71942021-02-234-5/+355
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | PERC H740P controllers supports RAID mode and Enhanced HBA mode. When the controller is in Enhanced HBA, it creates single disk RAID0 virtual disks of NON-RAID physical disks. Hence the user's request for VD creation with supported RAID fails due to no available physical disk. This patch checks the Perc H740P controllers whether it supports enhanced HBA mode and if controllers are found in enhanced HBA mode it converts back to RAID mode. Change-Id: I9d295135e6059a47cb541ae1218b11c3d56f85e1 Story: 2007711 Task: 39844 (cherry picked from commit 325f28043468472c2f97f659c66817192aba39f7)
* | Lazy-load node details from the DBArne Wiebalck2021-03-095-75/+153
| | | | | | | | | | | | | | | | | | | | In order to reduce the load on the database backend, only lazy-load a node's ports, portgroups, volume_connectors, and volume_targets. With the power-sync as the main user, this change should reduce the number of DB operations by two thirds roughly. Change-Id: Id9a9a53156f7fd866d93569347a81e27c6f0673c (cherry picked from commit 82cab603bbb21d81769cdc4f50d4fa445d026e5c)
* | [Trivial] Fix testing of volume connector exceptionArne Wiebalck2021-03-081-1/+1
| | | | | | | | | | | | | | Restore test symmetry. Change-Id: I54a9fed73e366a30545c3cd1982588d2f544d228 (cherry picked from commit 61c5b3fd2fb1ae0df1cbfbca83e5bda393d0e8e4)
* | Merge "CI: switch the multinode job to tempest-multinode-full-base" into ↵Zuul2021-02-131-2/+6
|\ \ | | | | | | | | | stable/train
| * | CI: switch the multinode job to tempest-multinode-full-baseDmitry Tantsur2020-12-212-3/+6
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The non-base job is designed for the integrated gate and may have unnecessary side effects. It has recently overriding the OVS agent bridge settings, breaking our job. Make the job voting again. Also Remove lower-constraints job As discussed during the upstream ironic community meeting on Monday Dec 14 2020, the lower-constraints job is being removed. Plus Cap version of ipa-builder to 2.2.0 Versions higher than 2.2.0 of ironic-python-agent-builder use tinycore 11.x to build tinyipa, and that uses a kernel too recent to be built on bionic. Change-Id: Ied8cafd32c3e634d498467ebe878a411f0b24e6d (cherry picked from commit 97ceb38a725cac797f9acf2c643d76c36e7293e0) (cherry picked from commit 840488e5951a360bb0f61ce36d33b5253ed19655) (cherry picked from commit 85a1e3d23aa72c20364f7b684e5029c7af219745)
* | Remove grenade jobs from old stable branchestrain-em13.0.7Riccardo Pittau2021-02-011-9/+0
| | | | | | | | | | | | | | | | | | | | As discussed and approved during the ironic wallaby midcycle, the grenade jobs in old stable branches, starting from EM branches and up the oldest not-EM (at this moment train) are removed. Also remove lower-constraints job. Change-Id: I0ecb145469753f9ccabeac881fcaf0976ba723e4
* | Merge "Sync boot mode when changing the boot device via Redfish" into ↵Zuul2021-01-193-14/+36
|\ \ | | | | | | | | | stable/train
| * | Sync boot mode when changing the boot device via RedfishBob Fournier2020-11-173-14/+36
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | After changing the boot device via Redfish, check that the boot mode being reported matches what is configured and, if not, set it to the configured value. Some BMCs change the boot mode when the device is set via Redfish, this will ensure the mode is set properly. Change-Id: Ib077f7f32de029833e6bd936853c382305bce36e Story: 2008252 Task: 41103 (cherry picked from commit 685131fd3658b2ff0b131d19d32fd82d74f3bb17) (cherry picked from commit 861e91c8616db39e589589629bd5305909067331) (cherry picked from commit a6f38ab05a64802aec1b17c058e62ce7244e9a81)
* | [stable-only] Fix bandit upper constraintElod Illes2021-01-081-1/+1
|/ | | | | | | | | | | | | The 1.6.3 [1] release has dropped support for py2 [2] but the release is faulty and pip still picks it up for py2 [3][4], so cap to 1.6.2 when using py2. [1] https://github.com/PyCQA/bandit/releases/tag/1.6.3 [2] https://github.com/PyCQA/bandit/pull/615 [3] https://github.com/PyCQA/bandit/issues/663 [4] https://github.com/PyCQA/bandit/issues/665 Change-Id: I64da924b84d6a96d0440a562c0a7925406aff4c4
* Merge "DRAC: Fix a failure to create virtual disk bug" into stable/trainZuul2020-11-113-2/+176
|\
| * DRAC: Fix a failure to create virtual disk bugRachit71942020-10-063-2/+176
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Certain RAID controllers (PERC H730P) require physical disks to be switched from non-RAID (JBOD) mode to RAID mode to be included in a virtual disk. When this conversion happens, the available free space on the physical disk is reduced due to some space being allocated to RAID mode housekeeping. If the user requests a virtual disk (a RAID 1 for example) with a size close to the max size of the physical disks when they are in JBOD mode, then creation of the virtual disk following conversion of the physical disks from JBOD to RAID mode will fail since there is not enough space due to the space used by RAID mode housekeeping. This patch works around this issue by recalculating the RAID volume size after physical disk conversion has completed and the free space on the converted drives is known. Note that this may result in a virtual disk that is slightly smaller than the requested size, but still the max size that the drives can support. Conflicts: ironic/tests/unit/drivers/modules/drac/test_raid.py Change-Id: I720ab15e811f498aa15b88bfe8bb35fc49df292b Story: 2007359 Task: 38912 (cherry picked from commit 84e8b11a6d1ec04da188f5b34a1396cd92d88d5a)
* | clean up mac address with the pxe configuration filesArmstrong Liu2020-11-022-2/+27
| | | | | | | | | | | | | | | | | | | | In pxe_utils.py/create_pxe_config function, mac pxe configs will always be created, so when we clear pxe configs, no matter whether the ip address is None or not, we need to clear them. Change-Id: I5cee9c4465630b162baf911ef9efef5f471671c0 Signed-off-by: Armstrong Liu <vpbvmw651078@gmail.com> (cherry picked from commit 41f15dba65559a7132cb6e407ae169a2447d50e9)
* | Merge "opt: Enhance old stable branches to use latest python-ibmcclient" ↵Zuul2020-10-304-6/+13
|\ \ | | | | | | | | | into stable/train
| * | opt: Enhance old stable branches to use latest python-ibmcclientQianbiao.NG2020-10-224-6/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to some compatibility issue previously, stable branches fix python-ibmcclient version to python-ibmcclient>=0.1.0,<0.2.0. To let user benefited from latest python-ibmcclient, will update the code to support latest version. Change-Id: I1a9e8a956f0432d2244cba31c1e8b3c4ebdb84a6 Story: 2008144 Task: 40885
View Lorry Controller Status