Resolved and Known Bugs

4 Resolved and Known Bugs

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

BSF Resolved Bugs

Table 4-1 BSF 1.10.1 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33459045	3	1.7.2	Prometheus issue in functional lab
33459109	3	1.9.0	Diameter Peer in GR setup keeps going down
33459148	3	1.9.0	Policy and BSF installation is not working

Table 4-2 BSF 1.10.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33132080	3	1.9.0	Failed to remove the diam connection when the last peer node configuration is deleted
32377395	3	1.7.0	occnp_diam_conn_backend measurement is incremented for {appType="pcf",} for bsf

CNC Console Resolved Bugs

Table 4-3 CNC Console 1.8.1 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33316527	4	1.7.0	Unable to open Common Services component GUI through CNCC
33316539	4	1.7.0	Policy project deletion not happening through CNCC GUI
33446327	4	1.7.0	Modifying SiteID to SiteName in NRF (CNCC GUI) and custom yaml

Table 4-4 CNC Console 1.8.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33173804	Minor	1.6.1	VzW _CNCC test pod comes up before the application pods
32291223	Minor	1.5.0	CNCC: CNE Common Services type should be ClusterIP when accessed via CNCC
33157991	Minor	1.7.0	Update custom annotation for Metallb address pool in CNE environment

CNE Resolved Bugs

Table 4-5 cnDBTier 1.9.2 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33398973	2	1.8	cnDBTier 1.9.2 GA build to VzW with MySQL NDB bug fixes
33237783	2	1.8	cnDBTier 1.9.2 GA build to VzW with MySQL NDB bug fixes
32820167	3	1.8	cnDBTier 1.9.2 GA build to VzW with MySQL NDB bug fixes
33488981	2	1.9	cnDBTier install without ndbapp sql nodes i.e. ndbappReplicaCount as 0
33488770	2	1.9	cnDBTier ndbapp pods are not replicating the user details and grants

Table 4-6 CNE 1.9.1 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33405874	2	1.9.0	Kubespray fails installing K8s on OpenStack with TLS enabled
33431094	2	1.9.0	Container registry configuration needs update to handle some K8S containers
33431127	2	1.9.0	Missing parameter: type definition for Storage Class occne-metrics-sc
33431152	2	1.9.0	Post deployment observing no mount for Openstack certificate in lb controller pod
33431161	2	1.9.0	Remove subnetname from lb_controller
33431186	3	1.9.0	Update VM naming convention
33445871	2	1.9.0	createFailedLbvm.py and addPeerAddrPools.py script failures

Table 4-7 cnDBTier 1.9.1 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33393988	4	1.9.0	Provide support for old prometheus alert in cnDBTier
33410333	3	1.9.0	Correct annotation placement in dbparams.ini file

Table 4-8 CNE 1.9.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33355833	2	1.9	Allow ES curator to continue if individual steps fail
33355862	2	1.9	kubelet service is not using latest changes

Table 4-9 cnDBTier 1.9.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33352224	3	1.8	db backup svc sometimes not removing the backup directory after marking the backup id as purged
33352881	4	1.9	Continuous ERROR messages are printed in monitor svc when replication is not configured
33352911	3	1.8	Replication Channel information is partially loading into the cnDBTier replication service
33352927	3	1.8	Getting "No operations allowed after connection closed" for replication svc

NRF Resolved Bugs

Table 4-10 NRF 1.14.1 Resolved Bugs

Bug Number	Severity	Found In Release	Title	Customer Impact
33446224	4	1.12.1	OcnrfDbReplicationStatusInactive Alert not firing even if NRF detected replication is down	When replication goes down, Operator will not see alarm regarding it.
33446277	4	1.14.0	Correct the indentation for ingress-gateway and egress-gateway actuator port in umbrella values.yaml file	If Custom Value is not used for deployment, then there will be no impact
33446327	4	1.14.0	Modifying SiteID to SiteName in CNCC GUI and REST	Name SiteID is misleading, SiteName should be configured instead
33446378	4	1.14.0	Default value in "replicationStatusUri" should be "http://occne-db-monitor-svc:3306/db-tier/status/replication"	NRF will not be able to detect replication is down due to wrong URI

Table 4-11 NRF 1.14.0 Resolved Bugs

