Resolved and Known Bugs

4 Resolved and Known Bugs

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

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

CNC Console Resolved Bugs

Table 4-1 CNC Console 1.7.2 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33134335	Minor	1.7.0	CNCC is not supporting ASM with mTLS disabled

Table 4-2 CNC Console 1.7.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
32918829	Minor	1.6.2	VzW: CNCC 1.6 ServiceDown alert rules do not allow for custom pod name prefixes
32292169	Minor	1.2.0	VZW CNCC: CNCC IAM Pods showing healthy when db is down. No Reading or Liveliness Errors observed
31355530	Minor	1.1.0	CNCC IAM - Unable to remove assigned User Role

BSF Resolved Bugs

Table 4-3 BSF 1.9.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
32995049	3	1.7.2	bsf-management-service deployment.yaml not checking global.bsfApiRoot for BSF_APIROOT
32995104	3	1.8.1	BSF 1.8.1 performance pod keeps restarting
32995437	3	1.8.1	BSF mgmt unable to find ipv6 binding prefix with 128 length for Rx AAR corresponding prefix length is 64 from SM service
32995469	3	1.7.1	Session viewer doesn't display bindings if SNSSAI is not used

CNC Policy Resolved Bugs

Table 4-4 CNC Policy 1.12.3 Resolved Bugs

Bug Number	Severity	Found In Release	Title
33321419	3	1.12.0	PCF sending NULL smPolicyDecision in audit messages

Table 4-5 CNC Policy 1.12.2 Resolved Bugs

Bug Number	Severity	Found In Release	Title
33208990	3	1.11.3	"attribute in SMF request" block throws unhandled exception when the path in request is not valid
33209010	3	1.11.4	Policy Association table while updating/storing the association fails with error "Data truncation: Data too long for column 'v' at row 1
33209741	3	1.11.0	PRE keeps on polling and retrieving PolicyTable periodically irrespective of any changes done in Policy Table
33209755	3	1.11.4	Null Pointer Exception In PolicyDs when SSV is disabled
33209763	3	1.12.0	Policy custom yaml files are still using the deprecated SCP configuration.

Table 4-6 CNC Policy 1.12.1 Resolved Bugs

Bug Number	Severity	Found In Release	Title
32998157	2	1.11.3	Overload Control: Pending req count is not decreased in IGW
32995443	3	1.11.2	PCF sends PATCH request to UDR even in the absence of policies - not working after fix also
33123449	3	1.12.0	CM GUI : Open Policy Table throws Error when it has Session/PCC Override columns
33123500	3	1.12.0	Diam connector not connecting to new IP of diam-gateway
33123500	3	1.12.0	Diam connector not connecting to new IP of diam-gateway
33123511	3	1.11.2	BSF Selection for IPv6 Prefix not considering the end range
33123529	3	1.11.0	Incorrect QOS rule after PRA change message
33123548	3	1.11.3	SM service unable to trigger "Sent User Service Request" for CHF Info
33123564	3	1.11.3	PCF_SERVICE_DOWN alert does not show all services that are down
33066007	3	1.12.0	send a notification to Syslog blockly is missing in 1.12

Table 4-7 CNC Policy 1.12.0 Resolved Bugs

Bug Number	Severity	Found In Release	Title
32877378	3	1.11.3	DNS Core IP address configuration shall be automated in the DNS stub
32995088	3	1.11.0	UDR and CHF metrics not getting into promethues
32995089	3	1.11.1	SM Create without IP , binding fails even though Session is created
32995091	3	1.11.1	Policy Design: possibility to change the AND/OR block from "horizontal" to "vertical"
32995094	3	1.11.1	PCF includes smPolicySnssaiData=NULL in 'body' written to UDR
32995096	3	1.11.1	PCF doesn't delete Subs State Variables after Session Deleted
32995098	3	1.11.0	PCF generating old diameter routing config file in bulk export
32995101	3	1.11.0	Timer profile not present in bulk policy export
32995012	3	1.11.2	Failed to sent RAR/ASR to AF with different realm
32995022	3	1.11.2	Diameter connection to DAR flash during traffic run
32995030	3	1.11.0	QOS APN-Aggregate-Max-Bitrate-DL/UL AVPs setup
32995031	3	1.11.0	Intermittent VoNR call failures involving PCF. Identified that egress pod is unable to deliver the smpolicycontrol
32995245	3	1.10.3	PCF - No BSF profile selected due to missing bsfInfo but should be optional
32995036	3	1.11.0	Subscriber State Variable Handling Negative Scenario when PATH is configured at Attribute Level
32995041	3	1.11.0	Implement Policy Action to set Charging Server
32995043	3	1.11.0	PCF cannot parse NRF.CHF cfg topic due to unexpected ServiceName value 'nchf-offlineonlycharging'
32995046	3	1.11.2	PA session processing failures - exception: illegal character in the Rx session id URI

