)]}'
{
  "log": [
    {
      "commit": "7860f2ba3189b0361693c8ee9c65d8d03fb115d6",
      "tree": "9ff43d22cf86a103c28dc2fbb8643a0d844fdcf0",
      "parents": [
        "db6cb078aecf90c7b0cb30778903c61770a25861"
      ],
      "author": {
        "name": "Sean Dague",
        "email": "sean@dague.net",
        "time": "Tue Nov 17 11:59:07 2015 -0500"
      },
      "committer": {
        "name": "Sean Dague",
        "email": "sean@dague.net",
        "time": "Wed Nov 18 10:59:50 2015 -0500"
      },
      "message": "install ebtables locking workaround\n\nebtables is racing with itself when nova and libvirt attempt to create\nrules at the same time in the nat table. ebtables now has an explicit\n--concurrent flag, that all tools must opt into to prevent ebtables\nfrom inherently being unsafe to run.\n\nlibvirt gained this support in 1.2.11, which is too new for our ubuntu\nprimary testing environment. Nova still hasn\u0027t added this support,\nthough even if it did, we\u0027d run into the issue with libvirt.\n\nWe can do the most ghetto thing possible and create a wrapper for\nebtables that does explicit locking on it\u0027s own. It\u0027s pretty terrible,\nbut it should work. And it is the kind of work around that people\nunable to upgrade libvirt will probably need to do.\n\nThis is an opt in value which we should set in the gate to True.\n\nRelated-Bug: #1501558\n\nChange-Id: Ic6fa847eba34c21593b9df86a1c2c179534d0ba5\n"
    }
  ]
}