4 Resolved and Known Bugs

This chapter lists the resolved and known bugs for Cloud Native Core release 2.22.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.

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

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

4.2.1 BSF Resolved Bugs

BSF 22.1.4 Resolved Bugs

The following table lists the resolved bugs for BSF Release 22.1.4:

Table 4-1 BSF 22.1.4 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
34282375	BSF Upgrade Failure to 22.1.3 Release	BSF upgrade failed due to bsf-mgmt post upgrade hook pod timing out	3	22.1.3

BSF 22.1.3 Resolved Bugs

The following table lists the resolved bugs for BSF Release 22.1.3:

Table 4-2 BSF 22.1.3 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
34199532	IGW pod takes longer to come up compared to PI-D with xfcc enabled in BSF NF	Ingress Gateway application thread and Scheduler thread are undergoing a race condition. Due to this, both the threads try to resolve FQDN from DNS leading to failure in DNS resolution.	3	22.1.0

BSF 22.1.2 Resolved Bugs

There are no resolved bugs in BSF Release 22.1.2.

BSF 22.1.1 Resolved Bugs

There are no resolved bugs in BSF Release 22.1.1.

BSF 22.1.0 Resolved Bugs

The following table lists the resolved bugs for BSF Release 22.1.0:

Table 4-3 BSF 22.1.0 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
33904598	BSF Missing Alert for Diameter Gateway PodCongestion Control Feature	Missing Alert for Diameter Gateway PodCongestion Control Feature	3	1.10.1

4.2.2 DBTier Resolved Bugs

DBTier 22.1.3 Resolved Bugs

Table 4-4 DBTier 22.1.3 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
34308261	Use latest Ol8+JDK base image OL85s220614|JDK17.0.3.1 in all cnDBTier k8 services	The OL85s220614|JDK17.0.3.1 docker image must be used for DB Tier Kubernetes services running on JVM (that is, db-monitor-svc and db-replication-svc).	3	22.1.2
34308316	DR scripts will fail if release name of cnDBTier contains container name of cnDBTier	Disaster recovery scripts fail to download the backup and then restore it if the release name of cnDBTier contains the container name of cnDBTier.	3	22.1.2
34308341	Allowing the Disaster recovery of cnDBTier clusters even if the cluster2 and cluster3 is getting reinstalled without cluster1	Automated disaster recovery is stuck in the initial state and it is triggered again if cnDBTier cluster2 and cnDBTier cluster3 are installed as mated pairs without installing the cnDBTier cluster1.	3	22.1.1
34213452	Error=Failed getting connection; pool exhausted in db backup svc	If the disaster recovery is being performed multiple times, the connection between the database and the backup service is denied, as the connection pool gets exhausted.	3	22.1.1
34308402	Revert back db-monitor-svc port name change in cnDBTier 22.1.3	OSO Prometheus expects the port name of the monitor svc to be "cnc-metrics". Since monitor svc has a separate port name, the OSO is not able to scrape metrics from monitor svc.	3	22.1.2
34308412	Fix the CI/CD pipeline to upload the checksum file in correct format	The build containing the CSAR package and checksum file are uploaded to the cnDBTier Artifact hub. The format of the checksum file is getting changed in the Artifact hub.	3	22.1.2
34308439	cnDBTier helm test uses deployment name to grep for pod name	cnDBTier helm test fails if db-replication-svc deployment name is longer than 58 characters.	3	22.1.2
34327850	1.10.3 to 22.1 cnDBTier upgrade (without ServiceAccount) is failing	cnDBTier upgrade fails as helm does not have permission to list events and therefore is not able to run the pre and post-upgrade hook correctly.	3	22.1.1
34308385	DBTier 22.1.x documentation should reference global repository as occne-repo-host not the bastion host	Update the default value for /global/repository in the "Customizing DBTier" section of the Oracle Communications Cloud Native Core DBTier Installation and Upgrade Guide.	4	22.1.0
34269846	cnDBTier helm test fails checking db-replication-svc pod is on ASM clusters	To determine if db-replication-svc pods are READY state, the test script checks if the number of containers that are in READY state are equal to the number of containers in the pod.	4	22.1.2

DBTier 22.1.2 Resolved Bugs

Table 4-5 DBTier 22.1.2 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
34084015	Update Spring boot to 2.6.6 for DBTier K8s applications	The uplift of the Spring Boot to 2.6.6 is required	2	1.10.2
34084783	Create cndbtier Rollback Procedure for standalone cluster	A procedure to Rollback an upgraded cluster from release 22.1.x to 1.10.1 or 1.9.2 needs to be written since the documentation only has a one to rollback systems with multiple replicating clusters.	2	22.1.1
34084849	Use ASM acceptable port name in the cnDBTier helm chart	cnDBTier monitor svc port 8080 is an HTTP Tomcat server port but the name has been given as CNC-metrics due to which the ASM sidecar is treating the same port as a TCP type and creating multiple TCP connections rather than treating the port as an HTTP port	2	22.1.0
34094355	Correction in updateclusterdetails.sh dr-procedure script	The updateclusterdetails.sh script does not work correctly when 2 or 3 sites are in fatal error. The script must be updated so that it works for all the cases of DR procedure.	2	22.1.1
34108029	Update Spring boot to 2.6.7 for DB Tier K8s applications	The uplift of the Spring Boot to 2.6.7 is required	2	1.10.2
34084036	Mysql hosts are frequently getting blocked	MySQL hosts are frequently getting blocked which needs to be manually unblocked by executing flush command on it.	3	1.10.1
34084808	Use compact json logging format for the db monitor svc	The db monitor svc is using the extended logging format, but at the same time all other DBTier Kubernetes services are using the compact logging format. The extended logging format makes it more difficult to read the logs.	4	22.1.0

DBTier 22.1.1 Resolved Bugs

Table 4-6 DBTier 22.1.1 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
33923166	Remove auto mounting of default service account	The pods except replication service gets default service account through auto mount feature.	2	1.10.1
33923122	Use 127.0.0.1 in probes to identify the pod health instead of ::1	When cnDBTier is installed on AWS environment, SQL pods were failing continuously due to probe failure.	2	22.1.0
33978772	Increase ephemeral storage size for different cnDBTier containers	Increase the ephemeral storage size so that the pods will not go to the evicted state.	3	1.10.0
34017881	Change image pull policy name in the values.yaml for pre & post upgrade job	Image pull policy defined in the values.yaml file for the pre and post-upgrade file is not reflected in the helm templates.	4	22.1.0
33959813	DBTier 22.1.0 upgrade w/istio-injection enabled fails while stuck at pre-upgrade-hook error	cnDBTier 22.1.0 upgrade hooks do not wait for istio proxy to be ready before trying to communicate with other pods. Also, pre-upgrade and post-upgrade hooks should terminate istio-proxy upon completion.	4	22.1.0
33959600	Add commonLables for db-backup-svc	Kubernetes resources associated with db-backup-manager-svc are not getting labels under the global.commonlabels section of values.yaml.	4	22.1.0
33959954	DBTier 1.10.1 dr-procedure scripts use pod's default container on some "exec" and "cp" cmds	DR scripts do not explicitly specified the container on some "kubectl exec" and "kubectl cp" commands.	4	22.1.0
34017934	auto restore fails when pod prefix is used while installing the cluster	The pod prefix auto restore is failed because when the auto restore is done in replication service pod prefix is not used for FQDNs of the management nodes.	4	22.1.0

DBTier 22.1.0 Resolved Bugs

Table 4-7 cnDBTier 22.1.0 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
33702005	Use the username & password from Environment variables instead of passing/using it from command line	The user name and password are updated in the environment variables instead of populating it in the command line arguments.	3	1.8.8
33865430	Configure cnDBTier to pass custom annotations to services	Added the custom annotations to enable retrieving of the load balancer IP address.	3	1.8.0
33865474	Remove the HTTP response payload in DB Status API when the status code is 503 (Service Unavailable)	The response code is removed when the status code 503 SERVICE UNAVAILABLE	3	1.10.0
33865496	Labels of cnDBTier DB-Monitor and DB-Replication pods should be common via helm	Added the common labels for db-monitor and db-replication pod template metadata.	3	1.9.2
33865486	Adding site_name and namespace attribute values/ labels in the cnDBTier Alerts	Added the attribute values such as site_name and namespace for cnDBTier alerts. These values are loaded in Prometheus GUI when the alerts are raised.	4	1.9.2

