Loosing 'auth' when using "Cloud Foundry" menu

[svollath]

Frontent Deployment type

• Cloud Foundry Application (cf push)
• Kubernetes, using a helm chart
• Docker, using docker compose
• Docker, single container deploying all components
• npm run start
• Other (please specify below)
  Console 2.1.0 with CAP 1.2.1

Backend (Jet Stream) Deployment type

• Cloud Foundry Application (cf push)
• Kubernetes, using a helm chart
• Docker, using docker compose
• Docker, single container deploying all components
• Other (please specify below)
  UAA/CF 2.13.3 on CaaSP3 (NFS storage)

Expected behaviour

• Goto https://<domain>:8443/cloud-foundry, select "Organizations" and create org 'suseqa'
• Click on org 'suseqa', select "Spaces" and create space 'susetest'

Actual behaviour

• After clicking org 'suseqa' and selecting sapces, "'Cloud Foundry > suseqa' Spaces" loads forever.

• From here on any other menu, e.g. "Services" loads forever, too, even when you return to "Cloud Foundry" - it seems like not being authenticated with the endpoint anymore

• Simply reloading the browser page on a page that "hangs" fixes the issue.

Steps to reproduce the behavior

Log output covering before error and any error statements

Unfortunately I was not able to see any error logged:

Request: [2018-10-01T11:57:11Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/auth/session/verify" Status:401 Latency:65.157µs Bytes-In:0 Bytes-Out:43
INFO[Mon Oct  1 11:57:17 UTC 2018] Found existing cloud foundry endpoint matching https://api.10.160.64.141.omg.howdoi.website. Will not auto-register 
INFO[Mon Oct  1 11:57:17 UTC 2018] Determining if user should auto-connect to https://api.10.160.64.141.omg.howdoi.website. 
INFO[Mon Oct  1 11:57:17 UTC 2018] Yes, user should auto-connect to auto-registered cloud foundry https://api.10.160.64.141.omg.howdoi.website. 
INFO[Mon Oct  1 11:57:17 UTC 2018] Auto-connecting to the auto-registered endpoint with credentials 
INFO[Mon Oct  1 11:57:17 UTC 2018] CloudFoundry Connect...                      
Request: [2018-10-01T11:57:18Z] Remote-IP:"172.16.4.0" Method:"POST" Path:"/v1/auth/login/uaa" Status:200 Latency:532.690164ms Bytes-In:32 Bytes-Out:90
Request: [2018-10-01T11:57:18Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/auth/session/verify" Status:200 Latency:5.004533ms Bytes-In:0 Bytes-Out:2668
Request: [2018-10-01T11:57:18Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/info" Status:200 Latency:3.92472ms Bytes-In:0 Bytes-Out:2668
Request: [2018-10-01T11:57:18Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/proxy/v2/apps" Status:200 Latency:38.508909ms Bytes-In:0 Bytes-Out:115
Request: [2018-10-01T11:57:18Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/proxy/v2/organizations" Status:200 Latency:104.229272ms Bytes-In:0 Bytes-Out:3900
Request: [2018-10-01T11:57:24Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/proxy/v2/shared_domains" Status:200 Latency:14.122311ms Bytes-In:0 Bytes-Out:431
Request: [2018-10-01T11:57:24Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/proxy/v2/info" Status:200 Latency:27.536657ms Bytes-In:0 Bytes-Out:758
Request: [2018-10-01T11:57:24Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/proxy/v2/organizations" Status:200 Latency:36.196932ms Bytes-In:0 Bytes-Out:1627
Request: [2018-10-01T11:57:24Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/proxy/v2/organizations" Status:200 Latency:74.945893ms Bytes-In:0 Bytes-Out:6016
Request: [2018-10-01T11:57:24Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/proxy/v2/users" Status:200 Latency:107.604265ms Bytes-In:0 Bytes-Out:1959
Request: [2018-10-01T11:57:29Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/proxy/v2/organizations/9aaa261d-1236-4cda-8e11-ead1002512c0/users" Status:200 Latency:56.787312ms Bytes-In:0 Bytes-Out:115
Request: [2018-10-01T11:57:29Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/proxy/v2/organizations" Status:200 Latency:84.159799ms Bytes-In:0 Bytes-Out:1627
Request: [2018-10-01T11:57:36Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/auth/session/verify" Status:200 Latency:13.410628ms Bytes-In:0 Bytes-Out:2668
Request: [2018-10-01T11:57:36Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/info" Status:200 Latency:7.68204ms Bytes-In:0 Bytes-Out:2668
Request: [2018-10-01T11:57:36Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/proxy/v2/shared_domains" Status:200 Latency:15.229401ms Bytes-In:0 Bytes-Out:431
Request: [2018-10-01T11:57:36Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/proxy/v2/organizations/9aaa261d-1236-4cda-8e11-ead1002512c0/spaces" Status:200 Latency:29.989988ms Bytes-In:0 Bytes-Out:1448
Request: [2018-10-01T11:57:36Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/proxy/v2/organizations/9aaa261d-1236-4cda-8e11-ead1002512c0" Status:200 Latency:40.100252ms Bytes-In:0 Bytes-Out:3820
Request: [2018-10-01T11:57:36Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/proxy/v2/organizations" Status:200 Latency:29.595215ms Bytes-In:0 Bytes-Out:1627
Request: [2018-10-01T11:57:36Z] Remote-IP:"172.16.4.0" Method:"GET" Path:"/v1/proxy/v2/users" Status:200 Latency:290.600597ms Bytes-In:0 Bytes-Out:1959

[richard-cox]

This was fixed in upstream a few weeks back, we need to update and retest

[richard-cox]

Uber PR #59 has now merged. Have tested on v2-master and all looks good.