Skip to content
This repository has been archived by the owner on Aug 26, 2021. It is now read-only.

Failure to start in VIC appliance #250

Open
andrewtchin opened this issue Feb 12, 2018 · 2 comments
Open

Failure to start in VIC appliance #250

andrewtchin opened this issue Feb 12, 2018 · 2 comments

Comments

@andrewtchin
Copy link

andrewtchin commented Feb 12, 2018

In CI, @mdharamadas1 deployed and initialized a 1.3.1 VIC appliance. When navigating to the Admiral interface a blank page appeared at the SSO redirect.
Logging into the appliance showed that the Admiral process was running, but the Admiral journal showed

Feb 12 16:28:09 wdc-harbor-ci.eng.vmware.com start_admiral.sh[1639]: Exception in thread "pool-1-thread-1" com.vmware.admiral.auth.idm.psc.saml.sso.admin.SsoAdminClientException: Can not create SSO AdminClient.

A reboot of the appliance seems to have resolved this error, but it is initially in an unusable state.

At a minimum, the Admiral process should exit if it is unable to display an error message in case of failure https://github.com/vmware/vic-product/blob/master/installer/docs/DESIGN.md#requirements

How should users troubleshoot this? Please add these steps as part of #249

Log bundle is attached, please let me know if there is additional information that should be gathered in the log bundle
vic_appliance_logs_2018-02-12-16-51-43.tar.gz

@martin-borisov
Copy link
Contributor

@andrewtchin Is this issue still reproducible?

@andrewtchin
Copy link
Author

andrewtchin commented Mar 22, 2018

@martin-borisov We haven't seen it in a while, though I would like the error documentation and troubleshooting steps to still be addressed. Would you like me to copy those into the relevant issues?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants