Open caliraftdude opened 11 months ago
Hi @caliraftdude,
Thanks for reporting this issue. We will review it and as a workaround you can add bigip_command in your playbook to run "tmsh reboot volume HDX.Y"
Yup - that's precisely what I am doing as a workaround. Let me know if you need any additional information.
Hi @caliraftdude,
Thanks for the feedback. As there is a workaround and we are focusing new F5 platform and OS so there will be no fix to this issue.
how long it will take to fix the issue?
Hi @f5killer,
As there is a workaround and we are focusing new F5 platform and OS so there will be no fix to this issue.
COMPONENT NAME
f5networks.f5_modules.bigip_software_install
Environment
ANSIBLE VERSION
BIGIP VERSION
CONFIGURATION
cat ansible.cfg [defaults] host_key_checking = false
OS / ENVIRONMENT
uname -a Linux ansible-mgr 6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
SUMMARY
bigip_software_install completes the task and indicates a successful completion:
ok: [f5 -> localhost] => { "changed": false, "invocation": { "module_args": { "block_device_image": null, "image": "BIGIP-15.1.10.2-0.0.2.iso", "provider": { "auth_provider": null, "no_f5_teem": false, "password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER", "server": "10.1.1.151", "server_port": 443, "timeout": null, "transport": "rest", "user": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER", "validate_certs": false }, "state": "activated", "type": "standard", "volume": "HD1.2" } } }
However, when reviewing the system: show sys software status
Sys::Software Status Volume Product Version Build Active Status
HD1.1 BIG-IP 14.1.4.2 0.0.5 yes complete HD1.2 BIG-IP 15.1.10.2 0.0.2 no complete
and the system does NOT reboot.
STEPS TO REPRODUCE
EXPECTED RESULTS
From the documentation: When installed, ensures the software is installed on the volume and the volume is set to be booted from. The device is not rebooted into the new software.
When activated, performs the same operation as installed, but the system is rebooted to the new software. Choices: "activated" ← (default) "installed"
I have tried both installed and activated as options and neither activates the volume, and as stated before 'activated' doesn't reboot the system into the installed volume. I have also tried, in both cases, to delete HD1.2 and leave the volume in tact. Same results with either initial conditions. Additionally, no failure conditions or errors are reported and the playbook thinks it has performed the actions correctly.
ACTUAL RESULTS