Resolved and Known Bugs

4 Resolved and Known Bugs

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

Table 4-1 OSO 1.6.3 Resolved Bugs

Bug Number	Severity	Found in Release	Title
33679493	3	1.6.2	OSO 1.6.2 pods missing podLabels and Image names have invalid prefixes
33650882	3	1.6.2	OSO 1.6.2 pods missing podLabels and Image names have invalid prefixes

Table 4-2 OSO 1.6.2 Resolved Bugs

Bug Number	Severity	Found in Release	Title
32224057	3	1.6.1	OSO: Targets oracle-cnc-service needs extra configurations
32224078	3	1.6.1	Remove TLS configurations from alertmanager
32224122	3	1.6.1	Adding support for PVC for Alertmanager
32224165	3	1.6.1	Disable Pushgateway Support
32224242	3	1.6.1	Increase Alertmanager Resource limits
32224256	3	1.6.1	Convert Descriptor Version to Software Version

Table 4-3 OSO 1.6.1 Resolved Bugs

Bug Number	Severity	Found in Release	Title
32222455	3	1.6.0	Truncate OSO prometheus component's fixed names
32222301	1	1.6.0	OSO Values File must be fixed
32223999	3	1.6.0	Modify Labels in Scrape Configuration
32224024	3	1.6.0	Modify Labels in Scrape Alert Configuration

Table 4-4 CNE 1.6.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
30756164	3	1.3.0	OCCNE 1.3 Bare Metal Installation Failure -- Replication IP not configured on Sql Nodes during DBTier installation
30756201	4	1.3.0	OCCNE 1.3 Bare Metal Installation Failure -- Pipeline.sh is not documented. Must be continually restart on error
30371715	4	1.2.0	OCCNE 1.2.0 Installation Guide does not provide guidance on Firmware Version.

Table 4-5 CNC Console 1.3.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
31836979	Major	1.2.0	CNCC 1.2: SLF Data Provisioning
31825563	Medium	1.1.0	VzW ME Lab – CNCC 1.1 issues
31773454	Minor	1.2.1	In the custom values, the image names and tags are not set correctly.
31773492	Minor	1.2.1	CNCC 1.2.1-rc.1: CNCC-IAM pod template restricts the name length to 20 characters.
31855444	Minor	1.0.0	After installing CNCC-IAM, a user cannot login with the initial user name.
31855476	Minor	1.2.1-rc.1	CNCC 1.2.1-rc.1: Question on FQDN Support
31889461	Minor	1.2.1	SCP Canary Release edit does not function as expected
31890147	Minor	1.2.1	CNCC IAM DB SQL file causes replication failure

Table 4-6 BSF 1.5.1 Resolved Bugs

Bug Number	Severity	Found in Release	Title
31972868	3	1.5.0	Binding query is not successful in BSF Management when we have shotrthand IPv6 prefix used in both SM create and AAR-I.

Table 4-7 CNC Policy 1.8.4 Resolved Bugs

Bug Number	Severity	Found in Release	Title
32186027	2	1.8.1	PCF does not send SuppFeatures IE for PRA in SM Policy Association Response
32186184	3	1.8.3	Upgrade --> Rollback --> re-upgrade issue/failure

Table 4-8 CNC Policy 1.8.3 Resolved Bugs

Bug Number	Severity	Found in Release	Title
32140574	3	1.8.0	Rx message are missing when do subscriber trace
32140590	3	1.8.0	Egress logs are not captured in Subscriber Tracing
32140598	3	1.8.0	All PCF resources (e.g. hook job templates) not configured to receive customExtension allResources labels and annotations using global.customExtension.allResources for ASM integration
32140631	3	1.8.0	Support for Configurable Http2 Client Connections implementation
32140689	3	1.8.0	When call-rate of delete PDU session is bigger than 50, sm-service throws exception of Failed to call BSF

Table 4-9 CNC Policy 1.8.2 Resolved Bugs

