generated from ansible-collections/collection_template
-
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
digital_ocean_load_balancer_info cannot select LB by ID #35
Labels
bug
Something isn't working
Comments
From @ansibullbot on May 03, 2020 09:15 Files identified in the description: If these files are inaccurate, please update the |
From @ansibullbot on May 03, 2020 09:15 |
From @jrkarnes on May 23, 2020 19:02 Is there any progress on this? |
andrewsomething
added a commit
to andrewsomething/community.digitalocean
that referenced
this issue
Apr 2, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From @Akasurde on May 03, 2020 09:13
From @jrkarnes on May 01, 2020 19:37
SUMMARY
When attempting to use the
digital_ocean_load_balancer_info
module, specifying aload_balancer_id
causes the module to experience a failure.ISSUE TYPE
COMPONENT NAME
/ansible/modules/cloud/digital_ocean/digital_ocean_load_balancer_info.py
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
I'm running this locally against my own machine so I suppose this would be MacOS Mojave 10.14.6.
Model Name: MacBook Pro
Model Identifier: MacBookPro11,3
Not sure what else you want here as this is running against
hosts: 127.0.01
andconnection: local
STEPS TO REPRODUCE
doctl compute load-balancer list
to see your newly created load balancer. Capture it'sid
and use it for step 3EXPECTED RESULTS
I would expect to receive information about my load balancer, preferably in the form of a
HashMap
ACTUAL RESULTS
Abject failure and sadness =(
Bonus Information
If you run the
digital_ocean_load_balancer_info
module without specifying theload_balancer_id
parameter, you will get a successful invocation withdata
in the response. Frustratingly, the "id" field for the load balancer I was trying to get data for was present in the response.Copied from original issue: ansible/ansible#69283
Copied from original issue: ansible/ansible#265
The text was updated successfully, but these errors were encountered: