)]}'
{"devstack-vm-gate.sh":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"7207a0c3ffbb84bf5fa3478288eb12bbd94b3f43","unresolved":false,"context_lines":[{"line_number":160,"context_line":"        echo \"IRONIC_VM_LOG_DIR\u003d$BASE/$localrc_oldnew/ironic-bm-logs\" \u003e\u003e\"$localrc_file\""},{"line_number":161,"context_line":"        echo \"DEFAULT_INSTANCE_TYPE\u003dbaremetal\" \u003e\u003e\"$localrc_file\""},{"line_number":162,"context_line":"        echo \"BUILD_TIMEOUT\u003d300\" \u003e\u003e\"$localrc_file\""},{"line_number":163,"context_line":"        echo \"IRONIC_CALLBACK_TIMEOUT\u003d240\" \u003e\u003e\"$localrc_file\""},{"line_number":164,"context_line":"        if [[ \"$DEVSTACK_GATE_IRONIC_BUILD_RAMDISK\" -eq 0 ]]; then"},{"line_number":165,"context_line":"            echo \"IRONIC_BUILD_DEPLOY_RAMDISK\u003dFalse\" \u003e\u003e\"$localrc_file\""},{"line_number":166,"context_line":"        fi"}],"source_content_type":"text/x-sh","patch_set":1,"id":"3a961159_0a6f1061","line":163,"updated":"2015-01-06 20:26:38.000000000","message":"Wondering if 299 would be safe(r)?  If we just want this to get a more specific failure, a 299 timeout should do that for us.","commit_id":"e7f8ee3ce56a02a398c621e0324df15370fd335f"},{"author":{"_account_id":1420,"name":"Adam Gandelman","email":"adamg@ubuntu.com","username":"gandelman-a"},"change_message_id":"68e69962f02cf1aece7a5bf826f3c478efa00a43","unresolved":false,"context_lines":[{"line_number":160,"context_line":"        echo \"IRONIC_VM_LOG_DIR\u003d$BASE/$localrc_oldnew/ironic-bm-logs\" \u003e\u003e\"$localrc_file\""},{"line_number":161,"context_line":"        echo \"DEFAULT_INSTANCE_TYPE\u003dbaremetal\" \u003e\u003e\"$localrc_file\""},{"line_number":162,"context_line":"        echo \"BUILD_TIMEOUT\u003d300\" \u003e\u003e\"$localrc_file\""},{"line_number":163,"context_line":"        echo \"IRONIC_CALLBACK_TIMEOUT\u003d240\" \u003e\u003e\"$localrc_file\""},{"line_number":164,"context_line":"        if [[ \"$DEVSTACK_GATE_IRONIC_BUILD_RAMDISK\" -eq 0 ]]; then"},{"line_number":165,"context_line":"            echo \"IRONIC_BUILD_DEPLOY_RAMDISK\u003dFalse\" \u003e\u003e\"$localrc_file\""},{"line_number":166,"context_line":"        fi"}],"source_content_type":"text/x-sh","patch_set":1,"id":"3a961159_8a0dc091","line":163,"in_reply_to":"3a961159_0a6f1061","updated":"2015-01-06 20:35:12.000000000","message":"Dont think that\u0027d work, it needs to be considerably lower. Ironic doesn\u0027t start its timer on the callback timeout until after its powered the machine on.  Prior to doing so, it needs to do some prep work (transfer glance images, update neutron, etc).  The nova build_timeout starts ticking after \u0027nova boot\u0027 on the client side.  It will be some amount of time before ironic finishes its prep and powers the thing on, 60 seconds should be enough.","commit_id":"e7f8ee3ce56a02a398c621e0324df15370fd335f"}]}