4 Resolved and Known Bugs

This chapter lists the resolved and known bugs for Network Analytics Suite Release 25.1.1xx.

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.1xx.

OCNADD Resolved Bugs

Resolved Bugs

Table 4-1 OCNADD 25.1.100 Resolved Bugs

Bug ID Title Description Severity Release Version
37109472 DD UI is stucked on feed creation screen during clone if multiple endpoints are added The feed did not get cloned when modification of endpoints was also done while cloning the feed. 3 24.3.0
37081797 MPS inconsistency in Dashboard The ingress MPS rate was not reflected correctly for the feed. The UI showed the feed as active even when no traffic was running. 3 24.2.0
37080184 DD Export Feature - SFTP IP is Not Accepted in Case IP has 0 octet The validation did not work correctly if any octet of the IP address contained "0." For example, 10.100.0.100 did not work, but 10.100.10.100 worked. 3 24.2.0
37043219 Synthetic feed l3l4 mapping are not getting applied, values are setting back to default after feed creation The L3L4 mapping rules were not saved during feed creation. The L3L4 information was not retained and reverted to default values. 3 24.3.0
36988659 Unable to create Ingress Feed when IntraTls is false The ingress adapter feed was not created when intraTLS was disabled. The initcontainer attempted to load the secret; however, the secrets did not exist, causing feed creation to fail. 3 24.3.0
36988213 filter service not spawning when DD installed on intraTLS false The filter service was not created when intraTLS was disabled. The initcontainer attempted to load the secret; however, the secrets did not exist, causing the service to remain in the init state. 3 24.3.0
36962114 CORRELATED-FILTERED feed does not work when upgraded or replicated to secondary site The CORRELATED-FILTERED feed did not work in the following scenarios: 1) When an upgrade was performed with a CORRELATED-FILTERED feed. 2) When a TSR was created with a CORRELATED-FILTERED feed (the replicated CORRELATED-FILTERED feed to the secondary site did not work). 3 24.3.0
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 failed because the initcontainer attempted to load secrets that were not present for all the services in DD. The customer had chosen intraTLS mode to be disabled. 3 24.2.0
36840514 Multiple "Affected microservice" listing for one alarm of kafka-broker crash The alarm listing showed multiple entries with different Kafka-broker service IDs, even though only one of the Kafka brokers was in a crash loop back state. 3 24.3.0
36714462 DD GUI : L3L4 and Filter details is missing Export Configuration Summary The user was able to see the filter and L3L4 configuration while creating the export configuration. However, the summary screen did not display them. 3 24.2.0
36653748 OCNADD Ingress Feed : Actual message is not printed when OCNADD is unable to decode the message The logging of the discarded message was incomplete. 3 24.2.0
36653996 OCNADD's Loss of Connection Alarm is not cleared automatically even when the service is up The Loss of Connection alarm was not cleared even after the respective service was up and running. 3 24.2.0
37203522 Data Director "Create filter" button grayed out The "Remove Condition" button did not gray out the "Create" button. 3 24.2.0
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" Disabling intraTLS required certificates to be created for each service, which caused the upgrade to fail when some certificates were missing. The intraTLS support was modified so that disabling it no longer required certificates for all internal Data Director services. 3 24.2.0
37093243 In Export config ui, start time backward scrolling is not working for hours field It was not possible to scroll the start time hours field in the backward direction. 4 24.3.0
36950517 Ingress feeds continue to show MPS line chart when there is no traffic running The ingress MPS rate was not reflected correctly for the feed. The UI showed the feed as active even when no traffic was running. 4 24.3.0
36845364 Kafka feed not visible in the GUI The UI did not display an appropriate error message when Kafka ACL-related parameters were not enabled. 4 24.2.0
36844425 Events of alarm is displayed randomly. When there were multiple events for an alarm, they were not listed in a particular order. The events should have been arranged in descending order so that the first event occurred at the bottom, and the latest event (or CLEARED event) appeared at the top. 4 24.3.0
36694587 DD-GUI : Export configuration summery does not show applied filter detail The summary page of the filter creation screen did not display the summary of the created filters. 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 25.1.1xx.

Table 4-2 OCNADD 25.1.100 Known Bugs

Bug Number Title Description Severity Found In Release Customer Impact and Workaround
36745554 Adapter and Alarm pods in crash-loop when datafeed created with incorrect endpoint The issue comes in the HTTP2 feed when the 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 the POD restart.

Workaround:

An incorrect third-party endpoint has been provided, resulting in the following error:

