)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":32553,"name":"Sven Kieske","email":"sven_oss@posteo.de","username":"skieske"},"change_message_id":"d88cff292465d1e406fa2c7cb0545fcb64a1d127","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"9b96a48e_c44e5566","updated":"2024-08-20 13:19:57.000000000","message":"I don\u0027t currently understand why, but in kolla-debian-podman with debian bookworm, python 3.11.2 we get:\n```\n File \"/tmp/ansible_kolla_toolbox_payload_vt0mlbby/ansible_kolla_toolbox_payload.zip/ansible/modules/kolla_toolbox.py\", line 16, in \u003cmodule\u003e\n\nModuleNotFoundError: No module named \u0027packaging\u0027\n\nfatal: [primary]: FAILED! \u003d\u003e {\n\n    \"changed\": false,\n\n    \"module_stderr\": \"Traceback (most recent call last):\\n  File \\\"\u003cstdin\u003e\\\", line 107, in \u003cmodule\u003e\\n  File \\\"\u003cstdin\u003e\\\", line 99, in _ansiballz_main\\n  File \\\"\u003cstdin\u003e\\\", line 47, in invoke_module\\n  File \\\"\u003cfrozen runpy\u003e\\\", line 226, in run_module\\n  File \\\"\u003cfrozen runpy\u003e\\\", line 98, in _run_module_code\\n  File \\\"\u003cfrozen runpy\u003e\\\", line 88, in _run_code\\n  File \\\"/tmp/ansible_kolla_toolbox_payload_vt0mlbby/ansible_kolla_toolbox_payload.zip/ansible/modules/kolla_toolbox.py\\\", line 16, in \u003cmodule\u003e\\nModuleNotFoundError: No module named \u0027packaging\u0027\\n\",\n\n    \"module_stdout\": \"\",\n\n    \"msg\": \"MODULE FAILURE\\nSee stdout/stderr for the exact error\",\n\n    \"rc\": 1\n```\n\nhttps://zuul.opendev.org/t/openstack/build/6b3345b8040c4139ac8e67a56274332c/log/primary/logs/ansible/deploy\n\nI can\u0027t replicate this in a local bookworm container with a venv based python 3.11.2 installation, I\u0027m able to `pip install packaging\u003e\u003d23.2` just fine inside the venv.\n\nDo we disable venv based installs in debian bookworm by chance?","commit_id":"461213534e1fdeca593fdae9b31531267c511aba"}]}