Resolved and Known Bugs

5 Resolved and Known Bugs

This chapter lists the Resolved and Known Bugs for this release.

These bug 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.

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
1. product inoperability (total or partial outage),
2. a reduction in the capacity capability, that is, traffic/data handling capability, such that expected loads cannot be handled,
3. any loss of emergency capability (for example, emergency 911 calls), or
4. 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 lesser immediate or impending effect on product performance, customers and the customer's operation and revenue such as
1. reduction in product's capacity (but still able to handle the expected load),
2. any loss of administrative or maintenance visibility of the product and/or diagnostic capability,
3. repeated degradation of an essential component or function, or
4. 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:

1 - Critical
2 - Major
3 - Minor
4 - Minor, No Loss of Service

Resolved Bug Listing

This section lists bugs that are resolved in the following build:

ELAP 11.0.0.4.0-110.19.0
ELAP 11.0.0.3.0- 110.16.0
ELAP 11.0.0.2.0-110.11.0
ELAP 11.0.0.1.0-110.8.0
ELAP 11.0.0.0.0-110.4.0

The Resolved Bugs tables show an impact statement for Severity 1 and 2 Bugs as well as for Severity 3 Bugs that are associated with an SR.

Note:

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

Table 5-1 ELAP Release 11.0.0.4.0-110.19.0 Resolved Bugs (January 2026)

Bug #	SR	Sev	Title
38482828	N	3	Configurable MySQL Password in ELAP
38429603	N	4	Perl-DBD-MySQL update
38795105	N	4	TPD update to TPD.install-8.10.1.9.0_150.20.0-OracleLinux8.10-x86_64.iso

Table 5-2 ELAP Release 11.0.0.3.0-110.16.0 Resolved Bugs (September 2025)

Bug #	SR	Sev	Title	Customer Impact
37351503	Y	3	SR: /var/TKLC/elap/drbd/mysql full due to excessive warnings in mysqldapp.log	Customer loses ELAP functionality as process fails due to lack of disk space.
37458004	Y	3	ELAP Prov Process using excessive memory	Customer may experience an interruption of functionality and provisioning when the system crashes due to high CPU usage because of a memory leak.
36767316	N	4	Upgrade MySQL to 8.4
37397754	N	4	TPD uplift to 8.10.1.1.0 or later
37417187	N	4	Upgrade drbd-utilties to latest compatible version
37417191	N	4	Upgrade drbd-kernel to latest compatible version

Table 5-3 ELAP Release 11.0.0.2.0-110.11.0 Resolved Bugs (August 2024)

Bug #	SR	Sev	Title
35995062	Y	4	ELAP Compatibility with Windows 2019
36355643	N	4	Unknown command BANNER TERMINATE received from GS is observed in gsConect.logs continuously
36485651	N	4	script usr/TKLC/elap/bin/Euidb_migration.pl needs modification
36738948	N	4	Update TPD to the latest release

Table 5-4 ELAP Release 11.0.0.1.0-110.8.0 Resolved Bugs (April 2024)

Bug #	SR	Sev	Title
36220743	N	4	ELAP 11 MR: Enable TLSv1.2 to support required tlsv1.2 ciphers
36199771	N	4	ELAP 11 MR: Update MySql 8 to the latest
36221656	N	4	ELAP 11 MR: Update jquery to the latest version.
36221685	N	4	ELAP 11 MR: Update perl DBD and module scandeps packages to the latest version
36271173	N	4	ELAP 11 MR: Update ACE to 6.5.20
36371912	N	4	ELAP 11 MR: Remove deprecated ciphers reported in tlsgis
36413185	N	4	ELAP 11 MR: TPD update to 8.9.0.1.0_130.6.0

Table 5-5 ELAP Release 11.0.0.0.0-110.4.0 Resolved Bugs (January 2024)

Bug #	SR	Sev	Title
33369065	N	4	MySQL uplift from 5.7 to 8.0
34498751	N	4	Update to TPD 8.x
35249457	N	4	TLS V1.3 encryption
35564249	N	4	DRBD in TPD 8
35643867	N	4	Update the ELAP NTP code for chrony in TPD 8
35647616	N	4	ELAP UT: remove jcterm from ELAP