4.2.3 CNC Console Resolved Bugs

Table 4-8 CNC Console 22.1.3 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
34232522	Password of CNCC users present in CNCC pod logs.	CNCC users password was not masked in CNCC pod log. Code changes are done to mask the password.	4	1.9.1

Table 4-9 CNC Console 22.1.2 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
34045995	SCP-SEPP_FT: scp-nrfproxy service not listed in Logging Config to change log level	Scp-nrfproxy service was not listed for change logging level in Console UI.CNCC UI is updated to list scp-nrfproxy under logging level.	4	22.1.0

Table 4-10 CNC Console 22.1.1 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
34034366	Telia-Policy is not fully evaluated due to error with Policy tables for Norway's 5G Telia_Norway_5G_build1	When multiple services such as pcf-sm, pcf-am are in the system, then PRE is unable to process the Policy Table. PRE is loading only the latest updated service related table.	2	1.15.0
34069128	"populateSlfCandidateList" option is not available under SLF Options in CNCC for feature "SLF Selection from registered NFProfiles"	Configuration for "populateSlfCandidateList" attribute was missing in CNC Console under SLF options. CNC Console GUI is update to list "populateSlfCandidateList"	4	22.1.0
33899527	Changing Log level option for Alternate Route Service is not showing up in CNCC GUI	Alternate RouteService log level change option was not present in CNC Console GUI. CNCC GUI is updated to display log level change option for Alternate Route Service.	4	22.1.0
34044562	enabling SLF feature via CNCC not working when SLF configuration mode is set to “STATIC_SLF_CONFIG_MODE”	Enabling SLF feature through CNC Console was not working for SLF configuration when mode is set to “STATIC_SLF_CONFIG_MODE”.CNCC logic is updated to enable the feature when mode is “STATIC_SLF_CONFIG_MODE”	4	22.1.0

Table 4-11 CNC Console 22.1.0 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
33701659	Console documents should include information on Ingress Gateway cache	Console documents are updated to include information on the Ingress Gateway cache. Added the note about cncc-iam-cncc-iam-igw-cache in the CNC Console IAM microservice section of Oracle Communications Cloud Native Core Console Installation and Upgrade Guide.	4	1.9.0
33729721	CnccCoreIngressGatewayServiceDown and CnccIamIngressGatewayServiceDown alerts issue	CnccIamIngressGatewayServiceDown and CnccCoreIngressGatewayServiceDown alert expressions are updated.	4	1.9.0
33746754	Issues in Manifest File of Oracle	Manifest File is updated as per suggestion to include newline character.	4	1.9.1
33794650	CNCC 1.9.0- Audit and Security logging not working as desired.	Console Audit and Security logging filter was not filtering some of the requests with lower case content type, Console logging filter logic is updated to fix the issue.	4	1.9.0
33894538	CNCC core metric query for user login failure incorrect	There is a documentation error in Login failure metric expression for both Core and IAM. resourcePath should have been /login-actions/authenticate instead of protocol/openid-connect/token for Group By User. The correct expressions are updated in the documentation.	4	1.9.0

4.2.4 CNE Resolved Bugs

CNE Release 22.1.3

Table 4-12 CNE 22.1.3 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
34644811	/var/log/messages file size zero	In the provision log_config task, we set a postrotate script for the logrotate program. This postrotate script is suppose to get rsyslog to reload the /var/log/messages and other file handles after rotation, but it is not working. This bug impacts all hosts or VMs of the baremetal and virtual OCCNE instances.	3	22.1.2,22.2.1,22.3.0
34650732	Improve OCCNE deployment time for large clusters	As systems scale up in number of nodes, the deployment time increases significantly.	3	22.1.2,22.2.1

CNE Release 22.1.2

There are no resolved bugs in CNE Release 22.1.2.

CNE Release 22.1.1

Table 4-13 CNE 22.1.1 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
33983820	LBVM Switchover fails when active lbvm physical host is down in openstack.	The failure to attach all ports that are being switched over to the new active lbvm is due to openstack ports are not getting detached properly from previous active lbvm.	2	1.10.0
34200356	LB monitor process exits on port recreate returning 500 error.	LB monitor process exits when port create request fails due to openstack controller issues.	3	22.1.0

CNE Release 22.1.0

