)]}'
{
  "commit": "1038a81977697c9d25873a2857ff3a14c08d8143",
  "tree": "e25cff06149be972eb47cd8d86af09ca20e0360b",
  "parents": [
    "f461244c9b841ec12f1cab86d584794483c9d184"
  ],
  "author": {
    "name": "Pavlo Shchelokovskyy",
    "email": "pshchelokovskyy@mirantis.com",
    "time": "Tue Nov 28 09:19:08 2017 +0000"
  },
  "committer": {
    "name": "Pavlo Shchelokovskyy",
    "email": "pshchelokovskyy@mirantis.com",
    "time": "Mon Dec 04 09:41:26 2017 +0000"
  },
  "message": "Revert \"Make libvirt safe again\"\n\nThis reverts commit 53a64cb871eb6889571a09e69c787681ba83e41c.\n\nThis commit was based on a wrong assumption that the default port\nis not used during live migration.\nIn fact, while libvirt can use another range of port during\nlive migration for copying disks and memory,\nthe main control channel still happens over connection\nto the port 16509 (default in /etc/libvirt/libvirtd.conf).\n\nBlocking this port manifests as \n\nLive Migration failure: operation failed:\nFailed to connect to remote libvirt URI\nqemu+tcp://cmp02/system: unable to connect\nto server at \u0027cmp02:16509\u0027: Connection timed out\n\nerror in nova-compute log when attempting to perform a live migration.\n\nChange-Id: I336a36cc5acc3c07cef3964bd889623b24324ce2\nRelated-Issue: PROD-15929\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e8b29ccd5f6f629da9408ca887f5893b5e638a66",
      "old_mode": 33188,
      "old_path": "nova/compute/cluster.yml",
      "new_id": "5d0e6a1d45cb9fdc4be08df82743e57e944cff02",
      "new_mode": 33188,
      "new_path": "nova/compute/cluster.yml"
    },
    {
      "type": "modify",
      "old_id": "d5126df826609cdadf5520675023b72ef571b756",
      "old_mode": 33188,
      "old_path": "nova/compute/single.yml",
      "new_id": "b9151457bba58ca5851c7498070a8203b5a4db4d",
      "new_mode": 33188,
      "new_path": "nova/compute/single.yml"
    }
  ]
}