LM-2566 Layer 7 Persistence: Enabling the Always Check Persist option in a Virtual Service breaks server cookie persistence for that Virtual Service. The only workaround is to disable Always Check Persist.
LM-1865 WAF Audit Logs: No output is returned when selecting a date range.
LM-1809, LM-1800 Azure VLM: Disk usage in the logging partition (/var/log/) may increase because of files used by the Azure agent (waagent) process that are never removed. Users that experience this issue will need to call support for a workaround.
LM-1723 GEO Partnering: There is a small window of time during a partner sync where concurrent changes on the partners may not be reflected on both systems. The only workaround is to repeat the modification.
LM-1557 Single Sign On: A segmentation fault in the SSO management process can occur under high load resulting in users being logged out. Messages like the following will be seen in the log:

kernel ssomgr[46119]: segfault at <num> ip <num> sp <num> error 4

kernel L7: verify_user: Auth request failed for id 0
LM-1527 GEO Cluster Checks: GEO cluster checks against LoadMasters configured in Clustering mode do not work.
LM-1412 API stats command: On a unit in Clustering mode, the up/down status value returned via the stats command may be different (and incorrect) compared to the status returned by listvs or vstotals.
LM-1373 Let's Encrypt ACME Certificates: After certificate renewal, the old certificate may still be in use by the Virtual Service. The workarounds are to either:
  • Remove and re-add the Virtual Service certificate
  • Disable and re-enable the Virtual Service
LM-1342 Kubernetes Ingress Controller: Ingress may stop working if the default admin gateway is modified. The workaround is to return the setting to the old gateway address.
LM-1325 Let's Encrypt UI: The UI for requesting a new certificate may not fully load with a large number of Virtual Services configured. The workaround is to use the API.