Restart services at first provisioning
Due to this MR: https://gitlab.com/coopdevs/somconnexio-mm-proxy-provisioning/-/merge_requests/34
Which didn't take into account two things:
- the first time we provision our machine, the write secrets task will have a "changed" status, but no services will be known by the host.
- In development we don't want this behavior, these services don't exist.
We run into this error the first time we provision our local machine:
RUNNING HANDLER [app_user : restart proxy-services] ************************************************************************************************************
failed: [somconnexio-mm-proxy.local] (item=celery-mm-proxy) => {"ansible_loop_var": "item", "changed": false, "item": "celery-mm-proxy", "msg": "Could not find the requested service celery-mm-proxy: host"}
failed: [somconnexio-mm-proxy.local] (item=mm-proxy-gunicorn) => {"ansible_loop_var": "item", "changed": false, "item": "mm-proxy-gunicorn", "msg": "Could not find the requested service mm-proxy-gunicorn: host"}
Edited by Administrator