spinnaker: unable to connect to spinnaker deck (GUI)

Issue Summary:

deck and gate reject port 8084 even though it is opened in the firewall

Cloud Provider(s):

kubernetes

Environment:

local debian: ubuntu 16.0.4

Feature Area (if this issue is UI/UX related, please tag @spinnaker/ui-ux-team):

@spinnaker/ui-ux-team

Description:

I installed spinnaker locally: hal config deploy edit --type localdebian on my machine which has also a public floating IP address assigned to it. The installation is successful and command sudo hal deploy connect is also successful. All ports including 9000 and 8084 are open (for testing spinnaker)

I also changed the host to 0.0.0.0 in both gate and deck and I updated UI security as the follwing:

echo "host: 0.0.0.0" | tee \
   ~/.hal/default/service-settings/gate.yml \
   ~/.hal/default/service-settings/deck.yml

hal config security ui edit \
    --override-base-url http://<my floating IP address>:9000

hal config security api edit \
    --override-base-url http://<my floating IP address>:8084

sudo hal deploy apply

Then I reloaded daemon and restarted apache2

sudo systemctl daemon-reload
sudo service apache2 restart

I can launch Spinnaker UI web page on http://<my floating IP address>:9000 but when trying creating a new application I got error message: Error initializing dialog. Check that your gate endpoint is accessible.

When I use the web inspector:

Access to XMLHttpRequest at 'http://x.x.x.x:8084/credentials?expand=true' from origin 'http://x.x.x.x:9000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
3vendors~app.js:278 

Possibly unhandled rejection: {"data":null,"status":-1,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"jsonpCallbackParam":"callback","url":"http://x.x.x.x:8084/credentials","cache":true,"params":{"expand":true},"timeout":65000,"headers":{"X-RateLimit-App":"deck","Accept":"application/json, text/plain, */*"},"withCredentials":true},"statusText":"","xhrStatus":"error"} undefined

Here is the screen shot of the problem:

Screenshot from 2019-03-12 09-58-25

Screenshot from 2019-03-12 09-55-08

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 27

Most upvoted comments

Hm. Are you using Minio to emulate S3? I’ve only ever seen that error in user reports about Minio.

If so, have you performed the step on this page about disabling the s3 versioning flag?

Editing your storage settings

Given that Minio doesn’t support versioning objects, we need to disable it in Spinnaker.

Add the following line to ~/.hal/default/profiles/front50-local.yml:

spinnaker.s3.versioning: false