4 Resolved and Known Bugs
This chapter lists the resolved and known bugs for Network Analytics Suite Release 24.1.x .
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.
Resolved Bug List
This section provides information on the resolved bugs in Network Analytics Suite products release 24.1.x.
OCNWDAF Resolved Bugs
OCNWDAF Resolved Bugs for OCNWDAF 24.1.0
Table 4-1 OCNWDAF Resolved Bugs for OCNWDAF 24.1.0
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 36365248 | AnalyticsInfo is falling with error 406 | The user sent an AnalyticsInfo request with the correct parameters and received an incorrect response code 406. The correct status code is either 204 or 200. | 2 | 23.4.0 |
| 36068419 | 3gpp NWDAF - Error message is wrong when trying to create a sub with MTLF down | When creating a subscription with MTLF unavailable, the API response was invalid. | 3 | 23.4.0 |
| 36068437 | NWDAF subscriptions with ONE_TIME value in notifMethod send more than 1 notification | The OCNWDAF subscriptions with the value "ONE_TIME" in the parameter notifMethod sent multiple notifications.
|
3 | 23.4.0 |
| 36068432 | PV API Consumer not logging request headers | The PV API consumer was not logging the HTTP headers for each request. | 4 | 23.4.0 |
| 36073817 | GUI Slice Load filter being applied when coming from NF Load | The user set a date range in the NF Load Monitoring GUI page and then proceeded to the Slice Load Monitoring page. The user observed an extra filter appeared in the filter bar. | 4 | 23.4.0 |
Note:
Resolved bugs from 22.1.0, 23.1.0, 23.1.0.0.2, 23.2.0, 23.3.0, 23.3.0.0.1, and 23.4.0 have been forward ported to Release 24.1.0.OCNADD Resolved Bugs
OCNADD Resolved Bugs for OCNADD 24.1.0
Table 4-2 OCNADD Resolved Bugs for OCNADD 24.1.0
| Bug Number | Title | Description | Severity | Found In Release |
|---|---|---|---|---|
| 36309089 | Attempted Upgrade to from 23.4.0 to 23.2.0.0.2 and rollback failure | The user upgraded from release 23.3.0 to release 23.4.0, and errors were reported for configuration secrets and admin services, though the intraTLS was disabled. | 2 | 23.4.0 |
| 36356432 | Adapters with egress filter associated are not able to process traffic | Adapters with Egress filters could not process traffic as the stream thread mapping was created for only up to eight stream threads. | 2 | 23.4.0 |
| 36346242 | Fabric8 error observed on admin service resulting in not upgrade of adapter feeds | The Admin service could not create the adapter due to a Fabric8 client error resulting from changes in the Fabric8 API. | 2 | 23.4.0 |
| 36310029 | Correlation pod did not spawned, SCP/NRF/SEPP/MAIN topics not created after backup restoration | After the backup restoration was performed, the correlation pod failed to spawn, and the SCP/NRF/SEPP/MAIN topics were not created. This was due to an issue with the restore script and admin service. A code block to recreate the correlation pod after DB restore was missing. | 2 | 23.4.0 |
| 36038818 | Log messages: error raising alarm | An error was reported in the adapter service while raising the alarm. | 3 | 23.4.0 |
| 36206970 | Data Director adapter pods fail to start due to CA cert path being incorrect | Data Director adapter pods fail to start due to an incorrect CA cert path. The caroot.cer was used in the certificate instead of the default cacert.pem. Support was added for the caroot.ca in the adapter service. | 3 | 23.4.0 |
| 36080286 | Egress filter of worker group1 is showing feeds of other WG as well in "association" dropdown | It was observed that while creating the egress filter, the adapter feed created for one worker group appeared for the other worker group and during the filter's association with the feed. | 3 | 23.4.0 |
| 36038805 | OCNADD GUI reloading a page takes 40 seconds | The OCNADD GUI took longer to reload after updating the feed configuration. | 3 | 23.4.0 |
| 36027600 | Worker-group not listed when MTLS is true | The MTLS was not working for the OCNADD GUI services. | 3 | 23.4.0 |
| 36022704 | Seeing a sudden drops in KPI's count after correlation service pod restarts | The Prometheus metric counters were reset when the container restarted. The GUI fetched the metrics from Prometheus, and upon resuming the correlation service pods, the metric counter was reset, which incorrectly resulted in observing a sudden drop in KPI count. | 3 | 23.4.0 |
| 36020488 | Deregistration and Registration Alarm for UIRouter and GUI is not logging on UI and database | The UI and UI router service could register (and deregister) with the health monitoring service. | 3 | 23.4.0 |
| 35926969 | Edit function in Correlation config not working properly | The user could not change the correlation mode and had to reselect all the fields for the new correlation mode individually. | 3 | 23.4.0 |
| 35842279 | DataDirector GUI Display issue 5G PROD | The feed status was displayed as inactive, though the feed was working correctly, and a third party could receive the data from the feed. | 3 | 23.4.0 |
| 36349976 | Data Director GUI users are not able to see feeds already created | The users with the "write" role could see each other's feeds, which is the expected behavior. | 3 | 23.4.0 |
| 36343889 | Average Latency for Data Feed" is not showing correct value | The OCNADD GUI user observed that the metric for a particular feed displayed incorrect Average Latency. The latency value was very low, and the GUI considered very low latency values to be "0." | 3 | 23.4.0 |
| 36071681 | In N12 and N13 service name labels are not correct. | The labels identifying the N12 and N13 transactions were incorrect. | 4 | 23.4.0 |
| 36017165 | KPI's graph not displaying correct information. | The label on the KPI graph was incorrect. msg/sec was displayed instead of transactions/sec. | 4 | 23.4.0 |
Note:
Resolved bugs from 22.1.0, 23.1.0, 23.2.0, 23.2.0.0.1, 23.3.0, and 23.4.0 have been forward ported to Release 24.1.0.Known Bug List
Known Bugs tables list the known bugs and associated Customer Impact Statements.
OCNWDAF 24.1.0 Known Bugs
The following table lists the known bugs for OCNWDAF Release 24.1.x.
Table 4-3 OCNWDAF 24.1.0 Known Bugs
| Bug Number | Title | Description | Severity | Found in Release | Customer Impact |
|---|---|---|---|---|---|
| 36422338 | UI SLL Threshold notifications for DD subs missing nf_id | OCNWDAF uses the OCNADD as a data source. Currently, the OCNADD events do not contain the previously mentioned values. | 3 | 24.1.0 | No customer impact.
Workaround: No workaround available. |
| 36422333 | Configuration_manager cell table should not contain tac attribute | The configuration_manager cell table contains the tac attribute, which is duplicate data that must be deleted.
|
3 | 24.1.0 | No customer impact.
Workaround: No workaround available. |
| 36422348 | UI Capex changing tabs styles | When the user selects either the View UE Group or Analytics tab on the Capex Optimization page, the modification style of the Monitoring tab currently differs from how the UI works. | 4 | 24.1.0 | Incorrect information is displayed in the GUI. Visualization in the Monitoring tab is incorrect.
Workaround: No workaround available. |
| 36451109 | CVE medium CVE-2024-29025 Netty DoS due to insufficient restrictions on the amount of memory | Netty is an asynchronous event-driven network application framework for rapidly developing maintainable, high-performance protocol servers and clients. Netty Denial of Service (DoS) is observed due to insufficient restrictions on the amount of memory. | 4 | 24.1.0 | Netty is not the base web server for NWDAF, hence no customer impact.
Workaround: No workaround available. |
OCNADD Known Bugs
OCNADD 24.1.0 Known Bugs
The following table lists the known bugs for OCNADD Release 24.1.x.
Table 4-4 OCNADD 24.1.0 Known Bugs
| Bug Number | Title | Description | Severity | Found in Release | Customer Impact |
|---|---|---|---|---|---|
| 36008271 | Synthetic feed adapter stops sending packets | The OCNADD's consumer adapter sometimes stops traffic to a particular third party application. The third party application frequently closes the connection with the OCNADD consumer adapter for the synthetic feed, causing the Kafka consumer threads to detach from the consumer group and stop reading the traffic. | 3 | 23.3.0 | Traffic to specific third-party applications may be disrupted.
Workaround: Restart the consumer adapter. |
| 36361882 | The kafka feed status is showing inactive even if it is properly processing traffic | The status of the feed is reported incorrectly on the OCNADD GUI. | 3 | 24.1.0 | Incorrect information is displayed in the GUI.
Workaround: No workaround available. |
| 36323339 | Correlation configuration created without kafka-feed at primary site | In a georedundant deployment, when the Kafka feeds on both sites are created and bidirectional sync mode is enabled in the redundancy mate configuration, the correlation configuration gets replicated on the primary site without its Kafka feed. | 3 | 24.1.0 | The correlation configuration only works correctly with the Kafka feed.
Workaround: For more information, see "Troubleshooting OCNADD" chapter in the Oracle Communications Network Analytics Data Director Troubleshooting Guide. |
| 36251097 | DD-GUI : Unable to create feed with thirdparty-destination having number in namespace | The GUI does not support the destination endpoint if the feed name contains fqdn with a namespace starting with a number. | 3 | 24.1.0 | While creating the third-party feed, a third-party application destination endpoint with a namespace starting with the number is not allowed.
Workaround: No workaround available. |
| 36108512 | Higher latencies upto 2sec reported with 100K MPS DD traffic when DD and NFs are deployed in same cluster | Replicated HTTP2 feeds display higher latency values when all the NFs and OCNADD are deployed in the same cluster. Network throttling is causing this increase. | 3 | 23.4.0 | Higher resource utilization is required.
Workaround: Distribute some NFs, such as SEPP and OCNADD, in different clusters. |
| 36481692 | Malformed Data in Message sent to monitoring system (with strange characters) when path is too long and has special characters | Unable to decode long URL strings correctly, junk characters are visible while sending long URL messages with special characters such as “{“, “[“, “:”, “””. | 3 | 23.3.0 | Troubleshooting tools are unable to decode the messages.
Workaround: No workaround available. |
| 36431442 | GUI created data feed with round-robin logic of consumer adapter fails | The user creates a consumer feed from the GUI with two destination endpoints and the load balancing type as "round-robin". One of the endpoints has a load factor of "null". | 3 | 23.4.0 | The adapter pod does not spawn for the configured feed, and GUI validation is missing.
Workaround: Use weighted load balancing and set the load factor to 50% for each destination endpoint. |
| 36411328 | Cannot close feed modification window after saving changes | The user is unable to save feed modifications. | 3 | 23.4.0 | The issue cannot be reproduced. No customer impact.
Workaround: No workaround available. |
| 36372176 | Pre-defined value for egress filters are not saved via kafka-template | While creating a Kafka template, the user provides a filter as message-direction, value as TxRequest, and so on. The configuration is saved, but the filter is not applied. On opening the configuration in edit mode, the value for message-direction is absent. | 3 | 23.4.0 | User configuration is not applied correctly.
Workaround: Create the Kafka feed with a filter without using the Kafka templates. |
| 36103165 | DD feed goes down and does not recover (name resolution issue ?) | The OCNADD's consumer adapter sometimes stops traffic to a particular third-party application. The application frequently closes the connection with the OCNADD's consumer adapter for the synthetic feed. The Kafka consumer threads detach from the consumer group and stop reading the traffic. This bug is a duplicate of bug 36008271. | 3 | 23.4.0 | Traffic to specific third-party applications is disrupted.
Workaround: Restart the consumer adapter. |
| 35971309 | [NF KPI DASHBOARD]: kpi interval end date is taking earlier date also | In the NF dashboard, the KPI interval end date field accepts an earlier date than the start date. | 3 | 23.4.0 | Missing field entry validation can result in user error.
Workaround: No workaround available. |
| 36475951 | [OCI] For SYNTHETIC FEED and KAFKA FEED with 5K MPS traffic most of the memory utilization is more than 99% | Memory resource utilization is high for a few service pods. | 4 | 24.1.0 | High resource utilization is observed.
Workaround: Increase the memory for the pods reporting high resource utilization. |
| 36407210 | Clone feed not cloning all default parameters in a new feed |
When the user clones a feed from a feed created using default parameters, the "Handshake Synthetisation" is disabled on the cloned feed. By default, "Handshake Synthetisation" is enabled when manually creating a feed. |
4 | 24.1.0 | The cloned feed behaves differently from the original feed and causes user confusion.
Workaround: Manually enable the "Handshake Synthetisation" in the newly created cloned feed. |
| 36372697 | Default values for TDR configuration not auto-filled when changed from SUDR to TDR (kafka-template) | When the correlation mode is changed from SUDR to TDR using the Kafka templates for configuration creation, the parameters for the TDR are not auto-filled. | 4 | 24.1.0 | The user has to manually provide all the default values.
Workaround: No workaround available. |