In the STAGE version 2.1 the following limitations exist:
STAGE
Changes to users managed outside of STAGE can briefly lead to blank Login Page
In some circumstances, a user may be presented with a blank screen instead of a Login page. This can be resolved by refreshing the browser window (pressing F5 or clicking the refresh button). This can happen in cases where a user is logged in via an external Identity Provider and changes are done to the user in the Identity Provider system while the user is logged in. After a manual logout or a session timeout, the user will be navigated back to the login screen, which in some cases can appear empty.
Job multicast allocation fails when multicast range is split up
When configuring two or more STAGE Jobs that have multicast ranges that overlap, the Job might never become fully allocated until the Job is restarted. For example, create a first job with the multicast allocation x.x.0.100 for one device. Now create a second job with a multicast allocation range set as x.x.0.99 to x.x.0.101 for two devices. One of the Jobs will not be fully allocated with devices as expected.
Workaround: Restart the Jobs.
Missing user feedback when Stage server is booting
While a STAGE cluster is rebooting, the STAGE Web User Interface may become temporarily unresponsive or display a 414 Request-URI Too Long error; this condition resolves automatically once the cluster startup process is complete, which may take several minutes depending on the hardware.