)]}'
{
  "commit": "bebefa776d58f26c048b434004adbaef0b699a2e",
  "tree": "66ada0040c7ca451e23406c03cf2302b83a65f21",
  "parents": [
    "ee3079db74bd8ce6be5115a99263907fd3958da3"
  ],
  "author": {
    "name": "lkuchlan",
    "email": "lkuchlan@redhat.com",
    "time": "Mon Dec 09 22:19:01 2024 +0200"
  },
  "committer": {
    "name": "Liron Kuchlani",
    "email": "lkuchlan@redhat.com",
    "time": "Mon Dec 09 20:45:39 2024 +0000"
  },
  "message": "Fix floating IP association by filtering port list using IP address\n\nThe recent change in Tempest introduced a step to ensure all VM ports are active before associating a floating IP.\nThis caused issues in the manila-tempest-plugin scenario tests, where the correct port couldn\u0027t be identified for floating IP association.\n\nThis patch fixes the issue by filtering the port list using the IP address of the fixed IP to narrow down the result to the specific port associated with the given address.\n\nDepends-On: https://review.opendev.org/c/openstack/tempest/+/937406\nRelated-Bug: #2089798\nChange-Id: I74ac4eafa41f0d6355716e7fe26d09b7dfcbc982\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "49fa20eb2a5479464e7375282364a7c55307b2ce",
      "old_mode": 33188,
      "old_path": "manila_tempest_tests/tests/scenario/manager_share.py",
      "new_id": "f9df340847993cf77d8adad12e8e83986d3849e5",
      "new_mode": 33188,
      "new_path": "manila_tempest_tests/tests/scenario/manager_share.py"
    }
  ]
}