1. Cloud Native Core Release Notice
  2. Resolved and Known Bugs

4 Resolved and Known Bugs

This chapter lists the resolved and known bugs for Cloud Native Core release 2.3.1.

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.

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.

Resolved Bug List

The following Resolved Bugs tables list the bugs that are resolved in Cloud Native Release 2.3.1.

Table 4-1 BSF 1.6.0 Resolved Bugs

Bug Number Severity Found in Release Title
31973019 3 1.5.0 S-NSSAI shall be Optional parameter in bsf discovery
32098522 3 1.5.0 BSF:1.4: pcfbnding discovery failed when we added s-nssai in the query parameters.
32098534 3 1.5.0 BSF:1.5: Session Viewer to support querying session information based on IPv6 in BSF

Table 4-2 CNE 1.7.0 Resolved Bugs

Bug Number Severity Found in Release Title
OCCNE-3467 2 1.6.0 occne/db_backup_svc:1.7.0 docker image is missing in the occne deliverable
OCCNE-3466 2 1.6.0 MySQL Cluster ERROR: Failed to allocate nodeid... No configured host found
OCCNE-3411 2 1.6.0 1.7.0-rc.7 BM upgrade identified issues
OCCNE-3338 2 1.6.0 Uplift Prometheus from v2.19.0 to v2.19.3
OCCNE-3385 2 1.6.0 1.7 vcne metallb deployment fails because of missing scripts and templates on lbvm
OCCNE-3321 2 1.6.0 Upgrade Vcne 1.7- Drain node task fails when pods on worker nodes take more than 3 minutes to terminate
OCCNE-3302 2 1.6.0 Grafana is not configured properly for accessing Prometheus as data source
OCCNE-3278 2 1.7.0 Bare Metal installation error in provision dbtier_bck_part role
OCCNE-3274 2 1.7.0 Upgrade 1.6 -> 1.7 failed for metallb task when upgrade octavia deployment.
OCCNE-3358 3 1.7.0 1.7 Install/Upgrade- Node exporter crashes/ restarts because of lack of resources

Table 4-3 CNC Console 1.4.0 Resolved Bugs

Bug Number Severity Found in Release Title
31958022 Minor 1.3.0 CNCC Core cmservice does not add helm/deployment name
31958056 Minor 1.3.0 CNCC cmservice pod does not come up in Webscale/ASM platform
32061426 Minor 1.3.0 CNCC Helm Test pod does not have Annotation Mustache code
32061435 Minor 1.3.0 CNCC Helm test failing - CPU/Memory requests/limits not specified 
32089275 Minor 1.3.0 Install Doc issue page 3.3 Version 1.3

Table 4-4 CNC Policy 1.9.3 Resolved Bugs

Bug Number Severity Found in Release Title
32505516 3 1.9.0 PCF 1.9 egress gateway shows constant oauth errors with oauth disabled.

Table 4-5 CNC Policy 1.9.2 Resolved Bugs

Bug Number Severity Found in Release Title
32427167 3 1.9.0 Policy 1.9.0- pre-install pods cannot create db connection with ASM istio-proxy (possible race condition)

Table 4-6 CNC Policy 1.9.1 Resolved Bugs

Bug Number Severity Found in Release Title
32150019 3 1.9.0 In the POST subscribe message to UDR, 'monitoredResourceUri' in 'PolicyDataSubscription' is not correct (when behind egress gw)
32150047 3 1.9.0 On AM-DELETE, udr-connector is responding with 500 INTERNAL_SERVER_ERROR
32263920 3 1.9.0 UDR Connector throwing "Error : Could NOT find any NFProfile" intermittently on UDR GET Request & returning to PDS with 500 Internal Server Error
32263949 3 1.9.0 PolicyDS - Support for Configurable Http2 Client Connections
32263962 3 1.8.0 ndbcluster produces error Got error 631 when reading table './ocpm_config_server_180/configuration_item' and PCF produces error calls
32264710 3 1.9.0

1.8.2 to 1.8.3 Upgrade --> Rollback --> re-upgrade issue/failure

This issue is there in 1.9.0 release as well and fixed in 1.9.1 to safeguard any further upgrades
32264711 3 1.9.0 Performance degradation observed in NRF-client 1.4.1 with PCF
32264748 3 1.9.0 Missing QOS in the N7 notify after receive prevous N7 notify with 400 BAD_REQUEST and ASR/STR 
32264778 3 1.9.0 PCF 1.9.0 am-service/ue-service update notify issue
32264787 3 1.9.0 Async CHF workflow update to be future proof
32264816 3 1.9.0 CHF record not deleted in PDS for Delete SMPolicyAssociation

Table 4-7 CNC Policy 1.9.0 Resolved Bugs

