These excludes were removed from the requirements repo[1] and are now
detected as errors.
[1] 314734e938f107cbd5ebcc7af4d9167c11347406
Change-Id: I0399c328ecbf74529658d0be0f88868049e6ba5f
The update() function is internal and not guaranteed to be stable.
Resource plugins should override _needs_update() to control
update/replace behaviour.
Change-Id: I247b68669e692f6705e8adee60572c8e775ce0b8
Story: 2011068
Task: 49828
This had a similar problem as when null values were passed explicitly
before the fix for bug 1709620.
Change-Id: I02fb4c8815bc24d4c0c339022aa857dc344d58e9
Story: 2011108
Task: 49921
This reverts commit 575827c9ac.
Reason for revert:
The issue with pyparsing bump was already resolved.
Change-Id: Ia01ad211eab1b8ae558a85b9e51df46164d7a1d1
With the previous detection logic removed by [1], we should update
the shebang so that the script is executed by python interpreter.
[1] 19bcbc0390
Change-Id: If116e89b75f450b818ed6b8819a0920fff6d34bb
SLURP is supported between only .1 releases so upgrade from 2023.1 (or
2023.2) to 2024.2 is not supported.
Change-Id: I8a6b41347b5f07b30320351b5b4ad78e3758e5f8
When creating Trove instances with a specific network configuration,
some validation logic would fail if the network/port resources did
not already exist.
For example, if a network and a trove instance were to be created
as part of the same stack, the network ID would not exist yet and
result in the ID being an empty string.
This commit fixes that logic to specifically test whether the value
is None, rather than the truthy test of None or ''
Story: 2011075
Task: 49772
Change-Id: I12c98828271be05d1d98d653eeb2ae21ede058f7
The update method has incomplete arguments and causes error during
actual stack update operation.
Story: 2011068
Task: 49751
Change-Id: I7b141f8846005da8379b1c646b298088d27a66bc
Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: Ib8ad88acb4cb65da2a44acaf76f189de57e81f0b
It seems the latest libvirt in Ubuntu is no longer affected by
the known problem with device handlings. This re-enables some test
cases which were previously disabled because of the problem.
Change-Id: I538462414f0a9b634d4d216230ed04b49cf71c40
This allows admin users[1] to use a different project id in request
path, to fix the unexpected access denials during redirection when
enforcing new default rules. This was allowed previously with
deprecated policy rules, and with the new SRBAC design we require
project scope auth to access project owned resources such as stack.
[1]
User with admin role in admin project in case admin_project_name is
set in Keystone. If it's not set then user with admin role in any
project are considered as "admin".
Story: 2011036
Task: 49532
Change-Id: I49f46e36828881d9700e0e178bd80eb04efe4510
This argument was deprecated in netaddr 0.10.0[1], and was removed in
netaddr 1.0.0[2].
[1] aca2f56344
[2] cc42742247
Change-Id: I24f26ee44af8fdfca89312351e67e5edbf7c81de
The 2024.1 release is the first release with SLURP supported. This
introduces a job to test direct upgrade from 2023.1 to 2024.1 .
Change-Id: Ie5ee5c7c06c64afad0c11219b8bcf583212758b8
Resolve the following deprecation warning:
DeprecationWarning: the load_module() method is deprecated and slated
for removal in Python 3.12; use exec_module() instead
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: I403289d5df2143872503fc246a993cb19ebba68e