Comment 3 for bug 1524395

Our current workaround is to use --limit, just for adding hosts.
But I'm more afraid of situations where people run playbooks just to rewrite config files.
The restart did only happen once, when we did restart the playbooks, at least in a test environment it did not restart the container.
Not knowing why files like /etc/network/interfaces.d/management.cfg got updated, they should never after the container got created, at least running the playbooks of the same release), make me believe we need a fail safe to suppress restarts when rerunning playbooks in a not 1st install scenario.