Bug 1955682

Summary: [RFE] Support for High Availability on IBM Cloud Bare Metal Servers
Product: Red Hat Enterprise Linux 8 Reporter: Shane Bradley <sbradley>
Component: pacemakerAssignee: Chris Feist <cfeist>
Status: CLOSED MIGRATED QA Contact: Brandon Perkins <bperkins>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.2CC: bperkins, cluster-maint, kgaillot, nwahl, sbradley
Target Milestone: betaKeywords: FutureFeature, MigratedToJIRA, TestOnly, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 19:02:20 UTC Type: Story
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Shane Bradley 2021-04-30 16:20:54 UTC
Description of problem:
Supportability of IBM Cloud - Bare Metal Servers

Customer stated:
  "We had created VSIs in the first
   place on IBM Cloud, but due to NO support availability by Red Hat, we are
   now creating bare metal servers to have Red Hat support. (There is a huge
   billing difference between VSI and bare metal servers, however, to take RH
   support, we decided to move to bare metal!)
   ...
   I just received the information that the new bare metal server is on Lenovo
   System-X 3250 - M6.

   That has IMM2 console. I do have IP address information and I will try to
   connect to the console, we will need to create rhcs_fence user to provide
   details in IPMI fence/stonith agent.

   Also advise whether Red Hat is going to support bare metal servers as
   pacemaker high-availability member on IBM cloud or not!"



An email thread about this issue:
  - Supportability of IBM Cloud Bare Metal Servers 
    https://mailman-int.corp.redhat.com/archives/cluster-list/2021-April/msg00049.html


Version-Release number of selected component (if applicable):
Latest

How reproducible:
None

Steps to Reproduce:
None

Actual results:
None

Expected results:
None

Additional info:

Comment 1 RHEL Program Management 2023-09-22 18:59:38 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-22 19:02:20 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.