[autotest] Temporarily disable autoupdate_ForcedOOBEUpdate.

The test is sometimes causing devices to download and apply consumer
images from Omaha, which leaves the devices untestable, and requires
a relatively expensive manual intervention to fix.

This disables the test to stop the bleeding until the problem can be
put under better control.

BUG=chromium:877107
TEST=None

Change-Id: I4d25f74abb761bec3d85d10792bc45ba3b8d6c5d
Reviewed-on: https://chromium-review.googlesource.com/1211162
Reviewed-by: Richard Barnette <jrbarnette@google.com>
Tested-by: Richard Barnette <jrbarnette@google.com>
diff --git a/server/site_tests/autoupdate_ForcedOOBEUpdate/control b/server/site_tests/autoupdate_ForcedOOBEUpdate/control
index b714a7b..6aaec91 100644
--- a/server/site_tests/autoupdate_ForcedOOBEUpdate/control
+++ b/server/site_tests/autoupdate_ForcedOOBEUpdate/control
@@ -9,7 +9,10 @@
 TEST_CATEGORY = "Functional"
 TEST_CLASS = "platform"
 TEST_TYPE = "server"
-ATTRIBUTES = "suite:bvt-perbuild"
+# TODO(crbug.com/877107) This test is sometimes causing DUTs to download
+# and install production images from Omaha, which breaks the DUT.
+# Disable the test until we find a better way to stop that event.
+# ATTRIBUTES = "suite:bvt-perbuild"
 DOC = """
 This tests the forced autoupdate flow at OOBE.