4 Resolved and Known Bugs
This chapter lists the resolved and known bugs for Network Analytics Suite Release 23.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:
- Critical outages.
- 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.3.x.
OCNWDAF Resolved Bugs
Table 4-1 OCNWDAF Resolved Bugs for OCNWDAF 23.3.0.0.1
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 35892172 | Maps are not available in OCNWDAF though internet is available. |
In the OCNWDAF GUI, when using CNC Console versions 23.3.0 or 23.2.x, a message "No Data Available" was displayed in the map area though an internet connection was available. |
3 | 23.3.0 |
| 35824361 | CNC console installation and integration with OCNWDAF Portal Suite is not clear. | Details of CNC Console installation and integration with the OCNWDAF portal were missing in the documentation. | 3 | 23.3.0 |
| 35824376 | The charts/ocn-smf-simulator-service/values.yaml file is pointing to a deprecated service. | The charts/ocn-smf-simulator-service/values.yaml file was referring to the configuration service which is deprecated.
|
2 | 23.3.0 |
| 35880649 | CVE-2023-40167: ECLIPSE Jetty update to atleast 12.0.1, 11.0.16, 10.0.16, or 9.4.5 |
CVE-2023-40167 is a known vulnerability. Eclipse Jetty 12.0.1, 11.0.16, 10.0.16, and 9.4.52 addressed CVE-2023-40167. The CVSS v3.1 score in NVD is 5.3. Jetty accepts the `+` character preceding the specified content length in the HTTP/1 header field, and this is acceptable by the RFC and other servers, which routinely reject such requests with 400 responses. |
2 | 23.3.0 |
| 35947044 | OCNWDAF GUI indicates thresholds for deleted subscriptions when the data source is the Data Director. | When the Data Director was the data source, the OCNWDAF GUI displayed thresholds for deleted subscriptions as old subscriptions were not adequately cleaned. | 3 | 23.3.0 |
Note:
Resolved bugs from 22.1.0, 23.1.0, 23.1.0.0.2, 23.2.0, and 23.3.0 have been forward ported to Release 23.3.0.0.1.OCNWDAF Resolved Bugs
Table 4-2 OCNWDAF Resolved Bugs for OCNWDAF 23.3.0
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 35611856 | Fortify Static Scanning on NWDAF service | Fortify's Static Scanning on NWDAF service discovered security vulnerabilities. | 4 | 23.3.0 |
| 35641878 | Fortify Static Scanning on ocn-nwdaf-analytics-info service | Fortify's Static Scanning on ocn-nwdaf-analytics-info service discovered security vulnerabilities. | 4 | 23.3.0 |
| 35688375 | Restfuzz testing on ocn-nwdaf-data-collection-service | Fuzz testing on ocn-nwdaf-data-collection-service discovered security issues. | 4 | 23.3.0 |
| 35688398 | Restfuzz testing on ocn-nwdaf-data-collection-controller-service | Fuzz testing on ocn-nwdaf-data-collection-controller-service discovered security issues. | 4 | 23.3.0 |
Note:
Resolved bugs from 22.1.0, 23.1.0, 23.1.0.0.2, and 23.2.0 have been forward ported to Release 23.3.0.OCNADD Resolved Bugs
OCNADD Resolved Bugs for OCNADD 23.3.0.0.1
There are no resolved bugs in this release. Resolved bugs from 23.3.x have been forward ported to Release 23.3.0.0.1.
OCNADD Resolved Bugs
OCNADD Resolved Bugs for OCNADD 23.3.0
Table 4-3 OCNADD Resolved Bugs for OCNADD 23.3.0
| Bug Number | Title | Description | Severity | Found In Release |
|---|---|---|---|---|
| 35386371 | OCNADD services are not upgraded and rolled back in defined order. | During the OCNADD upgrade (or rollback), the services did not upgrade (or roll back) in the required order resulting in service errors. | 3 | 23.2.0 |
| 35396464 | OCNADD SEPP/NRF/SCP aggregation pod CPU utilization reaches 90%, when weighted load balancing or filtering feature is enabled with 64K MPS aggregated traffic. | Resource utilization increased when the user configured load balancing or filtering on Data Feeds at a higher throughput rate. | 3 | 23.2.0 |
| 35399574 | Retry timer in synthetic feed should limit to a max value and reset after the max value is reached. | The retry timer increased exponentially in case of third-party connection failure for synthetic feeds. | 3 | 23.2.0 |
| 35320886 | Changes are required in the generate_certs.sh script to handle the SAN in the client CSR. | A request was received to introduce changes in the script for generating CSR to handle the SAN in the client CSR. | 3 | 23.1.0 |
| 35398515 | Install failed with the error message, "Error: container has runAsNonRoot and image will run as root". | The error "Error: failed pre-install" occurred during installation due to environment-specific PodSecurityPolicy. | 3 | 23.1.0 |
| 35391713 | Configuration Service does not expose Prometheus Endpoint correctly. | Prometheus was unable to scrape data from the Configuration Service. | 3 | 23.2.0 |
| 35391812 | Subscription was created for a non-existing target consumer. | Validation to verify if the target consumer name exists was missing. | 3 | 23.2.0 |
| 35385608 | Disassociation does not occur, when filter type is changed from Ingress to Egress. | Filter does not disassociate when the filter type changed from Ingress to Egress. | 3 | 23.2.0 |
| 34903802 | MsgCopy Packet loss between SCP or NRF and OCDD Kafka. | During long traffic runs from NFs, a difference between the total messages copied by NRF (or SCP) and total messages received at Kafka was observed. | 3 | 22.0.0 |
| 35385593 | Older Aggregation entries are not deleted on simultaneous restart of Configuration and Aggregation pods. | When multiple (or simultaneous) Aggregation and Configuration services restart, the Configuration service tries to reach the old pod IPs. | 4 | 23.2.0 |
| 35385541 | Wrong endpoint URI and storage values in HealthDB. | The UI Router and Cache services registered with the Health Monitoring service using incorrect information. | 4 | 23.2.0 |
Note:
Resolved bugs from 22.1.0, 23.1.0, 23.2.0, and 23.2.0.0.1 have been forward ported to Release 23.3.0.4.3 Known Bug List
Known Bugs tables list the known bugs and associated Customer Impact Statements.
OCNWDAF Known Bugs
OCNWDAF 23.3.0.0.1 Known Bugs
There are no known bugs in this release.
OCNWDAF 23.3.0 Known Bugs
There are no known bugs in this release.
OCNADD Known Bugs
OCNADD 23.3.0.0.1 Known Bugs
The following table lists the known bugs for OCNADD Release 23.3.0.0.1.
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 36038818 | Log messages: error raising alarm | There is an error reported in the adapter service during the raising of the alarm. | The original alarm is raised and the subsequent event does not
get updated in the alarm
Workaround: NA |
3 | 23.3.0 |
| 36038805 | ocnadd GUI reloading a page takes 40 seconds | The OCNADD UI takes longer to reload after the feed configuration has been updated. | The user has to wait for a longer time to perform the UI
actions.
Workaround: NA |
3 | 23.3.0 |
| 36008271 | Synthetic feed adapter stops sending packets | It has been observed that a OCNADD's consumer adapter sometimes stops the traffic to a particular third-party application. The third-party application frequently closes the connection with the DD consumer adapter for the synthetic feed, as a result, the Kafka consumer threads are detaching from the consumer group and stop reading the traffic. | Traffic to specific third-party applications (keysight) may be
disrupted.
Workaround: The workaround is to restart the consumer adapter. |
2 | 23.3.0 |
OCNADD Known Bugs
OCNADD 23.3.0 Known Bugs
The following table lists the known bugs for OCNADD Release 23.3.x.
Table 4-4 OCNADD 23.3.0 Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 35319683 | Zookeeper displays only two instances instead of three. | A correct number of Zookeeper instances is listed at the backend, but the GUI incorrectly displays fewer Zookeeper instances. |
No customer impact. However, incorrect display causes user confusion. Workaround: No workaround available. |
3 | 23.2.0 |
| 35651501 | Unable to create four parallel Egress filters only for ALLOW or DENY operations. | Users can create two parallel filters for Egress traffic and four for Ingress traffic. |
No customer impact. However, the number of parallel Egress filters is limited to two. Workaround: No workaround available. |
3 | 23.3.0 |
| 35607161 | The GUI does not display processing information when Kafka Feed deletion takes a long time. | The GUI displays no information when the Kafka Feed deletion takes a long time (more than "1" minute). |
No customer impact. Workaround: No workaround available. |
3 | 23.3.0 |
| 35677070 | In the GUI, the "Copyright Information" in the "About" section directs the user to the "About DD" section. | A hyperlink from the "Copyright Information" is mapped incorrectly. |
No customer impact. However, incorrect display causes user confusion. Workaround: No workaround available. |
3 | 23.3.0 |
| 35667048 | Create Kafka Feed is allows any user entry in ACL User and Host Name fields. | During Kafka Feed creation, the GUI allows incorrect entries for the "ACL User" and "Host Name" fields.
For example: ACL User = asdf*** or asdfhask8*((**))^%$ |
The fields allow incorrect entries. Workaround: The user must provide the "ACL User" name and "Host Name" in the correct format. |
3 | 23.3.0 |
| 35639519 | Replicated Feed Name of the Kafka Feed is missing from the .csv exported from the OCNADD GUI. | Replicated Kafka Feed is created, and this information is exported as a .csv file using the GUIs export functionality. The export option does not populate the file with the Replicated Feed Name. |
The Exported Kafka Feed .csv files do not contain the Replicated Feed Name. Workaround: No workaround available. |
4 | 23.3.0 |
| 35594082 | OCNADD GUI display style issues are observed. | Style issues are observed in the OCNADD GUI while displaying GUI content with extra spaces and some font sizes. |
No customer impact. Workaround: No workaround available. |
4 | 23.3.0 |
| 35679888 | In the GUI dashboard, the Average Message Size display disappears. | In the GUI dashboard, the Average Message Size display disappears when one of the producers goes down or stops sending traffic. |
No customer impact. However, incorrect display causes user confusion. Workaround: No workaround available. |
4 | 23.3.0 |