Open tdcox opened 9 years ago
We've just refactored the code to use a new watcher bit of code thats a bit more reliable & capable of dealing better with websocket timeouts. Lets see if the new latest docker image is any better - hopefully this is fixed!
Ok, there is a variant of this bug where the staging boxes fail to render entirely and it looks like a race condition: Listening on: /workspaces/:namespace/forge/createProject [fabric8-console] started, version: undefined [fabric8-console] commit ID: undefined [Developer] env found: [object Object] for nameppace test32-staging on buildConfig: [object Object] WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test32-staging/endpoints?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test32-staging/events?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/api/v1/nodes?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/api/v1/persistentvolumes?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test32-staging/persistentvolumeclaims?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test32-staging/pods?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test32-staging/replicationcontrollers?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test32-staging/resourcequotas?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test32-staging/secrets?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test32-staging/services?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test32-staging/serviceaccounts?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/oapi/v1/namespaces/test32-staging/templates?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/oapi/v1/namespaces/test32-staging/buildconfigs?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/oapi/v1/namespaces/test32-staging/routes?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/oapi/v1/namespaces/test32-staging/builds?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/oapi/v1/namespaces/test32-staging/deploymentconfigs?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/oapi/v1/namespaces/test32-staging/imagestreams?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/oapi/v1/oauthclients?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/oapi/v1/namespaces/test32-staging/policies?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/oapi/v1/namespaces/test32-staging/policybindings?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. WebSocket connection to 'wss://vagrant.f8:8443/oapi/v1/projects?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket is closed before the connection is established. [Developer] entity has changed!
There have been some reports on IRC of the content of the Testing, Staging and Production boxes in the fabric8 console UI not being rendered.
I have just seen the same behaviour here and it is associated with the following console log information: [Developer] entity has changed! WebSocket connection to 'wss://vagrant.f8:8443/oapi/v1/namespaces/default/buildconfigs?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket opening handshake timed out [Developer] entity has changed! WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test33-testing/replicationcontrollers?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket opening handshake timed out WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test33-testing/pods?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket opening handshake timed out WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test33-staging/replicationcontrollers?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket opening handshake timed out WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test33-staging/pods?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket opening handshake timed out WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test33-prod/replicationcontrollers?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket opening handshake timed out WebSocket connection to 'wss://vagrant.f8:8443/api/v1/namespaces/test33-prod/pods?watch=true&access_token=P9CE2p4mPLXGYeJAwIF0XxfgNivpEuzyviOdz8leMYE' failed: WebSocket opening handshake timed out [Developer] project versions has changed!