Ian Wienand 93bb1d549e letsencrypt : use date call for serial number ... Per [1] ansible_date_time is NOT actually the date/time -- it is the time cached from the facts. It seems this can not be changed because, of course, things have started depending on this behaviour. This is particuarly incorrect if you're using this as a serial number for DNS and it is not incrementing across runs, and thus bind is refusing to load the new entries in the acme.opendev.org zone during letsencrypt runs, and the TXT authentication fails. Use the suggested work-around in the issue which is an external call to date. [1] https://github.com/ansible/ansible/issues/22561 Change-Id: Ic3f12f52e8fbb87a7cd673c37c6c4280c56c2b0f		2019-05-22 16:41:51 +10:00
..
zone.db.j2	letsencrypt : use date call for serial number	2019-05-22 16:41:51 +10:00