)]}'
{
  "log": [
    {
      "commit": "40edd5837f3ee3bd3728570e2965b1e47e3a1a24",
      "tree": "178678a3d25ad72435ce49e049608bf7e1fcaf68",
      "parents": [
        "4d290b5eec3db30330b77e1f2fd1df1c2fb8c404"
      ],
      "author": {
        "name": "Mykyta Karpin",
        "email": "mkarpin@mirantis.com",
        "time": "Wed Jun 07 13:03:18 2017 +0300"
      },
      "committer": {
        "name": "Mykyta Karpin",
        "email": "mkarpin@mirantis.com",
        "time": "Wed Jun 07 13:05:25 2017 +0300"
      },
      "message": "Fix loopback service status\n\nCurrently when Salt starts setup-loopback-device service\nsystemd executes losetup command and even if it worked\nsuccessfully, systemd marks service as inactive(dead).\nAnd Salt considers service as dead. In order to fix\nthis behavior, we need to add RemainAfterExit\u003dtrue to\nloopback systemd unit template.\n\nOther changes:\n.gitreview added\n\nRelated Prod: https://mirantis.jira.com/browse/PROD-11760\n\nChange-Id: I6d0c3baf1c22d0a626ff1fd6aaab802c08fb029e\n"
    }
  ]
}