)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"d1c90c0cd29c28968d83dc7876d3d0f3e5208712","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"0714d7e0_626c24a3","updated":"2025-10-15 23:00:19.000000000","message":"Change merged to master when it was Dalmatian development, so the commit is in stable/2024.2.\n\nMy concern is that I think we\u0027re not supposed to make changes to requirements files except in the case of security issues.  This patch bumps oslo.reports from 2.2.0 to 3.2.0, and it needs to use 3.2.0 to catch change I95170542fecb\n\nThat being said, the upper-constraints value for oslo.reports in caracal is 3.3.0 [0], so that\u0027s what the code has been tested with in the gate.  However, I did a codesearch to see what other projects have (because if someone else already has \u003e\u003d3.2.0, then packagers would have to be using that as the min version).  Unfortunately, looking at current master, cinder is the only project that has oslo.reports\u003e\u003d3.2.0 in requirements.txt [1], so no one else is going to have that as a minimum in caracal.\n\nWe should check with the release team, though, because I can\u0027t find anything about this in the stable branch policy [2] ... unless bumping oslo.reports from 2.2.0 to 3.2.0 counts as introducing a \"new dependency\" (which maybe it does?).\n\nSo I\u0027m leaving a +1 because I\u0027m good with the code change, but not giving a +2 until we sort out whether this is an allowable backport.\n\n[0] https://opendev.org/openstack/requirements/src/branch/stable/2024.1/upper-constraints.txt#L398\n[1] https://codesearch.openstack.org/?q\u003doslo.reports\u0026i\u003dnope\u0026literal\u003dfosho\u0026files\u003drequirements.txt\u0026excludeFiles\u003d\u0026repos\u003d\n[2] https://docs.openstack.org/project-team-guide/stable-branches.html","commit_id":"14da00ca32ffbec09b144d554a01f542ed514969"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"352456356a0cac79bb9245732957b330ee3f3ecf","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f715055c_1d77e106","updated":"2025-10-16 21:39:39.000000000","message":"In general this *should* be okay.  The problem I see is that Ubuntu ship 2.3.0[1].  As mentioned on IRC[2] Debian and RDO are fine (I\u0027m not sure about other distros).  I have reached out the the cloud-archive team with a hypothetical question.\n\nWe shall see what we see.\n\n\n[1] https://launchpad.net/ubuntu/+source/python-oslo.reports/2.3.0-0ubuntu1\n[2] https://meetings.opendev.org/irclogs/%23openstack-release/%23openstack-release.2025-10-16.log.html#openstack-release.2025-10-16.log.html#t2025-10-16T19:35:31","commit_id":"14da00ca32ffbec09b144d554a01f542ed514969"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"c8ce24d6b3e08f06c73256b4fae7c81b3854db29","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"74806f60_af560ef6","updated":"2025-10-17 12:44:13.000000000","message":"Thanks Tony and Elod.  I\u0027ll put a reference to this patch somewhere appropriate in the cinder docs for the next time this question comes up.\n\nSince my question about the requirements.txt change has been resolved, upgrading to a +2 and approving the backport.","commit_id":"14da00ca32ffbec09b144d554a01f542ed514969"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"94833807837b3b3989cf34b0f40e4ad70f200814","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"2a48be91_625d349f","updated":"2025-10-17 23:20:57.000000000","message":"recheck grenade - failed during setup phase, [ERROR] /opt/stack/new/grenade/projects/70_cinder/resources.sh:199 SSH to the client did not work, something very wrong","commit_id":"14da00ca32ffbec09b144d554a01f542ed514969"},{"author":{"_account_id":11583,"name":"Arnaud Morin","email":"arnaud.morin@gmail.com","username":"arnaudmorin"},"change_message_id":"726f6fc78eb90a5a5ac9313013811cfe0ca3d03c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"451f2603_6787362c","updated":"2025-10-07 13:18:52.000000000","message":"recheck openstack-tox-py311","commit_id":"14da00ca32ffbec09b144d554a01f542ed514969"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"b351649f6e545f45f7d0e3f47934acdadc08963d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c231ed04_e685a364","in_reply_to":"0714d7e0_626c24a3","updated":"2025-10-16 19:16:19.000000000","message":"yepp, this is somewhat on the grey area i think. the dependency management has a page [1] that lists most of the things we should know/should be considered in dependency management, but does not contain exact information about this one. but in general i think we do not support of changing requirements.txt. But some occasions we probably allowed it in the past. Here are a couple of perspectives:\n\n- from consumer perspectives, bumping minimal version of a dependency can be problematic during upgrade -\u003e it could cause conflicts\n- on the other hand we are not that strict about openstack libraries\n- especially in such case as this: the bumped version is still from 2024.1 Caracal (and it\u0027s the 1st oslo.reports release on Caracal)\n- we should not allow to bump minimal version beyond stable/2024.1 versions of oslo.reports (e.g. a stable release from dalmatian, or epoxy; basically, above the version in upper-constraint.txt), but this is not the case here, as Brian and i wrote above\n\nI\u0027m slightly tending to say OK to this bump, but might be some others have different opinions. And of course if anyone has anything that proves me wrong, then let me know. o:)\n\n[1] https://docs.openstack.org/project-team-guide/dependency-management.html","commit_id":"14da00ca32ffbec09b144d554a01f542ed514969"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"b580f68fda8884992a1094fa5a1c2153961c04bc","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c16efd35_7261ae12","in_reply_to":"f715055c_1d77e106","updated":"2025-10-17 03:39:55.000000000","message":"I received a response from Canonical.   I don\u0027t have a direct link but\nhttps://openstack-ci-reports.ubuntu.com/reports/cloud-archive/caracal_versions.html shows python-oslo.reports as 3.3.0-0ubuntu1\n\nIt took a while to find but it looks like suse[1] has 3.3.0, although [2] doesn\u0027t have anything ?\nGentoo seems to only have packages for flamingo.  So that\u0027s probably fine.\n\nSo:\n * RDO \u003ccheck\u003e\n * Debian/Ubuntu \u003ccheck\u003e\n * suse \u003ccheck-\u003e\n * gentoo \u003cprobably okay\u003e\n\nI think this is okay.\n\n[1] https://build.opensuse.org/package/show/Cloud:OpenStack:Upstream:2024.1/python-oslo.reports\n[2] https://build.opensuse.org/project/show/Cloud:OpenStack:2024.1\n[2] https://packages.gentoo.org/maintainer/openstack@gentoo.org","commit_id":"14da00ca32ffbec09b144d554a01f542ed514969"}]}