Just in case you are not aware of the situation.

The change to enable GLOBAL_VENV in grenade job was recently merged[1] in
core grenade. As we saw when the same was introduced in devstack some time
ago, some project got their (grenade) jobs broken and need a few adjustments.

[1] https://review.opendev.org/c/openstack/grenade/+/930507

So far I'm aware that the change affected manila and designate, which I'm
fixing by the changes below. Please be careful in case you see grenade job
failing in your project.

designate:
  - https://review.opendev.org/c/openstack/designate/+/932697
    Disable GLOBAL_VENV in grenade
     This is temporal workaround and needs to be reverted once the actual fix
     below is merged in master and backported to stable 2024.1/2

  - https://review.opendev.org/c/openstack/designate/+/932697
    devstack: Fix manage.py execution with GLOBAL_VENV
     This actually fixes the current issue caused by GLOBAL_VENV=True.
     As noted above, we have to backport this to stable branches

manila:

  - https://review.opendev.org/c/openstack/manila/+/932671
    Disable GLOBAL_VENV in grenade
     This is temporal workaround and needs to be reverted once the actual fix
     below is merged in master and backported to stable 2024.1/2

  - https://review.opendev.org/c/openstack/manila/+/932665
    devstack: Fix missing manila command
     This actually fixes the current issue caused by GLOBAL_VENV=True.
     As noted above, we have to backport this to stable branches

Thank you,
Takashi

--
Takashi Kajinami
irc: tkajinam
github: https://github.com/kajinamit
launchpad: https://launchpad.net/~kajinamit