5 LSMS Release 13.5.x Resolved and Known Bugs
This chapter lists the resolved and known bugs for LSMS release 13.5.x.
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 build:
- LSMS 13.5.1.2.0-135.24.0
- LSMS 13.5.1.1.0-135.21.0
- LSMS 13.5.1.0.0-135.18.0
- LSMS 13.5.1.0.0-135.16.0
- LSMS 13.5.0.0.0-135.11.0
Note:
Resolved bugs are sorted in ascending order by severity and then by bug number.Table 5-1 LSMS Release 13.5.1.2.0-135.24.0 Resolved Bugs (April 2024)
| Bug Number | SR | Severity | Title | Customer Impact |
|---|---|---|---|---|
| 36158175 | N | 4 | Update MySQL to 5.7.44 | |
| 36213714 | N | 4 | Update Perl-PAR package to 1.019 | |
| 36213915 | N | 4 | Update Perl-PAR-Packer package to 1.061 | |
| 36312522 | N | 4 | TPD update |
Table 5-2 LSMS Release 13.5.1.1.0-135.21.0 Resolved Bugs (September 2023)
| Bug Number | SR | Severity | Title | Customer Impact |
|---|---|---|---|---|
| 35661350 | 4 | LSMS MR 13.5.1.1:Update TPD | ||
| 35661359 | 4 | LSMS MR 13.5.1.1: Update third party packages | ||
| 35712726 | 4 | Update Xerces-j Tar File | ||
| 35781286 | 4 | Update MySQL to 5.7.43 |
Table 5-3 LSMS Release 13.5.1.0.0-135.18.0 Resolved Bugs (June 2022)
| Bug Number | SR | Severity | Title | Customer Impact |
|---|---|---|---|---|
| 34192699 | 3 | Fix StartNode Issue After Upgrade On Secondary Node |
Table 5-4 LSMS Release 13.5.1.0.0-135.16.0 Resolved Bugs (December 2021)
| Bug Number | SR | Severity | Title | Customer Impact |
|---|---|---|---|---|
| 33199554 | 3 | Upgrade Flexera FlexNet Publisher package to take care of issue reported | ||
| 33530948 | 3 | Revert DSGRT rpm package in LSMS | ||
| 33429463 | 4 | Update TPD to latest available version | ||
| 33597976 | 4 | Update MySQL to 5.7.36 in Query Server |
Table 5-5 LSMS Release 13.5.0.0.0-135.11.0 Resolved Bugs (July 2021)
| Bug Number | SR | Severity | Title | Customer Impact |
|---|---|---|---|---|
| 31775118 | Y | 3 | npacagent will not stay up and stopped by user | The customer is unable to receive new updates from the NPAC while the region continues to restart. |
| 32504126 | Y | 3 | Blank lsms.jnlp file on LSMS | Customer is unable to administer the LSMS from the LSMS GUI. |
| 32593761 | Y | 3 | Sentry status view shows Eagle regions associated with NPAC , when regions have been stopped. | Customer does not see correct status in output of sentry status command. |
| 28829054 | 4 | LSMS 13.3.1_MR: Unexpected errors observed on starting SNMP services. | ||
| 31504002 | 4 | LSMS-13.4.1: Issue with Query Results from NPAC on LSMS GUI under NPAC Tab | ||
| 31946922 | 4 | uplift ACE open source software to latest version | ||
| 32282130 | 4 | Uplift 3rd party perl components for LSMS | ||
| 32282136 | 4 | Uplift 3rd party Xerces components for LSMS | ||
| 32439448 | 4 | Support 756M LNPDB in LSMS | ||
| 32535687 | 4 | Update number of backups that can stored on NAS | ||
| 32599692 | Y | 4 | Upgrade TMN DSG package | |
| 32928576 | 4 | Restrict mysql to use only TLS 1.2v for connection | ||
| 32969186 | 4 | Upgrade TPD to latest release of 7.8 in LSMS | ||
| 32972764 | 4 | Update xerces jar to latest available | ||
| 32979510 | 4 | Update Mysql To 5.7.34 | ||
| 33008424 | 4 | Update Mysql To 5.7.34 In LSMS Query Server |
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-6 LSMS Release 13.5.x Customer Known Bugs (April 2024)
| Bug Number | SR | Severity | Title | Customer Impact |
|---|---|---|---|---|
| 27156544 | 3 | LSMS13.3_FT:Unexpected error for module QS observed in syscheck. | Executing the syscheck command from the /root directory displays an error message in the output. | |
| 27525514 | 3 | Possible change in BDD File Compression | No impact to Customer Operations. | |
| 30536697 | 3 | LSMS_13.4:Default TT value is getting observed while sending different TT value on LSMS for different service names | No impact to customer operations. | |
| 32645547 | 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. | |
| 26545649 | 4 | For M-GET response ALTSPID xml tag should be NIL/NULL when data is not present | No impact to customer operations. | |
| 26576672 | 4 | LSMS13.2.1:Error must be thrown when VIP is updated to existing VIP of other EMS | No error is displayed when the VIP address is set to the IP address of another EMS system. | |
| 33143482 | Y | 4 | SR: Server Disk Space Shortage Error alarm | Customer must remove core files to free up space and to clear the alarm. |