Bug Number	Severity	Found In Release	Title	Customer Impact
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.
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
33245249	4	1.14.0	NFDiscover plmn-specific-snssai-list query is not returning matching NFProfile	Discovery with plmn-specific-snssai-list will not return NfProfiles even if there are matching perPLMNSnssai present
33245263	4	1.11.1	NRF fails to send notification to subscriber for profiles with more than one entry in nfSetIdList	Consumer NF will not get notified for NFs with more than one nfSetId in nfSetIdList
33245279	4	1.11.1	nfManagementOptions allowDuplicateSubscriptions can't be set to true once set to false	Operator can't change allowDuplicateSubscriptions configuration value alone. As a workaround, If the parameter is set to true along with other parameter in nfManagementOptions, then it will allow.
33245340	4	1.12.0	OCNRF considers PLMNID with 2 digit MNC and same PLMNID with 3 digit MNC with a leading 0 as different PLMN.	While Querying to NRF, PLMNID value needs to be sent with same format that is there in the NfProfile. Otherwise the query will result no match.
33245421	3	1.14.0	Initiator OCNRF is encoding Discovery Query with array of object attributes (e.g. target-plmn-list) incorrectly while forwarding the request to target NRF	Forwarding of Discovery query with array of object attributes (e.g. target-plmn-list) will always be rejected by target NRF with 4xx code.

NSSF Resolved Bugs

Table 4-12 NSSF 1.7.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33172166	2	1.6	CVE-2021-3426: PYTHON UPDATE TO AT LEAST 3.9.3, 3.8.9, 3.7.11 OR 3.6.14
33135303	3	1.6	Critical CVEs Identified in ocats-nssf using Anchore Security Scan

CNC Policy Resolved Bugs

Table 4-13 CNC Policy 1.14.1 Resolved Bugs

Bug Number	Severity	Found In Release	Title
33459222	3	1.12.0	Policy and BSF installation is not working
33459267	3	1.12.0	Bulk Import is not working properly in cnPCRF
33459271	3	1.14.0	Timer profile export fails with Bulk Export Operation
33459310	3	1.12.0	SM PCF cnDBTier 1.8.8 db replication failure
33463586	2	1.12.3	SW block "Remove all from Subscriber Remote" does not work - delete fails

Table 4-14 CNC Policy 1.14.0 Resolved Bugs

Bug Number	Severity	Found In Release	Title
32650916	2	1.11.3	Diamgw throws "No OCS/SH peer to send msg" even when it connected successfully
32995443	3	1.11.2	PCF sends PATCH request to UDR even in the absence of policies
32995086	3	1.11.0	ASA message is not sent to backend but back to peer
32995076	3	1.11.0	1.12.0 cmgui has configurations related to disabled services in pcrf mode.
32995073	3	1.11.0	UDR Notification for Multiple Resources is not handled by PCF
32650928	3	1.11.0	Pcrf-core should send the binding data entry and pds entry delete request after diameter session deletion.
32995081	3	1.12.0	Memory leak in diam-connector when diam-gw pod scales
33130516	3	1.11.4	PCF User Connector - base URI changes via GUI not taking affect
33159055	3	1.11.4	PCF unable to read UDR connector service configuration change
33131466	3	1.11.4	Diameter Peer Node Configuration FQDN validation issue during Bulk Import/Export
33223451	3	1.11.4	PCF sending NULL smPolicyDecision in audit messages

SCP Resolved Bugs

Table 4-15 SCP 1.14.1 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33460911	3	1.14.0	Application User missing NDB_STORED_USER permissions
33460920	4	1.14.0	Document update for privileged user permissions
33460931	3	1.14.0	Audit microservice upgrade failure due to namespace and releasename variable missing in upgrade hooks
33460935	3	1.14.0	Duplicate rules creation on scp worker pod restart
33460944	3	1.14.0	Hostmpper null pointer exception observed in scp worker
33460956	4	1.14.0	Enable R15 as input to New features ATS
33460975	4	1.14.0	Fix comments in ATS custom deployment file
3465417	3	1.12.0	Add Pod scale up in cleanup of NRF Registration feature file

Table 4-16 SCP 1.14.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33233332	3	1.11.1	Update Rate limiting scenarios to remove validation from cleanup scenario
33233343	4	1.12.0	Remove IGW images and charts in CSAR package for SCP 1.10.x onward releases
33233454	4	1.11.1	Perform validation of microservice names for logger API
33233561	4	1.12.0	Change Timestamp format for all logs to "2021-06-18T19:07:01.329+0000"
33249040	3	1.11.0	Under high traffic SCP keeps on processing requests even if connections are terminated
33233542	4	1.12.0	Add complete ats custom config templates content to ATS CSAR pacakage

SEPP Resolved Bugs

Table 4-17 SEPP 1.6.1 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33264360	2	1.5.0	Multipart message is not supported in SEPP
33263736	2	1.5.0	cn32f crashed during stress testing
33486560	2	1.5.0/ 1.6.0	Roaming NRF Discovery error at egress level
33373718	2	1.5.0/ 1.6.0	Media type payload is getting changed when passing from vSEPP to hSEPP

Table 4-18 SEPP 1.6.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33163603	2	1.4.0	Discovery Procedure is failing for query parameter
33160425	2	1.5.0	Query parameters of NRF discovery are removed by the SEPP n32f proxy
33160382	3	1.5.0	SEPP 1.5.0 MIBs Not Compiled Correctly
33118522	3	1.5.0	IP Based routing in absence of External DNS
33118491	2	1.5.0	Multiple values not supported in SAN
33184851	3	1.5.0	Roaming Partner Profile not getting deleted when the connection type is Responder