Bug Number Severity Found in Release Title
32146813 2 1.8.3 PCF does not send SuppFeatures IE for PRA in SM Policy Association Response 
31972768 3 1.8.0 Config Client Connection to Config Server hangs when DB issues are encountered
31895171 3 1.8.0 SM & User-service are not able to connect to alternate service with default 8000 port(unified port)
31898693 3 1.8.0 On loss of connectivity with OCS, Diam Gateway failed to reconnect to OCS 
32146883 3 1.8.1 OSO Prometheus shows PCF pods down
32146966 3 1.8.1 ATS - DNS Pod configuration requires each time, when DNS pod gets restarted

Table 4-8 NRF 1.9.0 Resolved Bugs

Bug Number Severity Found in Release Title
32135588 3 1.8.0 PI-D NRF ATS Forwarding test cases (VIA header) issue
32127690 3 1.5.1 When SLF feature is Disabled and SupportedNfTypeList is populated with Target NFType then SUPI from discovery query is getting ignored 
32127687 4 1.5.0 Supported NF type list for SLF query is missing in NRF User Guide
32127686 4 1.8.0 CSAR Package updates required for Automation
32127679 4 1.8.0 Incorrect metrics reference in KPIs section of NRF User Guide
31866858 4 1.7.0 replicationstatus alert should not be raised when Geo-Redundancy feature is disabled
31866838 4 1.7.2 Propagating Jaeger Headers for Forwarding/SLF requests
31866770 4 1.7.2 NRF service containers should not send HTTPs request to Sidecar container 
32140518 4 1.8.0 Limit NRF-ATS RBAC Verbs and Resource list

Table 4-9 SEPP 1.4.1 Resolved Bugs

Bug Number Severity Found in Release Title
31971775 2 1.4.0 pSEPP incorrectly update path in request URI
32098361 4 1.4.0 n32f requests metrics missing peer fqdn and domain

Table 4-10 SCP 1.9.3 Resolved Bugs

Bug Number Severity Found in Release Title
33429818 2 1.9.2 Addition/deletion of service in NF profile results in incorrect destination rules on SCP
33429831 3 1.9.2 Timestamp format update for SCP control plane services logs

Table 4-11 SCP 1.9.2 Resolved Bugs

Bug Number Severity Found in Release Title
32653951 2 1.9.1 AuditMaster thread is getting killed during DB exception
32699283 3 1.9.1 Handle Concurrent Modification Exception
32699327 4 1.9.1 Different log level shows for the same log

Table 4-12 SCP 1.9.1.1 Resolved Bugs

Bug Number Severity Found in Release Title
32553200 2 1.9.1 IGW gets into a failed state after heavy traffic before hitting CPU threshold for HPA
32553188 2 1.9.1 Issues with Ingress Gateway 1.10 with timeouts & added latency

Table 4-13 SCP 1.9.1 Resolved Bugs

Bug Number Severity Found in Release Title
32358097 3 1.7.4.1, 1.8.0 Topology source information is not retained after configuration pod restart
32215993 3 1.7.4.1 Ingress Gateway memory usage alarm addition:
  • SCPIngressGatewayPodAboveMinorMemoryUsage
  • SCPIngressGatewayPodAboveMajorMemoryUsage
  • SCPIngressGatewayPodAboveCriticalMemoryUsage
32216030 2 1.7.4.1 Intermittent 503 Error by Ingress gateway due to out of memory
32359780 4 1.8.0 Include Alerts and Dashboard files to CSAR
32359767 4 1.8.0 Update the vnfd.yaml file for SCP to not put NF name - in the product_name value

Table 4-14 SCP 1.9.0 Resolved Bugs

Bug Number Severity Found in Release Title
32134953 3 1.7.3 Modify SCP Role definition to remove wild card verbs (*)
32134966 3 1.7.4 SCP Metrics dashboard needs to be corrected from the metric "ocscp_http_0_0_0_80_downstream_cx_active" to the  metric "ocscp_http_downstream_cx_active"
32134973 3 1.7.3 Remove CRD creation as part of SCP installation
32134976 3 1.7.4 Success and Failure metric in Audit module
32135488 3 1.7.3 Exception due to NotEmpty constraint on PlmnId in taiRange class
32135496 3 1.7.3 Duplicate entries with empty SCP identifier is created in NRF_NF_DETAILS table after configuration pod restart
32135505 3 1.7.4 Security context addition to helm charts to enable custom user id for SCP containers

Note:

SCP 1.9.0 also includes bug fixes from SCP 1.7.5 patch release.

Table 4-15 UDR 1.9.0 Resolved Bugs

Bug Number Severity Found in Release Title
31889017 3 1.8.0 Issues observed on ProvGw on ASM machine

Customer Known Bug List

Customer Known Bugs tables list the known bugs and associated Customer Impact Statements. This information is provided for information purposes only.

