4 Resolved and Known Bugs
This chapter lists the resolved and known bugs for Network Analytics Suite Release 25.1.2xx.
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 25.1.2xx.
Release 25.1.201
Table 4-1 OCNADD 25.1.201 Resolved Bugs
| Bug ID | Title | Description | Severity | Release Version |
|---|---|---|---|---|
| 38353700 | Synthetic adapter sends messages through different TCP connections | The TCP feed sent messages belonging to the same transaction on different TCP connections. As required, all messages in a transaction should have been sent over the same TCP connection to the third-party application.
Doc Impact: There is no doc impact. |
3 | 25.1.200 |
| 38300170 | OCNADD metric Latency_critical_threshold_crossed alert level of 100% | The HTTP2 feed was unable to recover from high lag in the MAIN topic in DD. End-to-end latency was very high, measured in minutes, due to approximately 25 ms network latency from the third party sending a response to the HTTP2 feed.
Doc Impact: There is no doc impact. |
3 | 24.30 |
| 38592975 | Incorrect format of the body: Base64-encoded Body issue | When the Content-Type was multipart/*, the consumer adapter sometimes forwarded the payload as base64-encoded ASCII text in HTTP/2 DATA frames instead of as decoded raw multipart bytes.
Doc Impact: There is no doc impact. |
3 | 25.2.100 |
| 38636908 | DD Synthetic feed HTTP2 compliance issue: missing END_STREAM flag | When the payload (5g-sbi-message) was not present, the END_STREAM flag was not added in the HTTP2 headers frame of the synthetic packet encoding.
Doc Impact: There is no doc impact. |
3 | 25.2.100 |
| 38518152 | Stream-ID is changing for the same transaction | DD changed the HTTP2 stream ID for messages within the same transaction when any legs (pairs in the transaction) had a different network session.
Doc Impact: There is no doc impact. |
3 | 24.2.1 |
| 38637087 | DD wrong stream id parity for synthetic feed | Data Director increased the stream ID consecutively by one for the synthetic feed.
Doc Impact: There is no doc impact. |
3 | 25.2.100 |
| 38712673 | Metadata missing for RX and Tx Response in case of 2 SEPPs sending feed | When dual SEPPs were sending the feed to the DD, and the DD was configured to do a synthetic feed to the external application that performed the L3–L4 mapping, with the DD-Metadata feature enabled in DD with transaction-based message reordering: Then the DD-Metadata was being populated for all the trigger points in the flow, except for the originating SEPP Tx and Rx response message direction, which was incorrect.
Doc Impact: There is no doc impact. |
3 | 25.1.200 |
| 38327245 | Data Director 25.1.200 Synthetic feed / Mismatch in generated sequence numbers | TCP sequence misplacement. This bug is a duplicate of bug 38353700, which states that the TCP feed is sending messages belonging to the same transaction on different TCP connections, whereas per customer requirement all messages of a transaction should be sent on the same TCP connection to the third-party application.
Doc Impact: There is no doc impact. |
3 | 25.1.200 |
| 38656940 | Increased LAG and E2E latency reported | Aggregation service pods were stuck in the rebalancing phase due to an uncaught stream exception. This issue occurs only for MESSAGE_SEQUENCING of type REQUEST_RESPONSE when Model-D traffic is sent to DD.
Doc Impact: There is no doc impact. |
3 | 24.2.1 |
| 38688634 | Advanced Feed TLS Feed shows Destination Status as is Inactive | When a third-party app’s FQDN was used in the feed configuration, the destination and feed status were shown as inactive in the DD GUI, but when an IP was used in the feed configuration, the destination status was OK in the DD GUI.
Doc Impact: There is no doc impact. |
3 | 25.1.200 |
| 38687539 | Kafka broker load imbalance and internal topic rebalance || DD 25.1.200 | After scaling the Kafka brokers (adding kafka-broker-4 to kafka-broker-10), and then executing partition reassignment to redistribute partitions across all brokers for the MAIN and SCP topics, high CPU and memory usage was observed on the old three brokers. This was caused by the additional topics (__consumer_offsets and __transaction_state) still being located only on the first three brokers.
Doc Impact: The solution for internal topic reassignment after Kafka cluster scaling has been documented in the Kafka Cluster Capacity Expansion section of the Oracle Communications Network Analytics Data Director User Guide. |
3 | 25.1.200 |
| 38750604 | After upgrade to 25.1.200, connection to external helix adapter not established | After upgrading OCNADD from 24.3 to 25.1.200, the connection to the external Helix adapter failed. In 24.3, OCNADD attempted an HTTP/2 connection with a magic settings message (PRI * HTTP/2.0 SM), while in 25.1.200 it sent an HTTP/1.1 GET request with a header to upgrade to h2c.
Doc Impact: There is no doc impact. |
3 | 25.1.200 |
| 38765669 | Zookeeper restarting with "No space left on device" error | Kafka cluster was not in a stable state due to the Zookeeper PVC being full, causing the Zookeeper pod to enter a crash loop backoff state.
Doc Impact: There is no doc impact. |
3 | 24.2.1 |
| 38717264 | After DD upgrade from 25.1.200 to 25.2.100, some kafka-broker pods are in "CrashLoopBackOff" status | The Kafka broker pods crashed and went into CrashLoopBackOff status during the upgrade from release 25.1.200 to 25.2.100. This issue occurred because the KAFKA_CLUSTER_ID used in the KRaft cluster pods was different from the one specified in the scriptskraft-config.yaml file.
Doc Impact: Preupgrade Tasks section in the Oracle Communications Network Analytics Data Director Installation and Upgrade Guide has been updated. |
4 | 25.1.200 |
Release 25.1.200
Table 4-2 OCNADD 25.1.200 Resolved Bugs
| Bug ID | Title | Description | Severity | Release Version |
|---|---|---|---|---|
| 37522663 | kraft-controller detail not listed on UI dashboard | The Kafka was deployed in Kraft controller mode, but the details of the Kraft controller were not visible on the UI's services list.
Doc Impact: There is no doc impact. |
3 | 25.1.100 |
| 37516495 | DD High adapter latency in Production | The third-party application recorded a higher average latency for the end-to-end message from the user's device to the third-party system.
Doc Impact: There is no doc impact. |
3 | 24.2.0 |
| 37514557 | DD generating corrupted synthetic packets | The third-party application reported issues with some packets generated by the synthetic feed, which were found to be incorrect.
Doc Impact: There is no doc impact. |
3 | 24.2.0 |
| 37510716 | SUPI filter not getting applied correctly in trace | The SUPI filter encountered an issue where the actions 'allow' and 'deny' produced incorrect outcomes when applied in the tracing window.
Doc Impact: There is no doc impact. |
3 | 25.1.100 |
| 37496136 | UI not showing all the opened alarm | In the current release, a limitation was observed regarding the display of alarms. The system could only show a maximum of 1000 alarms for each severity type, including critical, major, minor, info, and warning.
Doc Impact: There is no doc impact. |
3 | 25.1.100 |
| 37467260 | DD 24.2.0 || Segmentation does not work as expected | The TCP segmentation for the synthetic feed exhibited an issue where a few packets exceeded the configured segmentation length.
Doc Impact: There is no doc impact. |
3 | 24.2.0 |
| 37459530 | Data Director synthetic adapter opens idle TCP connections | The Data Director Synthetic Feed Adapter opened more connections than the configured number. These excess connections remained idle because no data was transmitted over them.
Doc Impact: There is no doc impact. |
3 | 24.2.0 |
| 37411881 | Occasional Kafka Feed Creation Error for Correlated Kafka Feed | Occasionally, the creation of a Correlated Kafka Feed failed. Although the Admin service successfully created a topic, the process subsequently failed with an unknown exception.
Doc Impact: There is no doc impact. |
3 | 25.1.100 |
| 37405526 | HPACK incorrect in synthetic feed | The Data Director (DD) did not correctly advertise HPACK in the synthetic fields. According to the RFC, DD was supposed to implement static-only HPACK, but it incorrectly advertised support for dynamic HPACK, even though it did not actually use dynamic indexing.
Doc Impact: There is no doc impact. |
3 | 24.2.0 |
| 37404206 | Alarm for "topic not available" gets cleared even if the topic is not created | When a Kafka topic was not available, the 'Topic Unavailable' alarm was raised and then incorrectly cleared. The alarm should have remained active because the topic had not been created, and the new event should have been added to the existing alarm instead of clearing it.
Doc Impact: There is no doc impact. |
3 | 25.1.100 |
| 37375067 | DD UI: For alarm date query future data is being highlighted by default | When selecting an end date for an alarm, a future date was incorrectly displayed as the end date.
Doc Impact: There is no doc impact. |
3 | 25.1.100 |
| 37543035 | UI not accessible after configuration service re-start | After creating a correlation configuration, the UI became inaccessible when the Configuration service was restarted for any reason.
Doc Impact: There is no doc impact. |
3 | 25.1.100 |
| 37149677 | Adapter feed down until adapter is rebooted | When the consumer adapter feeds experienced frequent disconnections from the third-party service, the Kafka stream processing threads sometimes became detached from the consumer group and stopped consuming data.
Doc Impact: There is no doc impact. |
3 | 24.2.0 |
| 37556884 | ATS execution stops abruptly sometimes for ACL execution | The ATS test suite execution occasionally stopped when testing features that required Kafka ACL support.
Doc Impact: There is no doc impact. |
3 | 25.1.100 |
| 37407778 | CPU Overload false alarms are getting generated | The Health Monitoring service reported CPU overload logs, but the actual CPU usage, as measured by Prometheus metrics, did not exceed the threshold.
Doc Impact: There is no doc impact. |
4 | 25.1.100 |
4.3 Known Bug List
Known Bugs tables list the known bugs and associated Customer Impact Statements.
Release 25.1.201
There are no new known bugs in this release.
Release 25.1.200
The following table lists the known bugs for OCNADD Release 25.1.2xx.
Table 4-3 OCNADD 25.1.200 Known Bugs
| Bug Number | Title | Description | Severity | Found In Release | Customer Impact and Workaround |
|---|---|---|---|---|---|
| 38750604 | After upgrade to 25.1.200, connection to external helix adapter not established |
Starting with version 25.1.200, the HTTP client in the DD adapter feed establishes HTTP/2 connections using the h2c Upgrade mechanism over cleartext HTTP/1.1 only. The previously supported HTTP/2 prior-knowledge connection method (RFC 9113) is no longer used. During connection, the client initiates an HTTP/1.1 request with the following headers:
GET / HTTP/1.1 Host: <host> Upgrade: h2c HTTP2-Settings: <base64url-encoded settings> Connection: Upgrade, HTTP2-Settings If the server supports the h2c Upgrade, it responds: HTTP/1.1 101 Switching Protocols Connection: Upgrade Upgrade: h2c
After this exchange, communication proceeds using HTTP/2 frames. |
3 | 25.1.200 |
Impact: If a third-party application does not support the h2c Upgrade mechanism as specified in RFC 7540 section 3.2, connections from the DD adapter feed to that application will fail to establish over HTTP/2. Customers may observe connection failures or fallback to HTTP/1.1, depending on the third-party application’s configuration.
Workaround: To restore compatibility and enable HTTP/2 plaintext connections, Customer must ensure that their third-party applications support the HTTP/1.1 h2c Upgrade procedure as described in RFC 7540 section 3.2. If not, upgrading or adjusting the third-party application software is required to ensure compatibility. |
| 36745554 | Adapter and Alarm pods in crash-loop when datafeed created with incorrect endpoint | The HTTP2 feed malfunctions when incorrect endpoints are configured in the destination endpoint. | 3 | 24.2.0 |
Impact: Too many alarms and logs may cause the ephemeral storage usage to exceed resulting in the POD restart. Workaround: An 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 : An error occurred while processing the message. Error: Failed to resolve 'ocnaddthirdpartyconsumeroracle3.kp-wg1' [A(1), AAAA(28)] after 2 queries. To resolve the issue:
|
| 37490359 | Frequent heartbeat loss alarm raised and cleared every few seconds. | Heartbeat loss alarms are repeatedly raised and cleared every few seconds. | 3 | 25.1.100 |
Impact: It may cause the alarmDB to be flooded Workaround: NA |
| 37432163 | One of the pcap export stops without any reason |
When two exports are configured, one of the PCAP exports stops and remains in an "in progress" state, but no export occurs. It is also observed that PCAP export does not resume when traffic stops and resumes after a few hours. |
3 | 25.1.100 |
Impact: The PCAP export will be stopped. Workaround: Restart the export service |
| 37431732 | Pcap export stops as soon the config service restarts | PCAP export stops when the configuration service is restarted, even though PCAP and CSV exports are configured and export works continuously. | 3 | 25.1.100 |
Impact: The PCAP export will be stopped. Workaround: NA |
| 37403907 | Storage adapter does not resume storing xDR after upgrade | Upgrading from 24.2.0 stops the storage of xDRs. | 3 | 25.1.100 |
Impact: The storage of the xDRs is stopped after the upgrade. Workaround: The corresponding storage adapter should be restarted. |
| 38037643 | UI dashboard page becomes unresponsive when user clicks on pvc utilization tab | The UI page becomes unresponsive when a user clicks on PVC utilization for the Kafka or Kraft controller. | 3 | 25.1.200 |
Impact: The user may not be able to see the PVC utilization details. Workaround: NA |
| 37997391 | "Bad Request" error logs when config service is restarted | The configuration service logs error with "Bad Request" client exception when restarted. This happens due to the fact that admin service returns the 400 bad request in case the "deployment already exist", the configuration service is not handling this message and logs error in the log. | 3 | 25.1.200 |
Impact: The user confusion can be caused because of the error being logged, however, there is no issue in the configuration or the admin services. Workaround: NA |
| 37995257 | TSR Discrepancy Alarm is raised even when the TSR configuration is deleted and re-created | The discrepancy alarm raised when the two site redundancy configuration is deleted and recreated again. It is suspected that during the deletion of the TSR configuration, some configuration still left in the configuration or redundancy agent which is causing the discrepancy during TSR recreation. | 3 | 25.1.200 |
Impact: The user confusion can be caused because of the discrepancy alarm even though there is no discrepancy exist. Workaround: NA |
| 37990843 | Proper error is not being displayed when filter values are not properly filled | The validation failure message is not user-friendly and does not mention the cause of the validation failure. | 3 | 25.1.200 |
Impact: The user is not getting the appropriate information from the error message on UI. Workaround: NA |
| 37990808 | Filter dynamic values are being populated from browser cache | The dynamic values for the filter conditions are populated from the browser cache. The values should be populated from the new API call instead of the browser cache. | 3 | 25.1.200 |
Impact: The user may use old or incorrect values to create filters, which can result in incorrect messages being passed to the third-party application. Workaround: Clear the browser cache and then create the filters. |
| 37983780 | Ingress adapter crashes continuously when all kafka-brokers are down | The ingress adapter continuously restarts when Kafka broker pods are brought down and stops restarting when the pods are brought up again. | 3 | 25.1.200 |
Impact: The ingress adapter may not work correctly when the Kafka brokers are down. Workaround: NA |
| 37965808 | Loss of Heartbeat Alarm is raised for workerGroup when there is no wg added | The loss of heart beat alarm being raised for the worker group which has not been added yet. This could be due to the presence of older entry in the health DB. | 3 | 25.1.200 |
Impact: It can cause confusion to the user. Workaround: NA |
| 37914403 | "loss of connection" alarm with kraft-controller is not getting cleared | The "loss of connection" alarm for the Kraft controller is not cleared after Kraft migration is completed and all Kraft controller pods are running fine. | 3 | 25.1.200 |
Impact: No Customer Impact Workaround: NA |
| 36666809 | DD-GUI : "Done" button not getting active after saving kafka-template configuration | The "Done" button does not become active after clicking the "Save" button when editing the kafka-template configuration. | 4 | 24.2.0 |
Impact: No Customer Impact Workaround: NA |
| 38023343 | Alarm does not raise or raised with invalid Alarm's additional detail value in secondary site, when its admin svc down and config creation or sync action performed in Primary site |
No alarm is raised when the admin service is not available in the secondary site and mate configuration is created. A sync discrepancy alarm is raised with invalid additional information when the admin service is not available in the secondary site and mate sync action is performed. |
4 | 25.1.200 |
Impact: User will not see alarm or see incorrect alarm details. Workaround: NA |
| 38019752 | Warnings while installing DD with with IntraTLS false with OCCM |
Unknown field warnings are observed when DD is installed with intraTLS false and OCCM is used. W0601 10:25:57.161561 1963961 warnings.go:70] unknown field "spec.template.spec.containers[0].env[82].mountPath" W0601 10:25:57.161612 1963961 warnings.go:70] unknown field "spec.template.spec.containers[0].env[82].readOnly" |
4 | 25.1.200 |
Impact: No Customer Impact Workaround: NA |
| 37994508 | "TLS handshake failed" warning logs on every services |
A "TLS handshake failed" warning log is generated on all DD services at exactly 00:00:00 hours when DD is deployed with mTLS true. This issue is not seen with mTLS false |
4 | 25.1.200 |
Impact: No Customer Impact Workaround: NA |
| 37990804 | Alarm list does not change to selected WG when WG is switched from Ask-Oracle |
When switching worker groups, the alarm page displays the alarm of the previous worker group instead of the selected one, unless the page is refreshed again. The switching of alarm via "switch WG" from datafeed page works fine |
4 | 25.1.200 |
Impact: No Customer Impact Workaround: NA |