Comment 25 for bug 2003993

Reviewed: https://review.opendev.org/c/openstack/grenade/+/879119
Committed: https://opendev.org/openstack/grenade/commit/62ea9b6ba35ae28c299a4366e81f516c503a518c
Submitter: "Zuul (22348)"
Branch: stable/2023.1

commit 62ea9b6ba35ae28c299a4366e81f516c503a518c
Author: Ghanshyam Mann <email address hidden>
Date: Thu Mar 30 20:58:04 2023 -0500

    Fix tempest venv constraints for target branch tempest run

    We fixed the tempest venv constraints setting for tempest test run
    on base branch but forgot to do the same for target branch test run.
    It cause issue when base and target branch have different Tempest
    and constraints to use (for example stable/wallaby use old tmepest
    and stable/wallaby constraints but stable/xena use tempest master
    and master constraints), in such cases we need to set proper constraints
    defined in devstack and then run tempest.

    We do not see this issue as none of the job run tempest on target except
    heat (https://review.opendev.org/c/openstack/heat/+/872055/5).

    I reproduced the issue in grenade stable/xena by enaling the tempest run
    on target:
    - https://review.opendev.org/c/openstack/grenade/+/878247/1
    - https://zuul.opendev.org/t/openstack/build/1b503d359717459c9c77010608068e27/log/controller/logs/grenade.sh_log.txt#17184

    Closes-Bug: 2003993
    Change-Id: I05fcdb5045a33997bd1a4c340a16458d88399f5f
    (cherry picked from commit 4c9c059883158fd6bf3cb79ca89d52003a63b7fe)