Table 4-8 ATS 1.12.0 Resolved Bugs

Bug Number	Severity	Found In Release	Title
32877378	3	1.11.3	DNS Core IP address configuration shall be automated in the DNS stub

NRF Resolved Bugs

Table 4-9 NRF 1.12.1 Resolved Bugs

Bug Number	Severity	Found In Release	Title	Customer Impact
33104786	4	1.10.1	NFDiscover for AMF for AMFSetId in Guami attribute is returning no profiles due to case sensitive match	If Discovery query is sent with AMFSetID of different case then what the producer had used during registration, then the Discovery query will fail, and Consumer NF will not able to discovery the producer even if it is registered. Work Around: Consumer NF needs to send Discovery Query with same case that producer had used during registration
33108019	4	1.10.1	NFDiscover Query Needs to perform case in-sensitive match for target-nf-fqdn, snssais, requester-snssais, plmn-specific-snssai-list, dnn, tai, amf-region-id, amf-set-id, guami, ue-ipv6-prefix, pgw-ind, pgw-fqdn and upf-iwk-eps-ind	If Discovery query having Hex/Boolean value is sent with different case then what the producer had use during registration, then the Discovery query will fail, and Consumer NF will not able to discovery the producer even if it is registered. Work Around: Consumer NF needs to send Discovery Query with same case that producer had used during registration
33105051	4	1.10.1	Adding of Load using NFUpdate (patch) not working when only NFStatus and Add (load) attribute present in Patch request	NRF will reject the HeartBeat request with load if load is not present during NF Registration. Work Around: NF should always add Load in the NfProfile while registering.
33105412	4	1.12.0	Incorrect values in ATS annotations section for NRF ATS 1.7.0 Guide	ATS Pod will not able to scape metrics from the NRF PODs which will result into test case failure.

Table 4-10 NRF 1.12.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
32860876	4	1.10.2	Deleting bulk record from NRF table is creating some time locking issue	DB Replication channel may go down because of which NRF Geo-Redundancy will not work
32973002	4	1.11.2	False metric and log is raised for the response received from SLF	Wrong Metric Value will be pegged
32973008	4	1.7.0	RejectionReason missing in NfAccessToken response metric	When an Access Token is rejected, it will not be known the exact reason for the rejection by looking into metric
32973022	4	1.10.0	Removal of load attribute is setting load attribute in NF Profile to 0. Instead it shall be removed from NF Profile	Removal of load attribute is setting load attribute in NF Profile to 0. Instead it shall be removed from NF Profile

SCP Resolved Bugs

Table 4-11 SCP 1.12.1 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33249040	3	1.11.0	Pod restarts observed with 61.2K TPS when SCP deployed with 31 worker pods.

Table 4-12 SCP 1.12.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
32792888	2	1.10.2	SCP worker is encoding already encoded query parameters to egress requests URI
33036339	4	1.9.2	Make dimensions consistent for Control plane metrics
32989902	3	1.11.1	URI of notification from scp-w to scp-notification service has an extra '/' appended which is causing 301 error code responses for notifications.
33036348	4	1.11.0	Exception logs for deletion of virtual service during notification processing
32989925	2	1.11.0	Incorrect port picked in URL in case of fqdn only virtual service match
32989894	4	1.11.0	SCP 1.11.1 giving inconclusive value for "request processing time" falling under 2 second bucket
33036414	4	1.11.1	ATS Helm charts update to remove serviceMesh flag
33036425	4	1.11.0	ATS Scale Deployment step fix to wait and retry
33036429	4	1.11.1	ATS retry implementation on failure to fetch Metrics from SUT

SEPP Resolved Bugs

Table 4-13 SEPP 1.5.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
32924463	2	1.4.1	n32c handshake failed	If remoteSeppIpAddress is not provided in Roaming profile then n32c fails to initiate handshake. Workaround: Add remote IP address in remoteSeppIpAddress parameter when adding roaming profile.
32924486	3	1.4.1	HTTP requests rejected by the SEPP with 503 when using final destination fqdn as authority	When FQDN is set in authority as final destination, n32f message was getting rejected with 503 error.
32924531	4	1.4.1	SEPP config-pre-install pod not connecting to mysql.	SEPP- config-pre-install pod is going into error state and not able to connect to the DB. This was due to missing permission in SEPP 1.4.1 installation guide. Workaround: Add the REFERENCES when granting database access permission to user.

Bug Number

Severity

Found in Release

Title

Customer Impact

32924463

1.4.1

n32c handshake failed

If remoteSeppIpAddress is not provided in Roaming profile then n32c fails to initiate handshake.

Workaround: Add remote IP address in remoteSeppIpAddress parameter when adding roaming profile.

32924486

1.4.1

HTTP requests rejected by the SEPP with 503 when using final destination fqdn as authority

When FQDN is set in authority as final destination, n32f message was getting rejected with 503 error.

32924531

