-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to create a droplet and apply a firewall #302
Comments
I don't quite get it, can you clarify whether ...
|
maybe this one? i tested latest ansible + digitalocean community collection and if i specify firewall during droplet creation - droplet creation task always endups in failure. if i omit firewall definition - task gets proper changed state and consequent runs with firewall definition work as expected. all fails have
all consequent and/or successful runs does not have msg [ null, true ] in them. does not matter if it is a string or array or firewalls (should be array of strings according to manual) it still fails. to test just use simple droplet creation and specify firewall. it will always fail if droplet gonna be created for the first time. |
this is failed variant.
and this is successful creation of droplet without specifying firewall
|
SUMMARY
In my ansible playbook I create a firewall and it's successful. Then I create a droplet and apply the firewall to it, but it fails without a message. In Digital Ocean the droplet exists and is correctly configured with the firewall applied.
ISSUE TYPE
COMPONENT NAME
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
My ansible playbook:
EXPECTED RESULTS
I expect that either:
a. If there is an "ok" response, then the droplet has been created with the firewall applied to it.
b. If there is a "failed" response, then the droplet has not been created and there is an error message.
ACTUAL RESULTS
Command:
exec ansible-playbook -i inventory_prod.yml create_droplet_prod.yml --ask-become-pass -vvvv
Results:
In Digital Ocean in the droplet's "Networking" page I can see that this firewall was applied.
The text was updated successfully, but these errors were encountered: