Last commit made on 2022-12-25
Get this branch:
git clone -b stable/wallaby

Branch merges

Branch information


Recent commits

c9609c4... by Radosław Piliszek

Fix tox4 issues

New tox version 4 has changed interpretation of tox.ini

The passenv parsing requires the list to be comma-separated.
Since the names are case-insensitive, duplicates are removed.

skipsdist is now a synonym of no_package and avoids the
installation of the package in all cases.
However, some environments require it (for setup metadata).

Fix allowlist_externals where appropriate.

Change-Id: Icb067e85e4f4874a52710d7053a2048e337305c8
(cherry picked from commit 324fe6e69b40cd1eb1dfe449340a6a2811759436)

e3f6e78... by Mitya Eremeev

Handle host notification without host status

If an user sends host notification without host status:
openstack notification create COMPUTE_HOST <host> <date> '{"event": "STOPPED"}'
logging registers silly error like object None has not method 'upper' and
notification gets status 'running', host is set in maintenance status.
It's impossible to set manually host status to non-maintanence
until there are host-related running notifications.
Running notifications are expired in 24 hours by default.
The patch makes engine to set 'ignore' status for such

Closes-Bug: 1960619
Change-Id: Id873b3300b6de49082805654c85414a8868dd925
(cherry picked from commit 0837d7787c1be35df4b4330dbe6cdd2c160a69ab)

e6c5d3e... by Radosław Piliszek

[CI] Move queue setting to project level

Per [1] and [2].


Change-Id: Ifea988bf9b740618c58525f170c59b5cadfe0764
(cherry picked from commit 607da5931ac468d513e0f6331f897e5f561030b2)

1680a73... by suzhengwei

Fix stopping stopped instances

Nova-compute would periodically sync the instance status. So in the
instance failure recovery workflow,it would stop instance random failed
because of conflict, which will terminate the recovery workflow.
This patch can catch the Confict exception and continue the recovery
workflow if the instance already stopped.

Closes-Bug: 1980736
Change-Id: I59a1f9d7078614c1ddc8f4c362e967a15b8ec5e8
(cherry picked from commit 7241101163550b3cd981262468dc523ccb25cc9e)

6055e26... by Elod Illes

[CI] Install dependencies for docs target

When tox 'docs' target is called, first it installs the dependencies
(listed in 'deps') in 'installdeps' phase, then it installs masakari
(with its requirements) in 'develop-inst' phase. In the latter case
'deps' is not used so that the constraints defined in 'deps' are not
used. This could lead to failures on stable branches when new packages
are released that break the build. To avoid this, the simplest solution
is to pre-install requirements, i.e. add requirements.txt to 'docs' tox


NOTE(elod.illes): conflict is due to branch specific upper constraints
file link.

Change-Id: Ic5e214be240023f0e4f02cae3939e1d199ecb061
(cherry picked from commit aa13e4536eadbce8de35109f62a379e7e375bd02)
(cherry picked from commit d689abff9803a0fe7f9a3bce859e2d29eee32277)
(cherry picked from commit c1a31c8a053246307537ad184138a43f7baa9bd2)

05124e1... by Radosław Piliszek

[DevStack] Use xtrace

xtrace is useful to see the progress of DevStack deployment.
It is normally enabled in DevStack but was disabled in Masakari

Change-Id: Ib64f2c0a0fe46de9a9f3afa56079da0afbcad40b
(cherry picked from commit 01fa27cb98c1be69c340ca2b29d8a24eea26ce6d)

8ce2ad3... by Zuul <email address hidden>

Merge "[wallaby-only] [devstack] Fix path to dashboard policy" into stable/wallaby

e3cbcd2... by Mitya Eremeev

Fix Masakari API to properly return error codes

Change-Id: I538b9b143c868d9419709356daf0ffc48e2f0df9
Closes-Bug: #1932194
(cherry picked from commit 5c6fd44504e47ddbec3e0c29d454daeda87f86a4)

2115e51... by Radosław Piliszek

[wallaby-only] [devstack] Fix path to dashboard policy

In Wallaby, we merged the deprecation of JSON policy file and
moved to YAML by default.
However, dashboard has only really followed in Xena, leaving
the devstack plugin masakari dashboard policy symlink broken.
This patch fixes that.

Note we cannot easily move the dashboard policy file in Wallaby
without breaking existing (production) deployments, hence why
doing this instead of backporting.

Change-Id: Ie4687f4bfde4c29ba2805c3a6214267e3f1705e4

c366cde... by OpenStack Release Bot <email address hidden>

Update TOX_CONSTRAINTS_FILE for stable/wallaby

Update the URL to the upper-constraints file to point to the redirect
rule on 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/wallaby branch, tests will
continue to use the upper-constraints list on master.

Change-Id: Ibd11865ece39bc3b0d572ccfc7b7903063c94f50