Charm should only write out configs and call autocert on changes

Bug #1884701 reported by Haw Loeung
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
autocert-charm
New
Undecided
Unassigned

Bug Description

Hi,

When rolling out latest charm, which should only change the shipped out cron job, the autocert charm writes out all site configs in /etc/autocert/haproxy/ (or whatever service). It then calls autocert:

| tracer: ++ queue handler reactive/autocert.py:372:configure_autocert
| 2020-06-23 02:54:50 INFO juju-log Invoking reactive handler: reactive/autocert.py:372:configure_autocert
| 2020-06-23 02:54:50 DEBUG juju-log Writing file /etc/autocert/haproxy/mysite.ini root:root 640
| ...
| 2020-06-23 02:55:00 INFO juju-log Running autocert...
| 2020-06-23 02:55:13 DEBUG config-changed OK: Service 'haproxy', cert 'mysite' is present and correct
| ...
| 2020-06-23 02:55:13 INFO juju-log Successfully ran autocert

This also happens on config-changed enabling 'run_weekdays'. I think it should only write out configs on disk if the contents have changed and also call autocert (which then triggers service reload) on config changes.

Haw Loeung (hloeung)
summary: - Charm should only write on configs and call autocert on changes
+ Charm should only write out configs and call autocert on changes
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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