)]}'
{
  "commit": "425606b5902e2ad63b780331ac307c932d8f492c",
  "tree": "c391e745fa08a459102edaccd9027e1696ce3c9e",
  "parents": [
    "2f24b8233d240f9bb2a94204aa0a981a8ddb8731"
  ],
  "author": {
    "name": "Goutham Pacha Ravi",
    "email": "gouthampravi@gmail.com",
    "time": "Thu Feb 02 18:10:35 2017 -0500"
  },
  "committer": {
    "name": "Goutham Pacha Ravi",
    "email": "gouthampravi@gmail.com",
    "time": "Fri Feb 03 17:32:16 2017 +0000"
  },
  "message": "Fix wrong access-rule negative test\n\nThe test test_add_access_rule_on_share_with_no_host in\nmanila_tempest_tests.tests.api.test_rules_negative\\\n       .ShareIpRulesForNFSNegativeTest\nexpects a share to fail to schedule, and then validates that an\naccess rule cannot be added. However, the share may\nstill be \u0027creating\u0027 when the access change is being\nattempted.\n\nWhile the test passes (access rules cannot be added when\nthe share status isn\u0027t \u0027available\u0027), the intent of that particular\ntest is to ensure access rules cannot be added when the share has no\nhost.\n\nThis fixes the cleanup error that happens in consequence,\nbecause we don\u0027t allow deleting shares that are in\n\u0027creating\u0027 state.\n\nIn the spirit of true black box testing, we should ensure that the\nshare fails to schedule before attempting this test.\n\nChange-Id: Id150e0ef546ddfd40d97d9b1a54fd8ba23028720\nCloses-Bug: #1661421\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "20db4ebe1d45ba898e1cf498fa3485bd3b714230",
      "old_mode": 33188,
      "old_path": "manila_tempest_tests/tests/api/test_rules_negative.py",
      "new_id": "8049f1445e52811a8a3f261da04e93c33b53d87c",
      "new_mode": 33188,
      "new_path": "manila_tempest_tests/tests/api/test_rules_negative.py"
    }
  ]
}