5 Resolved and Known Bugs
This chapter lists the resolved and known bugs for Cloud Native Core release 2.1.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
The problem report sections in this document refer to bug severity levels. Definitions of these levels can be found in the publication, TL 9000 Quality Management System Measurement Handbook.
Problem Report: A report from a customer or on behalf of the customer concerning a product or process defect requesting an investigation of the issue and a resolution to remove the cause. The report may be issued via any medium.
Problem reports are systemic deficiencies with hardware, software, documentation, delivery, billing, invoicing, servicing, or any other process involved with the acquisition, operation, or performance of a product. An incident reported simply to request help to bring back the service or functionality to normal without the intent to investigate and provide a resolution to the cause of the incident is not a problem report.
-
Critical: Conditions that severely affect the primary
functionality of the product and because of the business impact to the customer
requires non-stop immediate corrective action regardless of time of day, or day
of the week as viewed by a customer on discussion with the organization such
as:
- Product inoperability (total or partial outage),
- A reduction in the capacity capability, that is, traffic/data handling capability, such that expected loads cannot be handled,
- Any loss of emergency capability (for example, emergency 911 calls), or
- Safety hazard or risk of security breach.
-
Major: Product is usable, but a condition exists that
seriously degrades the product operation, maintenance, or administration, etc.,
and requires attention during pre-defined standard hours to resolve the
situation.
The urgency is less than in critical situations because of a less immediate or impending effect on product performance, customers, and the customer's operation and revenue such as:
- Reduction in product's capacity (but still able to handle the expected load),
- Any loss of administrative or maintenance visibility of the product and/or diagnostic capability,
- Repeated degradation of an essential component or function, or
- Degradation of the product's ability to provide any required notification of malfunction.
- Minor: Other problems of a lesser severity than "critical" or "major" such as conditions that have little or no impairment on the function of the system.
The numbered severity levels in the tables below correspond to these definitions of 1-Critical, 2-Major, or 3-Minor.
Resolved Bug List
Table 5-1 SCP 1.5.3 Resolved Bugs
| Bug Number | Severity | Title | Found in Release | Fixed in Release |
|---|---|---|---|---|
| 30731829 | 3 | SCPC-Pilot is taking high CPU while applying updates if number of equivalent profiles/ServiceInstances are exceeding 100 | 1.4.0 | 1.5.3 |
| 31509529 | 3 | Per connection TPS enhancement for SCP using IGW | 1.5.0 | 1.5.3 |
| 31509566 | 3 | SCP not consistently routing UECM requests based mediation rule | 1.5.0 | 1.5.3 |
| 31509578 | 3 | SCP does not remove a UDM profile from VS and SE after DE-Register event | 1.5.0 | 1.5.3 |
| 31509590 | 2 | SCP is indicating Loop Detected on NRF Notification | 1.5.0 | 1.5.3 |
Table 5-2 IWF 1.4.1 Resolved Bugs
| Bug Number | Severity | Title | Found in Release | Fixed in Release |
|---|---|---|---|---|
| 31022468 | 3 | For SCP's ResponseIngress/Egress request, NF-Mediation responding with inappropriate dataype for the attribute Status code . | 1.4.0 | 1.4.1 |
Table 5-3 PCF 1.5.1 Resolved Bugs
| Bug Number | Severity | Title | Found in Release | Fixed in Release |
|---|---|---|---|---|
| 31026960 | 3 | User-service is opening HTTP2 connection directly to UDR for sub-to-notify delete operation | 1.5.0 | 1.5.1 |
| 31028222 | 3 | PCF: All previously queried SM associations are returned for subsequent invalid queries | 1.5.0 | 1.5.1 |
Table 5-4 SCP 1.5.2 Resolved Bugs
| Bug Number | Severity | Title | Found in Release | Fixed in Release |
|---|---|---|---|---|
| 31136820 | 3 | TCP Reset received on connections from SCP if kept idle for >15 minutes | 1.5.0 | 1.5.2 |
Table 5-5 SCP 1.5.1 Resolved Bugs
| Bug Number | Severity | Title | Found in Release | Fixed in Release |
|---|---|---|---|---|
| 31121719 | 2 | SCP - Audit to not delete virtual services when receiving 4xx or 3xx or 5xx for a NF in audit response | 1.5.0 | 1.5.1 |
| 31122457 | 2 | Not all NFs are unsubscribed when changed to Local | 1.5.0 | 1.5.1 |
| 31122469 | 3 | SCP doesn't reroute to secondary NRF by default on 404 response | 1.5.0 | 1.5.1 |
| 31122474 | 3 | SCP Audit doesn't read topology source from database on audit retry after failure | 1.5.0 | 1.5.1 |
| 31122104 | 2 | Ignore DB error is not working for UDM Dereg callback notification | 1.5.0 | 1.5.1 |
| 31122087 | 2 | scp worker | Initial cluster not considered for routing when in "AlternateRouting" congestion state | 1.5.0 | 1.5.1 |
| 31123331 | 3 | Deployment time configuration for topology source at NF type level | 1.5.0 | 1.5.1 |
Table 5-6 CNE 1.4.0 Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| OCCNE-1543 | 2 | 1.2.0 | Need add more severity values in snmp notifier. |
| OCCNE-1849 | 2 | 1.3.2 | Post-install procedure missing instructions on required reset of DB password. |
| OCCNE-1646 | 2 | 1.3.2 | Fix security group duplication in vCNE. |
| OCCNE-1706 | 2 | 1.3.2 | Documentation for 1.2 Installation preflight has wrong size for Management Subnet. |
| OCCNE-1469 | 2 | 1.3.2 | Fix fortify issue for DB tier monitor service. |
| OCCNE-1318 | 2 | 1.3.2 | Add external IPs to SQL nodes (vCNE). |
Table 5-7 NRF 1.5.0 Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 30736715 | 4 | 1.4.0 | Customer can only use default MySQL Port (3306). |
| 30737221 | 4 | 1.4.0 | No consumer NFs can ever know the when a UNDISCOVERABLE Profile becomes unavailable. |
Table 5-8 IWF 1.3.0 Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 30380965 | 3 | 1.0.0 | IWF Performance Benchmark Bottleneck Analysis and improvements. |
Table 5-9 PCRF 1.5.0 Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| CNPCRF-841 | 3 | 1.4.0 | cnPCRF:1.3:Dynamic pcrf-core configuration required in UDR for success response for SNR/PUR/UDR. |
| CNPCRF-781 | 3 | 1.4.0 | pcrf-core drops requests when 'Subscription-Id-Type' is received as 'END_USER_NAI' in CCR PCRF is not taking decision based on policy counter and status received from OCS` |
| CNPCRF-741 | 3 | 1.4.0 | Metrics were not captured by Prometheus from pcrf-core due to invalid annotations configurations in 'pcrf-core-service' |
| CNPCRF-732 | 3 | 1.4.0 | Getting "Error: container has runAsNonRoot and image will run as root" for PRE pod |
| CNPCRF-653 | 3 | 1.4.0 | Connection is not established when one create/update LDAP datasource from CM GUI |
| CNPCRF-573 | 3 | 1.4.0 | LDAP Gateway is not able to connect to Config Server |
Table 5-10 PCF 1.5.0 Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| OCNGF-606 | 3 | 1.4.0 | ocpm-pre service could not load the policies of wesp |
| OCNGF-621 | 3 | 1.4.0 | CM service crashed down unexpectedly |
| OCNGF-692 | 3 | 1.4.0 | If name of Sh data source is kept 'sh' and all other mandatory fields configured , then when trying to save it throws error " Error Code 1009" |
| OCNGF-794 | 3 | 1.4.0 | Update Policy creation to handle issues find during testing |
| OCNGF-795 | 3 | 1.4.0 | CHF Policy changes |
| PCF-1234 | 3 | 1.4.0 | Unsubscribe of subscriber not happening towards UDR for AM Policy delete |
| PCF-1295 | 3 | 1.4.0 | PCF1.3 version Rx interface will return dulplicate AVPs in AAA reponse messes |
Table 5-11 UDM 1.1.0 Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 30542078 | 3 | 1.1.0 | Encrypted authentication key support is not handled in UDM. |
Table 5-12 UDR 1.5.0 Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| OCUDR-562 | 3 | 1.4.0 | "changes" field value is missing in the notification payload. |
| OCUDR-563 | 3 | 1.4.0 | UDR rejects sdmSubscription creation after deleting it when SubscriptionDataSubscription already exist. |
Customer Known Bug List
Table 5-13 CNE 1.4.0 Customer Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 30756164 | 2 | 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 replication need to be configured manually following the automated installation. |
| 30756201 | 4 | 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. |
| 30761850 | 2 | 1.3.2 | DB-Tier did not recover from post weekend Lab Shutdown | DB-Tier requires manual procedure to recover from post weekend Lab Shutdown |
| 30832402 | 2 | 1.3.2 | Cisco 93180 (TOR) does not recover vrrp or port channels if DB1 fails simultaneous to loss of both TOR switches | DB-Tier requires manual procedure to recover from post weekend Lab Shutdown |
| 30838215 | 2 | 1.3.2 | OCCNE 1.3 Bare Metal Installation - Db-1 Management interface not re-configured by ansible script post pipeline | DB-Tier requires manual procedure to recover from post weekend Lab Shutdown |
| 30936847 | 3 | 1.3.2 | OCCNE 1.3 Admusr password expires after 90 days -- ssh by key stops working | ssh by key stops until password is updated |
| OCCNE-1265 | 2 | 1.2.0 | ToR issues reset to client connections after failover | There is significant impact on a TOR switch failover if the workaround is not in place. Coordinating NAT tables between switches can be done to mitigate the impact. |
| OCCNE-1289 | 3 | 1.3.2 | Identify the root cause in delay for VM's to come up after yum update on the host servers. | Hard coded, 5-minute, fixed delay can result in minor delay during DB Tier installation. |
| OCCNE-1337 | 3 | 1.3.2 | k8s_install produces non-executable kubectl binary in ../artifacts | Minimal impact. This only affects verification and diagnostic procedures. There is a simple workaround that requires manual intervention. |
| OCCNE-1398 | 3 | 1.3.2 | 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. |
| OCCNE-1428 | 3 | 1.0.0 | node_exporter generating error logs | Minor impact of an error be logged each minute from Prometheus Node Exporter. |
| 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. |
| OCCNE-991 | 2 | 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. |
Table 5-14 CnDRA 1.5.0 Customer Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 30720600 | 3 | 1.4.0 | enabling 1k/ pod diameter connections, causes invalid fd issue on draworker pod | 1k connections could not be configured on draworker pod. |
Table 5-15 NRF 1.5.0 Customer Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 30995372 | 4 | 1.5.0 | NRF Latency metrics should be pegged even when processing time is less than 0 milliseconds (i.e. if the value is in microseconds) | Latency values less than 0 milliseconds will not be considered. |
| 30995300 | 4 | 1.5.0 | AdditionalAttributes are getting stored inside nfInfo objects other than the nftype's nfInfo, even when the acceptAdditionalAttributes flag is false | Additional IEs received in nfType IEs will be accepted in registration message. |
Table 5-16 PCF 1.5.0 Customer Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 31027714 | 3 | 1.4 | PCF: Unable to view CM GUI on Internet Explorer | Customer will not be able to use Internet explorer to open the CM service GUI. Customer can use other web browsers like firefox and chrome to open the CM service GUI. |
| 31027743 | 3 | 1.4 | PCF: CM GUI allows user to delete a rule/Policy that is used elsewhere | Policy evaluation will not succeed if referencing data gets deleted. |
| 31028388 | 3 | 1.4 | PCF: Rejects AAR message if RxRequestType AVP is not present | AAR message is rejected if RxRequestType AVP is not present |
Table 5-17 PCRF 1.5.0 Customer Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 31047051 | 3 | 12.5.2.0.0 | cnPCRF:1.5:Getting 'Policy execution failed: FlowChange' error if OACT_FARGO_0 is included as action in policy |
Workaround: None. |
| 31047021 | 3 | 12.5.2.0.0 | cnPCRF:1.5:DWA result code DIAMETER_UNABLE_TO_COMPLY when pcrf-core restarted before diam-gateway |
Workaround: None. |
| 31046962 | 2 | 12.5.2.0.0 | cnPCRF:1.5:CMGUI: Password is getting updated automatically while updating LDAP Datasource |
Workaround: None. |
| 31046664 | 2 | 12.5.2.0.0 | cnPCRF:1.5:CCA not received when action pcc_rule with SCOPE_FLOW is used in Policy |
Workaround: None. |
| 31046603 | 3 | 12.5.2.0.0 | cnPCRF:1.5: Sy and LDAP call-flow is not working together |
Workaround: None. |
Table 5-18 SCP 1.5.0 Customer Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 30731782 | 3 | 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 and hence minimal impact for customer/user. Workaround: None. This is limited by underlying platform. |
| 30731844 | 3 | 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. |
Table 5-19 UDR 1.5.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. |
| OCUDR-633 | 4 | 1.5.0 | UDR notify service keeps triggering notification for single modification of any resources(eg AM_DATA) | Issue is seen only when client 204 result code with some content length |