OCL 2024-06-18T14:52:53.351Z ERROR 1 --- [-StreamThread-2] c.o.c.c.o.C.s.t.TopologyBuilderImpl : Error occurred while processing the message. Error: Failed to resolve 'ocnaddthirdpartyconsumeroracle3.kp-wg1' [A(1), AAAA(28)] after 2 queries.

To resolve this issue:

  1. Edit the feed and correct the endpoint so that traffic starts reaching the third party.
  2. If the correct endpoints are not currently available but will be in the future, edit the feed and change the "Data reach failure" parameter from "Do not try again" to "Keep trying".
  3. Adapter pods in the ERROR state must be deleted manually using the following command:

kubectl delete pods --field-selector status.phase=Failed -n <namespace>
37522663 kraft-controller detail not listed on UI dashboard Kafka can be deployed in Kraft controller mode; however, the Kraft controller details are not listed in the services list on the UI. 3 25.1.100

The user will not be able to see the Kraft controller POD details or resource usage details in the UI. However, this will have limited impact, as Kraft deployment is not yet recommended for production.

Workaround:

N/A
37516495 DD High adapter latency in Production The third-party application reported a higher average latency for the end-to-end (E2E) message from DD to the third party. 3 24.2.0

The third-party application reported a higher average latency for the end-to-end (E2E) message from DD to the third party.

The latency was higher because the site was not correctly configured as per the benchmarking guide.

Workaround:

  • Ensure that the DD configuration follows the planning guide.
  • Verify and correct the network latency between DD and the third party.
37514557 DD generating corrupted synthetic packets The third-party application reported that some of the packets generated by the synthetic feed are incorrect. 3 24.2.0

The third-party application encounters failures while decoding HPACK.

Workaround:

NA
37510716 SUPI filter not getting applied correctly in trace The SUPI filter is not functioning correctly in the tracing window. The "Allow" and "Deny" actions are producing incorrect results. 3 25.1.100

The user is unable to filter records by SUPI in the tracing window.

Workaround:

NA
37496136 UI not showing all the opened alarm In the current release, there is a limitation of displaying a maximum of 1000 alarms for each severity type (CRITICAL, MAJOR, MINOR, INFO, WARNING). 3 25.1.100

The user is unable to see the complete list of alarms on the alarm page in the UI.

Workaround:

Connect to AlarmDB using a MySQL client and execute the following queries:

Query Format:

SELECT * FROM ALARM WHERE ALARM_SEVERITY = '<Severity-Type>' AND ALARM_STATUS = '<Status-Type>';

Examples:

  • To show all MAJOR open alarms:

    SELECT * FROM ALARM WHERE ALARM_SEVERITY = 'MAJOR' AND ALARM_STATUS <> 'CLEARED';

  • To show all CRITICAL raised alarms:

    SELECT * FROM ALARM WHERE ALARM_SEVERITY = 'CRITICAL' AND ALARM_STATUS = 'RAISED';
37490359 Frequent heartbeat loss alarm raised and cleared every few seconds. The heartbeat loss alarms are raised and cleared every few seconds. 3 25.1.100

It may cause the alarmDB to be flooded

Workaround:

NA
37467260 DD 24.2.0 || Segmentation does not work as expected The TCP segmentation for the synthetic feed shows a few packets exceeding the configured segmentation length. 3 24.2.0

The processing may fail at the 3rd party application.

Workaround:

NA
37459530 Data Director synthetic adapter opens idle TCP connections The Data Director synthetic feed adapter appears to be opening more connections than the configured limit. These connections remain idle as no data is observed on them. 3 24.2.0

There is no customer impact.

Workaround:

NA
37432163 One of the pcap export stops without any reason

Two exports were configured, but one of the PCAP exports stops and remains in the "in progress" state without completing.

Additionally, when traffic stops and resumes after a few hours, the PCAP export does not resume.

 3 25.1.100

The PCAP export will be stopped.

Workaround:

Restart the export service
37431732 Pcap export stops as soon the config service restarts The PCAP and CSV exports are configured and work continuously; however, upon restarting the configuration service, the PCAP export stops. 3 25.1.100

The PCAP export will be stopped.

Workaround:

NA
37411881 Occasional Kafka Feed Creation Error for Correlated Kafka Feed Occasionally, Kafka feed creation fails for a correlated Kafka feed. The Admin service successfully creates the topic but fails afterward with an unknown exception. 3 25.1.100

Correlated Kafka feed creation may fail.

Workaround:

Retry the correlated feed creation from UI
37405526 HPACK incorrect in synthetic feed DD is not advertising HPACK correctly in the synthetic feed. It is supposed to implement only static HPACK as per the RFC, but it advertises dynamic HPACK without using dynamic indexing. 3 24.2.0

