<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Hi,</p>
The backported uwsgi fixes cannot merge yet, as Tempest jobs are
failing. (As an ansible post_run role in Tempest started to fail,
too, - in Rocky and older branches - after the new base images were
introduced.)
<p>Gmann prepared a workaround [1], unfortunately it does not work
as expected (as far as I understand) and still needs modification
in Tempest. Which is a catch 22, as the root of the issue is that
Tempest cannot be modified (in Rocky, Queens, ...), as it does not
have stable branches, just a master branch. But the stable
branches in Extended Maintenance are pinned to an older tag from
Tempest and we cannot modify that version of Tempest.</p>
<p>In my opinion, one solution could be to cut a (stable?) branch
from Tempest that can be used for branches currently in Extended
Maintenance (rocky, queens, ...) and fix there the failing role. I
know that Tempest is branchless, but can we have an exception
somehow, just to be able to fix the Rocky, Queens, Pike branches?<br>
</p>
<p>[1] <a class="moz-txt-link-freetext" href="https://review.opendev.org/#/q/topic:move-stackviz-role">https://review.opendev.org/#/q/topic:move-stackviz-role</a><br>
</p>
<p>Thanks,</p>
<p>Előd</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 2020. 06. 25. 12:03, Renat Akhmerov
wrote:<br>
</div>
<blockquote type="cite" cite="mid:a9a80c0c-4f27-4923-bdd9-7c415085de81@Spark">
<title></title>
<div name="messageBodySection">
<div dir="auto">Hi, any updates on the older branches?
Specifically, we’re interested in queens. We have a patch [1]
that waits for it.<br>
<br>
[1] <a href="https://review.opendev.org/#/c/736129/" target="_blank" moz-do-not-send="true">https://review.opendev.org/#/c/736129/</a><br>
</div>
</div>
<div name="messageSignatureSection"><br>
<div class="matchFont">Thanks<br>
<br>
Renat Akhmerov<br>
@Nokia</div>
</div>
<div name="messageReplySection">On 23 Jun 2020, 23:17 +0700,
Ghanshyam Mann <a class="moz-txt-link-rfc2396E" href="mailto:gmann@ghanshyammann.com"><gmann@ghanshyammann.com></a>, wrote:<br>
<blockquote type="cite" style="border-left-color: grey;
border-left-width: thin; border-left-style: solid; margin: 5px
5px;padding-left: 10px;">---- On Wed, 17 Jun 2020 13:17:26
-0500 Ghanshyam Mann <a class="moz-txt-link-rfc2396E" href="mailto:gmann@ghanshyammann.com"><gmann@ghanshyammann.com></a> wrote
----<br>
<blockquote type="cite">Hello Everyone,<br>
<br>
As you know devstack (so does grenade) got broken due to
uwsgi new release, the master branch is fixed<br>
and stable branches are in progress[1]. But It is hard to
maintain or fix the EM stable for those issues. Especially<br>
the greande job which depends on the source branch (previous
branch of one where the job is running).<br>
For example, for stein grenade job, we need to keep rocky
branch working and fix if failure.<br>
<br>
Till now, we have not removed the grenade testing from any
of the EM stable branches because they<br>
were running fine till now but with uwsgi issues, those are
failing and need more work to fix. This triggers<br>
the discussion of grenade testing on EM stable branches.<br>
<br>
Usual policy for grenade testing is to keep the job running
from the 'oldest supported stable +1' branch.<br>
For example, if stein is the oldest supported stable (in the
old stable definition) then run grenade from train onwards.<br>
But with the Extended Maintainance model, defining 'oldest
supported stable' is not clear whether it is the oldest<br>
non-EM(stein) or oldest EM stable(ocata).<br>
<br>
To make it clear, we discussed this in the QA channel and
come up with the below proposal.<br>
<br>
* 'oldest' is the oldest non-EM. In current time, it is
stein.<br>
* With the above 'oldest' definition, we will:<br>
** Make grenade jobs as n-v on all EM stable branches (which
is till stable/rocky as of today) + on stable/stein also
because that is 'oldest' as of today.<br>
** Keep supporting and running grenade job on 'oldest+1'
which is stable/train onwards as of today.<br>
<br>
NOTE: we will make n-v when they start failing and anyone
can volunteer to fix them and change back to voting.<br>
elod expressed interest to work on current failure.<br>
<br>
If no objection to the above proposal, I will document it on
the grenade documents to follow it whenever we see EM
failing and need more work.<br>
In Tempest, we already have the EM stable testing policy
documented which is to support those till they run fine[2].<br>
</blockquote>
<br>
I have pushed the patches making grenade jobs non-voting on
stable/stein[1]. With that patch merge in your project, it
will bring<br>
back the stable/stein onwards gate green. Once '<=
stable/rocky] gate is up you can backport these grenade-n-v
patches.<br>
<br>
Also, I am documenting the process in grenade for future
reference.<br>
- <a class="moz-txt-link-freetext" href="https://review.opendev.org/#/c/736866/">https://review.opendev.org/#/c/736866/</a><br>
<br>
[1]
<a class="moz-txt-link-freetext" href="https://review.opendev.org/#/q/topic:grenade-em-nv+(status:open+OR+status:merged)">https://review.opendev.org/#/q/topic:grenade-em-nv+(status:open+OR+status:merged)</a><br>
<br>
-gmann<br>
<br>
<br>
<blockquote type="cite"><br>
[1]
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015496.html">http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015496.html</a><br>
[2]
<a class="moz-txt-link-freetext" href="https://docs.openstack.org/tempest/latest/stable_branch_support_policy.html">https://docs.openstack.org/tempest/latest/stable_branch_support_policy.html</a><br>
[3]
<a class="moz-txt-link-freetext" href="http://eavesdrop.openstack.org/irclogs/%23openstack-qa/%23openstack-qa.2020-06-17.log.html#t2020-06-17T14:12:42">http://eavesdrop.openstack.org/irclogs/%23openstack-qa/%23openstack-qa.2020-06-17.log.html#t2020-06-17T14:12:42</a><br>
<br>
-gmann<br>
<br>
<br>
</blockquote>
<br>
</blockquote>
</div>
</blockquote>
</body>
</html>