)]}'
{
  "commit": "26bf3b501443ad9592446aac702afb4e6ca0b8b6",
  "tree": "ea364499db55d7ebd6cb5ab53c44ccf15e243d25",
  "parents": [
    "e8b6e91d2cb1d7883dc6692e1bd038ecfe10f8cc"
  ],
  "author": {
    "name": "Julia Kreger",
    "email": "juliaashleykreger@gmail.com",
    "time": "Mon Jan 27 06:36:34 2025 -0800"
  },
  "committer": {
    "name": "Julia Kreger",
    "email": "juliaashleykreger@gmail.com",
    "time": "Mon Jan 27 06:36:34 2025 -0800"
  },
  "message": "Remove reboot from basic baremetal ops\n\nWhile investigating the 4k job, I noticed the test sometimes has trouble\nSSHing back in to the host post-reboot due to no fault of the test.\n\nIn other tests, it looks like we manage to get SSH\u0027ed in just as the\ndeployed host is online.\n\nThis is because cloud-init or other configuration changes have been\napplied in the OS, which is outside the act of \"deploying\" the node.\n\nIn other words, we were spinning our basic job for several hundred\nseconds in some cases on just waiting for the OS to reboot, and then\ntrying to verify the OS behaves the same as before we rebooted.\n\nUltimately, to conserve resources *and* reduce failure risk by trying\nto test OS behavior, removing the reboot call and post-reboot re-ssh/ping\ncheck behavior.\n\nChange-Id: Ie08335e0e10f51f782a27270c62e33aa84a8c568\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2a36c6a53c28f5363f2976371b673605c210efc3",
      "old_mode": 33188,
      "old_path": "ironic_tempest_plugin/tests/scenario/test_baremetal_basic_ops.py",
      "new_id": "dcfc0235209edc4aed0d2368b6914713530822b6",
      "new_mode": 33188,
      "new_path": "ironic_tempest_plugin/tests/scenario/test_baremetal_basic_ops.py"
    }
  ]
}