Merge lp://qastaging/~gnuoy/charms/precise/openstack-dashboard/fix-for-apache24 into lp://qastaging/~openstack-charmers-archive/charms/precise/openstack-dashboard/trunk
Status: | Merged |
---|---|
Merged at revision: | 28 |
Proposed branch: | lp://qastaging/~gnuoy/charms/precise/openstack-dashboard/fix-for-apache24 |
Merge into: | lp://qastaging/~openstack-charmers-archive/charms/precise/openstack-dashboard/trunk |
Diff against target: |
244 lines (+89/-39) 3 files modified
hooks/charmhelpers/core/host.py (+14/-0) hooks/horizon_utils.py (+33/-9) unit_tests/test_horizon_utils.py (+42/-30) |
To merge this branch: | bzr merge lp://qastaging/~gnuoy/charms/precise/openstack-dashboard/fix-for-apache24 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Liam Young (community) | Needs Resubmitting | ||
James Page | Needs Fixing | ||
Review via email:
|
Description of the change
The name of the default vhosts was sensibly changed by the debian package maintainers for apache 2.4 (see line ~56 http://
This branch registers two new configs files corresponding to the new default http{,s} vhosts and uses them in preference to the old ones if the installed version of apache2 >= 2.4
There is a corresponding mp to add the cmp_pkgrevno function to charmhelpers ( https:/
While writing the unit tests it became apparent that some of the existing tests where not checking that the list of calls to register config exactly matched the test list but rather that the call had happened at some point:
"assert_
I've switched these tests to use assert_has_calls to ensure there is no mix of 2.2 and 2.4 config.
I've tested with precise/havana and icehouse/trusty