This might have been a transient issue or perhaps a user doing something they shouldn’t have. For now I’m unable to reproduce. If this happens again in the future let us know and in the meantime you can try a different login node. For example since you were on discovery2, you could specify the discovery1 hostname.