Horizon is not available by IP of a controller node
Bug #1312677 reported by
Nikolay Fedotov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cisco Openstack |
Fix Released
|
High
|
Unassigned | ||
Bug Description
Cisco Openstack installer leaves 15-default.conf virtual host configuration enabled. Both the default and horizon virtual hosts are bound to same *:80. But the default is loaded first. As a result the Horizon is available only by ServerName.
Expected result: Horizon is available by IP of a controller node too.
| Changed in openstack-cisco: | |
| milestone: | none → i.0 |
| Changed in openstack-cisco: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Don Talton (dotalton) |
Revision history for this message
| subconscious (subconscious) wrote | #1 |
| Changed in openstack-cisco: | |
| status: | Triaged → In Progress |
| Changed in openstack-cisco: | |
| status: | In Progress → Fix Committed |
| Changed in openstack-cisco: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
puppet-apache looks for two different params. "priority" and "default_vhost". If priority is set, then default_vhost is ignored and the priority of the vhost is set. If default_vhost is set, the site priority is set to '10'. If neither, then the default is '25'.
Puppet-horizon had a hard-coded priority of '15', which conflicted with the generic default site.
I exposed the priority parameter to puppet-horizon
https:/
And set it to be the default site in puppet_
https:/