4 Resolved and Known Bugs
This chapter lists the resolved and known bugs for Network Analytics Suite Release 23.4.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 23.4.x.
OCNWDAF Resolved Bugs
OCNWDAF Resolved Bugs for OCNWDAF 23.4.0
Table 4-1 OCNWDAF Resolved Bugs for OCNWDAF 23.4.0
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 35797700 | The ocn-nwdaf-data-collection-controller and ocn-oam-simulator-service are not available in the NWDAF 23.3.0 MoS package. | The ocn-nwdaf-data-collection-controller and ocn-oam-simulator-service images were unavailable in the OCNWDAF 23.3.0 MoS package. | 2 | 23.3.0 |
| 35814281 | Oracle Communication Consulting - Lab : NWDAF 23.3.0: NWDAF Images Missing in MoS patch | Some OCNWDAF images were missing in the 23.3.0 MoS patch. | 2 | 23.3.0 |
| 35931448 | Error occurred while fetching data from NWDAF GUI | Errors were observed while fetching data from the OCNWDAF GUI.
The error message "An Error occurred while fetching the data" is displayed in ML Model Selector, Slice Load Monitoring, Geofence Monitoring, and Monitoring screens. |
3 | 23.3.0 |
| 35892172 | Maps are not available in NWDAF even with internet reachable | Maps were not available in the OCNWDAF though the internet connection was present.
OCNWDAF 23.3.0 GUI was configured with CNC Console 23.3.0 or 23.2.0. When user tries to access the monitoring tab, data was not displayed in the map area. CNC Console releases 23.3.0 and 23.2.0 had a constraint to filter out HTTP HEAD requests. OCNWDAF uses HEAD requests to test internet availability. |
3 | 23.3.0 |
| 35824376 | The charts/ocn-smf-simulator-service/values.yaml is pointing to a deprecated service. | The charts/ocn-smf-simulator-service/values.yaml file was pointing towards a deprecated service. | 3 | 23.3.0 |
| 35824361 | CNC console installation and integration with NWDAF Portal Suite is not clear. | The procedure for CNC console installation and integration with OCNWDAF Portal Suite was not explained clearly in the Oracle Communications Networks Data Analytics Function User Guide. | 3 | 23.3.0 |
| 35751995 | ATS test cases in preconfigured pipelines in Jenkins are not listed | ATS testcases were not listed in the preconfigured Jenkins pipeline. | 3 | 23.3.0 |
| 35905766 | NWDAF install failing with "timed out waiting for the condition" | The OCNWDAF installation was failing with "timed out waiting for the condition" error. | 4 | 23.3.0 |
Note:
Resolved bugs from 22.1.0, 23.1.0, 23.1.0.0.2, 23.2.0, 23.3.0, and 23.3.0.0.1 have been forward ported to Release 23.4.0.OCNADD Resolved Bugs
OCNADD Resolved Bugs for OCNADD 23.4.0.0.1
Table 4-2 OCNADD Resolved Bugs for OCNADD 23.4.0.0.1
| Bug Number | 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; junk characters were seen when there was a message with a long URL containing special characters such as “{”, “[”, “:”, or “". | 3 | 23.4.0 |
| 36681307 | Data Director GUI page states "No Worker Groups are installed" when there is a Worker Group | The UI was unable to fetch the Worker Group
details. When clicking on "Select Worker Group" in the UI, the
following message was displayed: "No Worker Groups are
installed. Please install at least one Worker Group to configure
your Data Director." |
3 | 23.4.0 |
OCNADD Resolved Bugs for OCNADD 23.4.0
Table 4-3 OCNADD Resolved Bugs for OCNADD 23.4.0
| Bug Number | Title | Description | Severity | Found In Release |
|---|---|---|---|---|
| 36070022 | Adapters not upgrading after DD upgrade | The adapter did not upgrade, and the adapter pods did not restart, due to Kubernetes fabric client library issue. | 2 | 23.4.0 |
| 36072553 | Unable to create CORRLEATED_FILTERED kafka feed after upgrade | The correlated filter feed was not created as the enum feed type was incorrectly updated in the upgrade script. | 2 | 23.4.0 |
| 36072078 | Adapter is constantly trying to send messages to Disposed connection after 3rd Party is brought Down | CPU resource utilization by the adapters was high.
This issue was observed only when the third party endpoint was completely down and all the connection threads were disposed. |
2 | 23.4.0 |
| 35319683 | Zookeeper showing only 2 instance instead of 3 | Correct number of Zookeeper instances was listed at the backend, but the OCNADD GUI displayed lesser number of Zookeeper instances. | 3 | 23.2.0 |
| 35651501 | Not able to create 4 parallel Egress filters for only ALLOW or DENY | Two parallel filters could be created for Egress, but the user was able to create four parallel filters for Ingress. | 3 | 23.3.0 |
| 35667048 | Create Kafka Feed is allowing any user entry in ACL user and Host Name fields | In the 'Kafka Feed' creation, the input fields were incorrectly allowing all user entries in ACL 'user' and 'Host Name' fields. For example:
ACL User = asdf*** or asdfhask8*((**))^%$ |
3 | 23.3.0 |
| 35944566 | Unable to fetch Kafka feed after upgrade from 23.3.0 to 23.4.0 | Unable to fetch Kafka feed after upgrade as the retentionTime column was incorrectly updated in the upgrade script. | 3 | 23.4.0 |
| 36030381 | KPI settings options such as status code, service name getting applied to all KPIs | While configuring KPIs some settings were getting applied to all KPIs. Validation was missing on the GUI to restrict some of the options to the available KPIs. | 3 | 23.4.0 |
| 36030528 | N12 and N13 missing their respective service name in KPI query | The option to select the service name was not available in the KPI settings for the query. | 3 | 23.4.0 |
| 36278932 | Child namespace requirement for installing Data Director | The installation guide for release 23.4.0 needed an update to include the information if the HNS package is not available. | 3 | 23.4.0 |
| 35639519 | OCNADD UI: Replicated Feed Name missing in exported csv of kafka feed | When replicated Kafka feed was created and the information was exported in CSV format using the export functionality, the Replicated Feed Name did not get populated. | 4 | 23.3.0 |
| 35594082 | Style issues on OCNADD GUI | The OCNADD GUI had some style issues. The GUI displayed content with extra spaces or different font sizes. | 4 | 23.3.0 |
Note:
Resolved bugs from 22.1.0, 23.1.0, 23.2.0, 23.2.0.0.1, and 23.3.0 have been forward ported to Release 23.4.0.4.3 Known Bug List
Known Bugs tables list the known bugs and associated Customer Impact Statements.
OCNWDAF 23.4.0 Known Bugs
The following table lists the known bugs for OCNWDAF Release 23.4.x.
Table 4-4 OCNWDAF 23.4.0 Known Bugs
| Bug Number | Title | Description | Severity | Found in Release | Customer Impact |
|---|---|---|---|---|---|
| 36068437 | NWDAF subscriptions with ONE_TIME value in notifMethod send more than 1 notification | The OCNWDAF subscriptions with "ONE_TIME" as a value for the Notification Method sends more than one notification. | 3 | 23.4.0 |
The NF consumer may receive two similar notification reports instead of one report. Workaround: No workaround available. |
| 36068419 | 3gpp NWDAF - Error message is wrong when trying to create a sub with MTLF down | The user tries to create a subscription when the MTLF service is down and an incorrect 3GPP NWDAF error message is displayed. | 3 | 23.4.0 |
The NWDAF subscription is not created, but an incorrect error message is displayed to the user. Workaround: No workaround available. |
| 36068416 | Change NWDAF Spring Boot Parent | The OCNWDAF Spring Boot Parent must be changed. | 3 | 23.4.0 |
No customer impact. Workaround: No workaround available. |
| 36068412 | 3GPP Geofence subscriptions receive notifications before the startTs date | The 3GPP Geofence subscriptions are receiving notifications before the commencement of the timestamp mentioned in the startTs parameter. | 3 | 23.4.0 |
It is an edge case where the notification report is present before the expected date. Workaround: No workaround available. |
| 36068409 | SLL 3GPP subscriptions ONE_TIME send two notifications | The 3GPP Slice Load Level "ONE_TIME" subscriptions are sending two notifications. | 3 | 23.4.0 |
It is an edge case when the NF consumer receives two similar notification reports instead of one notification report. Workaround: No workaround available. |
| 36073817 | GUI Slice Load filter being applied when coming from NF Load | After you set the date range on the NF Load Monitoring page on the OCNWDAF GUI, if you proceed to the Slice Load Monitoring page, an extra filter appears in the filter bar. | 4 | 23.4.0 |
Two filters "Date Range" and "Last" are incorrectly displayed. Workaround: No workaround available. |
| 36068433 | ATS: Update function should be flexible enough to update any parameter's value from the subscription payload. | In the ATS, the Update function must update any parameter's value from the subscription payload. | 4 | 23.4.0 | No customer impact.
Workaround: No workaround available. |
| 36068432 | PV API Consumer not logging request headers | The PV API consumer is not logging request headers. | 4 | 23.4.0 |
The internal tool that uses it to simulate the NF consumer is not displaying headers at the log level. This is visible to the user. Workaround: No workaround available. |
OCNADD Known Bugs
OCNADD 23.4.0.0.1 Known Bugs
There are no new known bugs in this release. Known bugs from 23.4.0 have been forward ported to Release 23.4.0.0.1.
OCNADD 23.4.0 Known Bugs
The following table lists the known bugs for OCNADD Release 23.4.x.
Table 4-5 OCNADD 23.4.0 Known Bugs
| Bug Number | Title | Description | Severity | Found in Release | Customer Impact |
|---|---|---|---|---|---|
| 36008271 | Synthetic feed adapter stops sending packets | It has been observed that a OCNADD consumer adapter sometimes stops the traffic to a particular third party application.
The third party application frequently closes the connection with the OCNADD consumer adapter for the synthetic feed. As a result, the Kafka consumer threads are detaching from the consumer group and stop reading the traffic. |
2 | 23.3.0 |
Traffic to the specific third party applications may be disrupted. Workaround: Restart the consumer adapter. |
| 36038818 | Log messages: error raising alarm | When an alarm is raised, an error reported in the adapter service. | 3 | 23.3.0 |
The original alarm is raised and the subsequent event does not get updated in the alarm. Workaround: No workaround available. |
| 36038805 | OCNADD GUI reloading a page takes 40 seconds | The OCNADD GUI takes longer to reload after the feed configuration is updated. | 3 | 23.3.0 |
The user has to wait for a longer time to perform actions on the GUI. Workaround: No workaround available. |
| 36080286 | Egress filter of worker group1 is showing feeds of other WG as well in "association" dropdown | When an egress filter is created, the adapter feed created for one worker group appears for the other worker group during the filter's association with the feed. | 3 | 23.4.0 |
The user can incorrectly associate the filter with the data feed from the different worker groups. Workaround: No workaround available. |
| 36027600 | Worker-group not listed when MTLS is true | MTLS is not working for the OCNADD GUI service. | 3 | 23.4.0 |
OCNADD GUI is not working correctly when MTLS is enabled. Workaround: Disable MTLS in the 23.4.0 and previous releases of OCNADD deployments. |
| 36022704 | Seeing a sudden drops in KPI's count after correlation service pod restarts | The Prometheus metric counters reset when the container restarts. When the correlation service pods restart, the Prometheus metric counter resets. The GUI fetches these metrics from the Prometheus. Therefore, a sudden drop in the KPI count is observed. | 3 | 23.4.0 |
The KPI graph displays a sudden dip; the user may interpret this as a network issue. Workaround: Run the following Prometheus query to verify this scenario:
|
| 36022691 | Egress Filter Metrics for "kafka feed" is not displayed | The filter metrics for the Kafka feed associated with the Egress filter are not displayed. | 3 | 23.4.0 |
User cannot obtain the Egress filter metrics for the Kafka feed. Workaround: No workaround available. |
| 36020488 | Deregistration and Registration Alarm for UIRouter and GUI is not logging on UI and database | The GUI and the GUI router service cannot register (and deregister) with the health monitoring service. | 3 | 23.4.0 |
The health status of the GUI and GUI router service is not displayed on the dashboard. Workaround: No workaround available. |
| 35971255 | After selecting KPI interval time also showing other timestamp data | The Prometheus processes the queries and reports the metrics in UTC format, and the client must interpret the time in UTC format. | 3 | 23.4.0 |
Incorrect information is displayed in the GUI. Workaround: No workaround available. |
| 35926969 | Edit function in Correlation config not working properly | The user cannot change the correlation mode and must reselect all the fields to configure a new correlation mode. | 3 | 23.4.0 |
The user cannot change the correlation type from SUDR to TDR. Workaround: Select each field individually in the correlation configuration to modify the correlation mode. |
| 35842279 | Data Director GUI Display issue 5G PROD | The feed status is displayed as inactive. However, the feed is working correctly, and a third party consumer can receive the data from the feed. | 3 | 23.4.0 |
Incorrect information is displayed in the GUI. Workaround: No workaround available. |
| 35677070 | In UI about section the "Copyright Information" is taking to 'About' DD section | In the GUIs "About" section, the "Copyright Information" hyperlink is incorrectly linked to the 'About' DD section. | 3 | 23.3.0 |
Incorrect information is displayed in the GUI. Workaround: No workaround available. |
| 35679888 | In Dashboard the Average msg size display disappears | In the GUI dashboard, the average message size display disappears when one of the producers goes down or stops sending traffic. | 4 | 23.3.0 |
Incorrect information is displayed in the GUI. Workaround: No workaround available. |
| 36017165 | KPI's graph not displaying correct information | The label on the KPI graphs is incorrect; "msg/sec" is displayed instead of "transactions/sec". | 4 | 23.4.0 |
Incorrect information is displayed in the GUI. Workaround: No workaround available. |
| 36071681 | In N12 and N13 service name labels are not correct | The labels identifying the N12 and N13 transactions are incorrect. | 4 | 23.4.0 |
Incorrect information is displayed in the GUI. Workaround: No workaround available. |
| 36053334 | Configuration service logging error while editing filters | Error trace is incorrectly logged as an information log. | 4 | 23.4.0 |
No customer impact. Workaround: No workaround available. |