Bug Number	Severity	Found in Release	Title
32179811	2	1.8.1	User Service Threads are growing unbounded

Table 4-10 CNC Policy 1.8.1 Resolved Bugs

Bug Number	Severity	Found in Release	Title
31959719	2	1.7.4	PCF sending Abort to AF during traffic call flow
31959847	2	1.7.4	PRE not processing policies because of permission issues of the directory
31960033	2	1.8.0	AAR-U not respond in PCF mode
31880917	3	1.8.0	On AAR Update, diam-gateway fails to fetch dependent SessionBindingMapping from binding service
31883568	3	1.7.3	Timestamp is not consistent across services and the format is not supported by Kibana
31895101	3	1.7.1	UDR user sm policy profile update notify message to ingress not logged
31959765	3	1.7.4	Support for Configurable Http2 Client Connections implementation

Table 4-11 CNC Policy 1.8.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
31883568	3	1.7.3	REMOVE_ALL Policy Block is not working in PCF
31847912	2	1.7.1	Scaling is not working for nrf-discovery due to wrong deployment reference in HPA
31629612	3	1.7.1	One user-service pod throws error as "IllegalArgumentException" while other pod coming up properly

Table 4-12 NRF 1.8.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
31759596	4	1.7.0	DB-RTT and Response Processing Time metrics validation fails randomly
31866286	2	1.7.2	jobNames are exceeding the 63 character limit
31866323	3	1.7.0	nnrf-disc fails when TAI Query parameter is used
31866379	4	1.7.0	Grafana dashboard template includes time period set to 2020-07-06
31866498	4	1.5.0	Error in AMF to NRF registration because of defaultNotificationSubscriptions
31866529	4	1.5.0	Error in AMF registering to NRF because of nfInstanceId included in URL and body in different format (upper and lower case)
31866632	4	1.7.2	Timestamp keyword in log is resulting in log not coming in Kibana

Table 4-13 SCP 1.8.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
31868324	3	1.7.3	Add automatic quotes around annotations values using helm quote function
31868333	3	1.7.2	SS: Notification throws duplicate IpEndpoint validation error when within a profile two same services have only port present in ipEndpoint. The port present is same.
31877610	2	1.7.1	oscpw-router Envoy Filter port is not synced with gateway signaling port
31881944	4	1.7.1	Instead of having multiples summaries in ATS, have just one summary

Table 4-14 UDR 1.8.0 Resolved Bugs

Bug Number	Severity	Found in Release	Title
31608081	3	1.7.0	UsageMonitoring data request issue for UDR v15.3 PCF
31593712	3	1.7.0	Diameter request, where mandatory avps are missing, must be rejected
31618168	3	1.7.0	Diameter traffic fails when Data-Reference AVP is set to 0

Customer Known Bug List

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

Table 4-15 BSF 1.5.1 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
31973019	3	1.5.0	S-NSSAI shall be Optional parameter in bsf discovery	User needs to pass the s-nssai as part of query parameters.

Table 4-16 CNC Console 1.3.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
31355530	Minor	1.1.0	CNCC IAM - Unable to remove assigned User Role	User will be able to add roles but user will not be able to remove the assigned roles. Workaround: Delete user and recreate user with required role.

Table 4-17 CNC Policy 1.8.1 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
31972768	3	1.8.0	Config Client Connection to Config Server hangs when DB issues are encountered	This issue is observed when there are issues in database and config server not able to communicate with the database. When this happens service will not be able to get the new configuration from the database. Right now, this issue is observed in one particular cloud lab. Workaround: Database issue needs to be resolved and the affected service needs to be restarted.

Bug Number

Severity

Found in Release

Title

Customer Impact

31972768

1.8.0

Config Client Connection to Config Server hangs when DB issues are encountered

This issue is observed when there are issues in database and config server not able to communicate with the database. When this happens service will not be able to get the new configuration from the database.

Right now, this issue is observed in one particular cloud lab.

Workaround:

Database issue needs to be resolved and the affected service needs to be restarted.

