)]}'
{".zuul.yaml":[{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"e85ef992ce3bb1ef4ed629a3001ceff72f1526d1","unresolved":true,"context_lines":[{"line_number":8,"context_line":"      jobs:"},{"line_number":9,"context_line":"        - neutron-ovs-tempest-dvr:"},{"line_number":10,"context_line":"            vars:"},{"line_number":11,"context_line":"              tox_extra_args: --sitepackages"},{"line_number":12,"context_line":"        - neutron-tempest-plugin-dynamic-routing:"},{"line_number":13,"context_line":"            voting: false"},{"line_number":14,"context_line":"            vars:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"74d03858_3839d72e","line":11,"range":{"start_line":11,"start_character":32,"end_line":11,"end_character":44},"updated":"2023-08-23 10:06:30.000000000","message":"at the first glance this looks strange and i\u0027m still trying to come up with negative effects of this ... based on the definition of sitepackages, if we have the global packages under control (we know what\u0027s there) and how it affects our venv, it should be ok i guess\n\nhttps://tox.wiki/en/3.1.3/config.html#confval-sitepackages\u003dTrue|False\n\nthe ultimate goal is to influence the installation of the environment so that the newest (master with cherrypicked changes from gerrit, that\u0027s what we have required-projects for) os-ken is used, for example, in one of the projects I maintain, we change dir to that location (where zuul clones and cherry-picks) and installed from there: \nhttps://opendev.org/openinfra/python-tempestconf/src/commit/58e32bbe5ad6b225c6db6b14dd768fa085663fd5/roles/generate-tempestconf-file/tasks/main.yaml#L88\n\nos-ken is different, it\u0027s a dependency so we have to basically find a way how to force it to the installation of the environment. The sitepackages work and it should be safe if only os-key is installed globally and all other dependencies needed in the virtual env are not installed globally (so that we test with the approved constraints)\n\nOfficial openstack documentation suggest this solution to somehow override the constraints - that\u0027s something we could take into account too:\nhttps://docs.openstack.org/openstack-ansible/zed/reference/configuration/using-overrides.html#overriding-openstack-upper-constraints","commit_id":"53d2e1565902b9c848f1c26411a269b399c9c40f"},{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"310c86805f4e4ce1898597666eb7640e5793d97c","unresolved":true,"context_lines":[{"line_number":8,"context_line":"      jobs:"},{"line_number":9,"context_line":"        - neutron-ovs-tempest-dvr:"},{"line_number":10,"context_line":"            vars:"},{"line_number":11,"context_line":"              tox_extra_args: --sitepackages"},{"line_number":12,"context_line":"        - neutron-tempest-plugin-dynamic-routing:"},{"line_number":13,"context_line":"            voting: false"},{"line_number":14,"context_line":"            vars:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"c9bb3456_bb011090","line":11,"range":{"start_line":11,"start_character":32,"end_line":11,"end_character":44},"in_reply_to":"74d03858_3839d72e","updated":"2023-08-23 12:01:30.000000000","message":"discussion from the IRC for the record:\nthe job here uses tempest-run role to run tempest - https://opendev.org/openstack/tempest/src/branch/master/roles/run-tempest/tasks/main.yaml#L123 - and that results in installing tempest via tox, as a user would do. Therefore also tempest doesn\u0027t honor LIBS_FROM_GIT config devstack does. However, even if we used devstack to install tempest (not the run-tempest role) - https://github.com/openstack/devstack/blob/master/lib/tempest#L58-L61\nit wouldn\u0027t change a thing as devstack uses tox to install tempest as well - plus it obeys the upper-constraints too","commit_id":"53d2e1565902b9c848f1c26411a269b399c9c40f"}]}
