Resolved and Known Bugs

4 Resolved and Known Bugs

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

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.2.0.

Table 4-1 NRF 1.6.1 Resolved Bugs

Bug Number	Severity	Found in Release	Title
31380120	2	1.5.1	NRF's Ingress-Gateway PODs becomes unresponsive after processing HTTP/1.x message
31380143	3	1.5.1	NRF's Egress-Gateway through's Connection Error Exception after a Idle 15 minutes Timeout between NRF and SLF connection

Table 4-2 NRF 1.6.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
30995372	4	1.5.0	NRF Latency metrics should be pegged even when processing time is less than 0 milliseconds (i.e. if the value is in microseconds)

Table 4-3 SCP 1.6.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
30731829	3	1.4.0	SCPC-Pilot is taking high CPU while applying updates if number of equivalent profiles/ServiceInstances are exceeding 100
31315602	3	1.5.0	SCP to alert if 2xx is received in Audit with empty array for discovery or management

Table 4-4 UDR 1.6.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
30720600	4	1.5.0	UDR notify service keeps triggering notification for single modification of any resources(eg AM_DATA)

Table 4-5 CNDRA 1.6.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
30542078	3	1.4.0	Enabling 1k/ pod diameter connections, causes invalid fd issue on draworker pod

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-6 NRF 1.6.1 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
31331560	4	1.5.0	NRF is not validating unique serviceInstanceId	NFs should refrain sending duplicate serviceInstanceId.
31331608	4	1.5.1	Cachecontrol header is not being sent in forwarded discovery response	Intermediate Proxies cannot cache the Discovery Response.

Table 4-7 NRF 1.6.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
31331560	4	1.5.0	NRF is not validating unique serviceInstanceId	NFs should refrain sending duplicate serviceInstanceId.
31331608	4	1.5.1	Cachecontrol header is not being sent in forwarded discovery response	Intermediate Proxies cannot cache the Discovery Response.
31380120	2	1.5.1	NRF's Ingress-Gateway PODs becomes unresponsive after processing HTTP/1.x message	Ingress-Gateway POD will not be able to process any request until the POD restarts.
31380143	3	1.5.1	NRF's Egress-Gateway through's Connection Error Exception after a Idle 15 minutes Timeout between NRF and SLF connection	If the NRF-SLF connection remains idle for 15 mins, upto 4 initial SLF query will fail. Subsequent SLF requests will pass until there is no 15 mins idle time.

Table 4-8 SCP 1.6.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
30731782	3	1.2.0	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 and hence minimal impact for customer/user. Workaround: None. This is limited by underlying platform.
30731844	3	1.3.0	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. Workaround: None.

Bug Number

Severity

Found in Release

Title

Customer Impact

30731782

1.2.0

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 and hence minimal impact for customer/user.

Workaround: None. This is limited by underlying platform.

30731844

1.3.0

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.

Workaround: None.

Table 4-9 UDR 1.6.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
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.
30774755	3	1.4.0	Headers for few resources are not implemented as per spec 29505-v15.4.0	No impact.
31330261	4	1.6.0	UDR allows creating SLF data with empty nfGroupId	No impact.
31330361	3	1.6.0	Error response format from ProvGw is not as expected.	No impact. Needs error code enhancement
31330332	3	1.6.0	ProvGw does not send to second UDR within same segment.	Workaround: Configure all UDR FQDNs in the segments list in the values.yaml file.

Table 4-10 PCRF 1.6.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
31319315	2	CnPCRF 1.6.0	cnPCRF 1.6: Connection from Diam-GW to external SPR servers requires a core restart	Workaround: A restart of the core process.
31319428	3	CnPCRF 1.6.0	cnPCRF 1.6: No Options available to disable combine lookup and subscription for UDR data source	Workaround: None.
31319500	2	CnPCRF 1.6.0	cnPCRF 1.6: Unable to see policies in GUI after a Bulk import options	Workaround: Manual Creation.
31320395	3	CnPCRF 1.6.0	cnPCRF 1.6.0: Some types are missed on the page of Diameter peer nodes cfg making it unusable	Using the Kubernetes config map for the peer configuration.
31326154	4	CnPCRF 1.6.0	Getting 500 error while searching session by IPV6 if excessive space given after actual search value	Workaround: Remove excessive space from search text and try searching again.
31370072	3	CnPCRF 1.6.0	cnPCRF 1.6.0 : Diameter Gateway is not initiating connection towards OCS when one creates Peer Node from CM GUI	Workaround: Don't configure Peer from CM GUI and configure it in ConfigMap

Table 4-11 PCF 1.6.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
31366879	3	1.6	PCF: SM-service is not able to handle the request when PRE sends to to install Session Rule mapped to a Session Rule Profile	If PCF installed the session rule with ID as "sess1" and we want to override some of the parameters by keeping the same session rule ID by applying Session rule profile parameters. Currently SM-service is throwing exception while getting the request from PRE to override the session rule profile. Workaround: We can install new session rule with a different ID.
31366969	3	1.6	PRE evaluation: PRE evaluation throws error in case blockly access an object that is not present	Policy evaluation will fail in case blockly access an object that is not present. Workaround: To use Object expression block to validate the object against NULL, before using the object.
31367038	3	1.6	Remove clusterRole and ClusterRoleBinding from Policy solution	Workaround: None.
31367115	3	1.6	Bulk Import export does not work with Overwrite Option	User will not be able to do Bulk Import with Overwrite option. Workaround: Bulk Import can be used with Delete Option.

Table 4-12 CNCC 1.1.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
31355467	3	1.1.0	CNCC UDR screen - Minor issue in displaying error message having long text	Workaround: None.
31355421	3	1.1.0	CNCC UDR Screen - Open Items	Workaround: Direct API call can be made.
31367038	3	1.1.0	Remove clusterRole and ClusterRoleBinding from Policy solution	Workaround: None.
31355443	3	1.1.0	CNCC UDR Screen - Not displaying Authentication Error Messages	Error window will get popped up but no message will be displayed in case of unauthorized access. Workaround: None.
31355530	3	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. Workaround: Delete user and recreate user with required role.

Table 4-13 ATS 1.1.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
31377981	3	OCNRF 1.6.0	NRF ATS 1.1.0 can't be deployed using Helm3	Workaround: Either use helm2 to deploy or update the app version in deployment file of ATS helm charts.