4 Resolved and Known Bugs

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

Severity Definitions

Service requests for supported Oracle programs may be submitted by you online through Oracle’s web-based customer support systems or by telephone. The service request severity level is selected by you and Oracle and should be based on the severity definitions specified below.

Severity 1

Your production use of the supported programs is stopped or so severely impacted that you cannot reasonably continue work. You experience a complete loss of service. The operation is mission critical to the business and the situation is an emergency. A Severity 1 service request has one or more of the following characteristics:
  • Data corrupted.
  • A critical documented function is not available.
  • System hangs indefinitely, causing unacceptable or indefinite delays for resources or response.
  • System crashes, and crashes repeatedly after restart attempts.

Reasonable efforts will be made to respond to Severity 1 service requests within one hour. For response efforts associated with Oracle Communications Network Software Premier Support and Oracle Communications Network Software Support & Sustaining Support, please see the Oracle Communications Network Premier & Sustaining Support and Oracle Communications Network Software Support & Sustaining Support sections above.

Except as otherwise specified, Oracle provides 24 hour support for Severity 1 service requests for supported programs (OSS will work 24x7 until the issue is resolved) when you remain actively engaged with OSS working toward resolution of your Severity 1 service request. You must provide OSS with a contact during this 24x7 period, either on site or by phone, to assist with data gathering, testing, and applying fixes. You are requested to propose this severity classification with great care, so that valid Severity 1 situations obtain the necessary resource allocation from Oracle.

Severity 2

You experience a severe loss of service. Important features are unavailable with no acceptable workaround; however, operations can continue in a restricted fashion.

Severity 3

You experience a minor loss of service. The impact is an inconvenience, which may require a workaround to restore functionality.

Severity 4

You request information, an enhancement, or documentation clarification regarding your software but there is no impact on the operation of the software. You experience no loss of service. The result does not impede the operation of a system.

Resolved Bug List

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

Table 4-1 CNE 1.5.0 Resolved Bugs

Bug Number Severity Found in Release Title
30838215 Major 1.3.2 Bare Metal Installation - Db-1 Management interface not re-configured by ansible script post pipeline
30761850 Major 1.3.2 DB-Tier did not recover from post weekend Lab Shutdown
30832402 Major 1.3.2 Cisco 93180 (TOR) does not recover vrrp or port channels if DB1 fails simultaneous to loss of both TOR switches
30936847 Minor 1.3.2 admusr password on K8s nodes expires after 90 days

Table 4-2 CNC Console 1.2.1 Resolved Bugs

Bug Number Severity Found in Release Title
31756363 Minor 1.2.0 CNCC 1.2: SLF Provisioning Entries Missing from Custom Values File

Table 4-3 CNC Console 1.2.0 Resolved Bugs

Bug Number Severity Found in Release Title
31355467 Minor 1.1.0 CNCC UDR screen - Minor issue in displaying error message having long text
31355421 Minor 1.1.0 CNCC UDR Screen - Open Items
31355443 Minor 1.1.0 CNCC UDR Screen - Not displaying Authentication Error Messages

Table 4-4 CNC Policy 1.7.3 Resolved Bugs

Bug Number Severity Found in Release Title
31847726 2 1.7.1 PCF support for ClusterIP type on all services
31847827 2 1.7.1 PCF- SCP Integration - Headers incorrect/missing in msg from PCF to SCP
31847835 2 1.7.1 perf-info crashing when Prometheus is not scrapping the data and returning empty records
31847874 2 1.7.1 PCF does not route the call based on higher priority of CHF
31847879 2 1.7.2 Issue while switching between Policy project || cloned project not working
31847864 3 1.7.2 Not able to see session in session viewer GUI - 1.7.2
31847885 3 1.6.0 B2B SM CREATEs for the same subscriber, Subscription with CHF and UDR works fine, but Un-Subscription sequence is erroneous
31847901 3 1.7.1 After a Bulk Import into a PCF 1.7.1 System Policies are not populated with Policy Table Information
31847929 3 1.7.1 Scaling is not working for nrf-discovery due to wrong deployment reference in HPA

Table 4-5 CNC Policy 1.7.2 Resolved Bugs

Bug Number Severity Found in Release Title
31710638 2 1.6.3 Policy Table not working properly in PCF 1.7.1
31710693 2 1.6.3 PCF ingress pod sending 503 Service Unavailable
31710705 2 1.6.3 PCF throwing error Duplicate entry for SUPI , resulting N7 create failure

Table 4-6 CNC Policy 1.7.1 Resolved Bugs

Bug Number Severity Found in Release Title
31367038 3 1.6.0 Remove clusterRole and ClusterRoleBinding from Policy solution
31367115 3 1.6.0 Bulk Import export does not work with Overwrite Option
31647595 2 1.6.0 Not able to see Policy logs in Kibana
31647550 2 1.6.0 Diameter request timeout
31653316 3 1.6.0 EPS fallback PRE and Final AAR policy trigger issue

