Change-Id: Ie94279fb0d9ecf41e0c861ba7666a04b5f529dfc

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/2025.1 branch, tests will
continue to use the upper-constraints list on master.

Change-Id: I7bc8d8a70879e1dc7d2e72f41eef228838d47067

Change-Id: Ie8707db5f46449006647f402c60327144c39bdbc

As added in notes for INSTALL_TEMPEST variable we need to set
this as False for stable branch so that devstack does not
install Tempest at system wide.

Change-Id: I4a7ee61c77b2b1618761583ef3a02f61d93ff41b

This commit cap the API max microversions for compute, volume and
placement API for stable/2025.1.

Compute - https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/rest_api_version_history.rst#2100-maximum-in-20251-epoxy
Volume - https://github.com/openstack/cinder/blob/master/cinder/api/openstack/rest_api_version_history.rst#371
Placement - https://github.com/openstack/placement/blob/master/placement/rest_api_version_history.rst#139---support-for-the-any-traits-syntax-in-the-required-parameter

Change-Id: Ide4e776789ac9a337068a48aef39a42c38662df4

This commit cap the network, volume and swift extensions on
Tempest's config option api_extensions.

In 2025.1, new extension in neutron are:
- qing
- vpn-aes-ctr

and no new extensions in swift and cinder.

Change-Id: I85bf1c0c1571e2b7c8e2b493325e62cb87dc6575

This is triggering bug #2065685 [1] on Ubuntu 24.04 (Noble) if podman is
installed (since that brings in the broken paast and pasta packages).
Given the workaround is nearly 10 years old [2], it should not be
necessary anymore.

[1] https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2065685
[2] https://bugs.launchpad.net/networking-ovn/+bug/1466631

Change-Id: I525b1f30bca7093791f927ff647db7745d25df22
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Related-bug: #2065685
Related-bug: #1466631
(cherry picked from commit cbae989)

The nodepool "opensuse-15" is no longer available since [1].

[1]https://review.opendev.org/c/openstack/project-config/+/955214

Signed-off-by: Rodolfo Alonso Hernandez <ralonsoh@redhat.com>
Change-Id: I0c48ee0b7daded1f10eda5861ae1ac0bcedd168c

The z3fold compressed pages allocator is on it's way
out of the Linux kernel and running this on newer
systems will give you an error:

+ lib/host:configure_zswap:45              :   echo z3fold
z3fold
tee: /sys/module/zswap/parameters/zpool: No such file or directory

So, get ahead of things and move to the much faster
recommended by the kernel developers alternative.

[1]: https://lore.kernel.org/all/20240904233343.933462-1-yosryahmed@google.com/T/#u

Change-Id: I7c137114dd7585d3179a8d5dee818bb379bbcb1f
Signed-off-by: Mohammed Naser <mnaser@vexxhost.com>
(cherry picked from commit 5cb2abf)

... to fix the wrong libvirt group name detected.

Closes-Bug: #2119496
Change-Id: I2988fcb5010f333eab5a88b83ff14aab1cb15ebd
Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
(cherry picked from commit 5c338f4)

A bug in openldap mdb (memory database) causes it to crash in an attempt
to delete nonexisting tree, which is exactly what we do in the cleanup.
After the coredump it does not start automatically (what maybe make
sense to change). The fix is merged in
https://bugs.openldap.org/show_bug.cgi?id=10336 but we do not have this
fix in Noble. For now try simply to restart the process.

Change-Id: Iae597aae345d12a2c82f66342ff40ac0a387eddf
Signed-off-by: Artem Goncharov <artem.goncharov@gmail.com>
(cherry picked from commit 06633c6)

When using the LDAP identity backend, stack.sh fails
during the create_keystone_accounts phase when trying
to verify the newly created demo user.

This is caused by a BadRequestException from the
Keystone API with the error, 'enabled' is a required
property. The error occurs because the default LDAP
user object created by the DevStack scripts does not
contain an attribute that Keystone can map to its
mandatory enabled property.

This change fixes the issue by adding
user_enabled_emulation = True to the domain-specific
LDAP configuration in the create_ldap_domain function.
This tells Keystone to assume a user is enabled if
the attribute is not explicitly defined in their LDAP
entry, which resolves the schema incompatibility and
allows the script to complete successfully.

Signed-off-by: Grzegorz Grasza <xek@redhat.com>
Change-Id: I15ddf0b88ee93615c318d4845a026ca1e25c3e69
(cherry picked from commit e221349)

Change-Id: I221a03b2f8314fee66672c23d7ece4eb900c038c
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

…e/2025.1