Bug 1889702 - Wrongly hit pacemaker_on_vm rule on aws g3.4xlarge instance
Summary: Wrongly hit pacemaker_on_vm rule on aws g3.4xlarge instance
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Cloud Software Services (cloud.redhat.com)
Classification: Red Hat
Component: Insights - Rules
Version: unspecified
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Sachin
QA Contact: Jaylin Zhou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-20 12:18 UTC by Xiao, Liang
Modified: 2020-11-02 04:29 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-02 04:29:32 UTC
Target Upstream Version:


Attachments (Terms of Use)
pacemaker_on_vm.png (161.83 KB, image/png)
2020-10-20 12:18 UTC, Xiao, Liang
no flags Details

Description Xiao, Liang 2020-10-20 12:18:15 UTC
Created attachment 1722877 [details]
pacemaker_on_vm.png

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
Detected issues
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
Xen
[root@ip-10-116-2-199 id]# cat /sys/devices/virtual/dmi/id/bios_version
4.11.amazon

Version-Release number of selected components (if applicable):

RHEL Version:
RHEL-8.4(4.18.0-240.5.el8.x86_64)

How reproducible:
100%

Steps to Reproduce:
1. Start a RHEL-8.4 g3.4xlarge instance
2. Register insights-client and upload data
3. Check the advisor

Actual results:
Wrongly hit this rule in aws.

Expected results:
This rule should not be hit in aws.

Additional info:
- Not hit in t2.micro which is also a aws xen system.


Note You need to log in before you can comment on or make changes to this bug.