4 Resolved and Known Bugs
This chapter lists the resolved and known bugs for Network Analytics Suite Release 23.2.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.2.x.
OCNWDAF Resolved Bugs
Table 4-1 OCNWDAF 23.2.0 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 35074225 | Some pods fail to start after image is deployed when installing on DBTier cluster with multiple instances |
The customer was installing OCNWDAF on a cnDBTier cluster with multiple instances, and some pods failed to start after the image was deployed. On verifying the logs of the failed instances, the following or similar errors were observed: amf_notification' referenced by a foreign key constraint'amf_ue_event_report_ibfk_1' on table 'amf_ue_event_report'. [Failed SQL:(3730) drop table if exists `amf_notification`]. The issue was due to a few database creation scripts specifying the InnoDb engine, and this is not supported when NDB replication is enabled. |
2 | 23.1.0 |
| 35318818 | The nwdaf_subscription_notify feature is not getting 100% success result |
Implementation of “nwdaf_subscription_notify feature” was not entirely successful. The following test cases failed:
|
3 | 23.1.0 |
| 35318795 | Analytics Info test scripts are present in new-features and regression suites. |
The "Analytics Info" test scripts were present in the new features and regression suites. These scripts must not be included as a part of the feature suite as they are not in the scope of the release. |
3 | 23.1.0 |
| 35255779 | NWDAF - 23.1.0 GUI functionalities are not working |
The user accessed the NWDAF GUI through the CNC Console. The NWDAF GUI dashboard opened, and all the GUI options appeared. While accessing the GUI options, the GUI froze. It requested slices and cells over an incorrect local host URL instead of using the configured URL in the CNC Console. |
3 | 23.1.0 |
| 35074153 | Gateway and subscription service fail to answer to HTTP2 requests |
In releases 22.1.0 and 23.1.0, it was observed when the NWDAF gateway or subscription services received HTTP requests in the HTTP2 format, the NWDAF rejected such requests. The Event Subscription service triggered the Data Collection service, which responded with an HTTP 404 response. The Data Collection service log displayed warning or error messages such as: 2023-02-02T16:36:37,302 [ocn-nwdaf-data-collection] WARN [http-nio-8081-exec-4] [06c95627-a2c4-428f-bc43-4de48ad80bc4] com.oracle.cgbu.ocn.nwdaf.datacollection. application.subscription.service.Data CollectionSubscriptionService.lambda lambda$retrieveEventNotifications$0:77 - Event type UE_MOBILITY not supported yet |
3 | 23.1.0 |
| 35212772 | One SQL export parameter is incomplete in Installation Guide |
The export engine variable parameter mentioned in the "Installing NRF client" section of the Installation Guide was incomplete. |
4 | 23.1.0 |
Note:
Resolved bugs from 22.1.x and 23.1.x have been forward ported to Release 23.2.0.OCNADD Resolved Bugs
OCNADD 23.2.0.0.3 Resolved Bugs
There are no resolved bugs in this release. Resolved bugs from 22.0.x and 23.1.x have been forward ported to Release 23.2.0.0.3.
OCNADD 23.2.0.0.2 Resolved Bugs
Table 4-2 OCNADD 23.2.0.0.2 Resolved Bugs
| Bug Number | Title | Description | Severity | Found In Release |
|---|---|---|---|---|
| 35751205 | Blocking Kafka 9092 Cleartext port for external access | Incoming traffic to 9092 Kafka Port was restricted. | 3 | 23.2.0 |
| 35690437 | Sensitive capabilities on DD GUI pod | The GUI pod had sensitive capabilities. | 3 | 23.2.0 |
| 35751250 | Merging 23.2.0.0.1 patch changes to 23.2.0.0.2 | Forward ported the upgrade and rollback enhancement from OCNADD release 23.2.0.0.1 release to 23.2.0.0.2. | 3 | 23.2.0 |
| 35575434 | DD GUI is slow from computers with no external access | The GUI of the OCNADD instance through CNC Console was experiencing a lag. | 3 | 23.1.0 |
| 35751170 | Some DD pods have cluster-admin roles | The cluster or admin level privileges to Role and RoleBinding were restricted. | 2 | 23.2.0 |
| 35749037 | noTLS adapter are crashing after upgrade to 23.2.0.0.2 | The adapter pods of the data feed created with noTLS were in "CrashLoopBackOff error" state post upgrade. | 2 | 23.2.0.0.2 |
Note:
Resolved bugs from 22.0.x and 23.1.x have been forward ported to release 23.2.0.0.2.OCNADD 23.2.0.0.1 Resolved Bugs
There are no resolved bugs in this release. Resolved bugs from 22.0.x and 23.1.x have been forward ported to Release 23.2.0.0.1.
OCNADD 23.2.0 Resolved Bugs
Table 4-3 OCNADD 23.2.0 Resolved Bugs
| Bug Number | Title | Description | Severity | Found In Release |
|---|---|---|---|---|
| 35069179 | Adapter getting restarted when we make changes in the feed after restarting config service |
Editing any feed with Oracle ciphers resulted in its adapter POD restarting. |
3 | 23.1.0 |
| 35058236 | OCNADD UI not Validating Data feeds Endpoints |
The GUI did not validate invalid endpoints provided by users. |
3 | 23.1.0 |
| 35052457 | OCNADD: Incorrect correlation id observed in synthetic packet for specific x-request-id value | The synthetic packet x-request-id header value received by the third-party consumer did not match. | 3 | 23.1.0 |
| 35039749 | In Dashboard the Average Message Size per NF is incorrect | The "Average Message Size per NF" was incorrect in the GUI dashboard. | 3 | 23.1.0 |
| 34827399 | Discrepancy in OCNADD metrics - Tx messages are higher than Rx messages | The outgoing traffic handled by the Adapter service was higher than the incoming packets at Kafka due to Kafka consumer rebalancing. | 3 | 23.1.0 |
| 34786365 | OCNADD logging Error logs as INFO for Configuration service for when it is sending Notification to Adapter | The Configuration service logged a few ERROR logs as INFO when sending notifications to the Adapter. | 3 | 23.1.0 |
| 35067498 | For Synthetic feed, adapter is not raising alarm for 3rd party connection failure with low traffic | In the case of Synthetic packet feeds, the Adapter service did not raise an alarm when a third-party Pod went down while processing low traffic. | 4 | 23.1.0 |
| 35063634 | Improper description of the alarm - OCNADD02005: Third Party Connection Failure | The GUI displayed incorrect information for the "OCNADD02005: ThirdParty Connection Failure" alarm. | 4 | 23.1.0 |
Note:
Resolved bugs from 22.0.x and 23.1.x have been forward ported to Release 23.2.0.4.3 Known Bug List
Known Bugs tables list the known bugs and associated Customer Impact Statements.
OCNWDAF Known Bugs
The following table lists the known bugs for OCNWDAF Release 23.2.x.
Table 4-4 OCNWDAF 23.2.0 Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 3541729 | The ue_mobility_notification_id column has null value in the cap4c_ue_notification table | The ue_mobility_notification_id column has a null value in the nwdaf_data_collection. cap4c_ue_notification table. | No customer impact
Workaround: No workaround available |
3 | 23.2.0 |
| 35398099 | AB and Ue_mobility subscriptions with ONE_TIME value in notifMethod send more than one notification | If UE Abnormal behaviour and UE subscriptions are created with ONE_TIME value in notifMethod, only one notification should be sent, but more than one notification are being sent. | There is no customer impact. However, duplicate reports cause user confusion.
Workaround: No workaround available |
3 | 23.2.0 |
| 35397011 | NWDAF should cancel jobs in scheduler and Mesa |
When a subscription is active, reports and notifications are created from MESA and CAP4C, but when the subscription is canceled, the jobs from both services should also be canceled.
|
There is no customer impact. This issue occurs within the simulators currently used by the OCNWDAF.
Workaround: No workaround available |
3 | 23.2.0 |
| 35393789 | UE and AB subscriptions can't be deleted | Some UE subscriptions cannot be deleted after creation. | There is no customer impact. This issue occurs within the simulators currently used by the OCNWDAF.
Workaround: No workaround available |
3 | 23.2.0 |
OCNADD Known Bugs
OCNADD 23.2.0.0.3 Known Bugs
There are no known bugs in this release. Known bugs from 23.2.x have been forward ported to Release 23.2.0.0.3.
OCNADD 23.2.0.0.2 Known Bugs
There are no known bugs in this release. Known bugs from 23.2.x have been forward ported to Release 23.2.0.0.2.
OCNADD 23.2.0.0.1 Known Bugs
There are no known bugs in this release. Known bugs from 23.2.0 have been forward ported to Release 23.2.0.0.1.
OCNADD 23.2.0 Known Bugs
The following table lists the known bugs for OCNADD Release 23.2.x.
Table 4-5 OCNADD 23.2.0 Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 35386371 | OCNADD services are not upgraded and rolled back in defined order. | When an upgrade (or rollback) is performed on the OCNADD, the services are not upgraded (or rolled back) in the desired order, leading to errors in some services. | Since the upgrade or rollback sequence is not defined, some service errors are expected.
Workaround: No workaround available |
3 | 23.2.0 |
| 35396464 | ocnadd sepp/nrf/scp aggregation pod CPU utilisation reaches 90% in case weighted load balancing or filtering feature is enabled with 64K MPS aggregated traffic | Resource utilization increases when load balancing or filtering is configured on Data Feeds at a higher throughput rate. | No customer impact
Workaround: In case of higher resource utilization scenarios, the number of replicas can be increased. |
3 | 23.2.0 |
| 35399574 | Retry timer in synthetic feed should limit to some max value and resets after it | For any synthetic feed, the retry timer increases exponentially in case of any third party connection failure. | The retry window may become very large and prevent reconnection even after the third-party application comes up after being down for some time.
Workaround: The Adapter pod can be restarted to reestablish the connection once the third party application is available. |
3 | 23.2.0 |
| 35320886 | Changes needed in the script generate_certs.sh to handle specifically the SAN in the client CSR | There is a request to introduce a few changes in the script for generating CSR to specifically handle the SAN in the client CSR. | No customer impact
Workaround: No workaround available |
3 | 23.1.0 |
| 35398515 | Install fails with "Error: container has runAsNonRoot and image will run as root" | "Error: failed pre-install" error is observed during installation. It can be due to the environment specific PodSecurityPolicy. | Installation may fail, for more information see, Oracle Communications Network Analytics Suite Security Guide.
Workaround: No workaround available |
3 | 23.1.0 |
| 35391713 | Configuration Service is not exposing Prometheus Endpoint properly | Prometheus unable to scrape the data from the Configuration Service. | The Configuration Service status cannot be retrieved correctly.
Workaround: No workaround available |
3 | 23.2.0 |
| 35391812 | Subscription is getting created for a Target Consumer which does not exist | Validation to verify if the target consumer name exists is missing. | No customer impact
Workaround: No workaround available |
3 | 23.2.0 |
| 35409766 | OCNADD Performance: CPU Utilization for aggregation and adapter services observed on a higher side(>70%) on running 30K MPS synthetic packet runs | Higher resource utilization is observed for different load runs from SCP,NRF, and SEPP. | No customer impact
Workaround: No workaround available |
3 | 23.2.0 |
| 35385608 | Disassociation does not happen when filter type is changed from INGESS to EGRESS | Filter does not disassociate when the filter type is changed from Ingress to Egress. | The old filter continues filtering the data.
Workaround: Deactivate or disassociate the filter before changing the filter type from Ingress to Egress. |
3 | 23.2.0 |
| 35319683 | Zookeeper showing only 2 instance instead of 3 | GUI displays lesser number of Zookeeper instances while the correct number of instances are listed at the backend. | No customer impact, however, the incorrect information displayed causes user confusion.
Workaround: No workaround available |
3 | 23.2.0 |
| 34903802 | MsgCopy Packet loss between SCP/NRF and OCDD-Kafka | For any long traffic runs from NFs, difference is observed between the total messages copied by NRF or SCP and the total messages received at Kafka. | No customer impact is expected if the producers run with Ack and retries.
Workaround: No workaround available |
3 | 22.0.0 |
| 35385593 | Older Aggregation entries not getting deleted upon simultaneous restart of config and aggregation pod | The Configuration service tries to reach the older pod IPs when multiple or simultaneous restarts of the Aggregation and Configuration services occur. | No customer impact
Workaround: No workaround available |
4 | 23.2.0 |
| 35340864 | Service-name filter not filtering entire N12 nausf-auth call flow | This scenario is observed during lab simulation where the "Response" is received before the "Request". | No customer impact
Workaround: No workaround available |
4 | 23.2.0 |
| 35385541 | Wrong endpoint URI and storage values in HealthDB | The UI Router and Cache services register with the Health Monitoring service using incorrect information. | No customer impact
Workaround: No workaround available |
4 | 23.2.0 |