|Priority:||5 - Low|
|Created by:||Dan McDonald|
|Reported by:||Dan McDonald|
Reported by Alex Wilson here: [https://github.com/TritonDataCenter/mahi/issues/19|https://github.com/TritonDataCenter/mahi/issues/19|smart-link]
Fixed by Alex Wilson here: [https://github.com/TritonDataCenter/mahi/pull/20|https://github.com/TritonDataCenter/mahi/pull/20|smart-link]
Description from Alex:
UFDS can write log entries out of order, resulting in a log that can't be replayed by mahi. It's fine for mahi to stop replicating in this situation, but it should not crash.
Currently if you quickly add a user to a role and remove them, and the log entries get re-ordered, then mahi v1 will crash in
auth_cache.js around line 738. It should either truck on (because mahi v1 is loosey goosey about that generally) or stop replicating, not crash.
Testing notes from Alex:
https://github.com/TritonDataCenter/mahi/pull/21 Is what we’ll be pulling this in from.
mahi commit bcc382b49094144f9fd93f5dff41e57cd0630afb (branch master, by Alex Wilson)
TRITON-2316 mahi v1 crash on bad role mgmt log entry
Reviewed by: Dan McDonald <email@example.com>
Reviewed by: Brian Bennett <firstname.lastname@example.org>