Ahh, I've repeated the crash. I think I've reported something similar before and it's to do with the user interface refresh. You have to be quick but the process to get the console to crash is:
- Remove replica from node #2
- Before the interface refreshes, attempt to remove the replica from node #1
- Console crashes as shown in attached
I'm assuming the crash is due to attempting to remove the replica on node #1 which has actually already removed but the user interface hasn't yet refreshed.
But the query about *why* the storage disappears from the other node still stands. So two things here: bug/query about storage disappearing and bug that the code doesn't trap attempting an operation on storage that has been removed but is still visible on the console.
Cheers, Rob.