Exit with error when certificate request failed

[jaywink]

Exit with error when certificate request failed

[jaywink]

This is why I fear looking at error messages is an endless struggle. You could tackle these but in the end there is a lot of error message comparison going on and each certbot release might break some of it.

If we don't stop services at all as per discussion in #5 then case 1 here can always raise and case 2 should also - since we can stop looking at "to be ignored" error messages completely, right?

[gronke]

Sorry, but this bug was a false positive. We catch the error, but not in the task directly after. In case obtaining a certificate failed, we of course want to restart services. Let's say our certificate is still valid for 5 more days, but LetsEncrypt is down. Of course we want the webserver to spin up again before the role exits with a failure.