Configuration paradox

[sspreitzer]

This role introduces a paradox.

• The daemon can not be started if the configuration is not valid for the system
• The role can not change the daemon configuration unless the daemon is started

There are unknown cases in which by external dependencies the configuration is inapplicable.

• Eg. system has ipv6 disabled but localhost in /etc/hosts is 127.0.0.1 and ::1. postfix will not start as it can not bind to ::1

Please solve the configuration paradox.

[sspreitzer]

Can be solved by invoking postconf prior service start.

[richm]

patches welcome

[sspreitzer]

Okay, I will put it on my todo list

[sspreitzer]

@richm you can assign the issue to me

[scrubby]

Any updates about this paradox? I'm running into myself as well.

[richm]

Any updates about this paradox? I'm running into myself as well.

No updates - PRs/patches welcome

[scrubby]

Wouldn't the fix be as simple as splitting the enable service and the start service?
So in the main.yml change this

- name: Enable Postfix
  service:
    name: postfix
    state: started
    enabled: true

To this

- name: Enable Postfix
  service:
    name: postfix
    enabled: true

And then in the end of the file, in case it's run without applying a custom conf>

- name: Enable Postfix
  service:
    name: postfix
    state: started