The startup sequence sometimes fails to initialize the default ADMs on initial startup. The exact cause is unknown, but has recurred intermittently on some systems for a while and may be related to other warnings and startup timing.
This issue can be resolved by sending a POST request to http://{{hostname}}:5555/adms/load_default
To aide future users should this recur I suggest we:
- Document this on the troubleshooting section with a sample curl command
- As a user-friendly option, add logic to the UI
ADMs page that, if an empty list of ADMs is returned (does not show, or at least is not highlighted, if no response was received or any ADMs did load), an extra button is displayed to "Load defaults".
The startup sequence sometimes fails to initialize the default ADMs on initial startup. The exact cause is unknown, but has recurred intermittently on some systems for a while and may be related to other warnings and startup timing.
This issue can be resolved by sending a POST request to http://{{hostname}}:5555/adms/load_default
To aide future users should this recur I suggest we:
ADMspage that, if an empty list of ADMs is returned (does not show, or at least is not highlighted, if no response was received or any ADMs did load), an extra button is displayed to "Load defaults".