vitrage/devstack/upgrade
Ghanshyam Mann 52c7cc2352 Multiple fixes: grenade job fix and python 3.8 drop
1. Enable the vitrage services on grenade target node

Grenade job need services to be enabled on base as well
as target node. Vitrage upgrade/setting file do enable the
vitrage services for target node[1] but those are only for
the case where grenade install the devstack[2]. Our CI
have devstack installed ready foer grenade(
GRENADE_USE_EXTERNAL_DEVSTACK=True) and because of that
vitrage grenade target node see vitrage services are not enabled[3]

To fix that we need to enable all the required services
on job definition.

2. grenade has enabled the GLOBAL_VENV by default and vitrage
grenade job needs to install and run everything from venv. This
fixes the vitrage bin directory locaiton otherwise it will fail
with below error
- https://zuul.opendev.org/t/openstack/build/cc87495cade64928a414ba26a4e53af1/log/controller/logs/grenade.sh_log.txt#12870

3. This drop the python 3.8 support. Removing the python 3.10
tox job from pipeline as that is running from generic template.

[1] cf07494171/devstack/upgrade/settings (L10)
[2] cf07494171/devstack/upgrade/settings (L10)
[3] https://zuul.opendev.org/t/openstack/build/639acc47689d433a92bcb692c9fd1028/log/controller/logs/grenade.sh_log.txt#12498

Change-Id: If3693de2ed582b467856b0163a92a7e8fd2d138d
2024-11-12 22:53:38 -08:00
..
settings use by default uwsgi on devstack 2018-12-19 13:05:13 +02:00
shutdhown.sh Complete removal of vitrage-collector service. 2018-11-21 08:15:12 +00:00
upgrade.sh Multiple fixes: grenade job fix and python 3.8 drop 2024-11-12 22:53:38 -08:00