This patch is limiting the memory address space to 1 GiB when invoking qemu-img convert. The qemu-img command can be exploited so we better play on the safe side (See: bug #1449062). Change-Id: I2088f74b32d1392310c569cfaa7fd368cb737421 Closes-Bug: #1657808 (cherry picked from commit 449cda4fed51250992446c83a4b50bc45fd10c6d)
Fixes two root device hints, 'wwn_with_extension' and 'wwn_vendor_extension', that were implemented and documented, but were not added to the list of supported root device hints, and thus fail validation. This code was completely rewritten on master, so this change is not a backport. Change-Id: I7bcc8c10d461b388f306c467e42d1e72f4e8a0f7 Closes-Bug: #1620563
Currently, building ramdisks installs ironic-python-agent without any upper-constraints. This causes the package to be installed with newer, untested dependencies. This commits introduces a tool to generate a local upper-constraints file based on predefined strategies (below). Additionally, the fallback to the openstack/requirements uses the URL defined in tox.ini instead of redefining it. This prevents having to keep track of two separate variables when releasing. upper-constraints lookup strategies (in order): * UPPER_CONSTRAINTS_FILE points to a local file * UPPER_CONSTRAINTS_FILE points to a URL * /opt/stack/new/requirements/upper-constraints.txt * upper-constraints.txt from openstack/requirements git repository Partial-bug: #1616554 Change-Id: Ib5c0c57cafdb6ffd7456e61f3b1bb5fa57520e5a (cherry picked from commit a0ca6ce157b8a84f282d8abbdd27c75f48d991ff)
This configures tox to use upper-constraints for everything, except environments used for post jobs (as constraints aren't supported there yet). This also doesn't enable constraints for our image builds, as it isn't possible to pass an environment variable into the Dockerfile to allow folks to choose their own constraints file (and we don't want to force people to rely on git.o.o for building images). Closes-Bug: #1617087 Change-Id: I285855c6386f59e9dd352473aa28463109818c90 (cherry picked from commit 4e35b0ee64a249c8461efc1c4374dd6cd9253220)
Change-Id: I5f139376be9f216fcbc1a43f8e4698bf498a6649
Creating specific partitions will cause a udev event to trigger, causing systemd to attempt to mount the new partition at /usr/share/oem. This mount will not succeed, but will unmount /usr/share/oem, causing ironic-python-agent to die. Masking this unit disables this behavior. Change-Id: Ifea3482f36a354cbf988e6f6003f4284c5c2a21d Closes-bug: #1592163 (cherry picked from commit da0a8aff88e67fce7603b03a220b77b451349e7d)
Presently should the ATA erasure operation fails, IPA halts the cleaning process and the node goes to CLEANFAIL state as a result. This failure could be the result of a previous cleaning failure that left drive security enabled, for which code has been added in an attempt to address this case by attempting to unlock the the drive. In the event that an operator wishes to automatically fallback to disk scrubbing operations, the capability has been added through a driver_internal_info field "agent_continue_if_ata_erase_failed" that can be set to True, however defaults to False keeping the same behavior that IPA presently exhibits in the event of ATA erase operations failing. Partial-Bug: #1536695 Change-Id: I88edd9477f4f05aa55b2fe8efa4bbff1c5573bb1 (cherry picked from commit ed74a062c19a63a2c05a506c4ed8d3aa4ecfa09e)
Some kernel modules take substantial time to initialize. For example, with mpt2sas RAID driver inspection and deployment randomly fail due to IPA starting before the driver finishes initialization. This problem is probably impossible to solve in a generic case, as modern Linux environment do not have a notion of "hardware is fully initialized" moment. All hardware is essentially hotplug. To solve it at least for the simplest case, this patch adds a wait loop on start up waiting for at least one suitable disk to appear in inventory. Note that root device hints are not considered, as the node might not be known at that moment yet. Change-Id: Id163ca28f7c140c302ea04947ded3f3c58b284de Partial-Bug: #1582797 (cherry picked from commit c15ed6a48e36da26576242277aa531720fd15d2d)