Under heavy load, the qemu-img convert method may attempt to create
additional malloc arenas to complete its work. By default this number
is 8 * ncpu * which at about 250 MB of memory which can be consumed
in this mannor should the.

Since this is only something which should realistically occur under
heavy cross-thread load where memory locking prevents a thread from
unlocking a range of memory, (such as what can happen with hypervisors
and VMs inside those hypervisors), then a new arena gets created, and
the memory consumption spikes.

More information is avialable at:
https://www.gnu.org/software/libc/manual/html_node/Memory-Allocation-Tunables.html

Change-Id: I8b2b490f2cc0ac5f47c3aaaaa249ce59db6602d6
Story: 2008928
Task: 42529
(cherry picked from commit 76cbb962)
(cherry picked from commit f4cabc04)

Extended boot records (EBRs) are used in the MSDOS partitioning
scheme to manage extended partitions. EBRs are small partitions
themselves and Ironic will therefore treat them like any other
partition during cleaning. Since EBRs are smaller than a GPT
(33 sectors), dd'ing 33 sectors will fail. This patch proposes
a fix to handle EBRs (and other tiny paritions) by adjusting
the number of blocks writtent to be the partition size at max.

Story: #2008539
Task: #41628
Change-Id: Ie9809b3e4fe2bea6b66ee95c442111942e85d618
(cherry picked from commit 9a60d385)

As discussed during the upstream ironic community meeting on
Monday Dec 14 2020, the lower-constraints job is being removed.

Also 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: Iab279c57676dba8faa87ab7523e577d3b65eb428
(cherry picked from commit 0bbba8e6)
(cherry picked from commit d5ae74e9b8a6b2aa602095b60286d5ab2f1da63a)

qemu-img convert makes a number of allocation requests, and less
common than the "Resource temporarily unavailable" error is
"Cannot allocate memory". The first seems to be largely raised
upon a thread creation for the image conversion, where the first
appears to be on buffer setup on the original process.

Regardless, we should check for both and retry conversion
automatically.

rhbz# 1892773

Note: Because of a later patch which transformed the retry logic to
leverage tenacity, this change has been modified accordingly.

Change-Id: If435ed0efe034d4bb99f0281ebc73840c0f38fb3
(cherry picked from commit 9be6afc7)
(cherry picked from commit 97902803)

We are changing the default boot in ironic to local,
to avoid breaking the CI let's set all the partition
jobs to netboot.

Change-Id: Id4573ff7163475cabb74f2931ed0b377bedbc8f0
(cherry picked from commit db6bef0c)

The zeroconf library removed address in version 0.27.0 [1]
This patch should fix potential issues with that change.

[1] https://github.com/jstasiak/python-zeroconf/#changelog

Change-Id: I694ae5587ac8c3aae43d98902f56738773d31284
(cherry picked from commit 4c185438)

Change-Id: If571457351240f84ec130a8e1550bf07e1f0507f
(cherry picked from commit bba715c5)

This change fixes two potential issues with qemu-img on a busy machine:
1) Retry infrequent "Resource temporarily unavailable"
2) Make address space limits configurable instead of hardcoding to 1Gi

Story: #2007644
Task: #39702
Change-Id: I82a94e68e1aa1f634c7f0877ccd674574d1c9bb0
(cherry picked from commit 555c4948)

socket.sendto() requires bytes and we need explicitly convert str to
bytes in py3.

Change-Id: Ib3f928963b11a2041caf1c3b15825125567ce360
Story: #2007537
Task: #39356

Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.

Until the requirements repository has as stable/ussuri branch, tests will
continue to use the upper-constraints list on master.

Change-Id: I8942016ef88695fb9c2fad14f179168a608e4af9

Change-Id: I754a39e53aaae57313f2f2a53f4a3d7f4861f6e9

Change-Id: Ied8a0e728e08f4f3ea7a7db4e1047360cfe6d734

The new version enables a lot of standard flake8 checks, so a few
fixes are required. W503 is disabled as it conflicts with W504
and the latter seems to be preferred nowadays.

Change-Id: I929ff36eaa47a42bc551f5c37bd40f64bc4f14d0

The ironic-lib-base job is based on ironic-base job which
will default to dib.
To prevent breaking the ironic-lib CI we set the ramdisk
type to tinyipa for now and we'll convert the jobs here later.

Change-Id: I9a03943a838b53518b052874296744c97feea249

1) Log which hints matches the final root device
2) Log each rejection for easier debugging
3) Remove mentions of "root" from find_devices_by_hints, it's going
   to be also used for RAID ddevices.

Change-Id: I90e39f9a9bc9f690d0453bfe00cea8c08e8dbda1

It will be used to specify target devices for software RAID.

Change-Id: I879d11ae7c5b8f47746b765733d3d8162aeddba1
Story: #2006369
Task: #38988

The file was added to sources but not to setup.cfg which controls
which files are included in the wheel build.

Change-Id: Ied7ee2e3418673de7c2c9fa6f8407350d6b3314c
Story: 2006604
Task: 36772

The configuration option [disk_utils]iscsi_verify_attempts was
deprecated and marked for removal.

