4 Resolved and Known Bugs
This chapter lists the resolved and known bugs for Network Analytics Suite Release 23.1.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.
4.1 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.
4.2 Resolved Bug List
This section provides information on the resolved bugs in Network Analytics Suite products release 23.1.0.
OCNWDAF Resolved Bugs
Table 4-1 OCNWDAF 23.1.0.0.2 Resolved Bugs
| Bug Number | Title | Description | Severity | Found In Release |
|---|---|---|---|---|
| 35187774 | Installation Guide mentions the procedure to create the NWDAF databases twice in the document | The procedure to create NWDAF databases has been documented in two sections of the Installation Guide. The redundant section has to be removed. | 3 | 23.1.0 |
| 35241787 | NWDAF GUI helm charts are missing from NWDAF 23.1.0 MoS Package | The NWDAF portal and NWDAF portal service Helm charts are not available in NWDAF 23.1.0.0.1 MoS package. Although images for both the NWDAF portal services are present in NWDAF MoS package but their Helm charts are missing. | 3 | 23.1.0 |
| 35255779 | NWDAF - 23.1.0 GUI functionalities are not working | On accessing the NWDAF GUI through CNC Console, the NWDAF GUI dashboard opens and all the GUI options appear. While accessing the GUI options the GUI freezes. The GUI is requesting the slices and cells over an incorrect localhost URL instead of using the configured URL in CNC Console. | 3 | 23.1.0 |
| 35212772 | NWDAF 23.1.0 - A SQL export parameter is incomplete in Installation Guide | The export engine variable parameter mentioned in the "Installing NRF client" section of the Installation guide is incomplete. | 4 | 23.1.0 |
OCNWDAF Resolved Bugs
OCNWDAF 23.1.0 Resolved Bugs
There are no resolved bugs in this release.
OCNADD Resolved Bugs
Table 4-2 OCNADD Resolved Bugs
| Bug Number | Title | Description | Severity | Found In Release |
|---|---|---|---|---|
| 35175323 | Wrong information about the Advertised Listeners and Privileged users in the Installation Guide | Incorrect example mentioned to provision the Advertised Listeners.
OCNADD requires the database administrator to create a privileged user in MySQL database and provide the necessary permissions to access the databases. It is recommended to name this privileged user as "admin user" to avoid confusion with the other privileged user mentioned in ocnadd-secret-hook.yaml and ocdd-db-resource.sql files. |
3 | 23.1.0 |
| 34742422 | EGW instance keep increasing on every re-starts | De-registration is not happening when a POD gets restarted. | 3 | 22.0.0 |
| 34740421 | OCNADD logging Error logs as INFO for Adapter and EGW for when 3rd Party is not reachable/Down | The logs are being printed as INFO instead of ERROR for this particular scenario | 3 | 22.0.0 |
| 34740391 | OCNADD GUI not Validating endpoints | The URI endpoints for third-party consumer application are not getting validated For example, extra spaces, HTTPs are used in case of No-TLS | 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. | 3 | 22.0.0 |
| 34712921 | The x-axis is not giving correct interval | In the Dashboard section of Graphical User Interface (GUI), the Bar graph does not display correct intervals on the x-axis. It shows multiple zeros and ones. | 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 1. The alarm should not be raised for services that do not require more than 1 replica count. | 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. | 4 | 22.0.0 |
| 35045542 | TCP Connection getting closed after inactivity of 15mins or more for OCNADD's 3rd Party Simulator | When a Synthetic Feed is created and left idle for more than 15 minutes, the TCP connection breaks. | 2 | 23.1.0 |
4.3 Known Bug List
Known Bugs tables list the known bugs and associated Customer Impact Statements.
OCNWDAF Known Bugs
There are no known bugs for OCNWDAF 23.1.0
OCNADD Known Bugs
The following table lists the known bugs for OCNADD Release 23.1.0.
Table 4-3 Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 35087831 | 54K MPS ingress & 108K egress with data replication enabled is resulting in 100% of kafka-broker memory utilization | For a specific traffic load test it is observed that 100% of the allocated Kafka-broker memory is being utilized which is not an ideal scenario. | No impact. | 3 | 23.1.0 |
| 35069179 | Adapter getting restarted when we make changes in the feed after restarting config service | When any feed with oracle ciphers is edited its adapter POD is getting restarted. | No impact. | 3 | 23.1.0 |
| 35058236 | OCNADD UI not Validating Data feeds Endpoints | Invalid Endpoints given by users are not validated by the UI. | Missing validation can result in an incorrect configuration. Thus, the user needs to provide the correct endpoints. | 3 | 23.1.0 |
| 35052457 | OCNADD: Incorrect correlation id observed in synthetic packet for specific x-request-id value | There is a mismatch in x-request-id header value for the Synthetic packet received at the third-party consumer. | Incorrect x-request-id is observed in the header. | 3 | 23.1.0 |
| 35045999 | After deleting any Data Feed, Major Alarm raised | For a deleted Data Feed, the major alarm for connection status "Connection Could not be established with the server" remains for a specific duration. | No impact. However, the alarms shown for a deleted Data Feed (for a specific duration) can mislead the users. | 3 | 23.1.0 |
| 35039749 | In Dashboard the Average Message Size per NF is incorrect | In GUI dashboard, the "Average Message Size per NF" is incorrect. | No impact. However, the incorrect message size shown can mislead the users. | 3 | 23.1.0 |
| 34827399 | Discrepancy in OCNADD metrics - Tx messages are higher than Rx messages |
The outgoing traffic handled by the Adapter service is higher than the actual incoming packets at Kafka. This is due to Kafka consumer rebalancing. |
Duplicate packets may be sent to third-party consumers. | 3 | 23.1.0 |
| 34786365 | OCNADD logging Error logs as INFO for Configuration service for when it is sending Notification to Adapter | When sending the notifications to Adapter, the Configuration service is logging a few ERROR logs as INFO. | No impact. | 3 | 23.1.0 |
| 35067498 | For Synthetic feed, adapter is not raising alarm for 3rd party connection failure with low traffic | For a Synthetic feed, the Adapter service is not raising the alarm when third party pod is down while processing low traffic. | No impact. | 4 | 23.1.0 |
| 35063634 | Improper description for the alarm - OCNADD02005: ThirdParty Connection Failure | An improper description is displayed on UI for the alarm - "OCNADD02005: ThirdParty Connection Failure". | No impact. | 4 | 23.1.0 |