4 Resolved and Known Bugs

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

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

Table 4-1 CNC Console 1.6.0 Resolved Bugs

Bug Number Severity Found in Release Title
32611157 Minor 1.5.0 CNCC 1.5: ASM integration to wait for istio-proxy sidecar before executing application code
32151129 Minor 1.4.0 CNCC 1.4 : Policy bulk import screen progress bar is not getting updated
32291243 Minor 1.5.0 CNCC - OCCNE 1.7.0 Kibana API prefix is not working
32291262 Minor 1.5.0 CNCC : Disable Grafana login screen
32641844 Minor 1.5.2 VZW CNCC - Request to Change the Name of Alert Rules File

Table 4-2 CNC Policy 1.11.0 Resolved Bugs

Bug Number Severity Found in Release Title
32377213 3 1.8.0 Diameter connector to sm-service timer is hard coded to 2 sec
32377250 3 1.10.0 PCRF-Core should request to delete subscriber info from Policy-ds when subscriber detach
32388565 3 1.10.0 SM Service Memory Growth during ATS run
32388574 3 1.10.0 Audit Service getting hanged and thus not auditing the records
32388591 3 1.10.0 "udrconnector.apiroot" environment variable missing during helm upgrade from 1.9.1 to 1.10.0
32388592 3 1.10.0 SM Service getting hanged with 10 K TPS
32388606 3 1.10.0 Egress GW Internal Server Error while sending Notify Request (N7 Notification)
32388607 3 1.10.0 PCF Session Binding Issue in SM Service (Null Pointer Exeception)

Table 4-3 CNE 1.8.0 Resolved Bugs

Bug Number Severity Found in Release Title
OCCNE-2425 2 1.4.0 ES data not deleted when PV full
OCCNE-3896 2 1.8.0 OC-CNE 1.8 GA build fails
OCCNE-3751 2 1.7.0 Checking the status of the replication and switching the replication channel
OCCNE-3758 2 1.8.0 1.8 rc.1 Failure to install on BM with no CNDBTIER selected
OCCNE-3875 3 1.8.0 db-backup-executor-svc logs username/password
OCCNE-3876 3 1.8.0 cndbtier cross site replication does not work using loadbalancer ip in vCNE
OCCNE-3752 3 1.8.0 Upgrade fails for Elasticsearch Data
OCCNE-3810 3 1.8.0 lbvm ip rule/route is missing after some service created
OCCNE-3769 3 1.8.0 vCNE Openstack (at least) need to set MTU appropriately to communicate with cloud-provider
OCCNE-3803 3 1.8.0 cnDbTier fails to deploy in OCI environment
OCCNE-3802 3 1.8.0 haproxy_handler.py script creates haproxy configuration with error messages on lbvm which results in haproxy service failure
OCCNE-3766 3 1.8.0 Services exist from kubectl command, but failed for lookup lb-apiserver.kubernetes.local
OCCNE-3756 3 1.8.0 lbvm interfaces for haproxy are missing for ol8
OCCNE-3745 3 1.8.0 Upgrade fails for Grafana and Prometheus
OCCNE-3759 3 1.8.0 1.8 rc.1 Loadbalancer services are not assigned with ip address
OCCNE-2932 3 1.5.0,1.6.0 Openstack certificate not passed during upgrade results in upgrade failure during k8s stage
OCCNE-3455 3 1.6.0 Get Scanning working on clusters with multiple bastions
OCCNE-3861 4 1.8.0 db-backup-manager-svc runs as a user other than mysql (27)
OCCNE-3711 4 1.7.0 kubectl top command failing
OCCNE-3585 4 1.6.0 DBTier 1.8.0.0.1 CSAR descriptor_version value is not set to the software version in vnfd.yml file
OCCNE-3414 4 1.6.0 cndbtier deployment occasionally fails to create all mysql users
OCCNE-3760 4 1.7.0, 1.8.0 Implement resource limits on jaeger components
OCCNE-2543 4 1.4.0 The /etc/hosts names have duplicate names and additional very long names
OCCNE-1337 4 1.2.0 k8s_install produces non-executable kubectl binary in ../artifacts
OCCNE-3528 4 1.7.0, 1.8.0 Kibana default API Prefix in not working in CNCC setup for common services hyperlinks
OCCNE-3744 4 1.7.0, 1.8.0 Unable to drain worker nodes that host Istio pods
OCCNE-3532 4 1.7.0 Some of the OCCNE alert rules are not logically correct
OCCNE-3531 4 1.7.0 GRAFANA_DOWN alert not working
OCCNE-3345 4 1.6.0 k8s cannot verify user is non-root for db-monitor-svc and db-replication-svc

