twpsyn / f5-upgrade

Upgrade F5 BigIP Devices using Ansible

Hi there

May I present to you my collection of scripts and oddities.

I am a network engineer based out of South Wales, UK. I spend a fair bit of time working with network kit, firewalls, load balancers, and other things from a number of different vendors.

Some of the repositories here are functional pieces of code where I have had a purpose and written something to fullfill that. Others are more like collections of experiments. I've sought to have reasonable readmes in them all to give an idea of what they are.

Standard disclaimer: these are personal repositories, nothing here represents views, opinions, or recommendations of my employer. Indeed nothing here is in any way related to them beyond germinating ideas in my head.

If you find anything of particular use you could buy me a coffee via Ko-fi, but that's in no way expected.

f5-upgrade's Issues

How does the new installed volume know to install the current configuration?

When you activate a boot location in the GUI you can select "Install Configuration->Yes-> Source Volume"

Otherwise the F5 will boot up with the default config. Where do you specify this?

Don't see it here:

- name: Group 1 Activate Image (Will Cause Reboot)
  bigip_software_install:
    provider: "{{ provider }}"
    image: "{{ new_image }}"
    state: activated
    volume: "{{ dest_boot_loc }}"
  any_errors_fatal: true

Issue with reboot_group

Error says reboot_group is undefinded. I have the reboot_group=1 in my inventory

[LANDEVLB7_107]
LANDEVLB7.dev.site reboot_group=1
LANDEVLB107.dev.site reboot_group=2

plabook host definition looks like this,

• hosts:
  - LANDEVLB7.dev.site
  - LANDEVLB107.dev.site

Fails at bigip_image_upload

Ansible version is 2.9.11, python version is 2.7.5.

The issue is when trying to upgrade from 13.1.3.0.0.6 to 14.1.2.6-0.0.2. The error I'm getting is "Failed to create resource" . I have confirmed the ios is in the directory my playbook is pointing at and the permissions for the file are the same as the 13.1.3.0.0.6. I'm not sure what else I can check.

The full traceback is:
WARNING: The below traceback may not be related to the actual failure.
File "/tmp/ansible_bigip_software_image_payload_AaiSxc/ansible_bigip_software_image_payload.zip/ansible/modules/network/f5/bigip_software_image.py", line 472, in main
File "/tmp/ansible_bigip_software_image_payload_AaiSxc/ansible_bigip_software_image_payload.zip/ansible/modules/network/f5/bigip_software_image.py", line 258, in exec_module
File "/tmp/ansible_bigip_software_image_payload_AaiSxc/ansible_bigip_software_image_payload.zip/ansible/modules/network/f5/bigip_software_image.py", line 281, in present
File "/tmp/ansible_bigip_software_image_payload_AaiSxc/ansible_bigip_software_image_payload.zip/ansible/modules/network/f5/bigip_software_image.py", line 388, in create
fatal: [JTCILBL5005.entmconn.site]: FAILED! => {
"changed": false,
"invocation": {
"module_args": {
"force": null,
"image": "/automation/ansible/playbooks/f5/files/BIGIP-14.1.2.6-0.0.2.iso",
"provider": {
"auth_provider": null,
"password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
"server": "xxxxxxxxxxxxxxx",
"server_port": 443,
"ssh_keyfile": null,
"timeout": 1800,
"transport": "rest",
"user": "xxxxxxx",
"validate_certs": false
},
"state": "present"
}
},
"msg": "Failed to create the resource."
}