Home > Communication Service Provider Solutions > Telecom Multicloud Foundation > Red Hat > Release Notes > Release Notes—Dell Technologies - Red Hat OpenShift Reference Architecture for Telecom > Known issues
The following table describes known issues in this release.
NOTE: Access to Red Hat Bugzilla (BZ) and solution links may require Red Hat login credentials. Dell Internal JIRA issues are not publicly accessible—only partners with appropriate permissions can access this website.
Issue ID |
Functional area |
Description |
Workaround/solution |
Network configuration |
Active-backup bond leads to the active (primary) interface not taking over its role after a manual injected failure in the primary interface. The issue occurs after the primary interface goes down and then comes up again.
|
|
|
Network configuration |
Active/active bond leads to random image download errors. |
A fix is expected to be available with OpenShift Container Platform 4.6 backport. Note: With release 4.6.40, Red Hat has implemented changes to address this issue. After further testing, future releases will use an active-active bonding configuration. |
|
|
Operating system settings |
Management node and OpenShift cluster nodes in the same time zone. |
Ensure that the operating system time zone on the management node (CSAH) is set to UTC. It may be necessary to ensure that the system time zone at hardware level is set to UTC. Dell Technologies is working to provide an automated resolution in the next release. |
OpenShift Cluster Hardware Enablement |
OpenNESS Operator for Wireless FEC Accelerators fails to install for use with Intel® vRAN Dedicated Accelerator ACC100. |
Add the label fpga.intel.com/intel-accelerator-present= to cluster nodes where the ACC100 is installed. |
|
PXE server |
PXE Server Timeout – E18 error |
Manually delete the bootstrap KVM disk associated with kvm. Run the virt-install command again. Dell Technologies is working with Red Hat to understand the root cause. According to Red Hat, modifying the command from ‘network=bridge=br0’ to ‘network bridge=br0’ resolves the issue. We are testing this fix for this release. |
|
OCS operator |
Default installation of the OCS operator leads to an intermittent Security Context Constraints (SCC) for the pod. |
Manually edit the pod’s securityContext parameter and set runAsNonRoot: false. Dell Technologies is working with Red Hat to understand this issue. Although RH Solution 611560 addresses this concern, the solution assumes that the SCC is modified. However, the issue occurs without such changes. |