This fix has been proposed to lvm2 upstream[1]. This change can be
reverted once the fix is packaged. It is proposed here to unblock
upstream and downstream delivery pipelines.
[1] https://github.com/lvmteam/lvm2/pull/105
Change-Id: If187a2b1ec61ec47738b99b40919d4cc65fa9505
Closes-Bug: #2000226
Related: rhbz#2158628
tox now hard fails if there is mismatch in spec
attributes[1]. This works around the issue
temporarily. We probably have to drop py38 jobs
and specify basepython for py39 target in the
future.
Removes ansible-galaxy --timeout for py* jobs to
workaround. We may hit the timeout with py* jobs.
[1] https://github.com/tox-dev/tox/pull/2824/
Change-Id: Ie9bacf18cf167139601eff80bba91f2b3454b5dd
This change switches to MiB as the unit for all partitions and LVM
volumes. It includes comments stating overheads so any future changes
can be easily calculated.
All LVM MiB values are multiples of 4MiB, which is the size of an LVM
extent.
This change is in preparation for thin provisioning, where specifying
volume size by percentage no longer makes sense.
Change-Id: I768bb6def4fcea96a59357b4117d92efa3b9613b
Depends-On: https://review.opendev.org/c/openstack/diskimage-builder/+/839829
delorean-repo:
replaced by tripleo-repos and other repo setup approaches
hosts:
heat hasn't manage hosts file for many releases
localboot:
replaced by diskimage-builder grub2, bootloader elements
ntp:
replaced by installing chrony package
os-net-config:
the package is installed by other elements, and the script is now
called from ansible
overcloud-dracut:
replaced by diskimage-builder dracut-regenerate element
overcloud-partition:
no image now uses this, overcloud-hardened-uefi-full uses
overcloud-partition-uefi
Change-Id: I990493b51d87a40140c1648f2b04c982ce959b1d
The overcloud-hardened-uefi-full image now has a separate partition
mounted to /boot. This means grub no longer needs to mount the root
partition. This will allow trying layouts which grub doesn't support,
such as LVM thin-provisioning. Since grub now uses the common path of
loading an ext4 /boot partition, early boot may now be more robust, or
have better error messages for incorrectly built images.
Change-Id: I27be9c3e82ed20dcfc7a6f7dcb992006d44f933f
Depends-On: https://review.opendev.org/c/openstack/diskimage-builder/+/846838
the current master should be compatible with the Zed
release of the other projects.
Related-Bug: #1974244
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I4ae059fe095378c3ee3b072b6216908a8988bf26
This is an element which will run a script on first boot to rename
`/boot/loader/entries` filenames to match the new value of
`/etc/machine-id`. This is required for `grub2-mkconfig` calls to
incorporate existing values in the boot loader entry files.
It only runs when first-boot criteria is met, such as when
`uninitialized` is written to `/etc/machine-id`
rhbz#2073855
Change-Id: I354aeabed6d2993ae600b86381a7b625ca7f89dc
Depends-On: https://review.opendev.org/c/openstack/diskimage-builder/+/837251
Tripleo-ci jobs are broken after latest release of setuptools 61.0
because of breaking changes which are not backwork compatible,
details in related bug and [1].
Users that don't set ``packages``, ``py_modules``, or `configuration`
are still likely to observe the auto-discovery behavior, which may
halt the build if the project contains multiple directories and/or
multiple Python files directly under the project root.
To disable auto discovery, one can do below in setup.py
~~~
setuptools.setup(..,packages=[],..)
~~~
or
~~~
setuptools.setup(..,py_modules=[],..)
~~~
[1] https://github.com/pypa/setuptools/issues/3197
Releated-Bug: #1966382
Change-Id: I8db5e382576a820f756cc936ca0fe7ca6d0ec1d1
All strings are considered as unicode string from Python 3.
This patch drops the explicit unicode literal (u'...')
appearances from the unicode strings.
Change-Id: I7247c37d7e082ffa4ea9e8540b25351bb9b851c5
With this patch, we are removing yum_plugin_priorities_package
from delorean-repo element as a part of refactoring
to only support centos/rhel 8/9.
As these are the only thing defined in file - pkg-map and
03-install-yum-priorities, We are dropping these files.
This repo have stable branches, so train builds should be using
stable/train of tripleo-image-elements.
Change-Id: I683050dbceb79c9123fcefb16e34dc6085c93d85
Because the Xena release is not being created for TripleO repos, test
runtime is not updated by automation tools. This change updates
the job template to use the tested runtime for Yoga.
Change-Id: Iec0bc2e4d6a773e4085bc05f6b08e676cc9424f0
Add file to the reno documentation build to show release notes for
stable/wallaby.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/wallaby.
Sem-Ver: feature
Change-Id: I12783838405916e071a0520d6e5d00ab1753345b
The current size is big enough for the shim and grub packages which
are installed to it, however when doing a dnf upgrade or reinstall,
dnf may fail with an inadequate space error. Doubling the size of this
partition will avoid this error.
Change-Id: I1f8a189d0fc095cb2cc3bf7808756cd9b973c3b2
Blueprint: whole-disk-default
Most tripleo node roles store their state in /var with the exception
of the ObjectStorage role which stores its state in /srv.
This change adds a very small /srv volume which will generally remain
empty. A documentation change will be proposed which shows how to set
custom growvols values to grow /srv in the rare case that the
ObjectStorage role is used.
Change-Id: Ide8776ffdb62bff46c3df4773fc7b01e9710373f
Blueprint: whole-disk-default
* Replace .testr.conf by .stestr.conf for migration and update
.gitignore, tox.ini and test-requirements.txt files accordingly
Signed-off-by: HeroicHitesh <email.hiteshkumar@gmail.com>
Change-Id: Ia577800e7a342beaad58009239a98b9e7044d01a
Now that images are converted to raw on the undercloud we need to
consider the implications of creating a 40G whole-disk image which is
mostly empty.
The raw image file on the undercloud is sparse, so storage space is
not consumed. However transferring from the undercloud to deploying
nodes will transfer all 40G of mostly zeros, and ironic-python-agent
will also write all those zeros to disk during deployment. This makes
deployment unnecessarily slow and will cause network scalabilty issues
for large overcloud deployments.
This change reduces the size of the physical root partition to 6GB,
and makes the logical volumes big enough for space to not run out
during image building. The growvols utility will be used post-deploy
to grow all of the volumes (not just /var).
The growvols playbook now has the following default to ensure all
partitions are grown to an appropriate size:
/=8GB /tmp=1GB /var/log=10GB /var/log/audit=2GB /home=1GB /var=100%
Change-Id: I34b57958ba84714c54ed8148600e7fd0860e3ba8
Blueprint: whole-disk-default
This will install the growvols script, which will be run in the
ansible playbook stage of the overcloud node provision command.
Change-Id: I27257e0a95fc16e0099d4ee28f365f0bce02b262
Depends-On: https://review.opendev.org/c/openstack/diskimage-builder/+/791083
Blueprint: whole-disk-default
In recent centos 8 images tmp.mount is masked, which causes issues
with all defined LVM mounts (/ is readonly, other mounts fail).
This change unmasks and enables tmp.mounted so the existing LVM /tmp
mounts correctly. It also makes fsck-passno compliant with the
documentation[1] so that / has value 1 and all other mounts are set to
2.
Blueprint: whole-disk-default
[1] https://www.man7.org/linux/man-pages/man5/fstab.5.html
Change-Id: Ib517e73845a7698f873a4f3207ffa9c54cdbcbef
Element search order is not deterministic, so when
overcloud-partition-uefi depends on block-device-efi, it is not
possible to know which block-device-default.yaml will be applied.
To avoid this, don't depend on the block-device-* elements ever, and
just duplicate what they do within these elements.
Change-Id: Icea31169a68ab0ea24e6cd1ba0f7d8e88cc07f1f
Blueprint: whole-disk-default
If ifcfg-eth0 is defined but does not exist, this can cause the nodes to
fail to get an IP address on initial provisioning. This patch removes it
when the image is built to ensure we don't end up with a bad interface
network script.
Change-Id: I3b8cb5f8c413c109da1228878db9cff4d439273b
Closes-Bug: #1931495
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I01e07a0f954a61cc4fa645bbd19a239a71070ba8
Add file to the reno documentation build to show release notes for
stable/victoria.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/victoria.
Sem-Ver: feature
Change-Id: Ia6996f87c9e700fe1f9551b7a302fb01ba121478
- Ceiling of pbr version can create installation conflicts with pip.
- Fixes tox default env list to be python version agnostic
- Updated template to use newer jobs (include testing with newer python)
Bug: #1921679
Change-Id: Ifd0d2f810799992faa1db41b80bf93bc97d5d19d
It seems as though w/ CentOS-8.3 ens3 has crept
back into play. Ensure it's not in the overcloud
images. See bug for details.
Closes-Bug: #1910107
Change-Id: I29d632814577db0b720b07d4497983e267d46a4e
Move partition handling to overcloud-partition / overcloud-partition-uefi
as whole-disk images with kernel-rt would be impossible to create due to
dependencies between kernel-rt and kdump/kexec-tools. We need to be able
to create whole-disk image while some package should not be uninstalled.
Change-Id: I181cf4dc0c0976833e39e4df78a7cff184f0f0b2
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I5aedf5a96bc39825dac6b0ddd0005c9e8e0b1619
Add file to the reno documentation build to show release notes for
stable/ussuri.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/ussuri.
Change-Id: Ib38dc3b5e3887559202082d2c0438b9446d08151
Sem-Ver: feature