5 Resolved and Known Bugs

This chapter lists the resolved and known bugs for LSMS release 14.0.

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.

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.

    1. 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.
    2. 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.
    3. 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.
    4. 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.

Resolved Bug Listing

The tables in this section list bugs resolved in the following builds:

  • LSMS 14.0.0.4.0-140.26.0
  • LSMS 14.0.0.3.0- 140.22.0
  • LSMS 14.0.0.2.0-140.14.0
  • LSMS 14.0.0.1.0-140.10.0
  • LSMS 14.0.0.0.0-140.7.0

Note:

Resolved bugs are sorted in ascending order by severity and then by bug number.

Table 5-1 LSMS Release 14.0.0.4.0-140.26.0 Resolved Bugs (January 2026)

Bug Number SR Severity Title Customer Impact
38262402 N 2 Memory leak issue in npacagent Customer is unable to receive updates from NPAC until system is recovered.
37929663 N 3 LSMS 14.0.3: LSMS Migration document requires some modification  
38105634 N 3 LSMS 14.0.3: Migration Doc procedure 21 requires changes  
38105944 N 3 LSMS 14.0.3: Newly identified key exchange procedure between LSMS and ELAP requires changes  
38109521 N 3 LSMS 14.0: Query Server Installation Guide requires changes  
38187721 N 3 Date Synchronization not working properly in Initial Configuration  
38344557 N 3 Getting error in creating replication user  
38482905 N 3 Configurable MySQL password in LSMS  
37685153 N 4 Doc Update for Passwords should be changed on first-time use by customer  
37960759 N 4 Blocking the ability to ssh as root between servers  
38132285 N 4 LSMS 14.0.3: Migration documents need modification w.r.t to Procedure 6, Backup LSMS DB  
38177352 N 4 LSMS 14.0: Logs show error even when Servdi backup is successful  
38417424 N 4 Update perl-PAR, perl-PAR-Packer  
38428670 N 4 Version update for perl-DBD-MySQL  
38783248 N 4 Uplift TPD to 8.10.1.9.0_150.20.0  

Table 5-2 LSMS Release 14.0.0.3.0-140.22.0 Resolved Bugs (September 2025)

Bug Number SR Severity Title Customer Impact
36998040 N 3 LSMS14.0.2: $ special character is not allowed in Auth and Priv Protocol passwords on LSMS  
37285805 Y 3 Log Filled With mysql_native_password Messages Customer may lose functionality when the disk space is exhausted.
37576902 Y 3 LSMS / NAS not alarming Customer may not be able to restore data as the latest backups were not successful and available.
37701694 Y 3 LSMS 14.0 /usr/bin/sensors-e5appx is World Write -rwxrwxrwx Customer will see permissions flagged as an issue in scans.
37713683 Y 3 World Writeable Permission For File sensor-e5appx Customer will see permissions flagged as an issue in scans.
36022206 N 4 Web Server Misconfiguration: Unprotected File  
36767350 N 4 Upgrade MySQL to 8.4  
37258052 Y 4 LSMS replication and bin log issue - DB Proc Mon Err Customer may be misled as to the health of the system due to false alarms.
37441651 N 4 TPD uplift to 8.10.1.1.0 or later  
37447651 N 4 Upgrade Perl Module-scandeps to 1.37 or later in LSMS  
37447834 N 4 Update ACE to latest stable version in LSMS  
37472769 N 4 Replace Xerces-C with libxml in LSMS  
37923680 N 4 LSMS Increase MAX_SPIDS from 512 to support additional SPID/LRN/Services  

Table 5-3 LSMS Release 14.0.0.2.0-140.14.0 Resolved Bugs (August 2024)

Bug Number SR Severity Title Customer Impact
36641207 N 3 Automatic/Manual Resync on EMS Not Working From Primary LSMS  
36641311 N 3 Unable to edit SNMPv3 User from User configuration Menu  
36641424 N 3 The Group Configuration menu becomes unresponsive (freezes) when it is accessed after creating more than one user  

Table 5-4 LSMS Release 14.0.0.1.0-140.10.0 Resolved Bugs (May 2024)

Bug Number SR Severity Title Customer Impact
34624155 Y 3 TKLCha/comcol process creates /tmp/re_state directory Prevents customer from becoming compliant with CSO security scans.
36280621 N 4 Curses UI changes  
36424899 N 4 Update Perl-PAR package to 1.019  
36424926 N 4 Update Xerces-c to 3.2.5  
36424928 N 4 Update Perl-PAR-Packer package to 1.061  
36444720 N 4 perl-DBD-mysql update  

Table 5-5 LSMS Release 14.0.0.0.0-140.7.0 Resolved Bugs (January 2024)

Bug Number SR Severity Title Customer Impact
33143482 Y 4 SR: Server Disk Space Shortage Error alarm  
33369053 N 4 MySQL uplift from 5.7 to 8.0  
34273802 Y 4 LSMS 13.5.0 User Password Change via the GUI Generates Core Dump  
34498271 N 4 Update to TPD 8.x  
35193797 Y 4 Non-Unique Hostnames for LSMS Servers  
35345078 N 4 TLS v1.3 encryption in LSMS  
35677192 N 4 LSMS NAS on TPD 8  
35677225 N 4 LSMS QS on Oracle Linux8 and MySQL 8  
35677234 N 4 TMN Toolkit, DSG, DSGRT from Artifex for OL8  
35948608 N 4 Update MySQL to 8.0.33  

Customer Known Bug Listing

Please find below the known bugs and associated Customer Impact Statements. This information is provided for information purposes only.

Table 5-6 LSMS Release 14.0 Customer Known Bugs (January 2026)

Bug Number SR Severity Title Customer Impact
32645547 N 3 LSMS13.5: Alarm LSMS-NAS-MIB::volumeNearlyFull is not getting cleared A false alarm will be displayed on the LSMS that a volume is full on the NAS.
35928261 Y 3 LSMS lsmssec:DB Repl Err - Bin logs out of sync Issues cause secondary LSMS to report bin logs error, which prevents database replication between the Active and Standby LSMS servers.