Change-Id: I8e67430ba6c53420b7ad38b21adcf776d0c77ad0

Since removing support for Python 2, we changed the basepython
value to 3.
This means that all the tox tests run with the default python
version available in the system.
This is not quite correct when running on environment such as
py36, py37 or py38, since they imply running with different
Python versions based on the environment.
To enforce the correct version we need to add the option
ignore_basepython_conflict available since tox 3.1.0 [0].

[0] https://tox.readthedocs.io/en/latest/config.html#conf-ignore_basepython_conflict

Change-Id: I63127c91c708af3a215fc653e43e2017c46dd7ad

Since we've dropped support for Python 2.7, it's time to look at
the bright future that Python 3.x will bring and stop forcing
compatibility with older versions.
This patch removes the six library from requirements, not
looking back.

Change-Id: I4bf885bc7d1ccdf46dde3e0b10a8dbec304aaf9b

Currently an UnboundLocalError is raised when all addresses are
loopback, raise ServiceLookupFailure instead.

Change-Id: I7db3603d382c0cb4b81b94e2382ecd3a191f6977

Currently when [mdns]interfaces is not provided, we default to V4.

Change-Id: Iee637a46e134341d7cd28c1e16ee78a31c90b3f8

Also adding some more useful info on tox and link to its
official docs.

Change-Id: I13f2ba79c5f1df55e5926f00046a647f09bfbe4b

Updates the zeroconf requirement to 0.24.0, breaking compatibility
with Python 2 (dropped in an earlier patch).

Change-Id: Ib77720c3223074e89705f019848e1e4d19ebfdba

OpenStack is dropping the py2.7 support in ussuri cycle.

ironic-lib is ready with python 3 and ok to drop the
python 2.7 support.

Complete discussion & schedule can be found in
- http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html
- https://etherpad.openstack.org/p/drop-python2-support

Ussuri Communtiy-wide goal - https://review.opendev.org/#/c/691178/

Change-Id: Idfa5afedb607c99c34ff4a07594f698c9bd3bed8

- Remove unused ironic-python-agent-build-image-coreos
- Fix typo on tinyipa job name on post.

Change-Id: Iaff62b407a61ebc6f4f0c12fd84979d33803a3e9

This patch adds two new py3 jobs to cover the following py2 jobs:
- ironic-lib-partition-bios-ipmi-direct-tinyipa-src-python2
- ironic-lib-wholedisk-bios-ipmi-direct-tinyipa-src-python2

Also dropping unecessary variable `USE_PYTHON3` in the base job
that uses ironic-base.

Change-Id: Ib35683896f909a9cd88f88bb8170d8cde74364bd

Change-Id: I779bd55b11c3b719f96fa4e071588634afefa74b

This is the path where ironic searches for rootwrap filter files by
default.
This is important because ironic itself is going to remove [1] its
copy of the ironic-lib.filters file.

[1] https://review.opendev.org/#/c/684270

Change-Id: I2241bfd11c66fb84b8840ab76563af52fe93e5ad

The is one of community goals that each project could produce a
single PDF file. The pdf should be in the output of openstack-tox-docs
job.

TeX packages are required to build PDF locally, following is recommended:

* inkscape
* texlive-latex-base
* texlive-latex-extra
* texlive-fonts-recommended

More about the goal:
https://governance.openstack.org/tc/goals/train/pdf-doc-generation.html
https://etherpad.openstack.org/p/train-pdf-support-goal
https://etherpad.openstack.org/p/pdf-goal-train-common-problems

Change-Id: I8b42ab0f057cb33c1ec93adfa32c45aafc2730b0

It is not used in ironic-lib for anything explicitly iscsi-related.
Rename it, keeping the option present since ironic uses it.

Change-Id: I86f52dc7e36a35ebcd44eee4f317fe93b5d67cd6
Depends-On: https://review.opendev.org/679463

Long story short, we need to rescan after making
partition changes.

Without forcing a filesystem sync and rescan operation,
we rely upon lazy write-out from buffers to the block
device when operating with a ramdisk.

This is because ramfs does NOT actually operate with fsync
where as GNU parted utilizes fsync on the device in an
attempt to force the write to disk to occur. This is fine
if your booted with devfs, or say even a physical block
device that backs /dev, just not ramfs.

Change-Id: I66481d5f3c17a489f7bdf0af82e31b9107605968
Story: 2006423
Task: 36316

While `sgdisk -Z` is useful to wipe disk and partition
metadata, it will prevent execution and not do anything
if a CRC error is detected with the data already on disk.

We had previously run into this with IPA, however we never
addressed this with-in ironic-lib[0].

[0]: https://storyboard.openstack.org/#!/story/1737556
Story: 1737556
Task: 36305

Change-Id: I8fb390cb1daa481583ebcba6a010e9be3255b373

This matches the behaviour of the linux kernel, see:

https://github.com/torvalds/linux/blob/d3511f53bb2475f2a4e8460bee5a1ae6dea2a433/block/partition-generic.c#L39

Change-Id: Ic3963e5c4a1886aeabed6c5994599e72040a251e
Story: 2006154
Task: 35656