Since we are working in process of removing tempest container
from wallaby release and all the tempest run is switched to
os_tempest for all supported release in tripleo-ci.
This change is not going to affect any periodic jobs also.
It also removes run_tempest and tempest_format var.
Related-Bug: #1916875
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I3d046047833044fd2d75ba399f784be5d992fbef
In Ussuri we enabled pacemaker by default so when we landed a change[0]
in quickstart to handle this logic, it broke the upgrade job because
the ussuri job uses train initially and gets a non-ha standalone which
it tries to upgrade to HA. This results in an incorrect network config.
Since really the exepectation is that we'd always be upgrade HA to HA,
let's test that instead.
[0] https://review.opendev.org/#/c/725782/
Closes-Bug: #1895822
Change-Id: I78c1a0cf68534e574b14ad505404139d93983324
This param is now set at a higher level, directly in the job definitions
using the "featureset_override" variable.
Depends-On: I8a15852c18694703c31d6a418118446832b58081
Change-Id: I3379bca8dc532e16d959e12e2fe8fbd81fb0c005
The override to set the correct container cli
was missing from the standalone upgrade
Closes-Bug: #1822867
Change-Id: I6a0c1dc2e00c30da37ffd18e944c50748ae43625
It set the standalone_upgrade variable to true compared to the
standalone featureset 052 (all-in-one).
Change-Id: I3cbec1669fcf60d9e3c98278e1b60e57c3dd9999
Ghanshyam Mann