)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"824cf0ba68775f0d6bd4cb241b2f0898e19eca44","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"81bf7306_093ee2da","updated":"2024-07-30 23:40:48.000000000","message":"I think the potential for this to indirectly break things is high.\n\nPlease downgrade this to non-voting, and remove it from thew gate pipeline.\n\nWe can figure out the process for actually removing this later.  I think at this stage we\u0027ll need the rest of this cycle to figure things out with implementation next cycle.","commit_id":"a8bf47b2f26c287549315979d2dbfb8b99863539"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"4adfebbe6ee8f5c5d7e2e17b81dc660ee664f70b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"d6ecd595_a1c6fb84","updated":"2024-07-30 17:11:28.000000000","message":"IMO we should remove the caps for 3.8 in upper-contraints at the same time, doesn\u0027t make sense to keep them in place, but untested","commit_id":"a8bf47b2f26c287549315979d2dbfb8b99863539"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"6a62001bea524b2bc3564331170a587224db7c39","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"d6fd86a3_51315a09","updated":"2024-07-30 22:06:47.000000000","message":"So the last time we tried to do a large uncoordinated version drop from openstack it ended in a lot of broken CI and it largely had to be undone. What I took away from that was that these cleanups need to be coordinated across openstack and performed in a very careful order to avoid fallout.\n\nIn particular the application code bases should drop support first, then libraries, then tools like requirements, then finally (and probably quite some time later) tools like PBR whose versions are more difficult to control in the wild go very very last. Looking at zuul build history and digging around in gerrit it appears projects like tempest and swift (both fall under the application category) are still testing with python 3.8 on master. There may be others as well this was just a quick check.\n\nThe application runtimes document provides requirements for python3.9 and some newer versions but that doesn\u0027t means 3.8 is forbidden if I understand it correctly. That does mean that support projects like requirements and the zuul jobs and oslo libraries need to work more slowly.\n\nSide note: it looks like oslo projects may have already dropped testing? I think this too is a bug.","commit_id":"a8bf47b2f26c287549315979d2dbfb8b99863539"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"7adf66bdfec32f9a6a63aa4ce7ddd659303accac","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"218dc7d5_2c84a686","in_reply_to":"58b12994_bd64cc58","updated":"2024-10-24 13:36:18.000000000","message":"we\u0027re at the PTG now, so ready to proceed I\u0027d think","commit_id":"a8bf47b2f26c287549315979d2dbfb8b99863539"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"5772634c334284d701f7cce7f985f3df6eb7819d","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"58b12994_bd64cc58","in_reply_to":"d3ab2019_c7f869b0","updated":"2024-07-31 19:31:20.000000000","message":"I agree that dropping it from requirement should be the last step instead of first. \n\nI expressed my concern for oslo also to drop the py3.8 (make them uninstallable on py 3.8) on IRC also and we should continue encouraging projects to drop it first and then oslo and then here. One safe way or to speed up/coordinate effort is to plan it early next cycle (during PTG or before m-1 and oslo drop at m-1) so that if any project is late or not dropping it then we have enough time in the cycle to handle it.","commit_id":"a8bf47b2f26c287549315979d2dbfb8b99863539"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"a525410fbf5b0c5e547df5636914a35daf5c544d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"5c727a32_76fbef8e","in_reply_to":"d6ecd595_a1c6fb84","updated":"2024-07-31 16:20:54.000000000","message":"Done.","commit_id":"a8bf47b2f26c287549315979d2dbfb8b99863539"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"002655e6d59f172215c154aa3ce0496c29c0b6f9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"ee34a829_cf4055b0","in_reply_to":"d6fd86a3_51315a09","updated":"2024-07-31 03:58:17.000000000","message":"see also https://review.opendev.org/c/openstack/requirements/+/924992","commit_id":"a8bf47b2f26c287549315979d2dbfb8b99863539"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"a525410fbf5b0c5e547df5636914a35daf5c544d","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"d3ab2019_c7f869b0","in_reply_to":"ee34a829_cf4055b0","updated":"2024-07-31 16:20:54.000000000","message":"The initial trigger is horizon which removed python 3.8 support according to the testing runtime. I\u0027m also planning to remove python 3.8 support from heat this cycle.\n\nFor oslo, we allow installation in python 3.8 but the testing coverage is already removed. We can restore it, but I really hope that we get documented steps agreed with TC, to avoid further confusion.","commit_id":"a8bf47b2f26c287549315979d2dbfb8b99863539"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"ffd30fdfcb7a009d4d3d3bf66149a76bb767d3d9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"087d65e5_897c62ea","updated":"2024-09-27 07:46:23.000000000","message":"Dropping the -2 now since I\u0027ll be on holiday over the next weeks, but IMO best wait with approving until after the release is finished","commit_id":"9a3d769890836c31ca21c175d6e4be195f659be3"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"57f73c10a1049d8e0eeee0c410fa316a80422213","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"2277d83e_447ec472","updated":"2024-08-30 07:49:09.000000000","message":"procedural -2 since we are in reqs freeze now, we can continue discussing this early next cycle","commit_id":"9a3d769890836c31ca21c175d6e4be195f659be3"},{"author":{"_account_id":13861,"name":"yatin","email":"ykarel@redhat.com","username":"yatinkarel"},"change_message_id":"3c61f86a978b35309b92e074f9cd516412252a9b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"2686ace9_581514ce","updated":"2024-10-28 12:49:56.000000000","message":"This broke propose-translation-update(running on bionic) in master branch and tempest jobs on stable/2023.1,zed,yoga/xena as tempest uses master constraints on those branches.\nhttps://zuul.openstack.org/builds?job_name\u003dpropose-translation-update\u0026branch\u003dmaster\u0026skip\u003d0\nhttps://zuul.openstack.org/builds?project\u003dopenstack%2Fneutron\u0026pipeline\u003dperiodic-weekly\u0026skip\u003d0","commit_id":"4966810392d02cd032a682ba65b06fbe3caf562c"},{"author":{"_account_id":13861,"name":"yatin","email":"ykarel@redhat.com","username":"yatinkarel"},"change_message_id":"954ec32d2116bc1e83aeccd347f31f6919163719","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"433d3d46_5d9a18ae","in_reply_to":"014c9f7a_7d8eec0f","updated":"2024-10-30 06:46:24.000000000","message":"Still couldn\u0027t understand how https://review.opendev.org/c/openstack/tempest/+/933398 fixes the issue seen in stable/2023.1, may be you have not seen the failures, pasting here as tempest is installed from git source and use master constraints and fails as:-\n2024-10-30 02:36:10.106271 | controller | ++ lib/tempest:configure_tempest:722        :   tox -revenv-tempest --notest\n2024-10-30 02:36:10.361725 | controller | venv-tempest create: /opt/stack/tempest/.tox/tempest\n2024-10-30 02:36:10.740950 | controller | venv-tempest installdeps: -chttps://releases.openstack.org/constraints/upper/master, -r/opt/stack/tempest/requirements.txt\n...\n2024-10-30 02:36:15.378906 | controller | ERROR: Cannot install -r /opt/stack/tempest/requirements.txt (line 14) because these package versions have conflicting dependencies.\n2024-10-30 02:36:15.378912 | controller |\n2024-10-30 02:36:15.378916 | controller | The conflict is caused by:\n2024-10-30 02:36:15.378920 | controller |     stestr 4.1.0 depends on voluptuous\u003e\u003d0.8.9\n2024-10-30 02:36:15.378925 | controller |     The user requested (constraint) voluptuous\u003d\u003d\u003d0.15.2\n\nunmaintained xena,yoga, zed and stable/2023.1 are impacted which runs on ubuntu focal","commit_id":"4966810392d02cd032a682ba65b06fbe3caf562c"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"5e8dad1887739105b24468fd7c4350e302ccc9de","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"4f271422_6328796c","in_reply_to":"07ffc037_7cc39ca8","updated":"2024-10-30 17:48:35.000000000","message":"I see, I did not realize stable/2023.1 is using focal. As this is going to be in unmaintained status next week or so, we can pin the tempest there too. I will check you changes.","commit_id":"4966810392d02cd032a682ba65b06fbe3caf562c"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"4677cd3498210465bdac528ab01112accb2f3d21","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"5a7a7306_fd364190","in_reply_to":"2686ace9_581514ce","updated":"2024-10-28 17:59:17.000000000","message":"Yeah, We are fixing it on tempest side https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/FOWV4UQZTH4DPDA67QDEROAESYU5Z3LE/\n\nhttps://review.opendev.org/c/openstack/tempest/+/933398","commit_id":"4966810392d02cd032a682ba65b06fbe3caf562c"},{"author":{"_account_id":13861,"name":"yatin","email":"ykarel@redhat.com","username":"yatinkarel"},"change_message_id":"ec1cff2cfec09f82bf50a9fd1b7b4901c50d9170","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"07ffc037_7cc39ca8","in_reply_to":"433d3d46_5d9a18ae","updated":"2024-10-30 17:40:49.000000000","message":"Reported https://bugs.launchpad.net/devstack/+bug/2085886 for the tempest + py3.8 issue and pushed https://review.opendev.org/q/topic:%22bug/2085886%22, tempest and devstack patches require each other to pass, if direction is ok can get tempest one force merged.","commit_id":"4966810392d02cd032a682ba65b06fbe3caf562c"},{"author":{"_account_id":13861,"name":"yatin","email":"ykarel@redhat.com","username":"yatinkarel"},"change_message_id":"2fdb254d076e3d7de1f6793c80b5749af62b672b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"a3f57f9c_81eb0f56","in_reply_to":"5a7a7306_fd364190","updated":"2024-10-29 14:14:20.000000000","message":"okk thanks, but that looks just new tag patch, believe there will be follow up patches on stable/unmaintained branches to pin to that tag to unblock the jobs in those branches?\nCurrently those branches CI is just blocked without it and stable/2023.1 is about to go in unmaintained.","commit_id":"4966810392d02cd032a682ba65b06fbe3caf562c"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"30886257cf74e26b486458fa69d99d6c55c7acd9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"014c9f7a_7d8eec0f","in_reply_to":"a3f57f9c_81eb0f56","updated":"2024-10-29 17:39:51.000000000","message":"The fix is merged for the master Tempest which means stable/2023.1 till master jobs should work fine https://review.opendev.org/c/openstack/tempest/+/933398\n\nFor unmaintained branches, yes, Tempest needs to be pin as soon as branch goes to unmaintained branch with the compatible Tempest tag. Hope unmaintained branches team is keeping it up to dated for all the current unmaintained branches.\n- https://docs.openstack.org/tempest/latest/tempest_and_plugins_compatible_version_policy.html","commit_id":"4966810392d02cd032a682ba65b06fbe3caf562c"}]}