UDR Resolved Bugs

Table 4-19 UDR 1.14.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
32972133	3	1.12.0	Notify pod not sending notifications every time to the stub for PATCH of sdmsubscription
32377341	4	1.10.0	Fetch UDM authentication subscription on UDR returns Internal Server Error

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.

BSF Customer Known Bugs

Table 4-20 BSF 1.10.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
33262764	3	1.9.0	Ephemeral storage requirement for BSF	In absence of ephemeral storage requirement underlying HW will not reserve space for the BSF pods and pods can get evacuated if the storage space is not available
33262827	3	1.10.0	Default selection not seen and Export button enabled though there is no selection on Bulk Export modal	User needs to select the configuration that are needed for export
33263632	3	1.10.0	BSF SBI HTTP Error codes are not allowing custom error codes	Only Standard HTTP status code are allowed

CNC Console Customer Known Bugs

There are no customer known bugs in CNC Console 1.8.x.

CNE Customer Known Bugs

Table 4-21 CNE 1.9.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
32211087	2	1.4	nodename field is blank for CNE node alerts OUT_OF_MEMORY and NODE_UNAVAILABLE	The nodename field remains blank for the following CNE node alerts: OUT_OF_MEMORY NODE_UNAVAILABLE
33356061	3	1.4	Modify NETWORK_INTERFACE_FAILED alert to fire separate alert for gen10 and gen8 h/w	The current definition of NETWORK_INTERFACE_FAILED alert sends a false alarm for gen10 hardware.
33356081	4	1.6	vCNE/Metallb - genLbCtrlData.py script fails using IP ranges	When the `genLbCtrlData.py` script is run to generate the `lbCtrlData.json` file, it fails to add network id and other fields to the json file.
33353135	3	1.9	virtual CNE 1.9 upgrade ends with unattached cinder volumes causing outage	virtual CNE 1.9 upgrade ends with unattached cinder volumes, causing outage
33353123	3	1.9	1.9.0-rc.7 Fixed IP vCNE Install failure	The current Fixed IP install fails in the `deploy.sh` script.

NRF Customer Known Bugs

Table 4-22 NRF 1.14.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
33248344	4	1.14.0	slfOptions.featureStatus is accepting invalid values if CLI based REST client is used	The issue will occur only if CLI based REST client is used to enable SLF feature with an invalid value. With CNC Console GUI, this issue will never occur.

NSSF Customer Known Bugs

There are no customer known bugs in NSSF Release 1.7.0.

CNC Policy Customer Known Bugs

Table 4-23 CNC Policy 1.14.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
33263619	3	1.14.0	UDR/CHF updated binding header is not picked in routing binding header while sending Update/Unsubscribe request to UDR/CHF	If UDR or CHF updates its binding information in Update Response message or Notification request message, PCF will not honour the updated binding and shall continue to use the binding information received in Subscribe response in the Routing Binding Header while sending Update and Unsubscribe request to UDR or CHF.
33263638	3	1.14.0	Binding header is sent every time in UDR notification response even if NFSet of PCF is not changed	Extra header will be sent to HTTP peers but will not cause any functionality loss.
33131318	3		PCF SM service calling alternate route service on subsequent requests	This issue occurs when the Retry Profile is configured and DNS SRV records are not created. This can be avoided by performing the following steps: Remove the retry profile configuration from SM Service configuration (If customer does not want the Alt Routing for SMF Notification) If Alternate Routing is required then configure the DNS SRV records
33218137	3	1.12.0	BULK Export operation skips default service configuration during export	Default Service configuration is not exported unless it is saved at least once from the GUI. This will result in Bulk Export operation skipping the Service Configuration data.
33263667	3	1.12.0	Ephemeral storage requirement for CNC Policy	In absence of ephemeral storage requirement underlying hardware will not reserve space for the Policy pods and pods can get evacuated if the storage space is not available.

SCP Customer Known Bugs

There are no customer known bugs in SCP Release 1.14.0.

SEPP Customer Known Bugs

SEPP 1.6.1 Customer Known Bugs

Table 4-24 SEPP 1.6.1 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
33322009	3	1.6.1	Cache not getting updated for deleted entries.	If Roaming Partner Profile is deleted and n32f traffic is in progress, n32f will keep on finding the context and continue forwarding the message to receiving SEPP.
33323304	3	1.6.1	DB operations taking approximately 60 seconds to reflect in N32f services.	If N32f traffic is run immediately after performing any DB update related to Roaming Partner Profile (create or update), N32f message fails with 404 -Context not found error message.

SEPP 1.6.0

There are no customer known bugs in SEPP Release 1.6.0

UDR Customer Known Bugs

Table 4-25 UDR 1.14.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 egress gateway goes down before nrf-client during UDR deletion	No impact