Table 4-4 NRF 1.11.1 Resolved Bugs

Bug Number Severity Found in Release Title Customer Impact
32751028 3 1.11.0 App-Info restarts continuously due to probe failure While Deploying NRF, CPU of AppInfo micro-service needs to be increased
32751034 4 1.11.0 Alert file in the CSAR package needs to have static name If Orchestrator's expects that the Alert Rule fine name needs to be a static name, then loading may fail
32751048 4 1.11.0 IGW's Cache service should not get assigned with LB IP LB IP will get assigned to a non LB service if Operator uses Service section of IGW for assigning External LB annotations

Table 4-5 NRF 1.11.0 Resolved Bugs

Bug Number Severity Found in Release Title
32623131 3 1.8.0 NRF is replacing an incorrect FQDN in PATCH request when FQDN header validation is enabled
32365728 3 1.10.0 OCNRF's Host scheme can not be changed to HTTPs
32365433 4 1.10.0 Invalid SupiRange is accepted during NFs Registering with NRF
32365453 4 1.10.0 Invalid Identity Range is accepted during NFs Registering with NRF
32623138 4 1.10.0 AccessToken-svc is non-responsive for requests with empty/invalid request body
32623151 3 1.10.0 NFSetId Support - Access Token Claims don't support producerNfSetId

Table 4-6 SCP 1.11.0 Resolved Bugs

Bug Number Severity Found in Release Title
32653951 2 1.9.1 AuditMaster thread is getting killed during DB exception
32653962 3 1.10.0 SCP worker is crashing in handling inter-SCP case with location uri with relative URI
32653968 3 1.10.0 Log message to be included with exception stacktrace
32680387 3 1.10.1 SCP worker throws recursive call error in log with more response time for incoming messages
32653111 3 1.10.0 Update InterSCP Audit testcase to avoid race condition between notification and audit
32653117 3 1.10.0 Update Default SCP response timeout and Increase stub resources in ATS
32653129 3 1.10.0 Enhance ATS to retry on stub connection Errors
32699327 4 1.9.1 Different log level shows for the same log
32714175 4 1.10.0 VZW SCP - API specification document (Swagger or YAML) for SCP configuration services
32714191 4 1.9.0 Change the name of Alert rules file in future releases in CSAR package
32714230 4 1.10.0 The 5G (SCP) ATS Stubs should be helm deployable and stay static

Table 4-7 UDR 1.11.0 Resolved Bugs

