Given a Wazo installed before 2020-02-08
When I upgrade my engine
Then Asterisk fails to start at the end of wazo-upgrade and when launching with `systemctl start asterisk.service`
The workaround is to add a drop-in file to the the User field in systemd
Technical details:
Systemd patch: https://salsa.debian.org/systemd-team/systemd/commit/e9c8637d06e373430b8986643cfb537a23b0b1fd
For the record:
Technical solution:
for 20.03+: add `User=asterisk` to asterisk.service in asterisk package
for 20.02 and below: add `User=asterisk` to drop-in from wazo-asterisk-config package
commit:
Steps:
fix asterisk package in wazo-dev-buster
document bug and workaround in Jira
backport fix in package wazo-asterisk-config to:
pelican-buster
wazo-rc-buster
archive 20.02, 20.01, 19.17
archive 19.16 and 19.15
archive 19.14
archive 19.13
tag wazo-asterisk-config
paste the workaround on Mattermost wazo-platform for people that are stuck
Run wazo-daily-rolling-prod test