Created attachment 1722877 [details]
In aws g3.4xlarge instance, RHEL8 hit this rule unexpectedly.
The resolve steps suggest user to migrate to aws while the system is in aws.
Below is the details:
Red Hat does not support RHEL High Availability deployments consisting of members that are virtual machines running on OpenStack/Xen (other than AWS)/Microsoft Hyper-V
The cluster is running on xen platform. However, it is not supported as a RHEL High Availability member.
Steps to resolve
Red Hat recommends that you migrate the resource to other supported platforms mentioned in Support Policies for RHEL High Availability Clusters .
[root@ip-10-116-2-199 id]# cat /sys/devices/virtual/dmi/id/bios_vendor
[root@ip-10-116-2-199 id]# cat /sys/devices/virtual/dmi/id/bios_version
Version-Release number of selected components (if applicable):
Steps to Reproduce:
1. Start a RHEL-8.4 g3.4xlarge instance
2. Register insights-client and upload data
3. Check the advisor
Wrongly hit this rule in aws.
This rule should not be hit in aws.
- Not hit in t2.micro which is also a aws xen system.