)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"2f261cf215f9d1c9958267d78e30eb9ed8f466ca","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"58c22d4d_21f637fc","updated":"2024-11-13 06:18:12.000000000","message":"greande job still failing and depends-on did not fix it.\n\nHere problem is complex where Tempest master is used on granade target node (2023.2) but we have pinned Tempest on base node (2023.1). As Tempest is pinned on 2023.1 we use stable constraint there. Issue come when stable constraints usage setting is coming from base node (2023.1) and Tempest master is trying to use those constraints on target node(2023.2)\n\n- \nhttps://zuul.opendev.org/t/openstack/build/b8924d1069e24bdcbafb8749695c6e15/log/controller/logs/grenade.sh_log.txt#19335\n\n2024-11-11 20:03:25.773 | The conflict is caused by:\n2024-11-11 20:03:25.773 |     The user requested oslo.utils\u003e\u003d7.0.0\n2024-11-11 20:03:25.773 |     The user requested (constraint) oslo-utils\u003d\u003d\u003d6.2.1\n\nThis is difficult issue to resolve and that is why we recommended to stop testing the grenade on branch where it base branch is moving to Unmaintained (previously EM) branches. As constraints issue is difficult to solve we need to remove the greande job from 2023.1 as well as 2023.2 testing.","commit_id":"a4914b0e6d8af8e317a524a28aa1fb8500afed2b"}]}