After creating OpenStack with Mirantis Fuel 7 (or 6 as well) using pretty much default settings (including HTTPS for Horizon / TLS) and then going to the Horizon dashboard at https://172.16.0.3 (or https://public.fuel.local), it works differently depending on which subnet I'm accessing it from. It only works perfect (fast, no errors) if I plug my laptop ethernet cable into the 172.16.0.0/24 network (my laptop's IP is 172.16.0.26) and visit https://172.16.0.3. If instead I use my laptop in my preferred network 10.0.1.0/24 (my laptop's IP is 10.0.1.22) and contact 172.16.0.3, the Horizon dashboard does eventually load really slow with an error in the JavaScript debugging console. Then, when I log in, it runs slow and half the stuff is missing from the page when I click around (like the ability to log out). It again throws an error in the JavaScript debugging console. Here's the Firefox console debugging error output:
Error: [$injector:modulerr] Failed to instantiate module hz due to:
[$injector:modulerr] Failed to instantiate module hz.conf due to:
[$injector:nomod] Module 'hz.conf' is not available! You either misspelled
the module name or forgot to load it. If registering a module ensure that
you specify the dependencies as the second argument.
http://errors.angularjs.org/1.3.17/$injector/nomod?p0=hz.conf
minErr/<@https://172.16.0.3/horizon/static/dashboard/js/d5d0ae178ffc.js:674:
8
module/<@https://172.16.0.3/horizon/static/dashboard/js/d5d0ae178ffc.js:779:
1
ensure@https://172.16.0.3/horizon/static/dashboard/js/d5d0ae178ffc.js:777:32
0
module@https://172.16.0.3/horizon/static/dashboard/js/d5d0ae178ffc.js:779:1
loadModules/<https://172.16.0.3/horizon/static/dashboard/js/d5d0ae178ffc.js:779:1
loadModules/><@https://172.16.0.3/horizon/static/dashboard/js/d5d0ae178ffc.js
:878:35
forEach@https://172.16.0.3/horizon/static/dashboard/js/d5d0ae178ffc.js:680:3
91
loadModules@https://172.16.0.3/horizon/static/dashboard/js/d5d0ae178ffc.js:8
77:63
loadModules/<@https://172.16.0.3/horizon/static d5d0ae178ffc.js:674:8
Also, in case it's relevant, the /var/log/keystone/main.log spews out lots of stuff if I tail it while trying to use Horizon from the 10.0.1.0/24 network and the "Auth token not in the request header. Will not build auth context" message might provide a hint:
2015-11-21 16:26:42.629 8862 INFO keystone.common.wsgi [-] OPTIONS /?
2015-11-21 16:26:52.639 8862 INFO keystone.common.wsgi [-] OPTIONS /?
2015-11-21 16:26:54.977 8862 DEBUG keystone.middleware.core [-] Auth token not in the request header. Will not build auth context. process_request /usr/lib/python2.7/dist-packages/keystone/middleware/core.py:229
2015-11-21 16:26:54.983 8862 INFO keystone.common.wsgi [-] POST /tokens?
2015-11-21 16:26:54.985 8862 DEBUG keystone.common.cache._memcache_pool [-] Memcached pool 139632346844768, thread 139632540993280: Acquiring connection _debug_logger /usr/lib/python2.7/dist-packages/keystone/common/cache/_memcache_pool.py:181
2015-11-21 16:26:54.987 8862 DEBUG keystone.common.cache._memcache_pool [-] Memcached pool 139632346844768, thread 139632540993280: Acquired connection 139632340435232 _debug_logger /usr/lib/python2.7/dist-packages/keystone/common/cache/_memcache_pool.py:181
2015-11-21 16:26:54.990 8862 DEBUG keystone.common.cache._memcache_pool [-] Memcached pool 139632346844768, thread 139632540993280: Releasing connection 139632340435232 _debug_logger /usr/lib/python2.7/dist-packages/keystone/common/cache/_memcache_pool.py:181
...
I tried rebuilding OpenStack with Fuel 7 with the HTTPS for Horizon / TLS checkboxes unchecked to see if that was the issue. No, that didn't fix it; the issue still persists.