Last Modified: Aug 23, 2023
Known Affected Versions:
16.0.0, 22.214.171.124, 16.0.1, 126.96.36.199, 188.8.131.52, 16.1.0, 16.1.1, 16.1.2, 184.108.40.206, 220.127.116.11, 16.1.3, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 17.0.0, 220.127.116.11, 18.104.22.168
Opened: May 31, 2022 Severity: 3-Major
-- The tmsh utility may return an error when listing analytics configuration. -- TMOS installations may fail and return an error. -- Saving new UCS archives may fail and return an error. In all cases, the error is similar to the following example: TSocket::open() getaddrinfo() <Host: 127.3.0.2 Port: 9090>Name or service not known std exception: (Could not resolve host for client socket.), exiting...
The operation you were attempting fails and an error is returned.
-- Multi-blade VIPRION system (either metal or in the form of a vCMP guest). -- AVR is provisioned. -- At least one AVR scheduled-report is present in the configuration. -- An action such as listing the config, saving a UCS archive, performing a TMOS installation, etc. is performed on a secondary blade.
The only workaround consists in removing all AVR scheduled-reports, performing the intended task, and then re-defining the AVR scheduled-reports as necessary. This is of course disruptive and may not be indicated for your site. If you require an Engineering Hotfix for this issue, please contact F5 Support.
The presence of AVR scheduled-reports in the configuration no longer interferes with administrative tasks.