)]}'
{
  "commit": "a0d1b0151a9d9e169e6342f36a073e8154119924",
  "tree": "17bf81a03a7a0afaf99cd199f388ca56f0cb23e3",
  "parents": [
    "e60d52c392098192b6c666cb345c50a9a4842d1b"
  ],
  "author": {
    "name": "Brian Haley",
    "email": "brian.haley@hpe.com",
    "time": "Mon Nov 16 17:30:48 2015 -0500"
  },
  "committer": {
    "name": "Brian Haley",
    "email": "brian.haley@hpe.com",
    "time": "Tue Jan 05 12:12:16 2016 -0500"
  },
  "message": "Delete OVS port on unstack to retain system connectivity\n\nIf you configure devstack with the following three values,\nfor example:\n\nPHYSICAL_NETWORK\u003deth0\nPUBLIC_INTERFACE\u003deth0\nOVS_PHYSICAL_BRIDGE\u003dbr-eth0\n\nThis will cause devstack to create an OVS bridge, create a port for\neth0, and add it to the bridge (along with it\u0027s IP address).\n\nThe problem is that on unstack the port is never deleted from OVS,\nso eth0 gets \"trapped\", not showing up in any of the OVS commands,\nbut not usable by the system.  The only workaround is to unload the\nOVS kernel module.\n\nThere needs to be an \u0027ovs-vsctl del-port ...\u0027 call at the end of\n_move_neutron_addresses_route() on unstack - the antidote to the\n\u0027ovs-vsctl add-port ...\u0027, that happened on stack.\n\nCloses-Bug: #1516801\n\nChange-Id: Id2ff60f1f8e8fffff1eaffd68d9de4f6aa772943\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cc5b75e2b9c924ce371b3edb223a41a14099b3ce",
      "old_mode": 33188,
      "old_path": "lib/neutron-legacy",
      "new_id": "b8fce2833abaf49359dc866326fca51cd1c7fec8",
      "new_mode": 33188,
      "new_path": "lib/neutron-legacy"
    }
  ]
}