6 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.

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
    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

6.2 Resolved Bug Listing

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

  • ELAP 11.1.0.0.0-111.6.0

The Resolved Bugs table shows 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 6-1 ELAP Release 11.1 Resolved Bugs (October 2026)

Bug # SR Sev Title Customer Impact
39243596 N 3 /var/TKLC/elap/drbd/mysql 100% due to repl logs  
37441625 N 4 Introduction of DIU Upgrade Support in ELAP  
38544195 N 4 Implement UEK Kernel in ELAP  
39114321 N 4 APPD introduction with ELAP 11.1  
39114324 N 4 Add Cisco Switch Configuration option  
39432862 N 4 Updating ACE to 8.0.5  
39564591 N 4 Upgrade MySQL RPMS to 8.4.9  
39622677 N 4 Add switchconfig menu support to ELAP  
39677863 N 4 Replace Overlib.js  
39729932 N 4 Upgrading jquery.js  
39828730 N 4 Increase DSM Timeout from 5sec to 10sec  
40131810 N 4 TPD uplift to 8.10.1.16.0_150.39.0  

6.3 Customer Known Bug Listing

ELAP Release 11.1 Customer Known Bugs

There are no known bugs in this release.