Issues Resolved
- Last Updated: November 7, 2023
- LoadMaster
- LoadMaster GA
- Documentation
| PD-19882 | HTTP/2 URL Query Limitation: Fixed an issue (introduced in LMOS 7.2.55.0) that caused a limit of 4096 characters to be imposed upon the Query section of the URL. This issue has been fixed and there is now no limit on the URL query section. |
| PD-19822 | User Interface: When 2 or more network interfaces are configured for High Availability (HA) Mode health checks and 2 or more of the checks have failed, the Home Page may display random text in the status boxes. This bug has been fixed. |
| PD-19807 | Flowmon Collector Add-On: Fixed an issue that caused the add-on to fail to autostart after download and installation using the controls on the UI Network Telemetry page. |
| PD-19801 | Real Time Statistics: Fixed an issue that caused Cache Entries and Cache Memory to display very large arbitrary values when multiple services re enabled for caching. |
| PD-19668 | GEO: Disabled Clusters in UI: Fixed an issue that caused disabled clusters to be omitted from the UI under specific conditions. |
| PD-19663 | VLANs in UI: Fixed an issue that caused VLAN IDs to be corrupted on display. |
| PD-19661, PD-10586 | GEO: Disabled Clusters: In previous releases, responses were returned for disabled clusters in certain circumstances. GEO has been modified to no longer return responses for disabled clusters when the cluster is disabled and the "Disabled clusters are unavailable" option is turned on. |
| PD-19623 | WAF: Fixed a bug (introduced in 7.2.55) that caused Virtual Services to become unresponsive when WAF remote logging is enabled. |
| PD-19616 | Log Message Error Level: In previous releases, the message "kernel: L7: Intercept device not open" was set to the "Error" logging level. Since this message indicates that the WAF engine experienced an unexpected connection close and recovered, the log level has been reduced to 'informational'. |
| PD-19607 | Debugging: The ability to set process debug levels for sshd has been added to the System Administration > System Log Files > Debug Options > Enabled Extended Debug > Process Debug page. Logs appear in the system Warning Message File. These options should not be enabled on a production unit without the instruction and assistance of support. |
| PD-19584 | Health Checks: Fixed a bug that caused the server following health check functionality to fail to update the status of the following server when HTTP/1.1 is selected Service the check is taken used http/1.1 |
| PD-19570 | GEO: Fixed a bug (introduced in LMOS 7.2.55) where restarting GEO results in NXDOMAIN responses being returned intermittently for some FQDNS in cases where the AAAA record for the FQDN should have been returned. |
| PD-19507, PD-19509 | API: The ability to get, set, and remove the OCSP port value has been added to both the PowerShell and RESTful APIs. |
| PD-19502 | OIDC Authentication: Fixed a bug whereby token validation can be bypassed by under certain circumstances when the browser is refreshed. |
| PD-19496 | Stability: Fixed an internal error that caused an unexpected system panic and reboot when Virtual Service connections are dropped as new connection requests are being processed. |
| PD-19488 | Caching: Fixed an issue that caused expired cache entries to remain in the cache after the associated Virtual Service is stopped and restarted. |
| PD-19485 | GEO: Intermittent FQDN Resolution Failures: Fixed an internal issue that could cause intermittent FQDN resolution failures, with repeated retries resulting in a successful response. |
| PD-19376 | GEO: Fixed an issue (introduced in LMOS 7.2.55) that caused Site IPs to be incorrectly marked UP when DNS is restarted. |
| PD-19360 | Real Servers: Fixed a bug where adding a Virtual Service (VS) with 1024 Real Servers (RSs) prevents duplicating that VS using the same 1024 RSs. |
| PD-19226 | GEO Partner Stops Responding After Reboot: Fixed issues that could cause GEO to stop responding after a reboot, producing a "Cannot create BIND" log message and a segmentation fault. This was due to an internal operation (such as a partner synchronization) occurring immediately after the reboot and before all necessary resources for the attempted operation were available. |
| PD-19216 | WAF: Fixed an internal error that caused the log message "Cannot open kernel for [VIP], Child PID exited" to appear and WAF to stop functioning. |
| PD-19194 | AWS: It is not possible to downgrade a fresh install of LMOS 7.2.55.0 in the AWS Cloud to a earlier LMOS release. This issue has been fixed. |
| PD-19180 | GEO: When GEO is running in Cloud High Availability (HA) Mode, DNS remains running on the standby unit as well as the active unit. This issue has been fixed. |
| PD-19175 | ESP Logging: Previously, ESP Logs was printing domain/realm name in domain info at logon and session kill events. Now, ESP user logs prints SSO domain configuration name in domain info instead of domain/realm name. |
| PD-19168 | ESP Logging: Previously, L7 "Logged on" event log was missing for successful login via certificate in the ESP user log file. Now, L7 "logged on" event log generated upon successful login via certificate. |
| PD-19131 | Virtual Services: Fixed a bug where a Virtual Service (VS) with an Alternate IP Address configured cannot communicate with a Real Server that is not using the same port configured for the VS. |
| PD-19128 | Real Servers Are Local Option: In previous releases, if the Real Servers Are Local option is enabled and a Virtual Service is configured for Layer 7, communication with local servers is broken if the VS has no content rules defined. This issue has been fixed. |
| PD-19118 | HTTP/2 File Access: Customers reported HTTP/2 failures when accessing files using either a MAC client using Safari or Linux clients using the curl command, where the real server reports a broken pipe. The workaround was to disable HTTP/2. This bug has been fixed. |
| PD-19095 | Content Rule UI: When you configure a content rule, if the name of the rule is not valid, then the page will refresh and all previous input is lost. This issue is fixed. |
| PD-18974 | WAF UI: Removed the password length restrictions on the Web Application Firewall > Export Logs page. |
| PD-18968 | Multi-Tenancy: The "Reboot on link failure option" functionality does not work when LMOS is used as a VNF in a Multi-Tenancy (MT) configuration and so has been removed from the UI when LMOS 7.2.56.0 is used in an MT configuration. |
| PD-18830 | Single Sign-On: Fixed an intermittent internal issue that caused all SSO sessions to be terminated. |
| PD-18789 | SNMP: Fixed a bug where no SNMP traps are generated when only SNMP Trap Sink1 is configured. |
| PD-18736 | Single Sign-On: Fixed an internal issue where the cookie domain is being erroneously changed during response processing, leading to a login loop. |
| PD-18693 | WAF: Fixed issues that could cause a segmentation fault/reboot when the WAF configuration is modified while traffic is being processed by the WAF engine. |
| PD-18610 | LDAP: Fixed an API error where an LDAP endpoint is added despite the failure to set one or more options. |
| PD-18601 | Statistics: Some network interfaces are not displayed when there are one or more bonded interfaces. This issue has been fixed. |
| PD-18470 | HTTP/2: Fixed a bug that caused cookie persistence to fail with HTTP/2 enabled. |
| PD-16998 | LDAP UI Login: Fixed a bug that caused UI authentication to fail group checks. |
| PD-15859 | L7 Health Checks: When an AD DS server stops responding to authentication requests causing LDAP health check failures, it's possible that unrelated HTTPS health checks could also fail. This internal issue has been fixed. |