Customer Known Bug List
Cloud
Native Release 2.1, Customer Known Bugs table lists the known bugs and
associated Customer Impact Statements. This information is provided for
information purposes only.
Table 5-7 CNE 1.3.2 Customer Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 30761850 | 2 | 1.3.2 | DB-Tier did not recover from post weekend Lab Shutdown | DB Tier requires manual procedure to recover from power disruptiuon event. |
| 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. |
| 30756164 | 3 | 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 | 3 | 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. |
| 307766492 | 3 | 1.3.2 | OCCNE-VCNE 1.3 — Need to Add VM Sizing/Openstack Flavor information to Installation Documentation | No customer impact. This doc bug is to add useful information to the customer facing documentation. |
| OCCNE-991 | 3 | 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. |
| OCCNE-1318 | 3 | 1.1.0 | Add external IPs to SQL nodes (vCNE) | Cross-site replication will not function properly without external IPs. This is not an issue for applications not requiring replication to multiple sites. |
| OCCNE-1337 | 3 | 1.3.2 | k8s instaII 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. Workaround: To ssh to OA then from OA "connect interconnect 1(1 for switchl or 2 for switch2)" to access enclosure switches. |
| OCCNE-1464 | 3 | 1.2.1 | OCCNE 1.2.0 Installation Guide Does Not Provide Guidance on Firmware Version | Installation procedure could fail if running on a server with older firmware. |
Table 5-8 DRA 1.4.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-9 NRF 1.4.0 Customer Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 30736715 | 4 | 1.4.0 | Primary MySql Host only considers 3306 Port value | Customer can only use default MySQL Port (3306) |
| 30737221 | 4 | 1.4.0 | NRF is not suspending UNDISCOVERABLE profiles if HB missed | No consumer NFs can ever know the when a UNDISCOVERABLE Profile becomes unavailable |
Table 5-10 PCF 1.4.0 Customer Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 30776227 | 3 | 1.4 | Binding data is not deleted, when we delete PDU session | |
| 30776242 | 3 | 1.4 | Unsubscribe of subscriber not happening towards UDR for AM Policy delete | |
| 30776258 | 3 | 1.4 | PCF1.3 version Rx interface will return dulplicate AVPs in AAA reponse | |
| 30776213 | 4 | 1.4 | VPAT Issue in using keyboard for navigation using Policy Blocks |
Table 5-11 PCRF 1.4.0 Customer Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 30775276 | 2 | 1.3 | cnPCRF:1.3: DB 'Too many connections' seen in pcrf-core log during performance testing |
This Impacts the performance requirements. Workaround: None. |
| 30775328 | 2 | 1.3 | cnPCRF:1.3: CN-PCRF diam-gw support for Scaling of PCRF Core | This Impacts the scalability requirements.
Workaround: You should restart Diameter Gateway after increasing the number of PCRF cores. |
| 30775532 | 2 | 1.3 | cnPCRF:1.3: Diam-gateway support for scaling of PCRF Core microservice | This Impacts the scalability requirements.
Workaround: None. |
| 30775308 | 2 | 1.3 | cnPCRF 1.3: Policy action "Set session revalidation time to seconds" is not working | This impacts the functional requirement of event report
after timer expiry.
Workaround: None. |
Table 5-12 SCP 1.4.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. |
| 30731829 | 3 | 1.3 | SCPC-Pilot is taking high CPU while applying updates if number of equivalent profiles/ServiceInstances are exceeding 100 | More CPU is consumed if updates are frequent.
Workaround: To put pilot on a node where other processes are not consuming much of CPUs using node selector. |
| 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-13 UDM/AUSF 1.0.0 Customer Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 30542078 | 3 | 1.0.0 | Encrypted authentication key support is not handled in UDM | The data stored on UDR is accessible for only UDM and hence minimal impact for customer/user. |
Table 5-14 UDR/UDSF 1.4.0 Customer Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| OCUDR-463 | 3 | 1.4.0 | Headers for few resources are not implemented as per spec 29505-v15.4.0 | No impact. UDM(consumer of UDM APIs) does not send conditional attributes to UDR. |
| OCUDR-562 | 3 | 1.4.0 | "changes" field value is missing in the notification payload | Notifications rate is limited in initial release. |
| OCUDR-563 | 3 | 1.4.0 | UDR rejects sdmSubscription creation after deleting it when SubscriptionDataSubscription already exist | No impact. |
| OCUDR-418 | 4 | 1.3.0 | UDR is not validating the conditional attributes for UDM APIs. | Affects when UDM does not cleanup subs-to-notify which is linked to sdmSubscriptions. Workaround: UDM needs to cleanup subs-to-notify and sdmSubscriptions mandatorily. |
| OCUDR-455 | 4 | 1.3.0 | Notify Service delays notifications to PCF during traffic run | Affects only when multiple PATCH items are sent which triggers notifications. Workaround: You should not send delete and add in the same PATCH request. |
