Existing Known Issues
- Last Updated: June 27, 2025
- LoadMaster
- Multi-Tenant LoadMaster
- Documentation
| LM-6752 |
Netconsole: If a Netconsole Host is specified in the Troubleshooting options when the system is
rebooted, the following messages appear on the system
console:
These messages indicate that the Netconsole functionality did not start up properly. The workaround is to restart Netconsole by removing and re-adding the Netconsole Host. Note that these messages only affect Netconsole and do not indicate any issue with other LoadMaster functionality. |
| PD-11718 | Characters allowed in the VNF name during creation are invalid when the name is modified. |
| PD-11679 | Users are unable to download the backup file using the RESTful API if Session Management is enabled. |
| PD-11678 | Some user permissions available for selection are not valid for a user on a Multi-Tenant LoadMaster. |
| PD-11500 | There is a limit to the VNF size of the maximum number of cores of a single CPU on a multi-core platform. For example, in a dual CPU system with 6 cores per CPU, the maximum size that can be configured for a single VNF is 6 cores. |
| PD-11458 | The operation of the AutoStart button for Instantiated VNFs could be made clearer. |
| PD-11327 | You cannot restore backup files on Multi-Tenant LoadMaster VNFs, if the VNFs are running version 7.1.35.x. |
| PD-10203 | Users cannot apply a WUI certificate using the RESTful API or WUI. |
| PD-10098 | The following error message appears if no local users are configured on the Multi-Tenant host WUI: '_RO_USERS: No such file or directory'. There is no functional impact relating to this error. |
| PD-9950 | High Availability (HA) on the Multi-Tenant LoadMaster does not work with LoadMaster VNF firmware versions LTS 7.1.35.x and V7.2.36.x. |