6 Resolved and Known Bugs
This chapter lists the resolved and known bugs for LSMS release 14.1.
These lists are distributed to customers with a new software release at the time of General Availability (GA) and are updated for each maintenance release.
6.1 Severity Definitions
The problem report sections in this document refer to bug severity levels. Definitions of these levels can be found in the publication, TL 9000 Quality Management System Measurement Handbook.
Problem Report: A report from a customer or on behalf of the customer concerning a product or process defect requesting an investigation of the issue and a resolution to remove the cause. The report may be issued via any medium.
Problem reports are systemic deficiencies with hardware, software, documentation, delivery, billing, invoicing, servicing, or any other process involved with the acquisition, operation, or performance of a product. An incident reported simply to request help to bring back the service or functionality to normal without the intent to investigate and provide a resolution to the cause of the incident is not a problem report.
-
- Critical: Conditions that severely affect the primary functionality
of the product and because of the business impact to the customer requires
non-stop immediate corrective action regardless of time of day, or day of
the week as viewed by a customer on discussion with the organization such
as:
- Product inoperability (total or partial outage),
- A reduction in the capacity capability, that is, traffic/data handling capability, such that expected loads cannot be handled,
- Any loss of emergency capability (for example, emergency 911 calls), or
- Safety hazard or risk of security breach.
- Major: Product is usable, but a condition exists that seriously
degrades the product operation, maintenance, or administration, etc., and
requires attention during pre-defined standard hours to resolve the
situation.
The urgency is less than in critical situations because of a less immediate or impending effect on product performance, customers, and the customer's operation and revenue such as:
- Reduction in product's capacity (but still able to handle the expected load),
- Any loss of administrative or maintenance visibility of the product and/or diagnostic capability,
- Repeated degradation of an essential component or function, or
- Degradation of the product's ability to provide any required notification of malfunction.
- Minor: Other problems of a lesser severity than “critical” or “major” such as conditions that have little or no impairment on the function of the system.
- Minor, No Loss of Service: Oracle severity beyond what is defined by
TL 9000.
The numbered severity levels in the tables below correspond to these definitions of 1–Critical, 2–Major, 3–Minor, 4–Minor, No Loss of Service.
- Critical: Conditions that severely affect the primary functionality
of the product and because of the business impact to the customer requires
non-stop immediate corrective action regardless of time of day, or day of
the week as viewed by a customer on discussion with the organization such
as:
6.2 Resolved Bug Listing
The tables in this section list bugs resolved in the following builds:
- LSMS 14.1.0.0.0-141.6.0
Note:
Resolved bugs are sorted in ascending order by severity and then by bug number.Table 6-1 LSMS Release 14.1.0.0.0-141.6.0 Resolved Bugs (October 2026)
| Bug Number | SR | Severity | Title | Customer Impact |
|---|---|---|---|---|
| 37236212 | Y | 3 | syscheck gives "WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version." | Customer will observe these warnings on CLI of LSMS. |
| 39737326 | Y | 3 | After reboot, the server becomes standby and login is not possible | Customer will not be able to access the server with newly created user. |
| 39811893 | Y | 3 | lsms agent core dumps when running NPAC region sync with TN Range | Customer will not be able to perform range resync to maintain data sync with the NPAC. |
| 39828958 | N | 3 | lnpGenAck and lnpVerifyAck core dump | |
| 37441632 | N | 4 | DIU Upgrade support in LSMS | |
| 38544203 | N | 4 | Implement UEK Kernel in LSMS | |
| 38724617 | Y | 4 | XML Parsing Failure During Query For Self SPID | Customer will not be able to query SPID if it contains special character. |
| 38813451 | N | 4 | LSMS 14.0.0.4.0: service TKLClsmsCleanup start command needs to be updated with systmectl command | |
| 39034005 | N | 4 | APPD introduction with LSMS 14.1 | |
| 39520004 | N | 4 | Update ACE version in LSMS | |
| 39564718 | N | 4 | Upgrade MySQL version to 8.4.9 in LSMS | |
| 39823773 | N | 4 | Upgrade java to version 25 in LSMS | |
| 40131718 | N | 4 | TPD uplift to 150.39 | |
| 40187668 | N | 4 | krb5-devel, krb5-libs and libkadm5 package uplift |
6.3 Customer Known Bug Listing
Please find below the known bugs and associated Customer Impact Statements. This information is provided for information purposes only.
Table 6-2 LSMS Release 14.1 Customer Known Bugs (October 2026)
| Bug Number | SR | Severity | Title | Customer Impact |
|---|---|---|---|---|
| 38631905 | N | 3 | Error Mate Node Not Standby Error Observed While Changing GUI User Password From GUI | Customer will not be able to change the password or log into the GUI. |
| 40125748 | Y | 3 | LSMS GUI : Delete Default GTT Using Alternate SPID Fails | Customer is unable to verify that the data has been successfully deleted. |