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.
5.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:
5.2 Resolved Bug Listing
The tables in this section list bugs resolved in the following builds:
- 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.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-2 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-3 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 |
5.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 5-4 LSMS Release 14.0 Customer Known Bugs (August 2024)
| 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. |