commit 6818633834ad52c3de153235639ea9299a6e9a6d
author Matthew Sartori <msartori@chromium.org> Mon Apr 27 17:19:53 2015 -0700
committer ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> Fri May 01 01:07:48 2015 +0000
tree 4e11b77755828129cb8e5ae500d28d699fb91cd3
parent 8ef41dc9f66ad9bc533533c621b4a01e48d89ad0

[autotest] Require lock reason to lock device

When locking a device, a locking reason now must be provided.
This applies to both adding a new device, and modifying an
existing device from both the web frontend and the atest
command-line tool.

BUG=chromium:336805
DEPLOY=migrate
TEST=Tested adding locked/unlocked devices and locking/unlocking devices
from both the web frontend and using the 'atest host ...' command-line tools.

Change-Id: I3a8cd8891a2999f026dd709ae8a79e2b8cbc251a
Reviewed-on: https://chromium-review.googlesource.com/267595
Tested-by: Matthew Sartori <msartori@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Matthew Sartori <msartori@chromium.org>

frontend/afe/models_test.py

diff --git a/frontend/afe/models_test.py b/frontend/afe/models_test.py
index 8219755..6865bf5 100755
--- a/frontend/afe/models_test.py
+++ b/frontend/afe/models_test.py
@@ -434,6 +434,7 @@
                                        'only_if_needed': False,
                                        'platform': False}],
                            'leased': False,
+                           'lock_reason': '',
                            'lock_time': None,
                            'locked': False,
                            'protection': 0,