Table 4-14 CNE 22.1.0 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
33734036	LBVM: Duplicate svc names causing LBVMs to go into FAILED state	VCNE : If 2 load balancer service name in 2 different name spaces on vCNE are same, LBVM does not differentiate them and as a result LBVM process crashes and causes LBVM to enter failed state with all load balance IP addresses not available. When 2 cnDBTier are installed in 2 namespaces, such symptom will occur.	3	1.10.0
33831653	LB-Controller removes LBVM IP when a pod is restarted	vCNE : When a pod belonging to service with load balance IP restarts, LBVM logic removes the LBIP and then reassigns when pod is back in running state. The temporary removal of LBIP may cause remote user to unnecessarily divert messages.	3	1.10.0
33749273	Special Character in openstack password results in openstack commands failing within lb controller	vCNE: LBVM code does not handle special characters (!#$%^&) if configured for Openstack password. In this situation LBVM logic and functionality fails.	3	1.10.0
33876855	LBVM's in vcne do not add security group rule that allows ingress traffic on port 3306.	vCNE: LBVM does not allow cnDBTier geo replication traffic though load balance IP addresses.	3	1.10
33876886	Disk usage not reclaimed when files are deleted in BM pvc's. MountOptions : discard needs to be added to all storage class templates.	bmCNE: Ceph storage configuration is missing configuration that will automatically trim worker node storage usage when PVC data is deleted.	3	1.9.1
33733703	Fix PUSHGATEWAY alert rules to use correct reference of pushgateway service name	PUSHGATEWAY alerts are not getting triggered through supplied alert rules since introduction of Prometheus HA feature.	3	1.9.1
33564120	LBVM: addPeerAddrPool.py does not update haproxy template files	vCNE: Procedure to add new external network is manual and error prone. Automate the steps.	3	1.9.1
33564120	LBVM: createFailedLbvm does not update haproxy template files	vCNE: Procedure to recover failed LBVM has many manual and error prone. Increase automation and reduce manual steps.	3	1.9.1
33755419	Deploy.sh trying to set Openstack port post terraform apply from the hostfile input.	vCNE: unnecessary code is setting Openstack port post terraform apply from the hostfile input that will fail if Openstack network subnet is different then one used in Morrisville lab.	3	1.9.1
33356061	NETWORK_INTERFACE_FAILED alert not working for HP Gen10	bmCNE: NETWORK_INTERFACE_FAILED alert is not raised when bare metal OCCNE is installed on HP Gen 10 server.	3	1.7.0

4.2.5 CNC Policy Resolved Bugs

CNC Policy 22.1.4 Resolved Bugs

There are no resolved bugs in CNC Policy Release 22.1.4.

Table 4-15 CNC Policy 22.1.2 Resolved Bugs

Bug Number	Title	Description	Severity	Found In Release
34122498	PDS Stale Data Improvement - Revalidation	Customer has requested that for the very first SMCreate received for a particular UE, PCF will always subscribe to CHF and UDR, regardless of any existing PDS data. Below is an example for CHF use case: 1. When the new npcf-smpolicycontrol request is received and it is the first SM session request for this UE on this specific SM-PCF, SM-PCF shall check if policyCounterInformation and SpendingLimitContext subscription is already present. If yes, SM-PCF shall clean up the locally stored policyCounterInformation and its SpendingLimitContext subscription. 2. When the new npcf-smpolicycontrol request is received and it is the first SM session request for this UE on this specific SM-PCF, SM-PCF shall always trigger a new SpendingLimitContext subscription request to CHF.	3	22.1.0

Table 4-16 CNC Policy ATS 22.1.2 Resolved Bugs

Bug Number	Title	Description	Severity	Found In Release
34122608	SM notify contains null attibutes under SM Policy Decisions in PI-A	SM notify, triggered due to AAR, contains the null attributes within SM policy decision rules, which is causing the SMF or pcf Cli to reject. In earlier releases, PCF never used to send those null attributes.	3	22.1.0

Table 4-17 CNC Policy 22.1.1 Resolved Bugs

Bug Number	Title	Description	Severity	Found In Release
34051415	Bulwark pod CPU's are getting extremely high at 1cps and resulting into call failure.	With Bulwark service enabled the Bulwark pod CPU's are getting extremely high at 1cps and resulting into call failure.	3	22.1.0
34030726	PCF Upgrade causes Service configuration to display default values instead of values from DB	When upgrade from policy 1.15.3 to 22.1.0, GUI is not displaying the data saved in database. For some of the attributes, it is displaying only the default values irrespective of what is saved in the database.	3	22.1.0
34031184	SM Notify Message contains Null attributes causing 400 Reject from SMF.	Optional parameters when not set were getting send as NULL and was causing the issue.	3	22.1.0
34034366	Policy is not fully evaluated due to error with Policy Tables.	When multiple services such as pcf-sm, pcf-am in the system then PRE is unable to process the Policy Table. PRE is loading only the latest updated service related Table.	3	22.1.0
33904333	PCF does not cleanup PDS records when CHF responds with 404 not found.	During PDS Audit cycle, PDS tries to fetch the corresponding SM session from the query service. If query service responds with 404, then PDS will do the session cleanup. The code however currently is checking for 4xx instead and should check for 404 only.	3	1.15.1
34034448	PCF is sending appID info and flow info together in Npcf-UpdateNotify.	afAppId was being converted to appId and being sent out in UpdateNotify to SMF by the SM service.	3	1.15.0

Table 4-18 CNC Policy ATS 22.1.1 Resolved Bugs

Bug Number	Title	Description	Severity	Found In Release
34030777	PCF ATS NF Failure in 1st Run Scenario= Replace_Policy_Table	ATS PCF NF TC Feature Replace_and_Merge_Policy_Table with Scenario Replace_Policy_Table failed in 1st run and passed in automated re-run during VZW overnight runsAs per logs it seems default policy got applied and Error Response not matched was observed	3	22.1.0
34030797	PCF regression Failure in 1st Run Scenario=BindingCreation_AsynchronousMode_policy	ATS Regression TC EnhancedBinding Scenario BindingCreation_AsynchronousMode_policy seems to be regularly failing in 1st runs and passes in automated 1st run or sometimes even in 2nd Run	3	22.1.0

Table 4-19 CNC Policy 22.1.0 Resolved Bugs

Bug Number	Title	Description	Severity	Found In Release
33904100	Policy_Export_With_Missing_Sub_Dependency test case failed during the regression pipeline execution	During bulk import/Export the status record is saved in the database. The current design only supports one Bulk Import/Export at a time but PCF is saving the entries of each Bulk Import/Export execution in database. This is leaving set of stale entries in the database.	3	1.15.2
33804897	Failure in creating udr subscription post failue in DNS SRV lookup	This issue is applicable on systems having istio service mesh installed. PCF is not sending out Subscribe to Notify message to UDR when Retry Profile is configured but DNS is not configured to resolve the alternate NFs.	3	1.14.1
33810824	PCC Rule-Activation-Time avp appearing randomly	When using SystemTime() as Start Time in policy blockly, the potential system time difference between PRE and PCRF-Core could evaluate the Start Time to be behind of the current time of PCRF-Core and thus the Rule-Activation-Time failed to be installed.	3	1.14.0
33749188	PCRF-CORE not sending MCCMNC value to PRE when mccmnc not present in CCR_I	PCRF-CORE is not sending the serving mccmnc value to PRE, when the CCR_I does not contain the serving mccmnc. CCR_I contains the SGSN IP address. It was expected that PCRF-core maps the SGSN IP address to the MCCMNC (based on the SGW IP tablle) and then send that value to PRE.	3	1.15.0
33748869	SGW IP address does not match in the SGW list if list is configured with subnet	when the CCR comes without MCC/MNC and only with SGSN IP address, it is expected to match the Serving-Gateway list configured under Service-configuration -> PCRF CORE and extracts the MCC-MNC and then send that information to PRE for policy evaluation. If incoming CCR_I contains the SGSN IP address which is within the subnet defined in the serving—gateway table, then itdoes not work.	3	1.14.0
33904119	PCF does not install the required charging rule when the policy counter id update happens via SNR, when it is not part of initial SLA	Initially only the existing Policy Counters were considered for OCS update notification but now the new policy counters which are received as part of notification are added to existing policy counters(if not exists).	3	1.15.0
33697316	PGW config is not getting backed up in Bulk Export if duplicate entry present	PGW config is not getting backed up in Bulk Export if duplicate entry present.	3	1.14.0
33641919	Wrong RATtype and IP-CAN-Type values displayed in Session Viewer	Incorrect RATtype and IP-CAN-Type values are displayed in Session Viewer.	3	1.14.0
33904491	Stale PDS records are getting created	Policy was not handling the error response (404) received for CHF PUT request. This was resulting in stale subscriber information in PDS database. Now the CHF error (404) is handled and corresponding subscriber is cleaned up gracefully.	3	1.14.1
33904521	PCF ingress gateway oauthValidator rejects NRF notifications with 401 unauthorized	Policy deployment does not provide the flexibility to configure oauth validation on per interface level.	3	1.11.0
33889404	Policy engine stops after evaluation of Object expression	Policy engine throws an error on encountering a missing path inside the Object Expression block and thereby stops evaluating the policy.	3	1.11.1
33904538	PCF is sending Incorrect UDR URI for SM Create towards UDR	PCF is sending old configured UDR URI towards UDR even though base uri is modified from GUI/REST.	3	1.15.1

4.2.6 NEF Resolved Bugs

OCNEF Release 22.1.2

There are no resolved bugs in NEF Release 22.1.2.

OCNEF Release 22.1.1

There are no resolved bugs in NEF Release 22.1.1.

OCNEF Release 22.1.0

There are no resolved bugs in NEF Release 22.1.0.

4.2.7 NRF Resolved Bugs

NRF 22.1.4 Resolved Bugs

Table 4-20 NRF 22.1.4 Resolved Bugs

Bug Number	Title	Description	Severity	Found In Release
34450193	Discovery query not responded correctly with EmptyList feature when simultaneous requests are received	When the discovery requests are sent in parallel simultaneously and the EmptyList feature is on, the processing during emptyList filter sometimes may results into a race condition. Due to this race condition, the filtered profiles for multiple discovery requests are overlapping with each other which is resulting into inappropriate response.	3	22.1.3
34468772	NF Discover: SLF Lookup not happen for Suspended NF Profiles	SLF look up is happening when NRF has Registered target NF Profiles but Empty List feature works for Suspended target NF profiles Fix is done to perform SLF look up even if NRF do not have NF profiles matching target NF profile.	3	22.1.0
34468871	Supi and Gpsi filter being ignored when slfLookup request is not sent or SLFLookUp didn't result GroupId due to some error	In case SLF request is not sent due to skipping of SLF depending on configuration and SLF didn't result into groupid due to some error, Supi and Gpsi are getting ignored and NF Discovery Response returns NF profiles even SUPI/GPSI not matches with the NF profiles	3	22.1.0

NRF 22.1.3 Resolved Bugs

There are no resolved bugs in NRF Release 22.1.3.

NRF 22.1.2 Resolved Bugs

Table 4-21 NRF 22.1.2 Resolved Bugs

Bug Number	Title	Description	Severity	Found In Release
34122593	Null Pointer Exceptions thrown with high discovery traffic resulting into discovery failure.	When Discovery TPS is beyond 1K TPS, random Null Pointer Exceptions are thrown resulting into Discover processing failure. Issue is not seen if the traffic rate is below 1K	3	22.1.1

NRF 22.1.1 Resolved Bugs

Table 4-22 NRF 22.1.1 Resolved Bugs

Bug Number	Title	Description	Severity	Found In Release
33968318	NRF not maintaining EgressGw route config after helm upgrade, setting it to default config	During upgrade from 1.15.x to 22.1.0, NRF is resetting all the EGW SBI route configurations to default route. Hence, if any SBI Route is configured in EGW, after upgrade, all the Egress Traffic will only use Direct Route, not SBI Route based routing which may result into failure.	2	22.1.0
33893981	unknown attribute maxSlfAttempts is getting returned for slfOptions response	In response to GET/PUT request for nrf-configuration/v1/slfOptions, an unknow attribute maxSlfAttempts is getting returned. There is no impact on functionality. No Impact in functionality. An unused attribute will be returned by NRF in slfOptions response. Also with CNCC, this issue will not occur.	4	22.1.0
33899527	Changing Log level option for Alternate Route Service is not showing up in CNCC GUI	CNCC GUI is not showing option for log level change of alternate-route service.	4	22.1.0
33993237	Alert is missing when Artisan and Alternate-Route Service is down	Alerts are not raised when artisan service and alternate-route service are not available.	4	22.1.0
33979809	NRF 22.1.0 Upgrade from NRF 1.15.1 is failing at ocnrf-alternate-route-pre-upgrade stage in Clusters with Service-Mesh	Upgrading NRF from 22.1.0 is failing if Alternate-Route-Service is enabled. The upgrade fails only on Cluster having Service-Mesh enabled.	4	22.1.0
34033592	NRF - actual configurable parameter name 'populateSlfCandidateList' mismatch with UserGuide and Rest API doc (populateSlfDiscoveredCandidateList)	Actual GET result from the slfOptions configuration as below, GET: {apiRoot}/nrf-configuration/v1/slfOptions "populateSlfCandidateList": false, In NRF UserGuide & Rest API Guide, "populateSlfDiscoveredCandidateList": true Expectation: Parameter name should be aligned with all NRF documents.	4	22.1.0
34044562	[CNCC]: Edit operation in slfOptions in CNCC GUI is failing due to slfDiscoveredCandidateList parameter	Enabling SLF Feature via CNCC when the SLF configuration mode is set to “STATIC_SLF_CONFIG_MODE”, is resulting in Error code 400: Updation of slfDiscoveredCandidateList is not allowed. The same issue is being observed when doing it via REST API. (/nrf-configuration/v1/slfOptions). The issue is happening because of presence of “slfDiscoveredCandidateList” in the PUT payload. As a workaround, in the payload if we remove that parameter, then it works fine. [Expectation] When the SLF configuration mode is set to “STATIC_SLF_CONFIG_MODE” , “slfDiscoveredCandidateList” should be ignore by NRF.	4	22.1.0
34032766	NRF is not selecting SLF based upon Priority when No Locality is present NF Profile.	NRF should select the SLF based upon the Priority/Weight when SLF-NF profile Registered with no locality. 1. NRF Config: slfOptions: "slfConfigMode": "DISCOVERED_SLF_CONFIG_MODE", "maxSLFattempts": 3, "preferredSLFLocality": "", "populateSlfCandidateList": true "featureStatus": "ENABLED" 2. Multiple SLFs registered with NRF. With Locality parameter and Without Locality parameter. 3. Perform UDM Discovery with SUPI from AMF. 4. NRF should select SLF based upon SLF Priority from Registered Profiles. Issue: NRF is populating only SLFs with Locality parameter configured in Registration profile. Expectation: NRF should select SLF based upon Priority when No Locality is present NF Profile.	3	22.1.0
34044607	NRF- Incorrect default values for API slfOptions after Upgrade from 1.15.0 to 22.1.0	NRF- Incorrect default values for API slfOptions after Upgrade from 1.15.0 to 22.1.0 "slfDiscoveredCandidateList": [] (As per REST Guide, Default Value: "" ) Fix:- Rest API Document need to be updated to correct default value to [ ]	4	22.1.0
34044770	NRF- Incorrect default values for API slfOptions (populateSlfCandidateList shown as null) after Upgrade from 1.15.0 to 22.1.0	Incorrect default values for the below mentioned parameters as compared to mentioned in Rest Specification Guide after Upgrade Procedure from 1.15.0 to 22.1.0. URI: {apiRoot} /nrf-configuration/v1/slfOptions 1. "populateSlfCandidateList": null, (As per REST Guide, Default Value: false)	4	22.1.0
34036759	NRF appinfo pod throwing random 503 errors	Random 503 errors are seen in App-Info PODs, which is resulting into NfManagement Service Down in NRF. The issues gets autocorrected in next refresh interval of App-info. So this is an intermittent issue.	3	22.1.0
34053996	Namespace label is missing in few NRF Alerts (e.g. OcnrfTransactionErrorRateAbove50Percent)	Namespace label is missing in few NRF Alerts (for example, OcnrfTransactionErrorRateAbove50Percent).	4	22.1.0
34069128	"populateSlfCandidateList" option is not available under SLF Options in CNCC for feature "SLF Selection from registered NFProfiles"	Enabling below configuration for SLFOption using CNCC GUI: "slfConfigMode": "DISCOVERED_SLF_CONFIG_MODE" "populateSlfCandidateList": true, Configuration option for "populateSlfCandidateList" is not available in CNCC UI to enable the feature "SLF Selection from registered NFProfiles" Without "populateSlfCandidateList" parameter true, Feature can not be activated through CNCC.	4	22.1.0
34084674	Use realtime replicationStatus API as default in install and upgrade loader and documentation	NRF is using non-RealTime DB Status API which is intern have dependency on OSO to provide the replication status. Recommendation is to move to RealTime API which gets the data directly from ndbCluster, hence breaking dependency with OSO. NRF can start using realtime API by doing the below configuration change under geoRedundancyOptions: "replicationStatusUri": "http://occne-db-monitor-svc:3306/db-tier/status/replication/realtime"	3	1.15.1
34082186	Auditor Microservice experiencing JVM out of memory randomly	In NRF Auditor microservice,Due to high metrics data, the Auditor microservice experience JVM out of memory. Auditor is using default 256M JVM memory. Due to this some time Prometheus not able to scrap metrics data from NRF auditor microservice	4	22.1.0
34082174	Auditor Microservice pod restarting randomly while handling exception	OCNRF auditor microservice is restarting randomly when an Exception occurs. When an exception occurs with HeartBeatRemote auditor. Auditor microservice container restarts. This occurs only in corner rainy day cases when HeartBeatRemote auditor experiences the exceptions	3	22.1.0

NRF 22.1.0 Resolved Bugs

Table 4-23 NRF 22.1.0 Resolved Bugs

Bug Number	Title	Description	Severity	Found In Release
33893356	NRF not sending notification for CHF profile if chfInfo/chfInfoList IE is not present in the NFProfile.	NRF is failing to send Notification for the valid Subscriptions, when the chfInfo or chfInfoList IE, which is optional IE, is not present in the CHF's NFProfile. The NFRegister, NFUpdate and NFDeregister service operations are not impacted by this issue.	3	1.15.0
33893606	Discovery request fails if discoveryResultLoadThreshold based feature is enabled and NFProfile is not having load attribute	When discoveryResultLoadThreshold feature is enabled, while processing the discovery request, if NRF finds any NFProfile (for that given TargetNFType) is not having Load IE in the NFProfile, then NRF fails to process the Discovery Request and return error. This issue issue doesn't occurs when discoveryResultLoadThreshold feature is disabled (i.e. value is 0)	3	1.15.0
33893936	High increase in Discovery failure count observed during load test	When Ingress Discovery traffic is more than 1650 TPS, high latency is observed in Discovery Micro-Service which is resulting into timeouts in IGW.	3	1.15.0
33893546	Added Missing metrics and removed deprecated metrics from NRF Guides	There were some metrices which gets pegged by NRF micro-services, were not part of the NRF Documentation. Also there were some metrices which are no more pegged by NRF micro-services and also not part of any Alert file, were present in the NRF Documentation. All these have been fixed in the User Documentation.	4	1.15.0
33893578	NRF fails to consider the starting "0" (if configured) in dayZeroConfiguration.hplmnList[].mnc helm parameter	During NRF Installation, if dayZeroConfiguration.hplmnList[].mnc helm parameter is planned to be used to configure NRF's HPLMNs, and the MNC component of the HPLMN contains a leading "0" , then NRF is stripping the leading "0" while validating the HPLMN value. This is resulting into validation failure, thus the HPLMN never gets configured. Configuring the HPLMN using REST/CNCC (nrfPlmnList attribute of nrf-configuration/v1/generalOptions API) is not impacted by this issue.	4	1.15.0
33893626	NRF CSAR package validation is failing due to stricter CSAR validation logic.	As per CSAR best practice guideline, there should be escape new line character in-between the blocks present in the NFVD file of the CSAR package. The manifest file defines the location and digest of all the artifacts located in the CSAR package. IN the manifest file, the "Source", "Algorithm", "Hash" represents a single block where the "Source" field is mandatory and the rest are optional. The blocks defined in the manifest file must be separated with each other by a newline escape sequence. Otherwise, the same will not be accepted in the NFVD.	4	1.15.0
33604187	NRF should strip interPlmnFqdn from the NFService level if present for home scenario.	If an NF registers with NRF with interPlmnFqdn in NFService, then NRF is not stripping the interPlmnFqdn from the NFService while sending Discovery response for non-Roaming scenarios. However if interPlmnFqdn is present in NFProfile level, then for non-Roaming scenarios, NRF does the due diligence by stripping it out from the NFProfile while sending discovery response.	4	1.15.0
33893853	bucketizing Latency Metric to limit fix number of buckets	For the latency metrics pegged by NRF micro-services, there is no fixed number of buckets. This is resulting into creating time-series database for each unique latency value (which could be very large in number). This may result into filling Prometheus memory and/or NRF POD memory when the POD is running for a very long time. The latency values are now divided into fixed number of buckets so that for each unique latency value, a new time-series database will not be created.	4	1.15.0
33893864	Diameter identity regular expression is not aligned to 29571-15.5.0	As per 29.510, F50, DiameterIdentity IE (part of pcfInfo IE of NFProfile) is a String containing a Diameter Identity, according to clause 4.3 of IETF RFC 6733 [18]. Pattern: '^([A-Za-z0-9]([-A-Za-z0-9])\.)+[a-z]{2,}$' However NRF is mandating to have “-“ character in each label of the fqdn or realm of the diameter identity which is not required.	4	1.14.0
33893887	NRF is returning 500 Error if authorizeRequesterNf flag is set to disable in AccessTokenOptions and accesstoken request is sent to vNRF	NRF is hitting NullPointerException (which is resulting into 500 Error response) when authorizeRequesterNf under nrf-configuration/v1/nfAccessTokenOptions is set to disabled and a Roaming AccessToken request is being processed by NRF for sending it to vNRF.	4	1.15.0
33893900	CNC Console GUI -> forwardingOptions throws an error while trying to save the changes made.	CNC Console GUI -> forwardingOptions throws an error while trying to save the changes made. The attributes forwardingRulesConfig and forwardingFeatureRulesConfig names are mismatched from the Rest attributes which is resulting in forwardingOptions PUT operation failure. However user wills till be able to delete using CLI based REST client.	4	1.15.0
33521204	NRF CNCC SLF Look up configuration delete is not available	There is no option in NRF CNCC gui to delete SLF Look up configuration. However user wills till be able to delete using CLI based REST client.	4	1.12.0
33521288	Last value of keyDetailsList in nfAccessTokenOptions cannot be cleared using CNC Console	Last value of keyDetailsList in nfAccessTokenOptions cannot be cleared using CNC Console. However user wills till be able to delete using CLI based REST client.	4	1.12.0
33248344	slfOptions.featureStatus is accepting invalid values if CLI based REST client is used	slfOptions.featureStatus is accepting invalid value "ENABELD" as its value, instead of sending 400 BAD_REQUEST while updating the parameter.	4	1.15.0
33973036	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	If a NF has provided more than one than one allowedXXX attribute, then NRF is considering the profile as eligible profile for sending Notification, if one of the allowedXXX attribute is resulting into success (even if another allowedXXX attribute which got evaluated before is resulting into failure) NRF should not send Notification if at least of the allowedXXX attribute fails.	4	1.15.0
33893910	Wrong label reference in NRF Installation Guide while configuring PeerAuthentication for Service Mesh based deployment.	While creating the PeerAuthentication rule for deployment of NRF in Service Mesh enabled cluster, the user needs to provide correct label selector. In the documentation, it is mentioned that in the label ""app.kubernetes.io/part-of: ocnrf"", ocnrf is the NRF helm release name. Where as the value "ocnrf" is fixed and should not be changed.	4	1.15.0

4.2.8 NSSF Resolved Bugs

NSSF 22.1.2 Resolved Bugs

There are no resolved bugs in NSSF Release 22.1.2.

NSSF 22.1.1 Resolved Bugs

Table 4-24 NSSF 22.1.1 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
34119541	Data too long for column service_name.	Data are too long to accommodate in the column, service_name.	3	22.1.0
34122264	NSSF is answering 200 OK to POST nssai-availability subscriptions instead of 201	Instead of 201, NSSF is responding with 200 OK while sending a POST request for nssai-availability subscriptions.	2	22.1.0

NSSF 22.1.0 Resolved Bugs

There are no resolved bugs in this release.

4.2.9 SCP Resolved Bugs

Table 4-25 SCP 22.1.4 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
34673576	Inter SCP notification routing not working when request URI is missing service name	Inter SCP notification routing is not working when request URI is missing service name and the requests were forward routed to producer NFs.	2	22.1.2

Table 4-26 SCP 22.1.3 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
34177995	Addition of cleanup steps at the end of NF SUSPENDED state handling feature FTs	NF Suspended Feature files were missing some cleanup steps resulting in subsequent cases failures. Added missing steps to cleanup configuration done for feature.	3	22.1.2
34326927	Fix Notification service SSE client duplicate init and Log level change from DEBUG to Error for SSEClient Code	Fixed Notification service SSE client duplicate init and Log level changed from DEBUG to Error for SSEClient Code	3	22.1.2
34249989	Configuration module restart observed when scp-worker pod replica scaled to 0	Scaling scp-worker replica down and then up results in configuration module restart	3	1.15.3

Table 4-27 SCP 22.1.2 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
34094845	Existing ingress/egress traffic metrics are not getting pegged for https.	ocscp_metric_http_rx_req_total or ocscp_metric_http_tx_req_total metrics were not pegged for https traffic.	2	22.1.1
34019705	SCP should not add via header when request is initiated by SCP microservices itself.	SCP was adding header when initiating delegated discovery request towards NRF resulting in loop detection in SCP.	2	22.1.0
34019726	SCP appending "null" in 3gpp-sbi-target-apiroot in model-D inter plmn routing	SCP was adding null apirPrefix to 3gpp-sbi-target-apiroot when NF is registered without apiPrefix in the NF profile.	2	22.1.0
34037543	SCP sending incorrect format for 3gpp-sbi-target-apiroot header in response.	SCP was not adding scheme and port to 3gpp-sbi-target-apiroot header added in response.	2	22.1.1
34089227	SCP returns an incorrect root api header value in case of received Notification Request with Discovery headers.	SCP was responding with 3gpp-sbi-target-apiroot header as NA in case of Notification Request with Discovery headers.	2	22.1.1
34072394	Coherence Cluster Name correction to restrict the total length to 66 characters.	SCP deployment was failing because coherence cluster was exceeding 66 characters due to the long release name. Helm charts are updated not to append release name and namespace to coherence cluster name and value provided in the deployment file is only used.	3	22.1.0
34093590	Jaeger tracing not working for some scp generated error responses.	SCP was not sending spans to Jaeger for some of SCP generated error response.	3	1.15.0
34094893	Upgrade failed due to scp-worker-init missing resource limits.	scp-worker init container was missing resource definition for CPU and memory in the Helm charts.	3	22.1.1
34094914	Routing Options Update fails with Internal Server Error after upgrade.	errorProfileConfiguration in routing option was not populated with default values after upgrade resulting in error while trying to update routing options.	3	22.1.1
33990755	SCP responding with incorrect 3gpp-sbi-producer-id header to consumer NF.	SCP was sending incorrect format for 3gpp-sbi-producer-id header to consumer NF.	3	22.1.1
34093613	SCP responds with 508 LOOP_DETECTED for the UDM Notification request.	SCP was not updating destination host to NF from apiPrefix in URI in case of reverse proxy notification request routing. Therefore, forward routing request to itself resulting in loop.	3	1.15.2
34112492	ATS incorrectly building the location header for validation.	ATS was incorrectly building location header for validation of actual location header received in response and thus resulting in ATS testcase failure.	3	22.1.1
34084233	ATS Fetch logs upon failure for AppLog and PcapLog option not working.	ATS fetches logs upon failure for AppLog and PcapLog options were not working.	4	22.1.0
34045995	scp-nrfproxy service not listed in Logging Config to change log level.	Scp-nrfproxy service was not listed for logging level in the CNC Console. CNC Console is updated to list scp-nrfproxy under the logging level.	4	22.1.0

Table 4-28 SCP 22.1.1 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
33962241	Alternate route failed with apiroot and nfset when apiroot doesn't match any registered profile	Alternate routing using "3gpp-Sbi-Routing-Binding" headers is not happening when routing using "3gpp-Sbi-Target-apiRoot" is failed and profile is not learned by SCP.	2	1.15.0
33904845	Helm chart changes to bypass sidecar proxy for DNS queries	Helm chart changes to bypass sidecar proxy for DNS queries.	3	1.15.2
33924377	Forward Routing fix for 3gpp-Target-Api-Root Header with Intra Plmn fqdn where fqdn contains mcc and mnc	Forward route to 3gpp-Sbi-target-ApiRoot not working in case of inter PLMN FQDN in 3gpp-Sbi-target-ApiRoot.	3	22.1.0
33966463	SCP should not add "User-agent" header in indirect communication	SCP should not add the User-agent header in indirect communication.	3	22.1.0
33966476	SCP is adding "accept-encoding:gzip" header to requests while routing out	SCP is adding accept-encoding header resulting in two accept-encoding to producer.	3	1.14.1
33956765	Even with reverseProxyEnabled set to false, SCP append UDR and its own rootapi in location header back to PCF POST request	Location headers should not be updated with reverse proxy api prefix for Model D scenarios.	3	22.1.0
33956774	SCP is not adding 3gpp-sbi-producer-id when binding header is not sent from producer NF when Model-D feature is enabled in SCP	SCP is not adding 3gpp-sbi-producer-id when binding header is not sent from producer NF when Model-D feature is enabled in SCP.	3	22.1.0
33956778	SCP forwarding discovery header to UDR while model-d feature enabled	SCP forwarding discovery header to UDR while model-d feature enabled.	3	22.1.0
33966523	Location header is incorrectly updated in response when headers to be addition to apiPrefix for reverse proxy routing	Location header is incorrectly updated in response when headers to be added to apiPrefix for reverse proxy routing	3	1.15.0
33966529	SSE Session audit changes to iterate on local copy of SSE Handles	Observed that egressRL logs were written to worker pods during the duration runs.	3	22.1.0
33966543	ATS enhancement to support timeout at configuration client, if response is not received by configuration client	SCP ATS new features hung and had to abort manually.	3	1.15.1
33966511	Model D: Adding more validation and cache clearance when disable the feature	Adding more validation and cache clearance when disable the Model D feature.	4	22.1.0
33894405	Metric pegging is missing for ondemand	The ocscp_audit_ondemand_success_total metric is not pegging.	4	1.15.0
33904805	SCP sends duplicate subscription/unsubscription request towards NRF.	Connection reestablishment on configuration pod resulting in multiple threads and thus causing duplicate de-subscription/subscription requests are forwarded to NRF due to race conditions.	4	1.15.2

Table 4-29 SCP 22.1.0 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
33673751	Cluster domain is not getting updated in few New feature files	DNS Srv and Server header features are failing when executed in different cluster domain than default domain.	3	1.15.0
33791930	Fix of FT for "VZW:- Getting AttributeError "NoneType' while running Routing_Rules_API_R16.feature	Enhance ATS framework to handle scenario where incorrect data is received in routing rule API response.	3	1.15.0
33791945	SCP adding Empty data frame to request with HTTP GET Method.	SCP adds empty data frame with end stream set. Therefore, the end stream is set to false in header frame.	3	1.15.0
33791959	SCP-worker exception when updating location header for reverse proxy routing	SCP-worker has some limitations when updating the location header for request without apiPrefix for reverse proxy routing.	3	1.15.0
33882889	Exception in scp-worker on metric peg during message discard due to pod overload control	SCP-Worker is generating 500 internal server error due to metric peg failure when pod-overload-action-policy is set to SILENT_DISCARD.	3	1.15.0
33890294	Scp-worker is not re-routing to other producer if 307 response has incorrect location header	SCP-worker does not reroute to other producer NFs if 307 response is received if location header with incorrect syntax is received.	3	1.15.0
33882924	Perform validation on Topology Source in REST PUT operations	Enforce validation in topologysourceinfo object. It should not be null and must contain either NRF or LOCAL.	4	1.15.0
33883021	CSAR sha needs to have newline after each sha (manifest file)	An escape new line character in between the blocks is added to address missing escape new line character.	4	1.15.0
33883105	Fix the FT <Worker_Pod_Overload_Ctrl_Policy_Config_API.feature> for validating the response of step <Then Get data for SCP Worker_Pod_Overload_Ctrl_Policy ss1>.	Enhance Validate response step in ATS Framework to handle exception cases where incorrect data is received in response.	4	1.15.0
33885113	Update metric for SCPAuditEmptyArrayResponse	Metric in expression of alert is incorrect and thus no alert was raised even when empty response is received from NRF by audit.	4	1.15.0
33883056	Update rate limiting scenario which are high rate and tolerance	The rate limiting scenarios are updated with high rate and tolerance for better performance.	4	1.14.1
33883148	Enable automatic ATS cleanup to revert default values for different levels (WANR, MINOR, MAJOR, CRITICAL) for CPU overload control policy	Enhance ATS cleanup to enable reverting to default values for different levels (WANR, MINOR, MAJOR, CRITICAL) for CPU overload control policy.	4	1.15.0
33888551	Update EgressRateLimiting_InterSCP.feature to remove extra space in update json step	Correct Update json step in feature file which is adding additional empty characters in data file.	4	1.15.0

4.2.10 SEPP Resolved Bugs

SEPP 22.1.2 Resolved Bugs

Table 4-30 SEPP 22.1.2 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
34214949	SEPP on AWS Load Balancer IP not assigned to the Config-Mgr Service.	Due to an incorrect load balancer annotation in config-mgr-svc, load balancer IP is not assigned to config-mgr-svc in AWS. Corrected the annotation and formatting issue in Helm.	2	22.1.1

Table 4-31 SEPP 22.1.1 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
34101522	Multi-partner/Multi-PLMN routing is not working	SEPP drops all request for all roaming partners. A request destined for a PLMN for which there is a valid N32C handshake is dropped by N32 EGW with an error 500 -Route Not Found. This was a rare scenario which occurs if RemoteSeppSet is configured before handshake is completed with Remote Sepp	2	22.1.0
34101534	Delete Header table if already exist at the time of installation	When helm install is run after running the helm uninstall, at times installation fails as header table created as part of helm-install hook does not get deleted. As a part of fix, delete the helm table ( if already created) automatically while doing the helm-install.	3	22.1.0
34101518	SEPP 22.1.0 custom Yaml file Missing Parameters	Following details are missing from custom-values.yaml file Metalllb info N32 Keep alive info SEPP error response standards compliance	3	22.1.0
34041317	No data being displayed for KPI: cn32f Request Failures Total and pn32f Request Failures Total	Formula used: sum(ocsepp_cn32f_requests_failure_total) ocsepp_cn32f_requests_failure_total counter seems to be missing from Prometheus. pn32f Request Failures Total Formula used: sum(ocsepp_pn32f_requests_failure_total) ocsepp_ pn32f_requests_failure_total counter seems to be missing from Prometheus.	3	22.1.0
33967347	SEPP Handshake Alert is not firing at pSEPP	There are some pn32c-handshake-failure scenario in which ocsepp_n32c_handshake_failure metric is not getting updated. Wrong FQDN sent in securityCapabilityExchangeMessage.	3	22.1.0
34122246	Metrics lacking dimension details	ocsepp_cn32c_handshake_response_total was lacking dimension details.	3	22.1.0
34108902	Details for labels : namespace, podname are not populated in alert EgressSbiErrorRateAbove1Percent	Podname and namespace fields display no data. Also, all labels are not displayed in the alert EgressSbiErrorRateAbove1Percent.	4	22.1.0
34057469	SEPP Deployment Failing (in aws) with ViolationException: Duplicate entry '1' for key 'header.PRIMARY'	Currently pre-install-hook provides values of header_id column which is already defined with AUTO_INCREMENT. Fix: Added null to the column value so that mysql can provide with a unique value.	4	22.1.0
34041298	Formula for KPI cn32f Routing Success Rate, cn32f Requests Rate Per Remote SEPP and cn32f Response Rate Per Remote SEPP is different from what is stated in user guide.	Some of the formulas are incorrect in User guide	4	22.1.0
34031709	OCSEPP 22.1.0 Helm chart APP version reads 1.7.0.0.0	The Helm chart APP version field indicates version 1.7.0..0 when the actual version should be 22.1.0	4	22.1.0
34031351	Correct counter name needs to be corrected in KPI pn32f Routing Success Rate and pn32f Response Rate Per Remote SEPP	KPI: pn32f Routing Success Rate Present formula: (sum(ocsepp_pn32f_response_total)/sum(ocsepp_pn32f_requests_total))*100 Counter name ocsepp_pn32f_response_total needs to be corrected to ocsepp_pn32f_responses_total so that data is fetched. KPI: pn32f Response Rate Per Remote SEPP Present formula : sum(irate(ocsepp_pn32f_response_total[2m])) Counter name ocsepp_pn32c_handshake_response_total needs to be corrected to ocsepp_pn32f_responses_total so that data is fetched.	4	22.1.0
34031338	Align the response code and also correct the formula correspondingly for ocsepp_pn32c_handshake_response_total	Incorrect formula	4	22.1.0
34031200	Summary and label section need to display values to all variables for alert ocsepp_n32c_handshake_failure	Details for labels : namespace, podname, nfinstanceId are not populated in alert ocsepp_n32c_handshake_failure.Response returned from Prometheus as a result of query :ocsepp_n32c_handshake_failure ocsepp_n32c_handshake_failure	4	22.1.0
34031165	Appropriate response code should be returned for metric ocsepp_cn32c_handshake_response_total in case of SOCKET_TIMEOUT_EXCEPTION	As a part of metric ocsepp_cn32c_handshake_response_total response in case of SOCKET_TIMEOUT_EXCEPTION is returned as a part of response code whereas appropriate response code should be returned.	4	22.1.0
34031118	Formula needs to be corrected for cn32c Handshake Success rate	P resent Formula (sum(ocsepp_cn32c_handshake_response_total {responseCode="200"})/sum(ocsepp_cn32c_handshake_requests_total))*100 No data is returned as a result of this formula.	4	22.1.0
34108923	Metric details missing from SEPP user guide	Some of the ingress GW metrics details were missing from Installation guide	4	22.1.0
34031698	SEPP documentation issues in 22.1.0 Installation Guide	Improvements suggested in installation guide	4	22.1.0
34030603	Get handshake status API needs to be updated	Updated REST API document	4	22.1.0
33957599	Documentation gap for SEPP topology hiding	Added documentation details for Topology hiding and recovery in the document	4	22.1.0

Table 4-32 SEPP ATS 22.1.1 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release	Fix available in SEPP ATS Release
33967864	SEPP PI-A ATS Regression test cases are Failing	Kubernetes service was not created, due to which few cases in regression pipeline are failing.	2	22.1.0	22.1.1
3957569	ATS New Features PN32F_Topology_Hiding cases are Failing	Kubernetes service was not created, due to which few Topology Hiding cases in regression pipeline are failing.	2	22.1.0	22.1.1

Table 4-33 SEPP 22.1.0 Resolved Bugs

Bug Number	Title	Description	Severity	Found in Release
33672972	Add support for 'content-type: x-www-form-urlencoded' messages in SEPP	After the movement from undertow to jetty in N3f microservices,x-www-form-urlencoded is no longer supported in SEPP. When a message withcontent-type=x-www-form-urlencoded is received on N32F interface,,"error":"Unsupported Media Type" is reported .	2	1.7.1
33714546	SEPP registration does not get initiated with default helm values	With the default configuration, the registration request is not being sent to NRF. Workaround: The customer has to update the default configuration in HELM before running the HELM install. Fix: Fixed the default configuration to do the SEPP registration in NRF without making any change.	3	1.7.1
33714643	Error logs seen in NF management pods	While ding HELM install, a few errors and warning logs were visible in the NF Management pod. Port used to communicate with config-mgr-svc was incorrect in the default configuration file. Workaround: The customer has to update the config-mgr-svc port in HELM before running the HELM install. Fix: Updated the correct port in the default configuration file.	3	1.7.1

4.2.11 UDR Resolved Bugs

UDR Release 22.1.2

Table 4-34 UDR 22.1.2 Resolved Bugs

Bug Number	Title	Description	Severity	Found In Release
SR: 3-29763249271	SLF-CSAR Package-p34124422_116000_Tekelec- udr-nfvd.yaml is having path mismatch	There is a patch mismatch in the SLF-CSAR Package-p34124422_116000_Tekelec- udr-nfvd.yaml file. Resolution: Updated the CSAR with correct info	4	22.1.1
SR-3-29709747751	VZW ME LAB: SLF 22.1.1 ProvGW Auditor Enabled / Large No of "OcudrSubscriberNotFoundAbove50Percent"	Need changes in SLF_Alertrules_old.yaml for subscriber not found. Resolution: Updated the Alert file with correct metrics	4	22.1.1
SR 3-29451282341	VZW RCN LAB SLF PI-A 2022: nudr-dr-provsevice pod down alerts is firing even when pod is up/running	Pod down alerts triggers even when the pod is up and running Resolution: Updated the Alert file with correct metrics	4	22.1.0

UDR Release 22.1.1

There are no resolved bugs in UDR Release 22.1.1.

UDR Release 22.1.0

There are no resolved bugs in UDR Release 22.1.0.

4.3 Known Bug List

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

4.3.1 BSF Known Bugs

BSF 22.1.4 Known Bugs

There are no new known bugs in BSF Release 22.1.4.

BSF 22.1.3 Known Bugs

There are no new known bugs in BSF Release 22.1.3.

BSF 22.1.2 Known Bugs

There are no new known bugs in BSF Release 22.1.2.

BSF 22.1.1 Known Bugs

There are no new known bugs in BSF Release 22.1.1.

BSF 22.1.0 Known Bugs

The following table lists the known bugs for BSF Release 22.1.0:

Table 4-35 BSF 22.1.0 Known Bugs

Bug Number	Title	Description	Customer Impact	Severity	Found in Release
33904434	"RoleBinding is deprecated in v1.17+" Warning observed while installing PCRF 1.15.0 in CNE 1.9.1	During BSF deployment helm installation will throw a warning.	None	4	1.15.0

4.3.2 cnDBTier Known Bugs

DBTier Release 22.1.3

Table 4-36 DBTier 22.1.3 Known Bugs

Bug Number	Title	Description	Customer Impact	Severity	Found in Release
34305187	After cnDBTier stop and start, data (ndbmtd) pods go into CrashLoopBackOff	NDB MySQL Cluster never comes up, as not all of the data (ndbmtd) pods start.	NDB MySQL Cluster does not comes up. Workaround: Set an appropriate StartPartialTimeout value in the [custom_]values.yaml file for a cluster before installing cnDBTier. To stop and start the cnDBTier clusters with a large number of data pods, see Oracle Communications Cloud Native Core DBTier User Guide.	3	22.1.2

DBTier Release 22.1.2

There are no known bugs in DBTier Release 22.1.2.

DBTier Release 22.1.1

There are no known bugs in DBTier Release 22.1.1.

DBTier Release 22.1.0

There are no known bugs in DBTier Release 22.1.0.

4.3.3 CNC Console Known Bugs

CNC Console Release 22.1.3.

There are no new known bugs in CNC Console Release 22.1.3.

CNC Console Release 22.1.2.

There are no new known bugs in CNC Console Release 22.1.2.

CNC Console Release 22.1.1

There are no new known bugs in CNC Console Release 22.1.1.

CNC Console Release 22.1.0

There are no new known bugs in CNC Console Release 22.1.0.

4.3.4 CNE Known Bugs

CNE Release 22.1.3

There are no known bugs in CNE Release 22.1.3.

CNE Release 22.1.2

There are no known bugs in CNE Release 22.1.2.

CNE Release 22.1.1

There are no known bugs in CNE Release 22.1.1.

CNE Release 22.1.0

There are no known bugs in CNE Release 22.1.0.

4.3.5 CNC Policy Known Bugs

CNC Policy 22.1.4 Known Bugs

There are no new known bugs in CNC Policy Release 22.1.4.

CNC Policy 22.1.2 Known Bugs

There are no new known bugs in CNC Policy Release 22.1.2.

CNC Policy 22.1.1 Known Bugs

The following table lists the known bugs in CNC Policy Release 22.1.1:

Table 4-37 CNC Policy 22.1.1 Known Bugs

Bug Number	Title	Description	Severity	Found in Release	Customer Impact
34051841	For On Demand UDR Discovery Subsequent messages failure are not retried on Alternate Route based on NF Sets	For On Demand UDR Discovery Subsequent messages failure are not retried on Alternate Route based on NF Sets	3	22.1.0	For On Demand UDR Discovery Subsequent messages failure are not retried on Alternate Route based on NF Sets Workaround: DNS SRV records can be configured with the appropriate priority. Doing this way on subsequent message failure alternate route can be discovered from DNS SRV record.

CNC Policy 22.1.0 Known Bugs

The following table lists the known bugs in CNC Policy Release 22.1.0:

Table 4-38 CNC Policy 22.1.0 Customer Known Bugs

Bug Number	Title	Description	Severity	Found in Release	Customer Impact
33904351	Validation failed on update NF Comm Profile on CM UI	NF Communication profile is not handling the special character in the name. Either special character shall not be allowed and if allowed shall be supported across create, update and delete operation.	4	22.1.0	User will not be able to Edit the profile if they have used character like # in the name Workaround: Avoid using special character in the name
33904374	LDAP traffic stops being reported when SSV is enabled	When SSV is enabled, LDAP traffic stops.	3	22.1.0	This particular call model is not performant. Workaround: None
33904434	"RoleBinding is deprecated in v1.17+" Warning observed while installing PCRF 1.15.0 in CNE 1.9.1	During Policy deployment helm installation will throw a warning.	4	1.15.0	None
33904441	Policy UI sometimes allows Model D with discovery parameter as TARGET_NF_SET_ID and some other anomalies as well	In the Add Initial discovery parameter window, when CLOSE button is clicked, then PARAM NAME drop down is not getting refreshed.	3	22.1.0	When CLOSE button is clicked, then PARAM NAME drop down is not getting refreshed. Workaround: In the Add Initial discovery paramter window, Use SAVE and CANCEL buttons to close the window. Clicking CLOSE button, will cause the issue reported in the Bug.
33904838	Nevada_PCF_22.1.0_RC_ATS_test_case_failing- Pcrf_core_audit	PCRF Core Audit test cases in Converged mode is failing in ATS execution.	3	22.1.0	This issue is observed in seldom ATS runs, because of thread race condition. It is not observed while performing Manual Testing. Workaround: Rerun ATS.
33904333	SM sessions have no corresponding PDSsub data session	Subscriber sessions are getting deleted in Policyds tables for existing subscriber in SM.	3	1.14.1	Subscriber sessions are getting deleted in Policyds tables for existing subscriber in SM. Workaround: None

4.3.6 NEF Known Bugs

OCNEF Release 22.1.2

There are no known bugs in NEF 22.1.2.

OCNEF Release 22.1.1

There are no known bugs in NEF 22.1.1.

OCNEF Release 22.1.0

There are no known bugs in NEF 22.1.0.

4.3.7 NRF Known Bugs

OCNRF Release 22.1.3

There are no new known bugs in this release. For existing known bugs, see Table 4-39.

OCNRF Release 22.1.2

There are no new known bugs in this release. For existing known bugs, see Table 4-39.

OCNRF Release 22.1.1

Table 4-39 NRF 22.1.1 Known Bugs

Bug Number	Title	Description	Customer Impact	Severity	Found in Release
34082721	Continues Error Log in Perf-Info Pod for Jaeger Tracing Issue	In the perf-info service, error logs are observed periodically (in every 30 seconds) due to jaeger configuration. There is no functionality of perf-info impacted.	This does not have any impact on the Overload Control functionality. So the logscan can be silently ignored.	4	22.1.1
34086430	NRF- SLF Discovered Candidate List is still populated even after "populateSlfCandidateList": false for feature NRF-SLFQuery via SCP	Once set parameter "populateSlfCandidateList": true and reset to "populateSlfCandidateList": false, "slfDiscoveredCandidateList" is still getting populated with Registered SLF.Expectation: "slfDiscoveredCandidateList" parameter should not get populated with Registered SLFs.	This does not have any impact in Traffic processing logic. When populateSlfCandidateList is set to false, NRF will not use the SLFs available in slfDiscoveredCandidateList even if it not empty.	4	22.1.0
33893981	unknow attribute maxSlfAttempts is getting returned for slfOptions response	In response to GET/PUT request for nrf-configuration/v1/slfOptions, an unknow attribute maxSlfAttempts is getting returned. There is no impact on functionality.	No Impact in functionality. An unused attribute will be returned by NRF in slfOptions response. Also with CNCC, this issue will not occur.	4	22.1.0
33894008	NFService level load is not used for calculating NF's load for discoveryResultLoadThreshold feature when Discovery Query is with service-names query parameter having one service in it.	When Discovery query is having service-names query parameter having one service in it, then during load calculation, for discoveryResultLoadThreshold, NRF should consider the NFService level load, if present, else, it will consider NFProfile level load, if present, else, it will use default configured load (defaultLoad). But NRF is not considering the calculated load for discoveryResultLoadThreshold feature when profile load is null and there is one service with load. If discoveryResultLoadThreshold feature is disabled, (value as 0), this issue is not observed.	Discovery for a single service, NRF will start using the configured defaultLoad for applying discoveryResultLoadThreshold feature even if load is present in NFService.	4	1.15.0

OCNRF Release 22.1.0

Table 4-40 NRF 22.1.0 Known Bugs

Bug Number	Title	Description	Customer Impact	Severity	Found in Release
33893981	unknow attribute maxSlfAttempts is getting returned for slfOptions response	In response to GET/PUT request for nrf-configuration/v1/slfOptions, an unknow attribute maxSlfAttempts is getting returned. There is no impact on functionality.	No Impact in functionality. An unused attribute will be returned by NRF in slfOptions response. Also with CNCC, this issue will not occur.	4	22.1.0
33894008	NFService level load is not used for calculating NF's load for discoveryResultLoadThreshold feature when Discovery Query is with service-names query parameter having one service in it.	When Discovery query is having service-names query parameter having one service in it, then during load calculation, for discoveryResultLoadThreshold, NRF should consider the NFService level load, if present, else, it will consider NFProfile level load, if present, else, it will use default configured load (defaultLoad). But NRF is not considering the calculated load for discoveryResultLoadThreshold feature when profile load is null and there is one service with load. If discoveryResultLoadThreshold feature is disabled, (value as 0), this issue is not observed.	Discovery for a single service, NRF will start using the configured defaultLoad for applying discoveryResultLoadThreshold feature even if load is present in NFService.	4	1.15.0

4.3.8 NSSF Known Bugs

NSSF 22.1.2 Known Bugs

There are no new known bugs in this release.

NSSF 22.1.1 Known Bugs

There are no new known bugs in this release.

NSSF 22.1.0 Known Bugs

There are no new known bugs in this release.

4.3.9 SCP Known Bugs

SCP Release 22.1.4

There are no new known bugs in this release. For existing known bugs, see Table 4-41.

SCP Release 22.1.3

There are no new known bugs in this release. For existing known bugs, see Table 4-41.

SCP Release 22.1.2

There are no new known bugs in this release. For existing known bugs, see Table 4-41.

SCP Release 22.1.1

There are no new known bugs in this release. For existing known bugs, see Table 4-41.

SCP Release 22.1.0

Table 4-41 SCP 22.1.0 Known Bugs

Bug Number	Title	Description	Customer Impact	Severity	Found In Release
33594355	Wrong ASM Server Header implementation causes ATS test case failures	An incorrect ASM server header implementation is causing ATS failures.	Due to ASM issue, some ATS test cases are removed.	4	22.1.0

4.3.10 SEPP Known Bugs

OCSEPP Release 22.1.2

There are no new known bugs in SEPP Release 22.1.2.

OCSEPP Release 22.1.1

There are no new known bugs in SEPP Release 22.1.1.

OCSEPP Release 22.1.0

There are no new known bugs in SEPP Release 22.1.0.

4.3.11 UDR Known Bugs

OCUDR Release 22.1.2

There are no new known bugs in this release. For existing known bugs, see UDR 22.1.0 Known Bugs.

OCUDR Release 22.1.1

There are no new known bugs in this release. For existing known bugs, see UDR 22.1.0 Known Bugs.

OCUDR Release 22.1.0

Table 4-42 UDR 22.1.0 Known Bugs

Bug Number	Title	Description	Customer Impact	Severity	Found in Release
30774755	Headers for few resources are not implemented as per spec 29505-v15.4.0.	Some of the headers including `Cache-Control¿, `ETag and `Last-Modified are not sent by UDR upon a success GET request for few resources.	No impact. UDM (consumer of UDM APIs) does not send conditional attributes to UDR.	3	1.4.0
30774742	UDR is not validating the conditional attributes for UDM APIs.	As per the spec 29.504, there are some conditional attributes for UDM data which are not validated by UDR. This affects only UDM APIs on UDR.	No impact. UDM (consumer of UDM APIs) does not send conditional attributes to UDR.	4	1.3.0