Installing haproxy again after teardown fails

[samuelallan72]

Running the sequence of site.yaml, teardown.yaml, site.yaml playbooks results in:

er", "     Loaded: loaded (\u001b]8;;file://maas2/lib/systemd/system/haproxy.service\u0007/lib/systemd/system/haproxy.service\u001b]8;;\u0007; enabled; vendor preset: enabled
)", "     Active: activating (auto-restart) (Result: exit-code) since Mon 2022-12-12 02:06:11 UTC; 3ms ago", "       Docs: \u001b]8;;man:haproxy(1)\u0007man:haproxy(1)\u001b]
8;;\u0007", "             \u001b]8;;file:/usr/share/doc/haproxy/configuration.txt.gz\u0007file:/usr/share/doc/haproxy/configuration.txt.gz\u001b]8;;\u0007", "    Process: 284
95 ExecStartPre=/usr/sbin/haproxy -Ws -f $CONFIG -c -q $EXTRAOPTS \u001b[0;1;31m(code=exited, status=1/FAILURE)\u001b[0m", "dpkg: error processing package haproxy (--configur
e):", " installed haproxy package post-installation script subprocess returned error exit status 1", "Errors were encountered while processing:", " haproxy"]}

This seems to be because when haproxy is re-installed, it will be started immediately, and then fails with an error because the configuration file isn't found.

Suggested fix: move Write HAProxy Config task to before Install HAProxy task. This fixed the issue for me.

Or perhaps disable the haproxy service before tearing it down? Or some other way to prevent it from auto-starting on install?

[samuelallan72]

Suggested fix: move Write HAProxy Config task to before Install HAProxy task. This fixed the issue for me.

Actually this may not be the best solution - this fails on a clean install:

TASK [maas_proxy : Write HAProxy Config] ***************************************
fatal: [192.168.122.217]: FAILED! => {"changed": false, "checksum": "8bca484491bcf78d8f07d00a8841ccb797b0391a", "msg": "Destination directory /etc/haproxy does not exist"}
fatal: [192.168.122.177]: FAILED! => {"changed": false, "checksum": "8bca484491bcf78d8f07d00a8841ccb797b0391a", "msg": "Destination directory /etc/haproxy does not exist"}
fatal: [192.168.122.139]: FAILED! => {"changed": false, "checksum": "8bca484491bcf78d8f07d00a8841ccb797b0391a", "msg": "Destination directory /etc/haproxy does not exist"}

[SK1Y101]

Hey @samuelengineer
Is this still an issue for you on the latest playbook version? We've had internal testing that deploys HA using these playbooks, so if there's something else we need to look into that would be great to know!

[samuelallan72]

@SK1Y101 sorry not sure, I haven't looked at this since last year. And I won't have time/resources to test again now I'm sorry. Feel free to close the bug. :)