firmware_Cr50SetBoardId: RLZ is checked after phase

cr50-set-board-id now checks the rlz after the phase. Modify the test
to reflect this.

BUG=none
TEST=run on octopus

Change-Id: Id2a47ee9497543cdac82a9038d8cc3341a8ee48e
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2020681
Commit-Queue: Mary Ruthven <mruthven@chromium.org>
Tested-by: Mary Ruthven <mruthven@chromium.org>
Reviewed-by: Dana Goyette <dgoyette@chromium.org>
diff --git a/server/site_tests/firmware_Cr50SetBoardId/firmware_Cr50SetBoardId.py b/server/site_tests/firmware_Cr50SetBoardId/firmware_Cr50SetBoardId.py
index f290806..7741ea5 100644
--- a/server/site_tests/firmware_Cr50SetBoardId/firmware_Cr50SetBoardId.py
+++ b/server/site_tests/firmware_Cr50SetBoardId/firmware_Cr50SetBoardId.py
@@ -126,8 +126,8 @@
         self.run_script(self.ERROR_INVALID_RLZ, 'dvt', 'A')
         # dummy_phase is not a valid phase
         self.run_script(self.ERROR_UNKNOWN_PHASE, 'dummy_phase')
-        # The rlz code is checked before the phase
-        self.run_script(self.ERROR_INVALID_RLZ, 'dummy_phase', 'A')
+        # The rlz code is checked after the phase
+        self.run_script(self.ERROR_UNKNOWN_PHASE, 'dummy_phase', 'A')
 
         self.eraseflashinfo()
         # Set the board id so we can verify cr50-set-board-id has the correct