masakari

masakari:stable/zed

  1. Git
  2. lp:masakari
  3. stable/zed
Last commit made on 2022-12-25
Get this branch:
git clone -b stable/zed https://git.launchpad.net/masakari

Branch merges

Branch information

Name:
stable/zed
Repository:
lp:masakari

Recent commits

09d5958... 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)

e496aad... by suzhengwei

Fix notfication stuck into running status when timeout

For instance or process failure workflow, the failure notification
would stuck into running status if timeout.

Closes-Bug: #1996835
Change-Id: I61e941ab9dd831369fcc46a132ae2b11c1dd23ba
(cherry picked from commit 7ec3edda1ada9c2464d79c84b0fd1d1be22f9336)

c813fa9... 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
notifications.

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

a5a25b0... by Radosław Piliszek

[CI] Move queue setting to project level

Per [1] and [2].

[1] http://lists.zuul-ci.org/pipermail/zuul-discuss/2022-May/001801.html
[2] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/030505.html

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

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

Update TOX_CONSTRAINTS_FILE for stable/zed

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

Change-Id: Ia4b3ff66f48cc0be040ddc717ec363b1b754b1d6

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

Update .gitreview for stable/zed

Change-Id: Ic8872bda45f199c3eb91b488a5b5281aa9d18137

6773fa9... by Zuul <email address hidden>

Merge "Cleanup py27 support"

16001fd... by Zuul <email address hidden>

Merge "Fix stopping stopped instances"

7241101... 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

56a9ec2... by suzhengwei

add notification_uuid into log message

Change-Id: If07f894a924b281c53b5a14b25409acbd1e3e7f2