Last Modified: Feb 11, 2025
Affected Product(s):
BIG_IP_NEXT(CM) MA-CM
Known Affected Versions:
20.2.0, 20.2.1
Opened: Jul 10, 2024 Severity: 2-Critical
The BIG-IP Next Central Manager UI sends an API request to the BIG-IP Next instance to retrieve the file ID of the uploaded upgrade bundle. If the API request encounters any file entries without a set 'fileName' attribute, the UI will display the following error message: "Failed to initialize upgrade process: Failed to initialize upgrade form: Failed to fetch instance files: Cannot read properties of undefined (reading 'endsWith')."
The BIG-IP Next Central Manager UI for initiating the BIG-IP Next instance upgrade will fail to load properly.
BIG-IP Next instance upgrade attempted via the BIG-IP Next Central Manager UI when files with no 'fileName' attribute exist on the BIG-IP Next instance.
The following steps must be followed using the BIG-IP Next Central Manager API: 1. Use the 'POST /api/login' endpoint to obtain a token. 2. Use the 'GET api/v1/spaces/default/instances' endpoint to identify the instance ID exhibiting this issue. 3. Use the 'GET api/device/v1/proxy/<instance ID>?path=/files' endpoint to identify the list of files for the instance that do not contain a 'fileName' attribute. 4. Use the 'DELETE api/device/v1/proxy/<instance ID>?path=/files/<file ID>' endpoint to delete each identified file.
None