Closed onurbrc closed 5 years ago
@onurbrc how did you "install" the module? did you use it through the f5devcentral.f5ansible galaxy role?
@onurbrc I cannot reproduce this using the galaxy role. I think there's a misconfiguration on your end.
@caphrim007 I was using the module as ad-hoc. I also have created a playbook after I downloaded the update of bigip_file_copy and its dependencies, module_utils/network/f5/icontrol.py. I'll check my actions again using those tasks above.
Thanks in advance.
@caphrim007
I just tested again after reviewing the parameters. I still have the message error telling me to use validate_certs=False. But, I was using it already. In my tasks I precise "validate_certs: no".
I'm using Ansible 2.7 and the latest icontrol.py. Should I have update another library ?
@onurbrc install this galaxy role via the instructions on the README page
https://galaxy.ansible.com/f5devcentral/f5ansible
and then modify a playbook (as shown in the instructions) to see if it makes a difference.
@caphrim007 YES !!! \o/ It worked properly. Thanks.
But I'm a little bit lost now. What was the problem ? I surely did something wrong, but I don't know what ?
So, I must use role: f5devcentral.f5ansible before tasks waiting for a stable version ? I'm asking because I don't use ansible-galaxy very much. Sorry.
Thanks very much. ;-)
I'm not sure what the problem was. I would guess its some difference in module utils in your installation.
The galaxy role is for people who need solutions "now" and not "4 months from now". Since Ansible itself is released quarterly, and the F5 team makes enhancements and fixes daily, there is a significant waiting period in place before you the customer can get these fixes and enhancements.
Galaxy is the method we use to package up our current development code for faster public consumption.
The galaxy role is essentially what you'll get automatically when you upgrade to the next stable version of Ansible. Except...you can get it today, and you don't need to worry about screwing up your existing ansible installation to make it work.
For instance, if you install it and it doesn't work, then you can just comment out the roles
section that you added to include the galaxy role.
For people like yourself that interact with the developers on Github, the Galaxy approach is far more suitable (ie easier and less error prone) than trying to do-it-yourself by copying files around.
You can force install the galaxy role daily because we build it nightly at midnight Pacific time. Alternatively, we also release it bi-weekly on Friday's (also pacific time) for those who don't want to upgrade every night.
In terms of stability, the galaxy role is technically considered "development" and "unstable". However, with that said, it is also the most up-to-date and if there are bugs, they are fixed much faster than what you get in Ansible itself.
I personally consider the galaxy role as relatively stable code because it is ultimately what will be included in the next stable version of ansible.
I appreciate your explanation @caphrim007. It is very clear now. Thank you very much. I'll use ansible-galaxy \o/. Best regards.
ISSUE TYPE
COMPONENT NAME
bigip_file_copy
ANSIBLE VERSION
PYTHON VERSION
BIGIP VERSION
LIBRARY VERSIONS
CONFIGURATION
OS / ENVIRONMENT
SUMMARY
Hello,
I don't know if I'm doing something wrong, but iControl seems ignore "validate_certs: no" using the bigip_file_copy module. I'm using the updated icontrol.py to run bigip_file_copy and bigip_monitor_external associated to issue #778 .
STEPS TO REPRODUCE
TMSH commands :
EXPECTED RESULTS
ACTUAL RESULTS