HPACK incorrect for the HTTP2 message encoding while synthesizing the packet.

Workaround:

NA
37404206 Alarm for "topic not available" gets cleared even if the topic is not created The "topic unavailable" alarm is being raised and cleared repeatedly when the Kafka topic is not available. The alarm should not be cleared if the topic has not been created, and instead, the event should be appended to the existing alarm. 3 25.1.100

It may cause the alarmDB to be flooded .

Workaround:

The alarms can be stopped by creating the required topic in the Kafka.
37403907 Storage adapter does not resume storing xDR after upgrade It has been observed that after upgrading from version 24.2.0, the storage of xDRs stops. 3 25.1.100

The storage of the xDRs is stopped after the upgrade.

Workaround:

The corresponding storage adapter should be restarted.
37375067 DD UI: For alarm date query future data is being highlighted by default Future date is coming in the end date while selecting the end date in the alarm. 3 25.1.100

There is no or minimal customer impact.

Workaround:

NA
37543035 UI not accessible after configuration service re-start The UI becomes inaccessible when the correlation configuration is created and the configuration service is restarted for any reason. 3 25.1.100

The user may not be able to access the UI.

Workaround 1: Edit Deployment for Configuration Service

Edit the configuration service deployment and add the following parameter in the environment variables:

 - name: logger.levels.com.oracle.cgbu.cne.ocnadd.configuration.correlation.service.configuration   value: DEBUG

Workaround 2: Update Custom Values and Perform Helm Upgrade

  1. Update the parameter in the ocnaddconfiguration service section of the custom values file:
    ocnaddconfiguration:
  name: ocnaddconfiguration
  env:
    logger.levels.com.oracle.cgbu.cne.ocnadd.configuration.correlation.service.configuration: DEBUG
  2. Perform a Helm upgrade of the management group:

    helm upgrade <management-release-name> -f ocnadd-custom-values-<mgmt-group>.yaml --namespace <source-release-namespace> <helm_chart>

Example:

helm upgrade mgmt -f custom-templates/ocnadd-custom-values-mgmt.yaml -n mgmt-ns ocnadd
37149677 Adapter feed down until adapter is rebooted When there are frequent disconnects from the 3rd party for the consumer adapter feeds, it has sometimes been observed that Kafka stream processing threads get detached from the consumer group and stop consuming data. 3 24.2.0

The data consumption from Kafka may stop, and as a result, adapter feeds may stop sending data to the 3rd party.

Workaround:

The corresponding consumer adapter instances should be restarted.
37556884 ATS execution stops abruptly sometimes for ACL execution The ATS test suite execution sometimes stops for the features which require Kafka ACL support.     The user will not be able to see the final execution result with number of testcases passes/failed status.

Workaround:

Run the features requiring ACL using CLI:

  1. Exec into the ATS pod: Run the following command in the namespace where ATS is running:

    kubectl exec -it -n <namespace-name> <ats-pod-name> -- bash

  2. Open and update the environ.sh file: Navigate to the following location and verify/update the setup-related parameters (as provided in the Jenkins pipeline variables):

    vi /var/lib/jenkins/ocnadd_tests/environ.sh

  3. Navigate to the feature file location: Move to the directory containing the feature file for the terminated test case:

    cd /var/lib/jenkins/ocnadd_tests/features/newfeatures/nadd/stage1/group1

  4. Run the test case(s) using the behave command:

    behave -f plain <Feature>/<FeatureFile>.feature --tags=<TagNameForTestcase1>,<TagNameForTestcase2>

    For example:

    behave -f plain TDR_CorrelationService/TDR_CorrelationService.feature --tags=@TDR_ConfigurationIsCreatedWithFewOrAllOptionalXDRContentForCorrelatedAndCorrelatedFilteredFeed,@TDR_ConfigurationIsCreatedWhenMetaDataHeadersDataOptionIsSelectedForIncludeMessageWithXDRCorrelatedAndCorrelatedFilteredFeed

  5. Check the results after running.
36666809 DD-GUI : "Done" button not getting active after saving kafka-template configuration It is observed that while editing the Kafka-template configuration, after making changes and clicking the "Save" button, the user needs to click the "Done" button to exit the screen. However, the "Done" button does not become active. 4 24.2.0

There is no customer impact.

Workaround:

NA
37407778 CPU Overload false alarms are getting generated The health monitoring service reports CPU overload logs; however, according to Prometheus metrics, the actual usage does not exceed the threshold. 4 25.1.100

There is no or minimal customer impact.

Workaround:

NA