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

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

7.2 Resolved Bug List

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.

EPAP Release 17.1.0.0.0-170.34.0

The following table lists the bugs resolved in EPAP build 17.1.0.0.0-170.34.0:

Table 7-1 EPAP Release 17.1.0.0.0-170.34.0 Resolved Bugs (June 2025)

Bug SR Severity Title Customer Impact
37695351 N 4 510M MNP support  

7.3 Customer Known Bug List

EPAP Release 17.1 Customer Known Bugs

The following table lists the known bugs and associated customer impact statements.

Table 7-2 EPAP Release 17.1 Customer Known Bugs (June 2025)

Bug # SR Sev Title Customer Impact
27722102 N 3 EPAP16.2_FOA:Disaster Recovery not working on a Sync Redundant setup. No impact to customer operations.
32319917 Y 3 SR- Frequent switchover in EPAP state observed in EPAP Customers lose functionality to update Eagle which may impact calls.
37218161 Y 3 SR: Remote Proxy PDBA Level stale There is no impact to the customer other than viewing inconsistent proxy information.
37549366 Y 3 LSBLSET -2 seen in file when exporting PDBA Customer is confused as to the validity of the data when it sees the value in the export file.
37807944 N 3 EPAP17.0.6 - Eagle not getting synced and EPAP status toggle at the time eagle card reboot There is little impact except for unclear status when the temporary change in the status of the active RTDB toggles while the Eagle card is reloading.
25644469 N 4 Dangling asd in pdb.asd table When multiple DNs are added at the same time from the "Add DN" screen in the GUI and the main DN is then deleted, the remaining DNs from the prior add command will have an invalid ASD value.
28486363 N 4 EPAP16.3_ST:Data replicated to standby PDB when ROP is run with noStandby. ROP data is always replicated to the standby node if the gmt command is ever executed without the --noStandby option.
28595734 N 4 Provide Read Access to OTHER users also for certain log files Certain log files are only viewable by the epapdev and root users. Other users will not be able to read these files.
36473817 Y 4 gsconnect.pl CPU usage 135% May be some confusion as CPU usage can exceed 100% on multi-core system.
37739295 N 4 Delete and Ent are not returning in logs (pdba.cmd) for PROV BL (PDBA>>ManageData>>PROV BL >> Add)) Missing entry for Add and Delete event in the PDBA log file. No impact to customer operations.
37739366 N 4 "Server Kernel Dump File Detected" alarm not displayed for syscheck after (echo c > /proc/sysrq-trigger') Alarm related to Server Kernel Dump File will not be displayed on the GUI and syscheck output.
37759948 N 4 EPAP17.0.6: Server Application Process Error is observed on Non-Prov nodes Syscheck may show failures/minor alarm for server application process error. This is a false alarm which has no impact to customer operations.