F5Networks
bigip_lx_package module does not create the "enable" file
ISSUE TYPE
- Bug Report
COMPONENT NAME
bigip_lx_package
ANSIBLE VERSION
ansible 2.9.5
config file = /home/michal/ccloud-net/ansible.cfg
configured module search path = ['/home/michal/ccloud-net/plugins/modules']
ansible python module location = /home/michal/venv/prod/lib/python3.7/site-packages/ansible
executable location = /home/michal/venv/prod/bin/ansible
python version = 3.7.5 (default, Nov 20 2019, 09:21:52) [GCC 9.2.1 20191008]
PYTHON VERSION
Python 3.7.5
BIGIP VERSION
Sys::Version
Main Package
Product BIG-IP
Version 13.1.1.4
Build 0.0.4
Edition Point Release 4
Date Wed Jan 16 18:04:36 PST 2019
CONFIGURATION
Only connection timeout and inventory options are modified
OS / ENVIRONMENT
Ubuntu 19.10 server
SUMMARY
The bigip_lx_package module installs the AS3 package properly but randomly doesn't create the /var/config/rest/iapps/enable file and the Package Management LX menu is then missing in the GUI.
STEPS TO REPRODUCE
tasks:
- name: Install the AS3 package.
throttle: 1
bigip_lx_package:
provider: "{{ remoteprovider }}"
package: ../tmp/{{ as3package }}
state: "present"
delegate_to: localhost
- name: Enable the lx package extensions.
copy:
content: ""
dest: /var/config/rest/iapps/enable
force: no
EXPECTED RESULTS
The /var/config/rest/iapps/enable file is created and the Package Management LX menu item is available in GUI.
ACTUAL RESULTS
Running the playbook above against 8 target devices results in only 4 of them having the file installed via the bigip_lx_package module, remaining 4 are missing the file and it gets installed with the additional copy task.
For the devices where the module doesn't create the file, Ansible reports the AS3 as already installed (task has status ok, no changes).
TASK [Install the AS3 package.] *******************************************************************************************************************************************
changed: [ap-cn-1a-f511-01 -> localhost]
changed: [ap-cn-1a-f511-02 -> localhost]
changed: [ap-cn-1a-f511-03 -> localhost]
changed: [ap-cn-1a-f511-mgmt -> localhost]
ok: [ap-cn-1b-f511-01 -> localhost]
ok: [ap-cn-1b-f511-02 -> localhost]
ok: [ap-cn-1b-f511-03 -> localhost]
ok: [ap-cn-1b-f511-mgmt -> localhost]
TASK [Enable the lx package extensions.] **********************************************************************************************************************************
ok: [ap-cn-1a-f511-02]
ok: [ap-cn-1a-f511-01]
ok: [ap-cn-1a-f511-mgmt]
ok: [ap-cn-1a-f511-03]
changed: [ap-cn-1b-f511-01]
changed: [ap-cn-1b-f511-02]
changed: [ap-cn-1b-f511-03]
changed: [ap-cn-1b-f511-mgmt]
The module on enables the file if it has to take action for installing a package. Was AS3 installed on the B boxes prior to the module running? If so, is the request here that the module always enable the file even if its not installing a package?
AS3 was not installed prior to the module running. But, the target devices shown in the example are in HA sync-failover device group setup (4 pairs). It looks like when the module installs AS3 on the first member of such group, it is automatically installed on the remaining member, but the enable file is not created there, so the GUI menu item for AS3 is missing.
So, yes, if you can confirm this is the intended behavior (automatic installation within device-group), then the module should also check whether AS3 is installed and if yes, then check whether the enable file exists, and if not, create it. Even if the module did not install AS3 itself.
I hope it makes sense..
@focrensh Is anything required from me to provide? Just noticed the awaiting-user-action tag..
Currently I am not able to remove the tag but @trinaths should be able to assist & confirm. Since it is not installing directly on the 2nd machine, it seems likely that the enable file is not moving over. I know that in later TMOS versions you dont have to add that file for the GUI to show the section.
@focrensh @trinaths Thanks for the response. You're correct about the change in the later TMOS, and we have since upgraded to v15.1.3 and so this issue is no longer relevant for us. I will leave it up to you as to how you want to proceed here but I will not be able to provide any more updates here as I have no way to test/validate.. Thanks again for looking into it.