1.4.1

SEPP config-pre-install pod not connecting to mysql.

SEPP- config-pre-install pod is going into error state and not able to connect to the DB. This was due to missing permission in SEPP 1.4.1 installation guide.

Workaround: Add the REFERENCES when granting database access permission to user.

UDR Resolved Bugs

Table 4-14 UDR ATS 1.12.1 Resolved Bugs

Bug Number	Severity	Found in Release	Title
CNCES-3022	NA	1.11.0	SLF_Nrf_Client_Scenarios failed-GPSI

Table 4-15 UDR 1.12.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
31877256	4	1.8.0	ProvGw: GET response sometimes does not have segment1 related data for subscriber does not exist case
32631173	3	1.11.0	udr_rest_request_total not pegged for Unsuppported Media Type messages.
32631219	3	1.11.0	PUT/POST request for policy-data/UDM with empty payloads returns 5xx errors
32631240	3	1.11.0	UDR returns 5012 when vsaLevel set to either dnn or nssai

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.

CNC Console Customer Known Bugs

Table 4-16 CNC Console 1.7.x Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
32291223	Minor	1.5.0	CNCC: CNE Common Services type should be ClusterIP when accessed via CNCC	User will be able to access CNE common services directly using LoadBalancer IP.

CNC Policy Customer Known Bugs

Table 4-17 CNC Policy 1.12.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
32980584	3	1.11.0	LDAP-GW fails to fetch ldap user data after FI and UI.	This issue is seen in converged mode of deployment. For fresh installation, it would work fine but if LDAP-Gateway is installed and upgrade is done - this issue will be observed. Currently, this condition can be recovered on restarting LDAP-Gateway pod.
32995076	3	1.11.0	1.12.0 cmgui has configurations related to disabled services in pcrf mode.	Configurations that are not relevant for PCRF mode of deployment may confuse the customers.
32995081	3	1.11.0	Memory leak in diam-connector when diam-gw pod scales	When Diameter Gateway pod scales, Diameter Connector does not release the old connection buffers, which results in memory leak. This condition can be recovered by setting reconnectLimit = 0 in Diameter Connector config map and diam-connector will not reserve any buffers for storing the connection context.
32995443	3	1.11.2	PCF sends PATCH request to UDR even in the absence of policies - not working after fix also	PATCH request is triggered towards Unified Data Repository (UDR) even when remote section is not updated.
32998157	2	1.12.0	Overload Control: Pending req count is not decreased in IGW	This issue may happen under very rapid surges in traffic. Pending Request Count, once increased because of the high surge in traffic, will not reset once overload condition is removed. This will lead to shedding of traffic. This condition can be recovered by restarting Ingress Gateway.

NRF Customer Known Bugs

Table 4-18 NRF 1.11.2 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
32973027	4	1.12.0	Invalid Via header port value returns 500 internal error instead bad request	Response with incorrect HTTP Status code will be sent to consume NF
32973036	4	1.12.0	More than one allowedXXX attributes are present in NfProfile, then NRF sending Notification if one of allowedXXX check is passing and other(s) are failing	In certain scenarios NF May get notification for a NF even if it is not allowed to access the service of that NF
32973074	4	1.12.0	GET All API is not returning siteIdToNrfInstanceIdMappingList configuration values	During Backup, apart from doing GET All API to collect the configuration, additionally, siteIdToNrfInstanceIdMappingList backup needs to be taken.
32973081	4	1.12.0	ocnrf_heartbeat_missed_total counter gets pegged erroneously in SUSPENDED -> REGISTERED case	Incorrect Metric value will be seen for Heart Beat missed for NFs moving from Suspended to Registered. No other functionality will be effected.

SEPP Customer Known Bugs

No Customer Known Bugs for SEPP Release 1.5.0.

SCP Customer Known Bugs

No Customer Known Bugs for SCP Release 1.12.0.

UDR Customer Known Bugs

Table 4-19 UDR ATS 1.12.1 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact/WA
32377439	4	1.10.0	De-Registration fails when egressgateway goes down before nrf-client during UDR deletion	No impact
32377341	4	1.10.0	Fetch UDM authentication subscription on UDR returns Internal Server Error	Occurs only with cnDBTier. Possible bug on MySQL Cluster
32972133	3	1.12.0	Notify pod not sending notifications everytime to the stub for PATCH of sdmsubscription	Affects only PATCH operations. No workaround
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

Table 4-20 UDR 1.12.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact/WA
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.
32377439	4	1.10.0	De-Registration fails when egressgateway goes down before nrf-client during UDR deletion	No impact
32377341	4	1.10.0	Fetch UDM authentication subscription on UDR returns Internal Server Error	Occurs only with cnDBTier. Possible bug on MySQL Cluster
32972133	3	1.12.0	Notify pod not sending notifications everytime to the stub for PATCH of sdmsubscription	Affects only PATCH operations. No workaround.