)]}'
{
  "commit": "49f721a0ba3531384bfaf920fdf1f4a606e6fa92",
  "tree": "e3908c03d1d91ee432b381b1a7b03d82379bbf36",
  "parents": [
    "d8355f728cb1f6144a18deeeade96753c7758de0"
  ],
  "author": {
    "name": "James E. Blair",
    "email": "jeblair@redhat.com",
    "time": "Tue Jul 07 15:18:03 2020 -0700"
  },
  "committer": {
    "name": "James E. Blair",
    "email": "jeblair@redhat.com",
    "time": "Tue Jul 07 15:23:33 2020 -0700"
  },
  "message": "Disable host key checking in nodepool\n\nWe\u0027re seeing a lot of builds fail with RETRY errors.  This is due\nto the host key on the remote node changing between the time that\nnodepool collects it (immediately at boot), and Zuul uses it.  It\nappears that the images we\u0027re using have an ssh host key baked in\nto them but then overwrite it at first boot.  Because we\u0027re using\nthe internal IP (which doesn\u0027t need to wait for NAT setup), Nodepool\ncan end up connecting to the VM very quickly and grabbing the\ninitial (as opposed to the newly generated host key).  When Zuul\ntries to talk to the node, it has changed and it throws an error.\n\nBy disabling this, we allow Zuul to simply accept the host key on\nfirst connection.  This is low-risk since we\u0027re only using the\ninternal cloud network anyway.\n\nChange-Id: I2b2347f37527a72866e92164e6779ab6b57ebfa7\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2f7dfea78f53c4314c7224001d703ba849798cf0",
      "old_mode": 33188,
      "old_path": "nodepool/nodepool.yaml",
      "new_id": "b2f3a6e9d286390db74eb3ba13d557f46dda5559",
      "new_mode": 33188,
      "new_path": "nodepool/nodepool.yaml"
    }
  ]
}