Table 4-16 BSF 1.6.0 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact
32098543 3 1.6.0 Seagull process are not cleaned and ended up as defunct process During ATS execution 1 defunct process will be created after the ATS run is complete. This defunct process will not utilize the RAM or CPU so it will not be an impact on the resources. But process Id will be utilized that can cause impact in long run.
32098560 3 1.6.0 ATS documentation in Chrome Browser not getting displayed properly ATS documentation is not rendering correctly in chrome. The same is opening up correctly in Firefox and IE.
32098550 3 1.5.0 BSF responds with UNKNOWN_SESSION_ID when binding is not found AAA is received with error UNKNOWN_SESSION_ID from BSF Connector instead of IP-CAN_SESSION_NOT_AVAILABLE.

Table 4-17 CNE 1.7.0 Customer Known Bugs

Bug Number Severity Found in Release Title
30756164 3 1.3.2 OCCNE 1.3 Bare Metal Installation Failure -- Replication IP not configured on Sql Nodes during Db-Tier installation
30756201 4 1.3.2 OCCNE 1.3 Bare Metal Installation Failure -- Pipeline.sh is not documented. Must be continually restart on error.
30371715 4 1.3.2 OCCNE 1.2.0 Installation Guide Does Not Provide Guidance on Firmware Version

Table 4-18 CNC Console 1.4.0 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact
31355530 4 1.1.0 CNCC IAM - Unable to remove assigned User Role User will be able to add roles but user will not be able to remove the assigned roles.

Table 4-19 CNC Policy 1.9.0 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact
32146869 2 1.8.0 High Latency & timeout observed when Ingress TPS is > 750 - Single POD Observed performance latency when running beyond750 TPS per pod when PCF is deployed with Aspen Service Mesh
32146896 2 1.8.0 ndbcluster produces error Got error 631 when reading table Getting temporary error 631 'Scan take over error, restart scan transaction' from NDBCLUSTER while accessing DB. There is no direct impact but this may impact the high performance run.
32146961 3 1.9.0 PCF:1.9.0:PDS timeout happens for first call (ATS case is failing) After the restart of the PDS service first call will fail.
32147046 3 1.9.0 Notification URI for nCHF is not valid in nCHF Connector Pod Trace No Impact, log traces will have the wrong notification URI which may be confusing.
32147073 3 1.9.0 PDS Project PRE Evaluation Failing with "Error 6/invalid_frame_length" User will not be able to control the call flow of PDS Project through policies. Call flow can be controlled using the Work Flows.
32150019 3 1.9.0 In the POST subscribe message to UDR, 'monitoredResourceUri' in 'PolicyDataSubscription' is not correct (when behind egress gw) In the POST subscribe message to UDR, 'monitoredResourceUri' in 'PolicyDataSubscription' is not correct (when behind egress gw)
32150047 3 1.9.0 On AM-DELETE, udr-connector is responding with 500 INTERNAL_SERVER_ERROR On AM-DELETE, udr-connector is responding with 500 INTERNAL_SERVER_ERROR

Table 4-20 NRF 1.9.0 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact
32127692 3 1.1.0 NRF not accepting Discovery Query with SUPI, if the value is not having "imsi-" or "nai-" prefix Discovery query with format other than "imsi-" or "nai-" will be rejected as back request by NRF
32127694 4 1.1.0 tacRangeList attribute in TaiRange is mandatory, if it is missed OCNRF not reporting bad request rather 500 response is returned Incorrect error code will be sent to the consumer NF by which it will never know that the request message is having syntax issue.

SEPP 1.4.1 Customer Known Bugs

Note:

Security Edge Protection Proxy (SEPP) 1.4.1 has no customer known bugs.

Table 4-21 SCP 1.9.0 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact
30731782 4 1.2 Limit of VS size is limited to 1 Mb by etcd/k8s. Impacts only if there are 100s of NFs with many service instances/NF.
30731844 4 1.3 Processing time of NRF notifications increases if more profiles (>10) with more many service instances (more than 10/profile)are registered. increase observed is 2-3 seconds more than previous registered in case of new registration. Updates also increases with more number of registered profiles.  There may be delay in rule creation if profiles are large in numbers.
30731829 4 1.4 SCPC-Pilot is taking high CPU while applying updates if number of equivalent profiles/ServiceInstances are exceeding 100 There may be delay in rule creation if profiles are large in numbers which can cause some call failures.

Table 4-22 UDR 1.9.0 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact
30774755 3 1.4.0 Headers for few resources are not implemented as per spec 29505-v15.4.0 No Impact
31889017 3 1.9.0 On demand migration issue for PATCH operation on UDR Rel. 1.8.4 No impact. This is a negative scenario
32122140 3 1.9.0 Subscriber Entity field issues on ProvGw from SOAP/XML No impact. The error codes needs changes.
30774742 4 1.3.0 UDR is not validating the conditional attributes for UDM APIs. No impact. UDM(consumer of UDM APIs) does not send conditional attributes to UDR
30774750 4 1.3.0 Notify Service delays notifications to PCF during traffic run Notifications rate is limited in initial release.
31877256 4 1.8.0 ProvGw: GET response sometimes does not have segment1 related data for subscriber does not exist case No impact. It is intermittent issue.