Bug Number Severity Found in Release Title Notes
32377421 3 1.10.0 nudr-config PUT request for DR-SERVICE fails with the error Internal Server Error Occurs only when on-demand migration is enabled.
32377299 4 1.10.0 Duplicate key entries in the database for PUR requests Occurs only when auto-enrolment is enabled.
32377325 4 1.10.0 subscription request fails with the error `Data field does not exist for Custom APIs NA
32377407 4 1.10.0 UDM SDM subscription PATCH giving Invalid data content instead of Schema validation failure NA

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-8 CNC Console 1.6.0 and 1.6.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.

32291223 Minor 1.5.0 CNCC : CNE Common Services type should be ClusterIP when accessed via CNCC

User will be able to access CNE common services directly using LoadBalancer IP.

Workaround: CNE common services type can be set as ClusterIP manually.

Table 4-9 CNC Console 1.6.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.

32291223 Minor 1.5.0 CNCC : CNE Common Services type should be ClusterIP when accessed via CNCC

User will be able to access CNE common services directly using LoadBalancer IP.

Workaround: CNE common services type can be set as ClusterIP manually.

Table 4-10 CNC Policy 1.11.0 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact
32650908 2 1.11.0 Diam-GW does not connect to pcrf automatically

Diam-GW does not connect to pcrf automatically

Workaround - In Diameter Config Map set "responseOnly=true" for PCRF Core.

32650916 2 1.11.0 Diamgw throws "No OCS/SH peer to send msg" even when it connected successfully

After diamgateway connects to OCS successfully, when it receives request to fetch for Sy, Sh datasource subscriber profile, diamgateway throws No OCS configured

Workaround - Need to create Realm base Diamter Routing Table keeping both identity and name as hosts name

32654621 3 1.11.0 Sub-Policies which are called using "deprecated call Policy blocks" are not exported

"call Policy" block when used in a policy is not able to export sub-policy.

This block is already deprecated and "call_policy_v2" is the new block to use.

32650967 3 1.11.0 Export Report not generating if the policy table of the policy got deleted There is no impact in export functionality. Export report will skip reporting the failure for the record that was deleted.
32650938 3 1.11.0 Failed to process metrics with java.lang.NullPointerException on Sm-create when BSF_URL is used No impact. Customers can use the real BSF URL. SM-service will throw exception when binding operation is enabled and local BSF configuration is used. This will lead to metric not getting pegged
32650943 3 1.11.0 SM Egress Metric is not pegged for BSF interactions Following two metrics will not be useful for SM to BSF intercations
  • ocpm_egress_request_total
  • ocpm_egress_response_total

Table 4-11 CNE 1.8.0 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact
OCCNE-3903 4 1.7.0 Kubespray task for applying cert issuer fails due to race condition which results in installation failure Installation fails on k8s install stage.Workaround: Skip cert manager installation on next rerun and continue with common services and db tier installation on failure.
OCCNE-3743 3 1.4.0, 1.5.0, 1.6.0, 1.7.0 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.Workaround: Alerts can be modified on a per-site basis if this issue is of high importance.
OCCNE-3874 3 1.7.0 LB Controller cannot talk to TLS-enabled OpenStack No load balancing service availableWorkaround: Manually copy the OpenStack certificate to the LB Controller.
OCCNE-3453 4 1.7.0 Geo-replication met with "Error_code: 1296; handler error HA_ERR_ROWS_EVENT_APPLY" error
We observed following behavior:
  • Established replication between two sites 1 & 2
  • Records are getting replicated from Site 1 to Site 2
  • Records are not getting replicated from Site 2 to Site 1

This error is happening on both BM and vCNE installation.

Workaround: Set EventLogBufferSize to 64K. You can use mcm client to do this:
set EventLogBufferSize:ndbmtd=65536 occnendbclustera;
OCCNE-2534 3 1.4.0 The openstack LDAP password should be hidden from the pipeline logs NA
OCCNE-1428 3 1.0.0, 1.2.0 node_exporter generating error logs Minor impact of an error be logged each minute from Prometheus Node Exporter.

Workaround: NA

OCCNE-3897 2 1.8.0 CIS Based Linux Hardening - OL8 NA
OCCNE-1658 2 1.2.0 Pods failover takes approximately 6 mins to start when kubernetes node is failed is restarted When a worker node fails completely or is restarted, it takes up to 7 minutes for K8s to recognize the failure and migrate the workload.

Workaround: NA

OCCNE-3523 2 1.7.0 istio preventing teardown of clusters

Iterating cluster creation/destruction in our lab environment is made much more laborious, as the cluster destruction hangs in Jenkins, and it needs manual intervention to delete all resource though the OpenStack GUI.

If the manual destruction is not performed, we orphan resources in our OpenStack tenancy, and this leads to collisions use of our limited allocated resources.

Workaround: NA

OCCNE-3485 3 1.4.0 Updating the Alerts, Varbind and alert groups of prometheus. NA
OCCNE-2965 3 1.5.0 Updating the labels and annotations in the dbtier services NA
OCCNE-3290 3 1.7.0 Install for fixedip deployment failed NA
OCCNE-2080 3 1.4.0 k8s_install pipeline process fails due to time out trying to access yum.oracle.com NA
OCCNE-3378 4 1.7.0 vCNE/Metallb - genLbCtrlData.py script fails using IP ranges Workaround: Change the mb_configmap.yaml file IPs to a list or a cidr.
OCCNE-3294 4 1.8.0 Change in default namespace for PCF-ATS

Workaround: Log in to Jenkins GUI : Configure: Advanced Project Option:

Pipeline Script: -d ocats (not working)

Pipeline Script: -d ocpcf (modified to 'ocpcf'...in working case)

FIX: This should ideally be set to default value 'ocpcf' in 1.8.0.

OCCNE-991 2 1.0.0, 1.1.0, 1.2.0 Correct osinstall yum update state Possible significant impact if a new yum update picks up an incompatible RPM. Possible to restrict Yum channel subscription to specific channels on Bastion host and central repo.

Workaround: NA

OCCNE-1398 4 1.0.0, 1.2.0 Can't ssh to enclosure switches after configure from procedure

Minimal impact since there is a simple workaround.

The workaround is to ssh to OA then from OA “connect interconnect 1(1 for switch1 or 2 for switch2)” to access enclosure switches. It is an easy workaround. I will see how to fix the ssh access later.

OCCNE-3765 3 1.8.0 Can't open occne-kibana GUI NA
OCCNE-3524 3 1.7.0 Sporadic k8s_install failure 'timeout (12s) waiting for privilege escalation prompt' NA
OCCNE-3311 3 1.7.0 1.7.0-rc.3 services restarting often. Test failures on services periodically NA
OCCNE-3310 3 1.7.0 BM Deploy CNE_SCAN fails on littlefinger (2 bastion) cluster NA
OCCNE-3312 3 1.7.0 1..70-rc.3 BM deploy kubespray failure NA
OCCNE-1579 3 1.3.0 Bastion host udp port domain unreachable traffic from tcpdump NA
OCCNE-3121 3 1.7.0 Security Hardening: Docker hardening in provision should be fixed/enabled NA
OCCNE-3122 3 1.7.0 Security Hardening 'rpm_verify_permissions' should be fixed/enabled NA
OCCNE-2386 3 1.4.0 Many network interface setting DEFROUTE=yes need to change to DEFROUTE=no NA
OCCNE-2384 3 1.4.0 The pxe_config_nic_list in hosts.ini for Gen10 blade server doesn't work well NA
OCCNE-2505 3 1.4.0, 1.5.0, 1.6.0 Worker nodes randomly becoming Not Ready NA

Table 4-12 NRF 1.11.0 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact
32623176 4 1.10.0 RejectionReason to be added in NfAccessToken response metric Reason for rejection of the AccessToken Request can't be known by looking into the metric
32623215 4 1.9.0 Add NfUpdate Patch Operation with Unknown attribute are getting dropped silently and returning 200 NF will not get notified that some of the attributes didn't get updated in NRF.

Table 4-13 SCP 1.11.0 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact
30731782 Minor 1.2 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.

For now customer impact is minimal to no.

Workaround: None.

Note: This limitation is not present in SCP 1.10 onwards.
30731844 Minor 1.3 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 Minor 1.4 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 which can cause some call failures.

Workaround: None.

Note: This limitation is not present in SCP 1.10 onwards.

UDR 1.11.0 Customer Known Bugs

Bug Number Severity Found in Release Title Customer Impact/WA
30774755 3 1.4.0 Headers for few resources are not implemented as per spec 29505-v15.4.0 No Impact
32631173 3 1.11.0 udr_rest_request_total not pegged for Unsupported Media Type messages. No Impact
32631219 3 1.11.0 PUT/POST request for policy-data/UDM with empty payloads returns 5xx errors No Impact
32631240 3 1.11.0 UDR returns 5012 when vsaLevel set to either dnn or nssai No 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.
31877256 4 1.8.0 ProvGw: GET response sometimes does not have segment1 related data for subscriber does not exist case No impact. It is intermittent issue.
32377439 4 1.10.0 De-Registration fails when egressgateway goes down before nrf-client during UDR deletion No impact
32377341 4 1.10.0 Fetch UDM authentication subscription on UDR returns Internal Server Error Occurs only with cnDBTier. Possible bug on MySQL Cluster