Fix #90 by hard-restarting postfix on configuration changes #94
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is probably the most straight-forward workaround for #90. If the postfix configuration changes, we will do a real
restart
(meaningstop
andstart
, in general) instead of doingreload
, which was the old behaviour.This also introduces two basic Beaker acceptance tests, to prove it is working. I have successfully tested them with the
ubuntu-14.04-x86_64-vagrant.yml
nodeset. I also noticed that thecentos-6-x86_64-vagrant.yml
seems to be broken (it fails already on in the preparational steps of the beaker run).