4 Resolved and Known Bugs
This chapter lists the resolved and known bugs for Network Analytics Suite Release 24.3.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.3.x.
OCNADD Resolved Bugs
Release 24.3.0.0.1
Table 4-1 OCNADD 24.3.0.0.1 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 37455083 | OCNADD GUI Requirements workaround request | For the OCNADD GUI to load successfully, the
following URLs needed to be accessible from the user's location:
These URLs either had to be accessible or a workaround needed to be provided. Without access, the GUI did not load, causing their pre-production DD environment to fail. This issue affected a new DD customer who was attempting to set up test and production labs. |
3 | 23.4.0 |
Release 24.3.0
Table 4-2 OCNADD 24.3.0 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 36623369 | DD GUI display issue in status and worker group name | It was observed that opening each site in the same browser caused the worker group (WG) name to be the same as the one initially opened. Additionally, the feed status "Fetching data" was incorrectly shown on the UI. | 2 | 23.4.0 |
| 36564047 | Kafka-broker STS not pointing to headless service | The Kafka broker STS manifest showed the service name "kafka-broker" instead of "kafka-broker-headless," so the pod headless FQDN was not pingable. Ideally, it should have pointed to the headless service. | 3 | 23.4.0 |
| 36751592 | CORRELATED_FILTERED correlation not replicating to mated site | In the case of the two-site redundancy feature, the correlation configuration was not replicated to the mate site when the Kafka feed type was "CORRELATED_FILTERED." | 3 | 24.2.0 |
| 36737090 | DD-OCCM: backup-related OCCM files were missing in the package | The manual backup and restore did not work if OCCM was enabled. | 3 | 24.2.0 |
| 36697937 | 24.2.0-Perf: ocnadd aggregation pods spinning beyond 90% CPU with 135K aggregation traffic | High resource utilization was seen in the aggregation service instances for high traffic rates (135K+ MPS). | 3 | 24.2.0 |
| 36697097 | Kafka without Zookeeper: DD worker group installation was stuck when installing without Zookeeper | The installation of the worker group was stuck as there were no certificates created using OCCM. | 3 | 24.2.0 |
| 36681307 | Data Director GUI page stated "No Worker Groups are installed" when there was a Worker Group | No worker group was allowed to be selected if a default worker group was used in the centralized deployment. | 3 | 23.4.0 |
| 36653996 | OCNADD's Loss of Connection alarm was not cleared automatically even when the service was up | The Loss of Connection alarm was not cleared even after the respective service was up and running. | 3 | 24.2.0 |
| 36590208 | Export functionality for CSV/PCAP was not working when applied with filters | The filters worked fine; however, if the filter returned a low number of records in the export query, the export failed. | 3 | 24.2.0 |
| 36688812 | DD-GUI: The Trace response showed one more page (with improper data) even if all records were already displayed | An additional page appeared on the trace screen even if all the records in the trace query had been displayed on the first page. | 4 | 24.2.0 |
| 36669047 | Alarm for "Kafka Consumption Paused" was raised even if all the topics were receiving continuous traffic | Alarms were raised to indicate that traffic consumption from Kafka was paused, even though the topics continued to receive traffic. | 4 | 24.2.0 |
| 36671638 | Alarms such as "SFTP Service Unreachable" and "No Data Available for Export" were not getting cleared | Alarms for the "SFTP service unreachable" and "No Data Available" were not cleared even after the issues causing the alarms were resolved. | 4 | 24.2.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 24.3.x.
Release 24.3.0.0.1
There are no new known bugs in this release.
Release 24.3.0
Table 4-3 OCNADD 24.3.0 Known Bugs
| Bug Number | Title | Description | Severity | Found In Release | Customer Impact & Workaround |
|---|---|---|---|---|---|
| 36745554 | Adapter and Alarm pods in crash-loop when datafeed created with incorrect endpoint | The issue occurs in the HTTP2 feed when incorrect endpoints are configured in the destination endpoint. | 3 | 24.2.0 | Too many alarms and logs may cause the ephemeral
storage usage to exceed, resulting in a POD restart.
Workaround: An incorrect third-party endpoint is provided, and the error is as follows:
|
| 37109472 | DD UI is stuck on feed creation screen during clone if multiple endpoints are added | The feed is not getting cloned when modification of endpoints is also done while cloning the feed. | 3 | 24.3.0 | Cloning the feed may not be possible in specific
scenarios, increasing the configuration effort.
Workaround: Create a new feed from the UI without using the cloning option. |
| 37081797 | MPS inconsistency in Dashboard | The ingress MPS rate is not getting reflected correctly for the feed. The UI shows the feed as active when there is no traffic running. | 3 | 24.2.0 | MPS reporting is inaccurate and may confuse users
about the actual status.
Workaround: Use Grafana dashboards to check the actual MPS and feed status. |
| 37080184 | DD Export Feature - SFTP IP is Not Accepted in Case IP has 0 octet | The validation is not working correctly if any octet of the IP address contains "0," for example, 10.100.0.100 is not working, but 10.100.10.100 is working. | 3 | 24.2.0 | The customer will not be able to use the IP address
containing any octet as "0" for the SFTP server.
Workaround: The SFTP server IP address should not contain "0" in any octet. |
| 37043219 | Synthetic feed L3L4 mapping is not getting applied, values are resetting to default after feed creation | The L3L4 mapping rules are not getting saved during the feed creation. The L3L4 information is not being saved and is reverting to default values. | 3 | 24.3.0 | L3L4 mapping rules are not saved, increasing the
configuration effort for the user.
Workaround: Edit and update the Synthetic feed mapping from the "L3L4 Configure" page and save it. |
| 36988659 | Unable to create Ingress Feed when IntraTls is false | The ingress adapter feed is not getting created when intraTLS is disabled. The init container attempts to load the secret, but the secrets do not exist, and feed creation fails. | 3 | 24.3.0 | Users cannot create ingress adapter feeds with
intraTLS disabled.
Workaround: Enable intraTLS and create certificates for all services, regardless of intraTLS mode. |
| 36988213 | Filter service not spawning when DD is installed with intraTLS disabled | The filter service is not getting created when intraTLS is disabled. The init container attempts to load the secret, but the secrets do not exist, and the service stays in the init state. | 3 | 24.3.0 | No impact on the user, as the filter service is only
required when Kafka feeds are used, and with Kafka feeds, intraTLS
must always be enabled.
Workaround: Enable intraTLS and create certificates for all services, regardless of intraTLS mode. |
| 36962114 | CORRELATED-FILTERED feed does not work when upgraded or replicated to secondary site | The CORRELATED-FILTERED feed does not work in the following scenarios: 1) when an upgrade is performed with CORRELATED-FILTERED feed; 2) when TSR is created with CORRELATED-FILTERED feed (the replicated CORRELATED-FILTERED feed to the secondary site does not work). | 3 | 24.3.0 | The correlated filtered feed will not work
post-upgrade and requires restarting the filter service.
Workaround: Restart the filter service to resume data on the CORRELATED-FILTERED topic. |
| 36907884 | DD upgrade from 23.4.0 to 24.2.0 fails with: warnings.go:70 unknown field "spec.template.spec.volumes[0].secret.secret" | The upgrade fails as the init container tries to load the secrets that are not present for all services in DD. The customer has chosen to disable intraTLS. | 3 | 24.2.0 | The upgrade fails when the secrets for all DD
services are not available. The customer needs to create additional
certificates even though they should not be required with intraTLS
disabled.
Workaround: Enable intraTLS and create certificates for all services, regardless of intraTLS mode. |
| 36840514 | Multiple "Affected microservice" listings for one alarm of kafka-broker crash | The alarm listing shows multiple entries with different Kafka-broker service IDs, even though only one Kafka broker is in a crash-loop back state. | 3 | 24.3.0 | Multiple alarms with different service IDs for the
same broker may confuse users into believing that multiple Kafka
broker PODs are crashing.
Workaround: NA |
| 36715614 | DD-GUI : Dashboard showing incomplete information for kafka-broker pod status | The Kafka service status reporting does not take into account the status of all the PODs and shows the service as Active even though one or more Kafka broker PODs are down. | 3 | 24.2.0 | The correct status of the Kafka broker service may
not be known to the user.
Workaround: NA |
| 36714462 | DD GUI : L3L4 and Filter details are missing from Export Configuration Summary | The user is able to see the filter and L3L4 configuration while creating the export configuration. However, the summary screen is not showing the same. | 3 | 24.2.0 | No impact.
Workaround: NA |
| 36653748 | OCNADD Ingress Feed : Actual message is not printed when OCNADD is unable to decode the message | The logging of the discarded message is not complete when OCNADD is unable to decode the message. | 3 | 24.2.0 | No impact.
Workaround: NA |
| 36653996 | OCNADD's Loss of Connection Alarm is not cleared automatically even when the service is up | The Loss of Connection alarm is not getting cleared even after the respective service is up and running. | 3 | 24.2.0 | This issue can mislead the user into believing that
the service has not come up correctly.
Workaround: NA |
| 37093243 | In Export Config UI, start time backward scrolling is not working for hours field | It is not possible to scroll the start time hours field in a backward direction. | 4 | 24.3.0 | The customer may not be able to scroll the start
time in a backward direction.
Workaround: NA |
| 36950517 | Ingress feeds continue to show MPS line chart when there is no traffic running | The ingress MPS rate is not reflected correctly for the feed. The UI shows the feed as active even when there is no traffic running. | 4 | 24.3.0 | MPS reporting is inaccurate and may confuse users
about the actual status.
Workaround: Use Grafana dashboards to check the actual MPS and feed status. |
| 36845364 | Kafka feed not visible in the GUI | The UI does not display a more appropriate error message when Kafka ACL-related parameters are not enabled. | 4 | 24.2.0 | The user is unable to find the cause of the failure
with the current UI message.
Workaround: NA |
| 36844425 | Events of alarm are displayed randomly | When there are more than one event for the alarms, the events are not listed in any particular order. The events should be in an order (preferably descending), such that the first event for the alarm is at the bottom and the latest event (or the CLEARED event) is at the top. | 4 | 24.3.0 | No impact.
Workaround: NA |
| 36694587 | DD-GUI : Export configuration summary does not show applied filter details | The summary page of the filter creation screen does not show the summary of the created filters. | 4 | 24.2.0 | No impact.
Workaround: NA |
| 36666809 | DD-GUI : "Done" button not getting active after saving kafka-template configuration | It is observed that while editing the kafka-template configuration, after saving the configuration, the "Done" button does not get activated. | 4 | 24.2.0 | No impact.
Workaround: NA |