)]}'
{
  "commit": "c9d5800cce4f945194e60384cf9d2675f6182661",
  "tree": "56bdf73c9b7c667f9a8db36889f12c37fae496cd",
  "parents": [
    "4411b2992c4f093ddc893e2e8149b2277d35c137"
  ],
  "author": {
    "name": "jeremy.zhang",
    "email": "zhangjun_inspur@163.com",
    "time": "Wed Mar 22 11:03:54 2017 +0800"
  },
  "committer": {
    "name": "jeremy.zhang",
    "email": "zhangjun_inspur@163.com",
    "time": "Wed Mar 22 11:39:03 2017 +0800"
  },
  "message": "Fix for test_volume_swap\n\nIn volume swap procedure, server\u0027s BDM is updated after the old volume has\nbeen changed to \u0027available\u0027 and the new volume to \u0027in-use\u0027. When the old\nvolume is \u0027available\u0027 and the new volume is \u0027in-use\u0027, it is possible that\nthe server\u0027s BDM has not been updated yet. So it is necessary to wait for\nvolume swap to make sure that the server\u0027s BDM has been updated.\n\nChange-Id: I069a603159ecdec924868f45f12408e55eb235ea\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "984f1a9b061f34316d093f5934f9cf9c41c1bc90",
      "old_mode": 33188,
      "old_path": "tempest/api/compute/admin/test_volume_swap.py",
      "new_id": "22a5bc48e15ea5fbd15f669b4e85a9046bdb0691",
      "new_mode": 33188,
      "new_path": "tempest/api/compute/admin/test_volume_swap.py"
    }
  ]
}