4 Resolved and Known Bugs
This chapter lists the resolved and known bugs for Network Analytics Suite Release 24.2.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.
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 24.2.x.
OCNWDAF Resolved Bugs
OCNWDAF Resolved Bugs for OCNWDAF 24.2.2
OCNWDAF 24.2.2 is a Critical Patch Update. Critical Patch Updates provide security patches for supported Oracle on-premises products. They are available to customers with valid support contracts.
For more information, see Critical Patch Updates, Security Alerts, and Bulletins.
Table 4-1 OCNWDAF Resolved Bugs for OCNWDAF 24.2.0
| Bug ID | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 36718361 | network_performance doesn't create statistics if time is not exact | Creation of a single statistics subscription for NWP was not possible if you didn't provide the exact time of a report or if you didn't provide start date older than the report. | 3 | 24.2.0 |
| 36422348 | UI Capex changing tabs styles | When selected either View UE Group details or Analytics tab in Capex Optimization page, the style of the monitoring tabs was modified, which was inconsistent with how the UI worked. | 4 | 24.1.0 |
| 36451109 | CVE-2024-29025 Netty DoS | Netty DoS occurred due to insufficient restrictions on the amount of memory. | 4 | 24.1.0 |
OCNADD Resolved Bugs
OCNADD Resolved Bugs for OCNADD 24.2.0.0.1
Table 4-2 OCNADD Resolved Bugs for OCNADD 24.2.0.0.1
| Bug ID | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 36935974 | DD Metadata Support should be added in Windowing based Message Ordering | The currently the windowing based message ordering does not provide the support for adding OCNADD metadata, the functionality has been enhanced. | ENH | 24.2.0 |
OCNADD Resolved Bugs for OCNADD 24.2.0
Table 4-3 OCNADD Resolved Bugs for OCNADD 24.2.0
| Bug ID | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 36481692 | Malformed Data in Message sent to monitoring system (with strange characters) when path is too long and has special characters | The decoding of the long URL strings was not working correctly, resulting in junk characters. When there was a message with a long URL with special characters, it displayed strange characters. | 3 | 23.4.0 |
| 36431442 | GUI created data feed with round-robin logic of consumer adapter fails | On creating the consumer feed from the UI with two destination endpoints and round-robin as load balance type, the load factor was appearing as null for one of the endpoints. | 3 | 23.4.0 |
| 36372176 | DD-UI: Pre-defined value for egress filters are not saved via kafka-template | While creating kafka template, if we provided filter as message direction and value as TxRequest, and so on, the configuration was saved, but the filter was not applied. If the user opened the configuration in edit mode, the value for message direction was not present. | 3 | 23.4.0 |
| 36361882 | The Kafka feed status is showing inactive even if it is properly processing traffic | The status of the Kafka feed was displayed as inactive even when it was active. | 3 | 24.1.0 |
| 36323339 | Correlation configuration created without Kafka-feed at primary site | The correlation configuration and Kafka feed creation were managed by different API calls. In this case, the Kafka feed creation on the primary site had failed as the maximum number of Kafka feeds exceeded; however, the correlation configuration was created successfully. | 3 | 24.1.0 |
| 36251097 | DD-GUI: Unable to create feed with third-party destination having number in namespace | The UI was not supporting the destination endpoint if the feed name contained FQDN with namespace starting with a number. | 3 | 24.1.0 |
| 36108512 | Higher latencies up to 2 seconds reported with 100K MPS DD traffic when DD and NFs are deployed in the same cluster | The higher latency values were seen with replicated HTTP2 feeds. This was observed in the cluster when all the NFs and DD were deployed in the same cluster. The network was throttled, causing the latency to go up. | 3 | 23.4.0 |
| 36103165 | DD feed goes down and does not recover (name resolution issue?) | It was observed that a DD's consumer adapter sometimes stopped the traffic to a particular third- party application. The third-party application frequently closed the connection with the DD consumer adapter for the synthetic feed. This resulted in the Kafka consumer feed detaching from the consumer group and stopped reading the traffic. | 3 | 23.4.0 |
| 36008271 | Synthetic feed adapter stops sending packets | It was observed that a DD's consumer adapter sometimes stopped the traffic to a particular third-party application. The third-party application frequently closed the connection with the DD consumer adapter for the synthetic feed. This resulted in the Kafka consumer feed detaching from the consumer group and stopped reading the traffic. | 3 | 23.4.0 |
| 36407210 | Clone feed not cloning all default parameters in a new feed | When cloning a feed from a feed created using default parameters, the "Handshake Synthetisation" was disabled on a cloned feed. | 4 | 24.1.0 |
| 36372697 | DD-UI: Default values for TDR configuration not auto-filled when changed from SUDR to TDR (kafka-template) | The parameters for the TDR were not getting auto-filled when the mode of the correlation was changed from SUDR to TDR by using the kafka-templates for the configuration creation. | 4 | 24.1.0 |
| 36475951 | [OCI] For SYNTHETIC FEED and KAFKA FEED with 5K MPS traffic most of the memory utilization is more than 99% | The MQL query expression was not correct on the OCI dashboard. | 4 | 24.1.0 |
4.3 Known Bug List
Known Bugs tables list the known bugs and associated Customer Impact Statements.
OCNWDAF 24.2.x Known Bugs
OCNWDAF Known Bugs for OCNWDAF 24.2.2
OCNWDAF 24.2.2 is a Critical Patch Update. Critical Patch Updates provide security patches for supported Oracle on-premises products. They are available to customers with valid support contracts.
For more information, see Critical Patch Updates, Security Alerts, and Bulletins.
Table 4-4 OCNWDAF 24.2.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.2.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.2.0 | No customer impact.
Workaround: No workaround available. |
| 36680820 | NWDAF - ATS version should be uplifted to the latest version | NWDAF - ATS version should be uplifted to the latest version. | 3 | 24.2.0 | No customer Impact.
Workaround: Upgrade ATS to the latest version. |
OCNADD Known Bugs
OCNADD 24.2.0.0.1 Known Bugs
Table 4-5 OCNADD 24.2.0.0.1 Known Bugs
| Bug Number | Title | Description | Severity | Found in Release | Customer Impact |
|---|---|---|---|---|---|
| 37278280 | Export service stuck in sequential Init stage when MTLS is enabled | The export service remain in init state when MTLS is enabled | 3 | 24.2.0 | Export Functionality Will Not Work
Workaround:
|
OCNADD 24.2.0 Known Bugs
Table 4-6 OCNADD 24.2.0 Known Bugs
| Bug Number | Title | Description | Severity | Found in Release | Customer Impact |
|---|---|---|---|---|---|
| 36564047 | Kafka-broker STS not pointing to headless service | The Kafka broker STS manifest incorrectly specifies the service name as kafka-broker instead of kafka-broker-headless, resulting in the pod's headless FQDN being not pingable. Ideally, it should point to the headless service. | 3 | 23.4.0 | It can lead to incorrect FQDNs and cause confusion
for users.
Workaround: No workaround available |
| 36590208 | Export functionality for csv/pcap not working when applied with filters | The filters function correctly; however, if a filter returns a small number of records in the export query, the export fails. | 3 | 24.2.0 | It can cause confusion for users who expect filtered
exports to work seamlessly.
Workaround: No workaround available |
| 36606756 | DD-GUI: Processing info should be shown if export configuration takes longer time to respond | The UI does not freeze while waiting for an API response to export configuration, allowing users to make additional configurations, potentially resulting in inconsistent setups. | 3 | 24.2.0 | It can lead to inconsistent configurations as users
may perform multiple operations before the initial operation
completes.
Workaround: No workaround available |
| 36623369 | DD GUI display issue in status and worker group name | Opening multiple sites in the same browser session shows the worker group name as that of the initially opened site. Additionally, the feed status "Fetching data" is incorrectly displayed on the UI. | 3 | 23.4.0 | Users will not receive accurate information on the
UI.
Workaround: Issue#1: Display issue of worker group Name: User needs to sign out of CNCC before displaying a different DD site. If multiple sites are opened in the same browser, it will show the worker group of the first site opened. Issue#2: Feed Status: No workaround available |
| 36653996 | OCNADD's Loss of Connection Alarm is not cleared automatically even when the service is up | The loss of connection alarm persists despite the service being operational. | 3 | 24.2.0 | Users may incorrectly believe the service has not
started correctly.
Workaround: No workaround available |
| 36681307 | Data Director GUI page states "No Worker Groups are installed" when there is a Worker Group | If a default worker group is used in centralized deployment, users are unable to select it and create configurations inside it. | 3 | 23.4.0 | Users will not be able to select the default worker
group and create configurations inside it.
Workaround: No workaround available |
| 36697097 | Kafka without zookeeper: DD worker group installation is stuck when installing without zookeeper | Worker group installation halts because certificates are not generated using OCCM. | 3 | 24.2.0 | No customer impact.
Workaround: Create certificates manually using the generate_certs script. |
| 36697937 | Perf: OCNADD aggregation pods spinning beyond 90% cpu with 135K Aggregation traffic | Aggregation service instances experience high resource utilization with high traffic rates (135K+ MPS). | 3 | 24.2.0 | The higher utilization may be necessary for some
aggregation service instances.
Workaround: Increase vCPUs in the aggregation service PODs. |
| 36714462 | DD GUI: L3L4 and Filter details are missing in Export Configuration Summary | While creating export configurations, users can view filter and L3L4 configuration details, but these details are not shown in the summary screen afterward. | 3 | 24.2.0 | No customer impact.
Workaround: No workaround available |
| 36737090 | DD-OCCM: Backup related OCCM files are missing in the package | Manual backup and restore operations will not function if OCCM is enabled. | 3 | 24.2.0 | No impact.
Workaround: Use the required manual backup template file as updated in the installation guide for use with OCCM. |
| 36745554 | Adapter and Alarm pods in crash-loop when datafeed created with incorrect endpoint | Incorrect endpoints configured in the HTTP2 feed cause adapter and alarm pods can enter a crash-loop. | 3 | 24.2.0 | Too many alarms and logs may cause ephemeral storage
usage to exceed, resulting in POD restarts.
Workaround: Incorrect third-party endpoint is provided and the error is as follows: OCL 2024-06-18T14:52:53.351Z ERROR 1 --- [-StreamThread-2] c.o.c.c.o.C.s.t.TopologyBuilderImpl : Error occurred processing message. Error Failed to resolve 'ocnaddthirdpartyconsumeroracle3.kp-wg1' [A(1), AAAA(28)] after 2 queries 1. Edit the feed and correct the endpoint so that the traffic starts reaching to third-party. 2. If the correct endpoints are not available at present and will be available in future, then edit the feed, change the value from "Do not try again" to "Keep trying" for "Data reach failure" parameter. 3. Adapter pods in ERROR state need to be deleted manually with
below command: |
| 36751592 | CORRELATED_FILTERED correlation not replicating to mated site | In 2Site Redundancy feature, CORRELATED_FILTERED Kafka feed type configurations are not replicated to the mate site. | 3 | 24.2.0 | There is low impact if the customer is using
two-site redundancy feature and has created a CORRELATED_FILTERED
Kafka feed type.
Workaround: As CORRELATED_FILTERED Feed is not getting replicated to the mate site, user can create the same configuration (for CORRELATED_FILTERED) on the mate site. For example from primary if CORRELATED_FILTERED (ex: corr-filter-1) is not replicated, on the secondary site: Go to Feed, Click on Kafka Feed tab, Click on Create Correlation Config, Create corr-filter-1 (CORRELATED_FILTERED) with same configuration as created in mate site. Manually clear the alarm that is created due to failure of creating CORRELATED_FILTERED (ex: corr-filter-1). |
| 36666809 | DD-GUI: "Done" button not getting active after saving kafka-template configuration | After editing kafka-template configuration and saving changes, the "Done" button does not become active. | 4 | 24.2.0 | No impact.
Workaround: No workaround available |
| 36669047 | Alarm for "Kafka Consumption Paused" raised even if all the topics are receiving continuous traffic | Alarms indicate traffic consumption from Kafka is paused, despite continuous traffic reception by topics. | 4 | 24.2.0 | It can confuse users who expect alarms to reflect actual traffic
status.
Workaround: The alarm should be ignored. |
| 36671638 | Alarms such as SFTP service is unreachable and No Data available for export not getting cleared | Alarms indicating "SFTP service unreachable" and "No Data Available" persist even after the conditions causing the alarms are resolved. | 4 | 24.2.0 | It can confuse users as the alarms do not reflect
current operational status.
Workaround: No workaround available |
| 36688812 | DD-GUI: The Trace response shows one more page (with improper data) even if all the records are already displayed | Additional page is displayed on the trace screen despite all records being shown on the first page. | 4 | 24.2.0 | No customer impact.
Workaround: No workaround available |