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.

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

5.2 Resolved Bug Listing

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

ELAP 10.2.1.2.0-102.24.0
ELAP 10.2.1.1.0-102.22.0
ELAP 10.2.1.0.0-102.20.0
ELAP 10.2.0.0.0-102.12.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 10.2.1.2.0-102.24.0 Resolved Bugs (March 2024)

Bug #	SR	Sev	Title	Customer Impact
36185853		4	TPD, MySQL update
36321967		4	TPD update

Table 5-2 ELAP Release 10.2.1.1.0-102.22.0 Resolved Bugs (September 2023)

Bug #	SR	Sev	Title	Customer Impact
35675310		4	ELAP 10.2.1.1 MR: Update TPD
35675680		4	Update mysql, perl-Module-ScanDeps, remove jcterm

Table 5-3 ELAP Release 10.2.1.0.0-102.20.0 Resolved Bugs (November 2021)

Bug #	Sev	Title
33056882	3	ELAP10.2.0_FT:Select mate gives iFrame error when clicked from ELAP GUI.
33056916	3	ELAP10.2.0_FT:Access Forbidden observed for viewRtdbStatus.cgi and for reboot MPS on ELAP GUI.
32380304	4	Support ELAP in new chromium based Microsoft Edge
32488099	4	ELAP - Managing deprecation of Java Applet plugin support from Browser
33429233	4	Update Mysql to latest available version
33429513	4	Update TPD to latest available release

Table 5-4 ELAP Release 10.2.0.0.0-102.12.0 Resolved Bugs (July 2021)

Bug #	Sev	Title
31097656	3	ELAP10.1.5_MR:Copy From Remote shows no RTDB files during first SSH attempt to Remote server.
32547383	3	Support EAGLE backward compatibility with ELAP 10.1
30792560	4	ELAP10.1.5_MR:Unwanted logs observed in /var/log/cron file.
30876421	4	Upgrade DRBD package
31217601	4	Upgrade ACE package to the latest available
32297664	4	Upgrade 3rd party perl packages to latest version in ELAP 10.2
32384999	4	Support greater than 504M LNPDB in ELAP
32969222	4	Update TPD to latest release of 7.8 in ELAP
32980838	4	Update Mysql to 5.7.34

5.3 Customer Known Bug Listing

The following table lists known bugs in this release:

Table 5-5 ELAP Release 10.2 Customer Known Bugs (March 2024)

Bug #	Sev	Title	Customer Impact
29543267	3	ELAP10.1.4_MR: On ELAP B GUI,Connect to MMI Port, java error was observed and the window did not open.	Users will not be able to log into the EAGLE via the ELAP GUI. They will need to open EAGLE terminal directly.
29836543	3	ELAP_10.1.4:SCCP cards not able to load data when ELAP switchover happens.	After switchover, some of the EAGLE cards will stop taking updates from ELAP. Work Around: Initialize the cards that are not taking updates from ELAP and are in SYN_RECEIVED state.
33569317	4	ELAP10.2.1: core.httpd along with .bt is observed	Customer might see space and core related alarms on GUI.
33569341	4	ELAP10.2.1_FT:URL moved permanently to a new address is observed when ELAP GUI is opened in Chromium based Microsoft Edge	GUI freezes when this error is observed and user will have to refresh the URL to access GUI again. Work Around: Refresh the GUI and login again.