Table 4-18 CNC Policy 1.8.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
31880875	2	1.8.0	Converged (PCF Mode): Sm service connection with PRE is breaking intermittently & sm-service throws up "Failed to call policy service" logs	This issue is intermittent and occurred in a call rate of 1250 TPS, and was seen eight times in a 12 hour run. When this issue occurs, the default policy will be applied.
31880883	3	1.7.1	timestamp is not consistent across services and the format is not supported by Kibana	User will not be able to sort and sequence the messages in Kibana board.
31880914	3	1.8.0	SM-Rx: Rx session mapping with IMSI/MSISDN fails with error 5065, though corresponding SM binding is available	During SM RX call flow, Rx with only IMSI/MSISDN identifiers without fails to fetch binding service information and respond back with error response 5065.
31886960	3	1.8.0	Bug 31886960 - SM-Binding: Metric for Binding delete does not increment on SM session deletion	Metrics for Binding delete is not incremented on successful SM session delete request.
31895171	3	1.8.0	SM & User-service are not able to connect to alternate service with default 8000 port(unified port)	SM & User will not be able to connect to alternate route service for in-session messages (Update/Delete/Update-Notify) and those transactions will fail.
31898693	3	1.8.0	On loss of connectivity with OCS, Diam Gateway failed to reconnect to OCS	Diam Gateway will not try to reconnect again after connectivity is lost between diam gateway to OCS server. Workaround: Restart the diam gateway pod.
31898707	3	1.8.0	Error Response(5065) for Gx request on switching OCS admin state from ON to OFF	On turning admin state of data source configuration from ON to OFF in CM GUI, Diam gateway will send error respond to Gx Call (5065).

Table 4-19 NRF 1.8.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
31866770	4	1.7.2	NRF service containers should not send HTTPS request to Sidecar container	Notification URI received with HTTPS scheme may fail with Service Mesh.
31866838	4	1.7.2	Propagating Jaeger Headers for Forwarding/SLF requests	Forwarding and SLF queries will not come under one parent Trace.
31866858	4	1.7.0	replicationstatus alert should not be raised when Geo-Redundancy feature is disabled.	Replication Down alert will be seen in a non-Geo-Redundant Deployment.

Table 4-20 SCP 1.8.0 Customer Known Bugs

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

Bug Number

Severity

Found in Release

Title

Customer Impact

30731782

1.2.0

Limit of VS size is limited to 1 Mb by etcd/k8s.

Impacts only if there are 100s of NFs with many service instances/NF and hence minimal impact for customer/user.

Workaround: None. This is limited by underlying platform.

30731844

1.3.0

Processing time of NRF notifications increases if more profiles (>10) with more many service instances (more than 10/profile)are registered. increase observed is 2-3 seconds more than previous registered in case of new registration. Updates also increases with more number of registered profiles.

There may be delay in rule creation if profiles are large in numbers.

Workaround: None.

30731829

1.4.0

SCPC-Pilot is taking high CPU while applying updates if number of equivalent profiles/ServiceInstances are exceeding 100

There may be delay in rule creation if profiles are large in numbers that can cause some call failures.

Table 4-21 UDR 1.8.0 Customer Known Bugs

Bug Number	Severity	Found in Release	Title	Customer Impact
30774742	4	1.3.0	UDR is not validating the conditional attributes for UDM APIs.	No impact. UDM (consumer of UDM APIs) does not send conditional attributes to UDR
30774750	4	1.3.0	Notify Service delays notifications to PCF during traffic run.	Notifications rate is limited in initial release.
30774755	3	1.4.0	Headers for few resources are not implemented as per spec 29505-v15.4.0.	No impact.
31877256	4	1.8.0	ProvGw: GET response sometimes does not have segment1 related data for subscriber does not exist case.	No impact. This issue is observed intermittently.
31889017	4	1.8.0	Issues observed on ProvGw on ASM machine	No impact. This issue is observed intermittently.