The vendor has published 2 unique mention(s) for this bug: 1. In rare scenarios, after the NetScaler Console HA failover, the secondary node incorrectly remains in the Stay as Secondary state, and prevents the node from participating in the HA setup. 2. In rare scenarios, after the NetScaler Console HA failover, the secondary node incorrectly remains in the Stay as Secondary state, and prevents the node from participating in the HA setup. Workaround: If you encounter this issue, run the following command from the NetScaler Console secondary node shell prompt to reset the flag: /mps/pgxl_node_client.py --stay_as_secondary false Modules: 1. Miscellaneous Latest urls for this bug: 1. https://docs.netscaler.com/en-us/updates?product=NetScaler%20Console%20on-prem%20%28ADM%29&version=13.1&build=61.28 2. https://docs.netscaler.com/en-us/updates?product=NetScaler%20Console%20on-prem%20%28ADM%29&version=13.1&build=62.27 3. https://docs.netscaler.com/en-us/updates?product=NetScaler%20Console%20on-prem%20%28ADM%29&version=14.1&build=60.57