Table 4-7 NRF 1.7.2 Resolved Bugs

Bug Number Severity Found in Release Title
31621074 3 1.7.0 Custom Annotation, Labels and Prefix-Suffix is not getting added to Helm Hook Jobs
31759592 3 1.7.0 NRF chart should not create clusterrolebinding/clusterrole
31759593 2 1.7.0 mysql host is hardcoded in appinfo for fetching replicationstatus

Table 4-8 NRF 1.7.0 Resolved Bugs

Bug Number Severity Found in Release Title
31331560 4 1.5.0 NRF is not validating unique serviceInstanceId
31331608 4 1.5.1 Cachecontrol header is not being sent in forwarded discovery response
31620906 3 1.6.1 NRF not sending notification to subscribed NFs

The following resolved bug fixes are not available in SCP 1.8.0 or 1.9.0.

Table 4-9 SCP 1.7.5.1 Resolved Bugs

Bug Number Severity Found in Release Title
32215993 3 1.7.4.1 Ingress Gateway memory usage alarm addition:
  • SCPIngressGatewayPodMemoryUsage
32216030 2 1.7.4.1 Intermittent 503 Error by Ingress gateway due to out of memory

The following resolved bug fixes are available in SCP 1.9.0 and not available in SCP 1.8.0.

Table 4-10 SCP 1.7.5 Resolved Bugs

Bug Number Severity Found in Release Title
32109782 3 1.7.4 SCP will not stop forwarding traffic to IWF mediation pods.
32109791 3 1.7.4 ELG SCP not reporting metrics after a topology source change.
32109793 3 1.7.4 SCP1.7.4.1 duplicate subscription records, after configuration-notifiction.

Table 4-11 SCP 1.7.4.1 Resolved Bugs

Bug Number Severity Found in Release Title
31979136 3 1.7.4 Add Heartbeat mechanism at worker-pilot interface.
31979141 3 1.7.4 Uplift to IGW 1.8.4 for connection balancing fix.

Table 4-12 SCP 1.7.4 Resolved Bugs

Bug Number Severity Found in Release Title
31862960 2 1.7.2 Exception occurred while applying RO on statically configured profiles
31862971 3 1.7.2 Fix NullPointer exception while creating Virtual service
31862976 3 1.7.2 Circuit Breaking not working if pod level retry is set to 1

Table 4-13 SCP 1.7.3 Resolved Bugs

Bug Number Severity Found in Release Title
31838841 3 1.7.1 scp-worker overrides received server header with it's own default
31838850 3 1.5.2 Same OID (7001) is being repeated in SCP MIB file
31838845 4   Update Severity of scpAlerts to Minor, major for some of the Alerts and Update MIB
31862946 3 1.7.1 Malformed Ip error occurs when message has ip as authority without port and routing from catchallRoute.

Table 4-14 SCP 1.7.2 Resolved Bugs

Bug Number Severity Found in Release Title
31777883 3 1.7.1 SCP need to use NDBCLUSTER as DB Engine instead of InnoDB
31777890 3 1.7.1 Test cases are Failing if ATS is not deployed in scpsvc namespace
31778232 2 1.5.2 Intermittent 503s are being observed upon processing NF Notifications received from NRF
31778238 3 1.7.0 Intermittent 404s are being observed upon processing NF Notifications received from NRF

Table 4-15 SCP 1.7.1 Resolved Bugs

Bug Number Severity Found in Release Title
31704412 3 1.5.3 Notification pod to recover from DB inconsistencies caused when notification crashed/deleted while processing or due to partial delete during deregister
31704425 3 1.5.3 Fix slowness observed in Notification Micro Service on long standing systems
31704428 3 1.5.3 Override x-envoy-original-dst-host with scp-w details to avoid loopback detection error.
31704462 3 1.6.0 Copy SCP-W needed file to /tmp in a pod to avoid any permission issues due to security policy.

Table 4-16 SCP 1.7.0 Resolved Bugs

Bug Number Severity Found in Release Title
31603629 3 1.6.0 SCP 1.6.0 does not create VS for Nudr or Nbsf services
31603719 3 1.6.0 CHF profiles registration failure when locality is absent from the profile
31604175 4 1.6.0 Make SCP Services Service type configurable to pick any of the ClusterID, NodePort, Load Balancer

Table 4-17 UDR 1.7.0 Resolved Bugs

Bug Number Severity Found in Release Title
31330261 4 1.6.0 UDR allows creating SLF data with empty nfGroupId
31330361 3 1.6.0 Error response format from ProvGw is not as expected.
31330332 3 1.6.0 ProvGw does not send to second UDR within same segment.

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-18 BSF 1.5.0 Resolved Bugs

