Customer Known Bug List

Table 4-1 lists the known bugs and associated Customer Impact Statements. This information is provided for information purposes only.

Table 4-1 Cloud Native Core 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.
OCCNE-1318	Enhancement	1.3.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-1642	Enhancement	1.3.0	OCCNE 1.3 Automation not correctly handling management IPs migrated from db-1 to Bastion 1	Not able to perform automated deploy of DB servers and bastion hosts due to insufficient number of IP addresses. A workaround is available. Workaround: As a work-around, if the Management subnet allocated for the bastion hosts is a /29, then the oam_host address for the first db-storage node (hosting bastion-1) can be omitted from the machine definition line in the hosts.ini inventory file, and the bastion-1 virtual-machine can take on the address initially used for the machine when it serves as the bootstrap-host.

Bug Number

Severity

Found in Release

Title

Customer Impact

30542078

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.

OCCNE-1318

Enhancement

1.3.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-1642

Enhancement

1.3.0

OCCNE 1.3 Automation not correctly handling management IPs migrated from db-1 to Bastion 1

Not able to perform automated deploy of DB servers and bastion hosts due to insufficient number of IP addresses. A workaround is available.

Workaround:

As a work-around, if the Management subnet allocated for the bastion hosts is a /29, then the oam_host address for the first db-storage node (hosting bastion-1) can be omitted from the machine definition line in the hosts.ini inventory file, and the bastion-1 virtual-machine can take on the address initially used for the machine when it serves as the bootstrap-host.