Closed Cajga closed 5 years ago
As per https://clouddocs.f5.com/products/orchestration/ansible/devel/usage/filing-issues.html please download the latest ansible galaxy role retest and post results with the role in use.
Once this information is provided we will re-open
Hi @wojtek0806,
Sry. for not trying it first with the role. Seems, with the role, it works fine. Do you have a rough schedule (in few days/weeks/months) when this will be released to the ansible github repo? Which firmware version would you recommend to use for the F5's in order to get a stable configuration environment with ansible (we are planning to use the "stable f5 modules" from he ansible github repo)?
Thank for the support and for the modules, Balazs
@Cajga The role is a wrapper for our development code and it is updated daily, so you can use it in the meantime without having to explicitly clone the repository. As far as ansible core development branch is concerned I do upstream the changes into ansible core every 2-3 weeks. For official ansible release to have those changes you need to wait for 2.8 to release in May.
Also closer to 2.8 release I will be marking some modules as stable so when they are merged finally into 2.8 you can be sure the interface will not change much without prior warning.
For the version, in all honesty any long term stability version starting from 12.x is fine, although we have tested all of these modules on 12.x and 13.x, 14.x is on the to do list before 2.8 is released.
One thing to note here that bigip_provision has some issues when APM/ASM/AVR modules are provisioned together, this is down to the fact that these modules take a long time to provision and sometimes platforms like Virtual Editions tend to respond to rest calls too early while the httpd and the entire api is not fully up.
See here: https://github.com/F5Networks/f5-ansible/issues/1105
@wojtek0806,
Thank you very much for the valuable information. For now we will stick to version 14.1 and the ansible core development branch and do the resource provisioning manually until the module changes appear there.
ISSUE TYPE
COMPONENT NAME
bigip_provision
ANSIBLE VERSION
PYTHON VERSION
BIGIP VERSION
CONFIGURATION
$ cat ansible.cfg [defaults] retry_files_enabled = False host_key_checking=False
OS / ENVIRONMENT
RHEL7.6
SUMMARY
I am trying to configure the vCMP host with ansible from scratch. Ansible fails to provision the vcmp module.
STEPS TO REPRODUCE
1) reset the LB config with the reset_config.yaml 2) change the admin user password from the web gui to q1w2e3!@# 3) run the provision_issue.yaml
EXPECTED RESULTS
ltm module gets disabled but vcmp module gets provisioned.
ACTUAL RESULTS
Ansible fails to provision the vcmp module.