Juju Charms Collection
apache2 package

Config files left behind after servername change

Bug #1578956 reported by Jacek Nykis
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apache2 (Juju Charms Collection)
New
Undecided
Unassigned

Bug Description

After updating servername parameter old vhosts are left behind.

To replicate:

* deploy apache2 with servername set to:
servername=myservice.internal

* change the setting like this:
juju set servername=myservice.company.com

* result

Units end up with the following files in /etc/apache2/sites-enabled:
myservice.internal_http.conf
myservice.internal_https.conf
myservice.company.com_http.conf
myservice.company.com_https.conf

* expected result

I expected "myservice.internal*" files gone from /etc/apache2/sites-enabled so that it only has:
myservice.company.com_http.conf
myservice.company.com_https.conf

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.