Comment 6 for bug 1976247

we may end up disabling stackviz to unblock the gate

the code in ansible-role-python_venv is a bit convoluted wrt the defaults e.g.

- name: Install python packages into the venv
  block:
    - name: Install python packages into the venv
      pip:
        name: "{{ _venv_install_pip_packages }}"
        state: "{{ venv_pip_package_state }}"
        virtualenv: "{{ venv_install_destination_path }}"
        extra_args: >-
          --constraint {{ venv_install_destination_path }}/global-constraints.txt
          --constraint {{ venv_install_destination_path }}/constraints.txt

i've tried to trace how the _venv_install_pip_packages (actually defined in this same file [1]) and constraints.txt and global-constraints.txt are formed and it is not obvious to follow :/

As there are other things that need pressing attention I am contemplating disabling this/stackviz as we already have for c9 already there [2] (thanks chkumar for reminder)

But not even sure if that will work. The earlier fix we have at [2] is for os_tempest itself whereas the failing task i nthis case is from ansible-role-python-venv_build

[1] https://opendev.org/openstack/ansible-role-python_venv_build/src/commit/e7307f5d01db07cc504eb619654a0829c9d4e92c/tasks/python_venv_install.yml#L29
[2] https://opendev.org/openstack/tripleo-quickstart-extras/src/commit/be5e48aeedf5ecd5ee4acdbed7c4fa1be2db0d50/playbooks/tasks/tempest.yml#L87