If I try and upgrade a package that has already been started, 'service' module doesn't seem to behave:
- name: Install Docker yum: name=docker-io-1.3.1 state=installed - name: Start Docker service: name=docker state=started If Docker has already been installed and started and we just upgraded, 'service' module blows up with: /var/run/docker.pid still exists... I have to manually issue a service state=restarted command to get hosts back in line. Is Docker misbehaving or should 'service' be smarter in this case? -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/1f46ebe4-2972-419a-b00d-f214d1ef0ba5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
