4 Resolved and Known Bugs
This chapter lists the resolved and known bugs for Network Analytics Suite Release 25.2.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.2.2xx.
OCNADD Resolved Bugs
Resolved BugsTable 4-1 OCNADD 25.2.200 Resolved Bugs
| Bug ID | Title | Description | Severity | Release Version |
|---|---|---|---|---|
| 38437217 | Kafka brokers down after disabling External access | Kafka brokers restarted after external access was
disabled during the broker extension process. FQDNs were updated on
SCP and external access was disabled in the worker group. Although
the brokers stabilized, traffic from SCP could not reach DD. SCP was
suspected to still use the old bootstrap configuration. Restarting
the SCP worker pod resolved the issue.
Doc Impact: No Doc impact. |
3 | 25.1.200 |
| 38413911 | Aggregation feed creation leads to UI un-responsive | While creating an aggregated feed, clicking the Submit button
returned a 500 internal server error. After this error, the UI
became unresponsive. The user had to restart the Config and Admin
services and refresh or re-login to the UI to continue working.
Doc Impact: No Doc impact. |
3 | 25.1.200 |
| 38371911 | DD feeds inactive after DD resizing activity. RCA Required | A resizing activity was performed on the DD deployment, during
which pod configurations and SCP/MAIN topic partitions were changed.
The DD services restarted successfully, but the feeds remained in an
inactive state after the operation.
Doc Impact: No Doc impact. |
3 | 25.1.200 |
| 38421397 | After resizing, new Kafka broker pods are in CrashLoopBackOff post helm upgrade | The Kafka broker count was increased from three to five. The
newly created broker pods entered a CrashLoopBackOff state due to
incomplete handling of storage format updates during the expansion
process.
Doc Impact: No Doc impact. |
3 | 25.1.200 |
| 38300170 | OCNADD metric Latency_critical_threshold_crossed alert level of 100% | When running a high-performance profile (for example, 270K MPS),
latency critical threshold alerts were raised even when traffic was
low (approximately 1K MPS). This occurred due to frequent adapter
rebalancing that caused lag buildup and increased latency, and
because an excessive number of Kafka partitions were created for
high MPS while actual traffic remained low.
Doc Impact: No Doc impact. |
3 | 24.3.0 |
| 38289680 | Message sequencing not working for REQUEST_RESPONSE type mode | DD did not maintain the expected message sequencing when
MESSAGE_SEQUENCING_TYPE was set to
REQUEST_RESPONSE. Correlation IDs showed
responses being processed before requests. REQUEST_RESPONSE
sequencing ensured correct ordering within request messages and
within response messages, but it did not guarantee full
transaction-level sequencing. Full sequencing required the
TRANSACTION sequencing type.
Doc Impact: No Doc impact. |
3 | 24.2.1 |
| 38656940 | Increased LAG and E2E latency reported | Increased end-to-end latency and message lag were observed in a
production environment. The environment carried live traffic, but
the overall traffic volume was relatively low.
Doc Impact: No Doc impact. |
3 | 24.2.1 |
| 38637087 | DD wrong stream id parity for synthetic feed | DD incremented HTTP/2 stream IDs sequentially for synthetic
feeds. This behavior violated RFC 9113, which required
client-initiated streams to use odd-numbered stream IDs. Stream IDs
should have incremented by two (1, 3, 5, and so on).
Doc Impact: No Doc impact. |
3 | 25.2.100 |
| 38636908 | DD Synthetic feed HTTP2 compliance issue: missing END_STREAM flag | When DD generated a synthetic service request without a message
body, the END_STREAM flag was not set in the HEADERS frame. This
behavior did not comply with RFC 9113, which required the END_STREAM
flag to indicate the end of the stream.
Doc Impact: No Doc impact. |
3 | 25.2.100 |
| 38594321 | Open TCP connections are not getting closed | A TCP connection was opened and an HTTP/2 SETTINGS frame was
sent, but no response was received. The connection was not reset or
properly closed. A new TCP connection was later opened using a
different local port. Repeated occurrences could result in a large
number of open TCP connections over time.
Doc Impact: No Doc impact. |
3 | 24.3.3 |
| 38592975 | Incorrect format of the body: Base64-encoded Body issue | The synthetic messages generated on DD were
containing the base64 encoded data instead of the muti-part or zip
encoded data as indicated in the content-type header of the original
received 5g SBI header frame and data.
Doc Impact: No Doc impact. |
3 | 25.2.100 |
| 38554975 | Upgrade process in the Upgrade Guide incorrectly references Management group instead of Worker group | The Upgrade Guide incorrectly referred to the Management Group
instead of the Worker Group in the centralized upgrade procedure
steps.
Doc Impact: Updated the OCNADD Upgrade section in the Oracle Communications Network Analytics Data Director Installation, Upgrade, and Fault Recovery Guide. |
3 | 25.2.100 |
| 38518152 | Stream-ID is changing for the same transaction | DD changed the HTTP/2 stream ID between the request and response
messages within the same transaction. For example, the request used
one stream ID while the response used a different stream ID.
Doc Impact: No Doc impact. |
3 | 24.2.1 |
| 38496514 | No traffic being processed. kafka-broker-0 continuously restarting due to crashloopback status as PVC is full | User found that the kafka-broker-0 was continuously restarting
due to crashloopback status. They identified that that this was
because the PVC for kafka broker-0 was full. This is causing no
traffic to be processed by DD.
Doc Impact: No Doc impact. |
3 | 24.3.0 |
| 38407695 | 25.1.100_DD_feeds Adapter pods dosen't restart during helm upgrade | During a resizing activity, a Helm upgrade was performed. Only
some adapter pods restarted successfully, while others did not
restart or apply the updated sizing, even when manually restarted.
Doc Impact: No Doc impact. |
3 | 25.1.100 |
| 38353700 | Synthetic adapter sends messages through different TCP connections | DD sent messages belonging to the same transaction over multiple
TCP connections. This behavior affected the correct sequencing of
messages within a transaction.
Doc Impact: No Doc impact. |
3 | 25.1.200 |
| 38347488 | TPS spikes for SCP Feed | The issue is similar to bug 38300170; the traffic
spikes seen are due to the frequent and continuous rebalancing of
the Helix adapter consumer group. Additionally, there was external
latency of up to 25 ms, which was causing the adapter to frequently
toggle between circuit breaking and the normal state of the adapter,
thus causing lag accumulation and spikes in the traffic
processing.
Doc Impact: No Doc impact. |
3 | 24.3.0 |
| 38235445 | DD Correlation Service Stopped Adding SNSSAI Optional xDR Field | After upgrading DD to version 25.1.200, the SNSSAI optional xDR
field was no longer included in generated TDRs.
Doc Impact: No Doc impact. |
3 | 25.1.200 |
| 38555780 | No DD service monitor yaml in custom templates | The Installation and Upgrade Guide referenced a service monitor
YAML file that was not present in the provided custom templates.
Doc Impact: Updated the Oracle Communications Network Analytics Data Director Installation, Upgrade, and Fault Recovery Guide to remove the mention of the unavailable file. |
4 | 25.2.100 |
| 38555530 | DD 25.2.100 / Post Upgrade Task need rework | The post-upgrade section of the 25.2.100 Installation Guide
contained unclear and misleading instructions. Certificate update
steps, Helm upgrade dependencies, and Kafka KRaft migration
requirements were not accurately described for supported upgrade
paths.
Doc Impact: Updated the Post Upgrade section of the Oracle Communications Network Analytics Data Director Installation, Upgrade, and Fault Recovery Guide. |
4 | 25.2.100 |
| 38555143 | Update request to the section to create topic in the Users Guide | The Users Guide section describing how to create Kafka topics
lacked clarity and required updates to improve accuracy and
usability.
Doc Impact: Updated the Create Kafka Topics section of the Oracle Communications Network Analytics Data Director User Guide for more clarity. |
4 | 25.2.100 |
| 38554792 | Migration of Kafka Cluster to Kraft mode" section in the Users Guide update | After completing Kafka KRaft migration,
configuration settings were not reset to their original values. If
left unchanged, these settings could cause failures during
subsequent upgrades.
Doc Impact: The Oracle Communications Network Analytics Data Director User Guide was updated. Since KRaft migration is not applicable for 25.2.200, the complete migration section has been removed from the 25.2.200 user guide, and the requested change has been updated in 25.2.100. |
4 | 25.2.100 |
| 38426124 | Health Profile not found for serviceId | A Kafka broker pod remained in a pending state. Logs from the
health monitoring pod showed errors indicating that a required
health profile for the Zookeeper service was not found.
Doc Impact: No Doc impact. |
4 | 24.3.0 |
4.3 Known Bug List
Known Bugs tables list the known bugs and associated Customer Impact Statements.
OCNADD Known Bugs
The following table lists the known bugs for OCNADD Release 25.2.2xx.
Table 4-2 OCNADD 25.2.200 Known Bugs
| Bug Number | Title | Description | Severity | Found In Release | Customer Impact | Workaround |
|---|---|---|---|---|---|---|
| 38749722 | Specific software loses sync with the Oracle DD Synthetic Feed | At low message rates, some synthetic feed messages are generated with malformed data that contains extremely large length values. This condition causes the receiving software to lose synchronization with the data director. | 3 | 25.2.100 | Packet decoding fails, which causes issues with packet analysis. | No workaround is available. |
| 38750604 | After upgrade to 25.1.200, connection to external helix adapter not established | After an upgrade from version 24.3 to 25.1.200, the system sends an HTTP GET request requesting an upgrade to h2c instead of sending the expected HTTP/2 magic settings message. As a result, the external adapter does not accept the connection. | 3 | 25.2.100 | The connection to the external application is not established after the upgrade. | No workaround is available. |
| 38737332 | OCNADD 24.3.0 || Continuous rebalacing and latency issue | Adapter pods continuously rebalance due to delayed responses from an external system. This behavior triggers frequent consumer thread rebalancing, which takes a long time to complete and eventually causes unrecoverable lag. | 3 | 24.3.0 | End-to-end latency increases due to continuous rebalancing and data lag. | The issue is resolved when the fix for the related defect is applied. |
| 38712673 | Metadata missing for RX and Tx Response in case of 2 SEPPs sending feed | When two network elements send feeds simultaneously, metadata is not populated for transmit and receive response messages because two transactions share the same correlation identifier. | 3 | 25.1.200 | Metadata enrichment is missing for transmit and receive response messages. | No workaround is available. |
| 38688634 | Advanced Feed TLS Feed shows Destination Status as is Inactive | When a secure feed with encryption is configured, data is received by probes, but the user interface continues to show the destination status as inactive and no data appears on dashboards. | 3 | 25.1.200 | The user interface does not reflect the actual data transfer status. | No workaround is available. |
| 38687539 | Kafka broker load imbalance and internal topic rebalance || DD 25.1.200 | One broker consumes significantly more CPU and memory than other brokers, even after partition reassignment. | 3 | 25.2.100 | High load on a single broker may increase latency and cause data lag. | Manual rebalancing of internal topics is recommended. |
| 38687508 | 'Save Changes' is allowed even when the required field (Message Direction) is cleared in an existing Ingress Feed | The user interface allows changes to be saved even when required fields, such as message direction, are empty or invalid. | 3 | 25.2.200 | Invalid configurations can be saved through the user interface. | No workaround is available. |
| 38636990 | DD synthetic feed does not handle well empty jsons in the data frame | When packets contain a content-length value but no payload, empty data frames are not generated as expected. | 3 | 25.2.100 | Data frames are missing for messages without payloads. | An empty payload attribute must be included so that an empty data frame is generated. |
| 38634795 | Not able to load translations in DD UI (25.2.100) when 25.1.100 CNCC is used | The user interface fails to load translation files due to a namespace mismatch between components. | 3 | 25.2.100 | Data feeds cannot be created from the user interface. | The namespace must be corrected and the component reinstalled. |
| 38579439 | Alarm not getting created for the failed export configurations | When an export configuration fails, the user interface indicates that an alarm should be checked, but no alarm is generated. | 3 | 25.2.200 | Failure causes cannot be traced through alarms. | No workaround is available. |
| 38538453 | pcap export logging and clearing no data alarm every 5 mins evenif the export is happenning properly | An alarm indicating no data availability is raised at regular intervals even though export processing is functioning correctly. | 3 | 25.2.200 | Misleading alarm information is displayed. | No workaround is available. |
| 38353700 | Synthetic adapter sends messages through different TCP connections | Messages belonging to the same transaction are sent over different TCP connections. | 3 | 25.1.200 | Message sequencing is compromised in the receiving application. | No workaround is available. |
| 38250181 | Admin service up before kafka (Old seq-init image 1.0.22) could cause kafka admin client might not initialize | The admin service starts before the messaging broker, which prevents proper initialization of the broker client. | 3 | 25.2.100 | Feed upgrades may fail and services may remain in an initialization state. | Old initialization images must be removed before installation or upgrade. |
| 38224529 | Pods are getting into Error state during DD uninstall | Pods enter an error state during uninstall when load balancing is enabled. | 3 | 25.2.100 | The deployment cannot be uninstalled. | The issue must be addressed at the container platform level. |
| 38216046 | DD services in Error/Unknown state after server maintenance | After a full system shutdown and restart, most services remain in error or unknown states and do not recover automatically. | 3 | 25.2.100 | Data processing stops due to service recovery failure. | No workaround is available. |
| 37995257 | TSR Discrepancy Alarm is raised even when the TSR configuration is deleted and re-created | A discrepancy alarm remains active even after redundancy configuration is deleted and recreated. | 3 | 25.1.200 | User confusion occurs due to incorrect alarms. | No workaround is available. |
| 37983780 | Ingress adapter crashes continuously when all kafka-brokers are down | The ingress adapter continuously restarts when messaging brokers are unavailable. | 3 | 25.1.200 | Data ingestion does not function correctly during broker outages. | No workaround is available. |
| 38187166 | Loss of Heartbeat alarm for secondary Redundancy agent is not getting cleared | The heartbeat alarm for a secondary redundancy agent is not cleared after recovery. | 3 | 25.1.200 | No functional impact occurs, but alarm state remains incorrect. | No workaround is available. |
| 38717264 | After DD upgrade from 25.1.200 to 25.2.100, some kafka-broker pods are in "CrashLoopBackOff" status | After an upgrade, broker pods enter a crash loop and fail to recover. | 4 | 25.2.100 | Data transmission stops during the upgrade process. | A worker group reinstallation must be performed when applicable. |
| 38661762 | Few services shows high CPU usage even-if there is no such heavy task hapenning | Some services show high CPU usage even when there is minimal traffic or processing activity. | 4 | 25.2.200 | False alarms are displayed in the user interface. | No workaround is available. |
| 38489994 | Kafka metrics not showing "container" and "service" labels when Prometheus is deployed without operator support | Metrics do not include container and service labels when monitoring is deployed without operator support. | 4 | 24.2.0 | Metrics analysis is limited due to missing context. | No workaround is available. |
| 36666809 | DD-GUI : "Done" button not getting active after saving kafka-template configuration | The Done button remains inactive after saving configuration changes. | 4 | 24.2.0 | The user interface workflow is disrupted. | No workaround is available. |
| 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 | Alarms are missing or contain invalid details when synchronization actions occur while the admin service is unavailable. | 4 | 25.1.200 | Alarm visibility and accuracy are reduced. | No workaround is available. |
| 38055171 | Non-Oracle NF showing as "Not Sending Data" even if the NON_ORACLE topic is getting updated with traffic | The user interface shows a feed as not sending data even though data is present in the messaging topic. | 4 | 25.1.200 | Incorrect status information is shown to the user. | No workaround is available. |
| 38228101 | The screen goes to top when we expand the Metadata attribute that be below in the list | The screen scrolls to the top when a metadata attribute is expanded. | 4 | 25.1.200 | User interface alignment is affected. | No workaround is available. |