Even when setting up the undercloud without SSL, puppet generates a configuration file that assumes we're using a version of the new HAProxy URLs (cf. https://blueprints.launchpad.net/tripleo/+spec/proxy-undercloud-api-services ):
window.tripleOUiConfig = {
"keystone": "http://192.168.24.1:5000/keystone/v2.0",
"heat": "http://192.168.24.1:8004/heat/v1/%(tenant_id)s",
"ironic": "http://192.168.24.1:6385/ironic",
"mistral": "http://192.168.24.1:8989/mistral/v2",
"swift": "http://192.168.24.1:8080/swift/v1/AUTH_%(tenant_id)s",
"zaqar-websocket": "ws://192.168.24.1:9000/zaqar",
// Default websocket queue name
"zaqar_default_queue": "tripleo"
};
This doesn't work when running a HTTP undercloud. The UI is displayed correctly on port 3000 but the user can't log in as http://192.168.24.1:5000/keystone/v2.0/tokens returns a 404.
The workaround is to manually modify /var/www/openstack-tripleo-ui/dist/tripleo_ui_config.js to use the regular URLs:
window.tripleOUiConfig = {
"keystone": "http://192.168.24.1:5000/v2.0",
"heat": "http://192.168.24.1:8004/v1/%(tenant_id)s",
"ironic": "http://192.168.24.1:6385",
"mistral": "http://192.168.24.1:8989/v2",
"swift": "http://192.168.24.1:8080/v1/AUTH_%(tenant_id)s",
"zaqar-websocket": "ws://192.168.24.1:9000",
// Default websocket queue name
"zaqar_default_queue": "tripleo"
};
What needs to happen is that the public_host specification needs to be changed to 3000, instead of the service's default port. Note that this change would only affect the *-ui-config endpoints generated by undercloud.py, such as:
https:/
These endpoints are only used in the configuration of tripleo_