search

cloudfoundry-incubator / admin-ui

Need new main contributor - An application for viewing Cloud Foundry metrics and operations data.
Apache License 2.0
71 stars 44 forks source link

A few tabs: This page requires data from service currently unavailable. #156

Closed tomsherrod closed 8 years ago

tomsherrod commented 8 years ago

Hi,

Deployed adminui against v230 CF. These tabs have the service currently unavailable message: Organizations, Service Instances, Service Bindings, Service Keys, Service Plan Visibilities, Cells.

Pointers to what the problem may be? This is a Diego default backend, expected?

Thanks, Tom

rboykin commented 8 years ago

The Organizations, Service Instances, Service Bindings, Service Keys and Service Plan Visibilities all come from the CCDB. Check the log and ensure your Admin UI can access your configured ccdb_uri.

The Cell information ultimately comes through the /v2/info/doppler_logging_endpoint. Ensure your configured cloud_controller_uri is correct and your configured uaa_client is correct and that client is created as documented in the Admin UI readme.

The Admin UI will handle both Diego backend and DEA backend.

tomsherrod commented 8 years ago

You are spot on.

The log indicates Doppler error, Unexpected response code: 401.

url="wss://doppler.domainname.com:4443/firehose/1459801858" What are the credentials being used for the doppler call, the ccdb_uri?

On Tue, Apr 5, 2016 at 7:06 AM, J Russell Boykin notifications@github.com wrote:

The Organizations, Service Instances, Service Bindings, Service Keys and Service Plan Visibilities all come from the CCDB. Check the log and ensure your Admin UI can access your configured ccdb_uri.

The Cell information ultimately comes through the /v2/info/doppler_logging_endpoint. Ensure your configured cloud_controller_uri is correct and your configured uaa_client is correct and that client is created as documented in the Admin UI readme.

The Admin UI will handle both Diego backend and DEA backend.

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/cloudfoundry-incubator/admin-ui/issues/156#issuecomment-205757356

rboykin commented 8 years ago

The doppler firehose access uses your configured uaa client. This client has to have the authority of doppler.firehose for this to work. Check out the readme on setting up your admin ui client. The doppler.firehose, clients.write and scim.write authorities have been recently added to the admin ui client.

tomsherrod commented 8 years ago

Correct again. I can now see the cells and apps. The interface actually helped me find an application that is still running, that shouldn't be.

A couple of tabs still have the error: Organizations, Spaces, Service Instances, Service Bindings, Service Keys, Service Plan, Service Plan Visibilities. No errors in the admin_ui.log now.

On Tue, Apr 5, 2016 at 9:01 AM, J Russell Boykin notifications@github.com wrote:

The doppler firehose access uses your configured uaa client. This client has to have the authority of doppler.firehose for this to work. Check out the readme on setting up your admin ui client. The doppler.firehose, clients.write and scim.write authorities have been recently added to the admin ui client.

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/cloudfoundry-incubator/admin-ui/issues/156#issuecomment-205791486

rboykin commented 8 years ago

If tabs with earlier alphabetized names have content like applications, buildpacks, domains, etc. then it is possible that the data has just not yet been retrieved. Retrieved in order here from the CCDB/UAADB: https://github.com/cloudfoundry-incubator/admin-ui/blob/master/lib/admin/cc.rb#L24

tomsherrod commented 8 years ago

Thank you for your time and responding. The tabs did not come up. I wiped out what was there and installed successfully, with all tabs.