Bug Number Severity Found in Release Title Customer Impact
31629098 Minor 1.5.0 OCCNP:1.7: ASR/RAR is getting failed in PCF diam gateway when GATEWAY_Mode is converged and AF is connected to BSF ASR/RAR is not getting routed to BSF-diam gateway
31629139 Minor 1.5.0 Binding ID is not stored properly in SQL database. pcf_binding table of ocpm_bsf database User will not be able to view the Binding association ID created for a subscriber from ocpm_bsf database
31629575 Minor 1.5.0 BSF/CNCPolicy - Default value for Diameter Identity need to be changed in SM-service configuration BSF will reject the binding creation

Table 4-19 CNE 1.5.0 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact
30756164 Minor 1.3.2 OCCNE 1.3 Bare Metal Installation Failure -- Replication IP not configured on Sql Nodes during Db-Tier installation The IP addresses for the replication need to be configured manually following the automated installation.
30756201 Minor 1.3.2 OCCNE 1.3 Bare Metal Installation Failure -- Pipeline.sh is not documented. Must be continually restart on error. An error in the installation pipeline script is not detected efficiently and requires the script to be restarted from the beginning.

Table 4-20 CNC Console 1.2.1 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.

31773454 Minor 1.2.1.rc.1 CNCC - In the custom values, the images names and tags are not set correctly. No impact, Customer needs to manually update image name and tags.
31773492 Minor 1.2.1.rc.1 CNCC 1.2.1-rc.1 : cncc-iam pod template restricts the name length to 20 characters The cncc-iam pod has a template function that restricts the name length to 20 characters. This makes it not follow this naming convention.

Table 4-21 CNC Console 1.2.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-22 CNC Policy 1.7.1 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact
31629098 Minor 1.7.0 OCCNP:1.7: ASR/RAR is getting failed in PCF diam gateway when GATEWAY_Mode is converged and AF is connected to BSF ASR/RAR is not getting routed to BSF-diam gateway
31629285 2 1.7.0 SM service restarts within 5 hours due to increase in RAM usage with "failed to call BSF " errors Longevity test and performance test will be impacted. Functional testing will be ok
31629332 Major 1.7.0 Binding service restarts within 5 min for 50 CREATE and 50 DELETE messages Binding service restarts, which in turn cause failures at SM-service. SM-service memory usage shoots up due to these failures
31629400 Minor 1.7.0 FileNotFoundException observed cm-service logs when user try to access Policy Table & Policy Project GUI None
31629502 Minor 1.7.0 cnPCRF: Info level logs dumping in pcrf-core with LOGGING_LEVEL_ROOT = ERROR None
31629532 Minor 1.7.0 cnPCRF: diam-gateway failed to reconnect to UDR on restart of UDR entity Fail to reconnect to UDR
31629612 Minor 1.7.0 user-service pod throws error as "IllegalArgumentException" while other pod coming up properly This is an intermittent issue. User Service will not be able to pull the saved configuration from DB
31629681 Minor 1.7.0 Unable to see policies in GUI after a Bulk import options Bulk Import will not import Policies from GUI

Table 4-23 NRF 1.7.2 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact
31620996 4 1.7.0 DB-RTT and Response Processing Time metrics validation fails randomly These metrics are debugging metrics. Failing to validate these metrics is not functionality failure.

Table 4-24 NRF 1.7.0 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact
31620996 4 1.6.1 Problem Details - Status Code should be Integer (instead of String) If Consumer NFs validating the datatype of the status IE in Problem Details, then they will reject the message.
31621054 4 1.6.1 Optional parameter with wrong values are being silently ignored in nfProfile and nfServices (ex. notificationType under defaultNotificationSubscriptions) Discovery Consumer will not get to know that invalid Discovery Query Parameter is sent by them.
31621074 3 1.7.0 Custom Annotation, Labels and Prefix-Suffix is not getting added to Helm Hook Jobs Operator Can't add Custom Annotation/Lables/Prefix-Sufix to Helm Hook Jobs.
31621085 4 1.7.0 OCNRF Configuration - generalErrorResponses is coming in response, it is not supported yet Operator needs to ignore the additional attribute in the GET response.

Table 4-25 SCP 1.7.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

Workaround: None.

Table 4-26 UDR 1.7.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.
31593712 3 1.7.0 Diameter request where mandatory avps are missing must be rejected No impact
31608081 3 1.7.0 UsageMonitoring data request issue for UDR v15.3 PCF WA: Run the rollbackPCFschema_15_3.py from customTemplates and then run the request
31618168 3 1.7.0 Diameter traffic fails when Data-Reference AVP is set to 0 WA: Data reference can be sent as 1 as a temporary solution