To Reproduce Steps to reproduce the behavior:

1. Depending on the services deployed before the Swift role, the directory /var/lib/edpm-config/firewall might not exist and/or permissions are (correctly) limited to root, failing later when adding firewall rules. For example: 

   fatal: [edpm-swift-0]: FAILED! => {"changed": false, "error": "Destination directory does not exist", "msg": "Directory /var/lib/edpm-config/firewall doesn't exist, please create it before trying to push files in there", "sucess": false}

Expected behavior

• EDPM role finishes successfully

Bug impact

• Swift EDPM role fails to deploy.

Known workaround

• Manually create /var/lib/edpm-config/firewall and set permissions.