4 Resolved and Known Bugs
This chapter lists the resolved and known bugs for Oracle Communications Network Analytics Data Director (OCNADD) Release 22.0.0 .
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.
Severity Definitions
Service requests for supported Oracle programs may be submitted by you online through Oracle’s web-based customer support systems or by telephone. The service request severity level is selected by you and Oracle and should be based on the severity definitions specified below.
Severity 1
Your production use of the supported programs is stopped or so severely impacted that you cannot reasonably continue work. You experience a complete loss of service. The operation is mission critical to the business and the situation is an emergency. A Severity 1 service request has one or more of the following characteristics:
- Data corrupted.
- A critical documented function is not available.
- System hangs indefinitely, causing unacceptable or indefinite delays for resources or response.
- System crashes, and crashes repeatedly after restart attempts.
Reasonable efforts will be made to respond to Severity 1 service requests within one hour. For response efforts associated with Oracle Communications Network Software Premier Support and Oracle Communications Network Software Support & Sustaining Support, please see the Oracle Communications Network Premier & Sustaining Support and Oracle Communications Network Software Support & Sustaining Support sections above.
Except as otherwise specified, Oracle provides 24 hour support for Severity 1 service requests for supported programs (OSS will work 24x7 until the issue is resolved) when you remain actively engaged with OSS working toward resolution of your Severity 1 service request. You must provide OSS with a contact during this 24x7 period, either on site or by phone, to assist with data gathering, testing, and applying fixes. You are requested to propose this severity classification with great care, so that valid Severity 1 situations obtain the necessary resource allocation from Oracle.
Severity 2
You experience a severe loss of service. Important features are unavailable with no acceptable workaround; however, operations can continue in a restricted fashion.
Severity 3
You experience a minor loss of service. The impact is an inconvenience, which may require a workaround to restore functionality.
Severity 4
You request information, an enhancement, or documentation clarification regarding your software but there is no impact on the operation of the software. You experience no loss of service. The result does not impede the operation of a system.
Known Bug List
The following table lists the known bugs for OCNADD Release 22.0.0.
Table 4-1 Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 34786365 | OCNADD logs Error logs as INFO for Configuration service when it is sending Notification to Adapter | The logs are printed as INFO instead of ERROR in this scenario. | No system impact | 3 | 22.0.0 |
| 34770614 | EGW instances keep increasing on every re-start | De-registration does not happen when a POD gets restarted. | No system impact | 3 | 22.0.0 |
| 34740421 | OCNADD logging Error logs as INFO for Adapter and EGW when 3rd Party consumer is not reachable or is down | The logs are being printed as INFO instead of ERROR in this particular scenario. | No system impact | 3 | 22.0.0 |
| 34740391 | OCNADD GUI not validating endpoints | The URI endpoints for third-party consumer application is not getting validated. For example, extra spaces and HTTPs is used in case of No-TLS. | Missing validation can result in an incorrect configuration, however, there is no impact when the correct information is provided during the configurations. | 3 | 22.0.0 |
| 34716751 | Heart Beat logs are not showing up (verified on Alarm Service) | The heartbeat logs are printed only in Debug mode. | No system impact | 3 | 22.0.0 |
| 34714292 | Performance Execution: Gateway POD has restarted with IllegalReferenceCountException exception during 39K MPS | When there are frequent errors reported from a third-party application at high traffic rate, then these "IllegalReferenceCountException" exceptions could occur, due to which there may be EGW pod restart. | If any EGW POD goes out of memory, then liveliness checks will re-spawn the new pod instantly, and the user may get an alert of POD restart, however, there will not be any message loss. | 3 | 22.0.0 |
| 34712921 | The x-axis is not giving correct interval | In the dashboard section of GUI, the Bar graph does not display correct intervals on the x-axis, it shows multiple zeros and ones. | The user is not be able to see the correct x-axis values. | 3 | 22.0.0 |
| 34793856 | Alarms reporting such as Max replica crossed 90% for a service such as adminservice when replica is 1 | The alarm "Max Replica crossed 90% for a service" is raised even though the replica count is one. The alarm should not be raised for services that do not require more than one replica count. | No system impact. | 4 | 22.0.0 |
| 34785610 | Connection status not changing to Inactive in GUI | The connection status does not change back to an Inactive state, even when directed to the random(wrong) endpoint of a third-party application. | When the configured endpoint is not valid, the incorrect connection status of the third-party feed is shown, however, there is no impact when the correct information is provided during the configurations. | 4 | 22.0.0 |
| 34742422 | Use OPTIONS request in Retry Mechanism of Adapter | Consumer Adapter's Retry Mechanism needs to update to use HTTP OPTIONS method instead of the existing implementation of periodic retrying with few messages. This scenario is observed only when the circuit breaker is enabled in OCNADD. The retry mechanism sends a message periodically to check the status of the endpoints, this will continue until the endpoint status is up and running. | Few of the messages will be delivered again to the endpoint, however, there will not be any data loss in this scenario. | 4 | 22.0.0 |
| 34684038 | Not able to change logging type to JSON | The logs are not printed in JSON format. | Users are able to see all the information in plain text format but not in JSON format. | 4 | 22.0.0 |