Apache2 site virtual host configuration created incorrectly
Bug #1313709 reported by
Darryl Weaver
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-dashboard (Juju Charms Collection) |
Fix Released
|
High
|
Liam Young |
Bug Description
When deploying openstack-dashboard on trusty.
cs:trusty/
The virtual host configuration in /etc/apache/
The default site should be on port 70.
The default-ssl site should be on port 433.
To match the apache ports.conf file, which is set correctly.
The haproxy load balancer then takes ports 80 and 443 and forwards to apache on ports 70 and 433.
This results in an incorrect configuration that prevents SSL connections from being forwarded correctly and breaking SSL logins via the dashboard.
Related branches
lp://qastaging/~gnuoy/charms/precise/openstack-dashboard/fix-for-apache24
Merged
into
lp://qastaging/~openstack-charmers-archive/charms/precise/openstack-dashboard/trunk
at
revision 28
- Liam Young (community): Needs Resubmitting
- James Page: Needs Fixing
-
Diff: 244 lines (+89/-39)3 files modifiedhooks/charmhelpers/core/host.py (+14/-0)
hooks/horizon_utils.py (+33/-9)
unit_tests/test_horizon_utils.py (+42/-30)
Changed in openstack-dashboard (Juju Charms Collection): | |
assignee: | nobody → Liam Young (gnuoy) |
Changed in openstack-dashboard (Juju Charms Collection): | |
status: | Triaged → Fix Released |
To post a comment you must log in.
This is an apache2.6 compat issue - Triaging as High.